Nested interactive controls are not announced by screen readers

[mgifford]

Title: WCAG 4.1.2: Nested interactive controls are not announced by screen readers (summary)
Tags: Accessibility, WCAG 4.1.2, nested-interactive

Issue: Nested interactive controls are not announced by screen readers (nested-interactive - https://dequeuniversity.com/rules/axe/4.3/nested-interactive?application=msftAI)

Target application: About | OpenACR Editor | GSA - https://gsa.github.io/openacr-editor/about

Element path: details:nth-child(8) > summary

Snippet:

How to fix:
Fix any of the following:
Element has focusable descendants

Environment: Microsoft Edge version 98.0.1108.62

====

This accessibility issue was found using Accessibility Insights for Web 2.30.1 (axe-core 4.3.2), a tool that helps find and fix accessibility issues. Get more information & download this tool at http://aka.ms/AccessibilityInsights.

FastPass_20220304_AboutOpenACREditorGS.html.zip

[dmundra]

@mgifford we actually ignore the check for 'nested-interactive' in pa11y-ci (https://github.com/GSA/openacr-editor/blob/main/.pa11yci#L8) because we both reviewed this and found that it might be a false positive. Sharing the previous discussion:

• Updated pa11y-ci to latest version (in all repos) #278 (comment)
• You mentioned in slack that it might be related to Rules Conflict / Nested interactive controls are not announced by screen readers dequelabs/axe-core#3155 and the rest of our slack conversation

Mike:
I'm trying to figure out if this is a bug and if it has been identified. I can just reach out to Wilco (who is the main developer) but want to make sure that we've understood it first.

Mike:
I don't see any problem with putting an H2 in a summary..

Daniel:
Right I don’t either but clearly there could be issue where the header is not announced by screen readers.

Mike
Which might frankly be a problem with either the AT or Browsers...

Would be good to revisit this though as it is an issue.