ArcGIS Experience Builder Accessibility and Usability Information

Get help

• Contact the DoIT Help Desk for general technical assistance or to report an accessibility or usability barrier. 

• ArcGIS Experience Builder accessibility documentation is available on the vendor's website.

Accessibility and usability barriers 

The following barriers were identified in a February 2026 evaluation of a map created with ArcGIS Experience Builder. The map was accessed as a webpage in the Google Chrome web browser.

Some content is inaccessible to keyboard and screen reader users

Some interactive map components are not accessible via keyboard navigation. This means keyboard users cannot place focus on elements within a map to interact with them, and screen reader users will not be alerted of the presence of these elements. For any data points in a map, the content owner should provide that information in a text format such as a data table or a list to support screen reader and keyboard users. This text format should be accessible from the same page as the interactive map, either as a link or text provided on the page. 

In a map's Legend panel, any images or icons associated with a map do not have alt text by default. The content owner must write alt text for each icon. 

In a map's Layers panel, an invisible layout table is used to structure the list of layers that can be toggled on and off. This invisible table structure is announced by screen readers and results in a confusing, tedious user experience. 

The map webpage also lacks heading structure, and keyboard focus may be lost for a couple tab stops in the page header region. 

Low color contrast and color-coded elements may be difficult to distinguish for users who are colorblind or have low vision

When colors are used to indicate different map components, the content owner should ensure the colors used have high contrast with one another (a contrast ratio of at least 3:1 is required for visual components). In addition to meeting minimum color contrast requirements, it is best practice to use patterns, shapes, or other visual indicators such as text labels — all map components should appear visually distinct without relying on color. 

Usability barriers may impact all users

In maps created with ArcGIS Experience Builder, users may access expert-level tools and functions that can interrupt or complicate the experience of finding and discovering information in the map. For example, in the Layers panel, users can access tools for zooming, setting filters, and calculating statistics for a specific layer. These advanced tools may not be what users expect based on the labels. Removing user access to these advanced tools is recommended to streamline the user experience.