The XWiki project follows the Web Content Accessibility Guidelines (WCAG) 2.2 at the AA level. All features, and especially new ones, must comply with them. The Accessibility Statement holds the public commitment and the current conformance status.

The Accessibility Manager keeps the statement up to date, organizes the audits and monitors the automated test results.

How Accessibility Is Ensured

• Development Rules: the HTML and CSS rules that the automated tests can't check.
• Automated Testing: Axe Core validation in the functional tests. It finds about half of the issues.
• Manual Testing and Audits: needed for the other half, to fully pass WCAG 2.2 AA.
• Tools and Resources: browser extensions, validators and checklists.

Related pages elsewhere:

• Documentation: accessibility of attachments, images and tables and accessible diagram colors.
• Vue components: Test the accessibility of a Vue component.
• Design: WCAG validation in build, the design of the automated testing.

Report an Accessibility Issue

• Search the open accessibility issues first, with a few keywords.
• Add the wcag label to the issue.
• Fill the WCAG 2.1 Rule ids field with the number and name of the broken success criterion, for example 2.4.1 Bypass Blocks.
• Add a screenshot of the element, showing both the page and its DOM tree.

History

• XWiki 18.10.0+ The Dutch Web Guidelines validation has been removed from the build. Our accessibility commitment is WCAG 2.2 AA, validated by Axe Core, and the DWG checks were either not WCAG requirements, AAA-only, obsolete, or already covered by Axe Core or the HTML5 validator.
• XWiki 15.8+ Incomplete checks and per test suite statistics are written to report files.
• XWiki 15.5+ Improved log traces of WCAG validation.
• XWiki 15.2+ XWiki uses Axe Core to validate accessibility.
• XWiki <15.2 XWiki was using the Dutch Web Guidelines to validate accessibility.
• XWiki Enterprise 2.1+ A first manual WCAG testing session checked the main pages against the Dutch Web Guidelines validator.