-
Notifications
You must be signed in to change notification settings - Fork 22
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
WCAG 2.2 plans? #413
Comments
Hello, we are currently integrating the latest version of Deque Axe which is used by Ace to perform the checks inside HTML documents. https://github.com/dequelabs/axe-core/releases/tag/v4.9.1 WCAG support is described here: https://github.com/dequelabs/axe-core/blob/develop/doc/rule-descriptions.md Note that the EPUB Accessibility specification currently only references 2.1, but this will be tracked upwards as the standards evolve: https://w3c.github.io/epub-specs/epub33/a11y/#sec-conf-reporting-pub |
Related: dequelabs/axe-core#4361 |
Thanks for all of this! |
I was just looking into the same issue. What about the older WCAG 2.1 which is recommended even though 2.0 is the absolute minimum? I did not find a way validate against the 2.1 ruleset. Or is 2.1 support something that will come together with the Deque Axe integration? |
Current Ace architecture is based on the premise that the latest revision of W3C EPUB Accessibility (1.1) is supported, there is no API control to select a target version, let alone to tweak WCAG conformance requirements. Ace simply executes Deque Axe for each XHTML documents in the EPUB publication. We do fork the Deque Axe codebase and we create our own build in order to address a few EPUB-specific points, so we have some scope to adapt the overall architecture and enable more flexibility (consumer-side) ... but this would be a non-trivial undertaking as I currently understand it. |
OK I see your point. Your target is W3C EPUB Accessibility (1.1) which supports different WCAG versions. But the new EU accessibility directive is actually requiring WCAG 2.1 or greater. This is an issue because now we cannot validate ePubs against this standard with Ace. |
Deque Axe level of support is a little bit unclear to me, when I read this: |
Did understood the commit correctly, now different ruleset combinations are supported and we can validate against spesific WCAG version? If that is the case, when is the next release coming out? |
Does anyone know if there are plans to include WCAG 2.2 criteria to the Ace testing?
Thanks!
The text was updated successfully, but these errors were encountered: