Skip to main content
RAWEBA

13.3 On each web page, does each downloadable office document have an accessible version (excluding special cases)?

WCAG references
  • 1.1.1 Non-text Content (A)
  • 1.3.1 Info and Relationships (A)
  • 1.3.2 Meaningful Sequence (A)
  • 2.4.1 Bypass Blocks (A)
  • 2.4.3 Focus Order (A)
  • 3.1.1 Language of Page (A)
  • 4.1.2 Name, Role, Value (A)
Techniques
  • F15
  • G10
  • G135

Official methodology to test criterion 13.3

Test 1 (13.3.1)

  1. Find in the document the links and form controls (a form button or download form, for example) allowing to you to download a file in office format.
  2. For each file in office format, check the presence of an alternative version presented as accessible:
    • For documents in .pdf format, check compliance with the PDF accessibility assessment framework (RAPDF).
    • For documents in .doc or .docx format, analyse the file with the Microsoft Office accessibility checker (from version 2010) and check that there are no accessibility errors (see note).
    • For documents in .odt format, analyse the document with the LibreOffice accessibility checker (from version 7.0).
    • For documents in EPUB/DAISY format, analyse the document with an EPUB/DAISY editor.
    • For documents in .html format, analyse the accessibility of the document.
  3. If this is the case for each file in office format, the test is validated.

Note on Microsoft Office: the software offers an accessibility checker as standard (accessible via the "File > Information > Check for problems > Check accessibility" menu).

Note on LibreOffice: the software offers an accessibility checker as standard, accessible via the "Tools > Accessibility Check" menu.

Note on the EPUB format: the Ace by DAISY App tool enables you to validate an EPUB 3 file efficiently.