Accessibility Issues: Certain ARIA roles must contain particular children

[sigccil]

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:
In this particular application we are using Dashboards and axeDev has flag that two of the divs do not contain certain ARIA roles for particular children. I haven't found anything in the Dashboard application interface that would allow me to add some aria labels as is in the case for the images. The issue is for both the div that shows the images and the div below it that allows the user to download the pdf; highlighted in the pink and red markup. 

Steps to reproduce. 

https://maps.cookcountyil.gov/sectionmonuments/

1. open up application
2. select a section corner from upper right of application (any marker with images) 
3. Run tool, we are use axeDev and it should match above image. 

Has anyone else run into similar challenges?

How are you approaching this process?

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

[Laura]

I’m still encountering the same error with AxeDev, specifically with my list widget in Experience Builder. Rebuilding every app isn’t feasible, so I’m hoping there’s a way to make these pass the guidelines. I’ll most likely be reaching out to support as well. So far, I haven’t found any solutions, and my searches—both online and with AI tools—haven’t yielded anything helpful.

Update: So far I've created bugs for all of m accessibility issues. They have all been flagged to be fixed in an upcoming release. 

[sigccil]

@Laura We filed a ticket with ESRI tech support and they turned it into a bug. We've have been encouraged by ESRI staff to post issues on the forums and submit tickets through tech support. 

[IC]

Found this post after encountering the same issue testing list- and table-containing dashboards with Axe (div.tabulator.medium.bottom-border for lists). Thanks for documenting!