RAWEB
15.1 Does each editing tool allow you to define the accessibility information needed to create content that complies with the digital accessibility rules?
Official methodology to test criterion 15.1
Test 1 (15.1.1)
- Identify the editing functions in the tool (for example, a text editor, but it could also be a media library or any other interface making it possible to enter text or define properties) that allow you to create content in web format (HTML, CSS).
- Check that it is possible to define the accessibility information needed to make the content compliant with RAWeb. For example
- defining the text alternative for an image from the text editor or a media library;
- defining the accessible name of a link;
- etc.
- If this is the case, the test is validated.
Test 2 (15.1.2)
- Identify the editing functions in the tool (for example, a text editor, but it could also be a media library or any other interface making it possible to enter text or define properties) that allow you to create content in PDF format.
- Check that it is possible to define the accessibility information needed to make the content compliant with RAPDF. For example
- defining the text alternative for an image from the text editor or a media library;
- defining the accessible name of a link;
- etc.
- If this is the case, the test is validated.
Test 3 (15.1.3)
- Identify the editing features in the tool (for example, a text editor, but it could also be a media library or any other interface making it possible to enter text or define properties) that allow you to create content in non-web format (other than PDF).
- Check that it is possible to define the accessibility information required to make the content compliant with the criteria of section 10 Non-web documents of European standard EN 301 549 v3.2.1. For example
- defining the text alternative for an image from the text editor or a media library;
- defining the accessible name of a link;
- etc.
- If this is the case, the test is validated.
Test 4 (15.1.4)
- Identify the editing functions in the tool (for example, a text editor, but it could also be a media library or any other interface making it possible to enter text or define properties) that allow you to create content for distribution in a mobile application.
- Check that it is possible to define the accessibility information needed to make the content compliant with RAAM criteria. For example
- defining the text alternative for an image from the text editor or a media library;
- defining the accessible name of a link;
- etc.
- If this is the case, the test is validated.