Accessibility | Salesforce Trailblazer Community

Hi team,

I'm trying to finich my trailhead assinged, but I have problems with the access and permision. I'm trying to create a Service Agnet with Agentforce Builder, but I can't to access. Show a message like this

Could you please to help me?

#Trailhead Challenges #Accessibility

1 comentário

Vishal Verma (Fluido)
26 de jun., 14:14
Hi @Daniel San Román - Ensure you have created a new playground from the challenge page
Go to Setup.
Search for Agentforce Settings or Einstein Setup.
Enable Einstein and Agentforce.
Assign the required permission set (such as Agentforce Admin or the one specified by the Trailhead module).
Refresh the page and try again.

Adicionar um comentário

Escrever um comentário...

0/9000

20 de mai., 23:03

My filter is excluded from the keyboard tab order no matter what I do!

Sorry for the drama, but I am a bit desperate over this. I'm definitely having a LOT of difficulty meeting my organization's accessibility requirements with Tableau.

At the moment, I have a filter that refuses to appear in the phone layout's tab order.

Note that this filter and its source worksheet only appear in my dashboard's phone layout -- not in the default layout.

Things I've tried:

Added a miniature version of the filter's parent worksheet to the default layout
Added a miniature of the filter itself to the default layout
In the dashboard XML, set enable-sort-zone-taborder='false' and changed the zone ID manually to ID='330'. This works fine with other elements, but not with this filter.
When the above didn't work, I tried removing the filter from the phone layout and re-adding it --this time by right-clicking on the filter in the Phone Layout element list, and selecting 'Add Zone to Phone.' Then I edited the zone in the XML but that didn't work either.

I don't know if this is relevant, but for some reason, the filter element appears slightly different in the phone layout element list when it's been generated via the context menu vs. by dragging the filter onto the phone layout (see below). But neither of these elements seems to obtain focus when its zone is assigned a unique ID number in the dashboard's XML.

Has anyone else run into this issue? I'm hesitant to modify zone ID's in custom layouts at all because it often seems to corrupt the layout which causes Tableau to crash when I attempt to re-open the workbook.

My filter is excluded from the keyboard tab order no matter what I do!

#Tableau Desktop & Web Authoring #Accessibility

6 respostas

Kathy Kaufman
1 de jun., 14:29
Thanks to everyone who's weighed in here. It's much appreciated.

I've made some headway in understanding this issue. It looks like the filter wouldn't appear on my phone layout because its parent worksheet isn't present in that device layout. (I have 2 versions of the parent worksheet, one for each device layout with the phone version being more compact.)

It turns out that it's very difficult, if not impossible, to meet the accessibility requirements for keyboard focus order if one of your device layouts contains elements that don't appear in your other layouts. This is because mismatched zone IDs across device layouts cause Tableau to crash, so every dashboard element must appear in all layouts in identical tab order. To hide elements like worksheets or textboxes that were extraneous, I had resorted to reducing their size to 1 x 1 pixels, but they still appear in the tab order, which violates accessibility standards (such as WCAG 2.1) which "require that every interactive element reachable via the Tab key must be visible to the user and present a visible focus indicator when active." My alternative approach involved placing those hidden elements at the end of the tab order, but the mismatching zone IDs cause Tableau to crash altogether.

This has become a very vexing problem. I'm hoping that someone who deals with accessibility at Tableau can weigh in on recommended solutions.

Adicionar um comentário

Escrever uma resposta...

0/9000

26 de jan., 15:26

Still time to register for our next #Analytics #Tableau User Group and learn about #LOD #MapLayers and #Accessibility

🖇️

https://usergroups.tableau.com/events/details/tableau-analytics-tableau-user-group-presents-analytics-tableau-user-group-lods-map-layers-amp-accessibility

📅 January 29th at 6PM Paris Time - 12PM New York Time - 10:30PM New Delhi

Event Details :

⭐

Chris Williams

: Explore the power of Tableau LOD (Level of Detail) ExpressionsLearn how these commands enable users to conduct complex calculations by managing data granularity independently from the view’s setup. Discover the importance of LOD expressions for achieving precise analysis and flexible reporting. We will delve into the three types of LOD expressions—FIXED, INCLUDE, and EXCLUDE—each enhancing analytical capabilities by facilitating diverse aggregation levels. Join us to enhance your data analysis proficiency.

⭐

Prasann Prem

: KPI Cards made simple with Map LayersDiscover how to design powerful KPI cards in Tableau using map layers. Learn how to combine BANs, variances, and trends all in one sheet for more flexible dashboards.

⭐

Doc Kevin Lee Elder 

Kevin Lee Elder : The First Step to Building Accessible Dashboards: Do You See the Data?The data viz rule for colorblindness? “Don’t use red and green together.” It is too simplistic and is actually wrong! We Do See Red & Green it just looks different to us! Learn how to select colors and design colorblind-friendly visualizations from a color vision deficient (CVD) point of view. Let everyone see your data more easily which is also the first step towards insights.

Come and ask questions to our guests! See you soon!

Adicionar um comentário

Escrever um comentário...

0/9000

24 de set. de 2025, 20:08

Seeking LWC Developer + Accessibility Specialist

I have a client in need of a Salesforce Accessibility Specialist with STRONG Apex and LWC developer skills and experience creating managed packages for third parties. If you have these skills, please reach out to me ASAP. Thank you!

#Job Postings #LWC Development #Accessibility

Adicionar um comentário

Escrever um comentário...

0/9000

10 de out. de 2024, 08:41

Sharing this idea for an improvement to Trailblazer Community in case folks here would like to vote and comment.

Include assistive text when adding an image

This will help blink and low vision users using screen readers to better understand an image appearing on a page. Note that this functionality is already possible within Idea Exchange.

#Accessibility

Adicionar um comentário

Escrever um comentário...

0/9000

6 de mar. de 2024, 10:45

Happy International Women's Day! 🎉

Join us in celebrating women in data and analytics at our upcoming Data + Women Zurich event on March 21, 2024 at 6PM CEST. You'll have the opportunity to learn from two amazing data leaders, Sophie Sparkes and Emily Kund.

Have you ever noticed how illustrations and data visuals share similarities? Do you enjoy combining your love for data with sketching? Then the first topic in our upcoming Data + Women Zurich event will be of interest for you: Sophie will guide us through her dynamic live data drawing process, sharing the secrets to its success, step by step. But that's not all - Emily will be joining us to deconstruct accessible dashboards. Ever wondered what makes a dashboard accessible and how to create one? This talk will break down the components of accessible dashboards and show you how to implement them in your own work.

Don't miss this chance to enhance your data skills and connect with other women in the field. We look forward to seeing you there! 💪✨

Sign up here: https://usergroups.tableau.com/events/details/tableau-data-women-zurich-presents-impact-the-future-all-you-need-to-know-about-live-data-drawing-and-data-accessibility/

⌗datapluswomen ⌗impactthefuture ⌗iwd ⌗WTMImpactTheFuture ⌗datavisualisation ⌗datadrawing ⌗accessibility

usergroups.tableau.com

Adicionar um comentário

Escrever um comentário...

0/9000

5 de fev. de 2024, 20:14

How to Run a Report Using a Screen Reader?

Hello everyone. I am totally blind, and I am having issues with creating reports. This part of the salesforce platform doesn't seem to be accessible for someone who is blind using a screen reader. I've been able to access everything else on my own on this platform, but this seems to be the only difficulty I am having. I am currently stuck in two trails because of the inaccessibility of creating reports. There doesn't seem to be a screen reader friendly tutorial available option when it comes to dealing with reports. I am currently working on building an app for a project which requires me to create and run a report.

For reference, I am using the screen reader NVDA. Is anyone here familiar with this issue, or can someone point me in the right direction to a group where I can get some assistance? Any help is greatly appreciated. Thank you!

#Accessibility #BlindAdmins

4 respostas

Christina Moore (Shell Admin Services LLC)
5 de fev. de 2024, 21:54
Of course.
1. Once in your Salesforce org, go to the app launcher and type Analytics; it should be the only option.
2. Once it is up, go to the "create button submenu" then find "report" and press enter. A new popup will appear to create the new report.
Hope this helps.
Thank you.
Christina

Adicionar um comentário

Escrever uma resposta...

0/9000

2 de nov. de 2023, 21:34

Accessibility Checks - HTML doc title and lang attributees

We use Litmus to view our email builds and I keep seeing these serious failures. We are using content builder, so the HTML templates is not allowing me to change the header details. How can I resolve this in my templates without switching to full HTML?

Document does not have a non-empty <title> element
The <html> element does not have a lang attribute

2 respostas

Mateusz Dąbrowski (mateuszdabrowski.pl) Forum Ambassador
21 de nov. de 2023, 20:20
You can change the template HTML on the Email Template (not Template-based Email) level and the leverage it then in your emails built with content blocks.