Salesforce Experience Builder Accessibility and Usability Information
Contact the DoIT Help Desk for general assistance or to report an accessibility or usability barrier.
Accessibility and usability barriers
The following information is provided to help people with disabilities know what potential barriers may exist.
Main content is not reachable via keyboard, making it impossible for keyboard only users, such as users with motor disabilities.
It is not possible to access and edit the HTML elements in the editor via keyboard only. It is not possible to reach the left-side menu buttons (such as components) via keyboard only. Both of these barriers make the tool impossible for people who use keyboard only, such as people with a motor disability.
Content is not able to be read or edited by a screen reader, making it impossible for screen reader users to use, such as people who are blind or people who have reading disabilities.
With a screen reader on, it is not possible to read or edit content inside of the HTML editor. The menu is not reachable via tab order, but can be reached via reading order navigation. However, menu items read simply as “Out of frame - clickable.” It is not possible to select these items. Additionally, it is not possible to access items in the pages menu via screen reader (tab, arrow, space bar do not work to reach menu items after “home”).
‘Drag and drop’ was implemented inaccessibly, making the platform impossible to use for users who are blind, low-vision, have motor disabilities, or others who navigate via a screen reader or keyboard only.
Components (how users develop in this platform) can be added only through ‘drag and drop,’ which can be developed accessibly but was not. When tested, it was not possible for someone using a screen reader or keyboard only to drag and drop components in Salesforce Experience Builder.
Screen reader navigation is out of order with tutorial modals, making the tutorial difficult for people who use screen readers, such as people who are blind or people who have reading disabilities.
When beginning with the tutorial, screen reader navigation requires users to move through the full page before reaching tutorial content.