Accessibility Issues: ARIA progressbar nodes must have an accessible name

sigccil — Thu, 05 Mar 2026 16:10:52 GMT

HI!

We're currently in the process of updating our applications to meet WCAG accessibility standards and are reviewing all of them as part of this effort. You may have seen my other post. Per our ESRI solution engineer has recommended that we post all issues in the community forum in addition to opening tickets. We're trying to collaborate and raise awareness of the issues we're seeing in our applications. We want to highlight ones that can be easily resolved by users and which ones fall under ESRI's purview.

Issue:

This is another calcite issue where the aria label does not exist. There's nothing in the instant app that let's me edit the image in the attachments section. Am I missing a step or where I can make this accessible from the instant app? Or, does this need to be fixed internally by ESRI? Has anyone else encountered similar challenges? How are you approaching this? Any tips or best practices would be greatly appreciated!

Steps to reproduce in app:

https://maps.cookcountyil.gov/hwyproject/

open up application
Run tool, we are use axeDev and it should match above image.

Re: Accessibility Issues: ARIA progressbar nodes must have an accessible name

IC — Mon, 13 Apr 2026 19:56:37 GMT

We use a dashboard where a list element filters an embedded content element (HTML infographics). That embedded content element throws the "progressbar nodes" error when testing with Axe as well as "Frames must have an accessible name," even though we assigned the element alt text in the dashboard editor. Again, thanks for documenting!

topic Accessibility Issues: ARIA progressbar nodes must have an accessible name in Accessibility Questions

Accessibility Issues: ARIA progressbar nodes must have an accessible name

Re: Accessibility Issues: ARIA progressbar nodes must have an accessible name