Very pleased to announce that Be Inclusive now supports the additional success criteria that were recently added as part of WCAG 2.2!
If you missed the news, WCAG 2.2 was officially published as a web standard on October 5th 2023. That new version added 9 additional success criteria bringing the total criteria from 78 in WCAG 2.1 to 87 in WCAG 2.2.
Audit Report Percentages
I’ve made some changes to the Audit Report percentages section in order to better support the additional standard, and to address some common feedback regarding that section.
This section is now titled “Overall Percentages” and now displays a single progress ring for percentage complete and for percentage passed based on the selected conformance target for the project.
Previously, this sections displayed six progress rings for the percent passed for all WCAG versions and levels of conformance. This section in particular was something that several subscribers had reported causing confusion with their clients, so rather than adding three more progress rings here for WCAG 2.2 I took this as an opportunity to simplify and more clearly explain what these percentages entail.
Looking for feedback especially on this update, please do reach out to let me know what you think about it.
Other Notable Updates
Here’s a rundown of other notable changes that were made to support WCAG 2.2.
- WCAG 2.2 Level AA replaced WCAG 2.1 AA as the default conformance target for new projects. You can still change this to any other version and level combination suitable for your project.
- The WCAG version filter in the audit editor now includes WCAG 2.2
- All 9 new success criteria are present in the Success Criteria section of the audit editor, as well as in the typeahead form for observations.
- Criterion details for these new criteria are available, linking to the new WCAG 2.2 Understanding and Techniques & Failures W3C WAI documentation. The content of these details have also been translated to Spanish, French, and Dutch. I used an automated translator so please do reach out if you have improvement suggestions on these translations.
Have any feedback about this blog post? Let us know!