Suppression du critère WCAG de l’analyse syntaxique #189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Le groupe de travail WCAG a publié une mise à jour des WCAG 2.1 le 21 septembre 2023 indiquant que le critère de succès 4.1.1 Parsing devait dorénavant être toujours considéré comme conforme.
Le RGAA étant une transposition des WCAG 2.1, nous proposons d'appliquer ce choix aux critères correspondants dans le RGAA. Ainsi, les critères 8.1 et 8.2 du RAWeb ne sont plus à tester et doivent toujours être considérés comme conformes.
Les critères sont conservés dans le référentiel (pour préserver la numérotation des critères de la thématique « Éléments obligatoires ») et sont accompagnés d’une note.
Cette modification provient des travaux réalisés dans le cadre du RAWeb 1.