Accessibility frameworks: spring cleaning before the big facelift

2026 will be a pivotal year for our accessibility assessment frameworks. The revision at the beginning of this year paves the way for a more extensive update, which will incorporate the update to the European standard.

Friday, February 6, 2026


Screenshot of the GitHub repository ReferentielAccessibiliteWeb
Screenshot of the GitHub repository ReferentielAccessibiliteWeb

The web and PDF accessibility frameworks, RAWeb and RAPDF, are both moving to version 1.1. This update is necessary following their introduction in 2024 and 2023 respectively.

The primary objective was to incorporate the numerous comments received from the community, which remains very active. The main purpose of these comments is to make the criteria, tests and methodologies more consistent where ambiguity may remain, but also to remove references to technologies that are no longer in use.

Together, this revamp, reviewed by the community, has led to the following advances:

On the RAWeb side

  • Support for the European Accessibility Act (EAA)
  • Simplification and clarification of ambiguities
  • Updating of obsolete techniques (e.g. Internet Explorer)
  • Updating of WCAG correspondences

The work covered a total of 33 criteria and 26 glossary entries (not including work related to mapping).

All changes are documented in the RAWeb 1.1 changelog.

The support of the EAA, particularly for criteria dedicated to videos, allows this framework to be used outside the strict frame of Luxembourg public domain websites.

In addition, certain criteria, tests, methodological elements and glossary items have been rewritten in order to be summarised following the removal of certain requirements (test 1.2.4, for example), or enriched to clarify the meaning (methodologies for criterion 3.1 in particular). New glossary items have been added, such as Document, Cryptic Content and Computed Role.

On the RAPDF side

  • Simplification and clarification of ambiguities
  • Removal of screen reader-based tests
  • Addition of PDF/UA-2 correspondences

The work covered a total of 9 criteria and 4 glossary entries (not including work related to mapping).

All changes are documented in the RAPDF 1.1 changelog.

The testing methodology has been streamlined so that a screen reader is no longer required for evaluation, with tests now based on two tools: Acrobat Reader and PDF Accessibility Checker (PAC).

The technical framework is therefore slightly more concise, even though it now includes PDF/UA-2 mapping for each criterion.

Waiting for the main course: EN 301 549, and therefore WCAG 2.2

These updates allow us to accommodate changes to the European standard, EN 301 549, which is due to be upgraded to version 4.1.1 in autumn. This version of the standard incorporates, among other things, version 2.2 of WCAG. It also offers a much broader scope, allowing for the evaluation of a wide range of goods and services (bank counters, transport ticket machines, e-books, etc.), a task dedicated to OSAPS in Luxembourg.

However, the SIP's mission will continue to be limited to accessibility assessment tools for the web, mobile applications and PDF documents. Our three frameworks - RAWeb, RAAM and RAPDF - will therefore undergo a major overhaul this autumn. RAWeb 2 and RAAM 2 are scheduled for publication in early January 2027.

In addition, we remain attentive to the community and are keen to include your suggestions for improving these frameworks on a regular basis.