Skip to main content
RAAMA

13.1 Can each editing tool be used to define the accessibility information needed to create content that complies with digital accessibility rules?

Official methodology to test criterion 13.1

Test 1 (13.1)

iOS and Android
  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 that lets you enter text or define properties).
  2. For functions that allow content to be created in web format (HTML, CSS), check that it is possible to define the accessibility information needed to make the content compliant with the RAWeb. For example:
    • defining a text alternative for an image from the text editor or a media library;
    • defining the accessible name of a link;
    • etc.
  3. For functions that allow content to be created in PDF format, check that it is possible to define the accessibility information required to make the content compliant with the RAPDF. For example:
    • defining a text alternative for an image from the text editor or a media library;
    • defining the accessible name of a link;
    • etc.
  4. For functions that allow content to be created 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 in section 10 Non-web documents of the European standard EN 301 549 v3.2.1. For example:
    • defining a text alternative for an image from the text editor or a media library;
    • defining the accessible name of a link;
    • etc.
  5. For functions that enable content to be created and delivered in a mobile application, check that it is possible to define the accessibility information needed to make the content compliant with the 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.
  6. If this is the case, the criterion is validated.