RAAMA
11.3 On each screen, does each office document available for download have, if necessary, 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)
Official methodology to test criterion 11.3
Test 1 (11.3)
iOS and Android
- Identify the components on the screen (a link, a button (form) or a download form for example) used to download a file in office format (.doc, .docx, .pdf for example).
- For each file offered for download in an office format, check that an alternative version is presented as accessible.
- If the alternative is offered in an office format (pdf, odt, doc, docx, EPUB/DAISY):
- download the file containing the proposed alternative;
- if this file is in PDF format, check that it complies with the PDF accessibility assessment framework (RAPDF 1).
- if the file is in another format, check that it complies with the criteria of section 10 Non-web documents of European standard EN 301 549 v3.2.1.
- If the alternative is proposed in the application, check that the content complies with this framework.
- Otherwise, for documents in office format (pdf, odt, doc, docx, EPUB/DAISY):
- download the file;
- if the file is in PDF format, check that it complies with the PDF accessibility assessment framework (RAPDF 1).
- if the file is in another format, check that it complies with the criteria of section 10 Non-web documents of European standard EN 301 549 v3.2.1.
- If this is the case, the criterion is validated.