RAAMA
13.3 Does the content generated by each content transformation comply with digital accessibility rules (excluding special cases)?
Official methodology to test criterion 13.3
Test 1 (13.3)
iOS and Android
- From the editing functions (a text editor, but it can also be a media library or any other interface that lets you enter text or define properties), enter the types of content proposed by the editor (heading, list, table, image, etc.). Also use the various parameters for defining accessibility information (enter the text alternative for an image, add a description to a link, etc.)
- Save your entries.
- View the generated content:
- in the editing function (for example, in the text editor);
- and in the content publication interface (for example, the publication web page).
- For each piece of content in web format (HTML, CSS), check that:
- the information necessary for it to comply with the RAWeb (e.g. the alternative of an image, the headings levels) is preserved in the generated content;
- the information, if restructured, remains compatible with assistive technologies (for example, if the author enters an HTML table and, after saving, the tool linearises the table, the restructured information must be understandable to assistive technology users as it would have been in its original form).
- For each content item in PDF format, check that:
- the information necessary for it to comply with the RAPDF (e.g. alternative image, headings levels) is preserved in the generated content;
- the information, if restructured, remains compatible with assistive technologies (for example, if the author enters a table and, after saving, the tool linearises the table, the restructured information must be understandable to assistive technology users as it would have been in its original form).
- For all content in non-web format that is not PDF, check that:
- the information required to comply with section 10 Non-web documents of the European standard EN 301 549 v3.2.1 is preserved in the generated content;
- the information, if restructured, remains compatible with assistive technologies (for example, if the author enters a table and, after saving, the tool linearises the table, the restructured information must be understandable to assistive technology users as it would have been in its original form).
- For each content displayed in a mobile application, check that:
- the information necessary for it to comply with the RAAM (e.g. alternative image, identification of headings) is preserved in the content generated;
- the information, if restructured, remains compatible with assistive technologies (for example, if the author enters an HTML table and, after saving, the tool linearises the table, the restructured information must be understandable to assistive technology users as it would have been in its original form).
- If this is the case, the criterion is validated.