Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring Parsing in spec with the release of WCAG 2.2 #7400

Open
jeremyZX opened this issue Jul 26, 2024 · 1 comment
Open

Bring Parsing in spec with the release of WCAG 2.2 #7400

jeremyZX opened this issue Jul 26, 2024 · 1 comment
Assignees
Labels
feature request status: ready for work This issue is ready to be worked on.

Comments

@jeremyZX
Copy link

jeremyZX commented Jul 26, 2024

Is your feature request related to a problem? Please describe.

WCAG 2.2 removes the success criterion 4.1.1 Parsing (Level A). In addition, with the release of WCAG 2.2, Parsing is deprecated in WCAG 2.0 and 2.1, and the criterion is updated in those versions to always be considered satisfied by any content using HTML or XML.

The Accessibility Insights extension reflects this update with a small "Deprecated for WCAG 2.2" notice, which is not completely accurate, and the test does not reflect current WCAG guidance.

Describe the desired outcome

Remove the Parsing test from the guided Assessment.

Describe alternatives you've considered

Update the Parsing test automatically pass if the detected content is XML or HTML, and describe how to test for non-XML/non-HTML content.

@microsoft-github-policy-service microsoft-github-policy-service bot added the status: new This issue is new and requires triage by DRI. label Jul 26, 2024
@JGibson2019 JGibson2019 added needs PM input This issue has open question(s) that needs to be answered by PM. and removed status: new This issue is new and requires triage by DRI. labels Aug 5, 2024
@madalynrose madalynrose added the status: needs investigation This issue requires investigation (PM, Design, or SWE) by the Accessibility Insights team. label Aug 12, 2024
Copy link
Contributor

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

@madalynrose madalynrose moved this from Needs triage to Accepted in Accessibility Insights Sep 23, 2024
@madalynrose madalynrose assigned codeofdusk and unassigned nang4ally Sep 23, 2024
@madalynrose madalynrose added status: ready for work This issue is ready to be worked on. and removed status: needs investigation This issue requires investigation (PM, Design, or SWE) by the Accessibility Insights team. needs PM input This issue has open question(s) that needs to be answered by PM. labels Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request status: ready for work This issue is ready to be worked on.
Projects
Status: Accepted
Development

No branches or pull requests

5 participants