RAAM 1.1 : Changelog

Below we present the list of notable changes that appeared in version 1.1 of RAAM.

Tools

The evaluation spreadsheet has been updated.

Criteria and tests

• The warning has been enhanced.
• Where possible, criteria have been mapped to APPT documentation.
• For the criteria subject to the non-interference principle, a note has been added.

Theme 2 “Colours”

• Criterion 2.2: the methodology for assessing colour contrasts has been improved so that the actual size of the text can be evaluated to refine the evaluations.

Theme 3 “Multimedia”

• Criterion 3.7: added a test for live synchronized media to cover entities subject to the law of March 8, 2023 on the accessibility requirements for products and services.
• Criterion 3.8: added a condition on the language of captions and a test for live synchronized media.
• Criterion 3.14: improved the methodology and added an example.
• Criteria 3.15 and 3.16: improvement of the methodology.
• Criterion 3.17: revision of the wording of the criterion and improvement of the methodology.
• Criterion 3.18: revision of the wording of the criterion, addition of conditions and improvement of the methodology.

Theme 8 “Presentation of information”

• Criterion 8.2: improvement of the methodology.

Theme 9 “Forms”

• Criterion 9.8: revision of the wording of the criterion to cover all fields whose format is controlled.

Theme 11 “Consultation”

• Criterion 11.7: modification of the condition "less than 3 per second" to "less than or equal to 3 per second".
• Criterion 11.15: improvement of the methodology.

Theme 12 “Documentation and accessibility features”

• Criterion 12.1: revision of the wording of the criterion and improvement of the methodology.
• Criterion 12.2: revision of the wording of the criterion and improvement of the methodology.
• Criterion 12.4: revision of the wording of the criterion (a note has been added to specify the scope of evaluation of the documentation) and addition of tests to cover each format.

Theme 13 “Editing tools”

• Criterion 13.1: revision of the criterion wording and addition of tests to cover each format.
• Criterion 13.2: revision of the criterion wording and improvement of the methodology.
• Criterion 13.3: revision of the criterion wording and addition of tests to cover each format.
• Criterion 13.5: revision of the criterion wording and addition of tests to cover each format.
• Criterion 13.6: revision of the wording of the criterion to cover all formats.

Note: for criteria 13.1, 13.3 and 13.5, the methodologies have been revised to include the evaluation of content intended for publication in a mobile application. Although the corresponding criteria of the EN 301 549 standard (11.8.2 Accessible content creation and 11.8.3 Preservation of accessibility information in transformations) only target sections 9 (Web content) and 10 (Non-web content), and not section 11 (Software, dedicated to the mobile context), it seemed essential to still include the evaluation of the elements targeted by these criteria if they appeared in a mobile application.

Theme 14 “Support services”

• Criterion 14.1: revision of the wording of the criterion to better reflect what is evaluated.
• Criterion 14.2: improvement of the methodology.
• Criterion 14.3: new criterion. It was previously included in theme 12 “Documentation and accessibility features”. But for reasons of readability of the criteria and requirements, a criterion dedicated to the accessibility of the documentation of the assistance service has been created.

Theme 15 "Real-time communication"

• Criterion 15.1: improvement of the methodology.
• Criteria 15.1, 15.2, 15.6, 15.11: added to the methodology the statement “If the information cannot be found in the interface or its documentation, and the editor of the application is unable to answer about this technical characteristic, the criterion will be considered non-compliant.”
• Criterion 15.2: removed the condition relating to a terminal integrating a real-time written communication functionality.
• Criterion 15.3: improvement of the methodology.
• Criterion 15.4: creation of 2 tests.
• Criterion 15.6: improvement of the methodology.
• Criterion 15.9: revision of the wording of the criterion (the criterion contained a misinterpretation) and improvement of the methodology. Old criterion “For each two-way voice communication application that provides caller identification, is there a way to present this identification for sign language users?”; New criterion “For each two-way voice communication application that makes it possible to identify the activity of a speaking interlocutor, it is possible to identify the activity of a signing interlocutor. Is this rule respected?”

Glossary

Additions

1. Help with creating accessible content
2. Documentation
3. Mandatory field indication
4. Visible text
5. Lists
6. Mechanism enabling to activate an accessibility feature
7. Modifying or cancelling data and actions taken
8. Pressed
9. ​​Digital accessibility rules
10. Released
11. Data type and format

Modifications

1. Real-time text communication: added a paragraph detailing an example with collaborative editing tools.
2. User Interface component: added a paragraph detailing the particularities of form fields in a mobile context.
3. Contrast (text size): revised the definition of text size, aligned with the RAWeb regarding sizes in px.
4. Primary control is renamed Primary features (of a time-based media)
5. Accessibility feature: added additional examples.
6. Time-based media (sound, video and synchronized): added a note.
7. Support services: added the feedback mechanism of the accessibility statement to the examples of support services.
8. Relay service: editorial changes.

Methodology

• The document has undergone a major modification. The section "Assessment of compliance with the reference standard" previously present in the page "Obligations" has been taken up at the beginning of this page.
• The non-interference principle is taken up, as in the RAWeb, and adapted to the criteria of the RAAM.
• The section « External keyboard » now explains that it is possible to test with or without a keyboard accessibility service on Android.
• The section « Taking screenshots » has been revised in depth, in particular to meet the needs of calculating text sizes for criterion 2.2.

Test environment

• It is now noted in the table that previous versions are authorized to perform the tests.