Esri is committed to making ArcGIS Experience Builder accessible for all users by following the World Wide Web Consortium (W3C)'s Web Content Accessibility Guidelines (WCAG) (2.0 & 2.1 & 2.2 AA) and the Revised Section 508 Standards. Certified accessibility professionals have tested ArcGIS Experience Builder with the Voluntary Product Accessibility Template (VPAT), a template used to document a product's conformance with accessibility standards and guidelines.
Esri Accessibility Conformance Report for ArcGIS Experience Builder.
For more information about Esri's commitment to accessible technology, visit Esri Accessibility. For legal information about accessibility, visit Esri Legal. For accessibility best practices, read Accessibility best practices for ArcGIS Experience Builder.
The following sections describe current Experience Builder features for building accessible apps. More accessibility features will continue to be added with future software updates.
Note:
The content of the following sections is subject to change with incremental releases.
Pages
Three types of pages are available to be added on the Page panel—full-screen, scrolling, and grid. We recommend using full-screen and scrolling pages to build accessible apps.
Full-screen pages use a fixed layout where widgets exist on the page at absolute positions. By default, the keyboard tab order follows the order in which widgets and other app elements were added to the canvas. If you enable a more intuitive tab order, you can turn on the A11Y button at the bottom right corner of the builder. If you do, Experience Builder creates a logical tab order for all widgets in full-screen pages (and in fixed layout containers, such as Card and List widgets, which behave like full-screen pages). For best results, turn on the A11Y button first before building an accessible app.
Scrolling pages are arranged into blocks and screen groups. A block container is similar to a Row widget. The keyboard tab order follows a logical reading order for scrolling pages.
The following table summarizes the information in this section:
| Page type | Accessibility status | Notes |
|---|---|---|
Full-screen | Supported with limits | Utilize the A11Y button at the bottom right corner of the builder. Try to avoid using Auto size and position settings. |
Scrolling | Supported |
Screen readers
Accessibility support for Experience Builder has been tested with the following browser and screen reader combinations.
| Operating system | Browsers | Screen reader |
|---|---|---|
Windows | Google Chrome, Mozilla Firefox | NVDA |
macOS | Safari, Google Chrome | VoiceOver |
Note:
There may be behavioral differences between different screen readers.
Note:
Other screen reader and browser combinations not listed here, such as VoiceOver combined with Microsoft Edge, are not fully covered.
Themes and colors
The app theme determines the colors in an app. The six default themes—Default, Dark, Ink, Violet, Vivid, and Organization Shared—have optimized color contrast for each band. If you choose custom theme colors, you should ensure they meet contrast and color accessibility requirements.
In the settings of many widgets, such as the Text widget and Chart widget, you can set custom colors that are different from the theme colors. Some widgets, such as the Timeline widget, allow you to select foreground and background colors. If you use custom colors in your app, you should ensure that the colors meet accessibility standards.
Widgets
The following widgets support accessibility. There are some exceptions for specific features and arrangement styles. Exceptions are noted.
Note:
Some interactions that involve the Map widget and other widgets, such as drawing on a map with the Draw widget, do not yet support keyboard navigation or screen readers.
| Widget | Accessibility status | Notes |
|---|---|---|
Basemap Gallery | Supported | |
Button | Supported with limits | The link to Page top feature and the Button click message action are not yet supported by the keyboard. |
Column | Supported | You can add padding to display the focus ring for widgets inside a column. |
Coordinates | Supported with limits | Obtaining the coordinates from the map is not supported by the keyboard. |
Directions | Supported with limits | Re-ordering stops and adding stops by clicking the map are not supported by the keyboard. |
Divider | Supported | |
Draw | Supported with limits | Drawing on the map is not supported by the keyboard. |
Embed | Supported | |
Filter | Supported with limits | The Vertical arrangement style is supported. |
Fixed Panel | Supported | |
Image | Supported | You can manually add alt text to images. |
List | Supported | You can use the Esc key to exit a dynamic list. |
Map Layers | Supported with limits | You can use the left and right arrow keys to expand and collapse group layers. The Options pop-up close behavior is not fully supported by the keyboard. |
Menu | Supported | |
Placeholder | Supported | |
Supported with limits | Only Classic mode is supported. | |
Row | Supported | |
Share | Supported | |
Survey | Supported | |
Table | Supported with limits | Selecting table records is not supported by the keyboard. |
Text | Supported | |
Timeline | Supported | |
Views Navigation | Supported with limits | The quick styles Slider, Arrow 1, and Arrow 3 are not supported with screen readers. |
Note:
Icons have empty alt text by default.