Accessibility Issues: Buttons must have discernible text

[sigccil]

We’re currently working on updating our applications to meet WCAG accessibility standards and are reviewing all of them as part of this process. One challenge we’re facing is identifying which accessibility issues we can address ourselves and which fall under Esri’s responsibility.

Has anyone else encountered similar challenges? How are you approaching this? Any tips or best practices would be greatly appreciated!

 Originally posted here: https://community.esri.com/t5/arcgis-online-questions/accessibility-issues-buttons-must-have-discern...
cross referenced per recommendation 

[KatherineMichael]

From my previous experience with ESRI web applications, the only way I can think of that you would have control over the code for the buttons would be if you wrote the app yourself using the java script API or if you were using Experience Builder developer edition. I do not believe that the standard Experience Builder platform allows access to the code for the buttons.  That being said, ESRI has made a number of updates recently to increase accessibility in the web applications so this may on the list to be addressed from their end.  

We are also undertaking a review of our web applications for WCAG compliance, so I am interested to see what others have to say on the subject.  

[sigccil · Accepted solution]

It looks like this issue has been solved in the recent AGO release from 2/25/2026. Inspecting the source html there is now labels for these buttons.

Here is the app in question. 
https://maps.cookcountyil.gov/imagery-tile-downloader/

EDIT: It is solved for this app but I'm seeing a similar issue across other applications in our portfolio. 
reference here: https://community.esri.com/t5/arcgis-instant-apps-questions/accessibility-issues-ensure-role-quot-im...