Accessibility Issues: Buttons must have discernible textARIA hidden element must not be focusable or contain focusable elements

Question

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. One challenge we’re facing is determining which accessibility issues we can resolve ourselves and which fall under Esri’s responsibility. For example, we’ve encountered issues with the address search functionality (address details removed from image for privacy).  * Has anyone else run into similar challenges?
* How are you approaching this process?
* Will Esri teams review and compile these issues and provide guidance on fixes for users, or will this fall entirely under their purview?

Any tips, best practices, or insights would be greatly appreciated!

Edit: Adding link to application and steps to reproduce.

https://maps.cookcountyil.gov/taxmapviewer/ 
1. open app

2. enter pin or address on left pane search bar. ex: 69 W Washington St, Chicago, IL, 60602, USA Selecting an option from drop down will not always trigger it.

2a. type in address and hit enter

3. run accessibility tool. We run axeDev browser extension

sigccil · Answer

Hi,

Thanks for the response. 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.

KlaraSchmitt · Answer

Hello @sigccil,

While it is a little hard to determine what app you are using from the screenshot above, it looks like you had also posted a similar question to the Online community, which provided a bit more reference. Generally, for applications with inline actions that don't support customization, the action label would be provided by Esri. Some applications may ask for labels, accessible names, or titles depending on what component is being configured or customized. In that type of scenario, the app publisher would set the label.

To address the error you received from axe—we'd recommend you open an issue with Esri Support who can help ensure it makes it to the right product team.

When logging accessibility issues with Support, we encourage you to provide as much information as possible about the application, your method of testing, and the error encountered, including:

* OS platform/Browser  
* Testing Tool  
* Repro Steps  
* Source Code  
* Issue  
* Image / Video  
* Success Criteria (from WCAG)  
* URL

Thank you,
Klara