What the Methodologies Are Based On

  • Status: draft for discussion.
  • Reading time: about 10 minutes.
Several sources connect to the methodologies’ shared technical core; a globe represents international experience.

The methodologies use international guidance and standards as their common reference framework, with national and regional instruments identified separately by jurisdiction. Where the methodologies add a requirement beyond these documents, it is marked separately with the "Project proposal" label and is not mixed with normative criteria.

International basis

  • WCAG 2.2 (W3C Recommendation, 12 December 2024). The main testable standard: the 55 current level A and level AA success criteria formed the basis of the check protocols and of the checklist of the assessment methodology.
  • WCAG Evaluation Methodology (WCAG-EM) 2.0 (W3C Group Note, 23 July 2026). Used to build the sample, its structured and random parts, and the structure of the assessment report.
  • Making Content Usable for People with Cognitive and Learning Disabilities (COGA) (W3C Working Group Note, 29 April 2021). The source of advisory requirements for cognitive accessibility: clarity of language, memory support, error prevention. These requirements complement WCAG and are not part of the WCAG conformance levels.
  • Accessibility Conformance Testing (ACT) Rules Format 1.1 (W3C Recommendation, 5 February 2026). The format for describing transparent, reproducible test rules, applied when formatting the protocol cards.
  • Involving Users in Evaluating Web Accessibility (W3C WAI). The basis for the requirement to combine testing against the standard with evaluation involving people with disabilities, and not to replace one with the other.
  • W3C WAI reference materials: ARIA Authoring Practices Guide, Understanding WCAG, Techniques for WCAG, WAI Tutorials and WAI Audio and Video Media. Used as references for implementation and testing techniques, not as independent normative sources.
  • The user testing practice of the Norwegian supervisory body Uutilsynet. Taken into account when describing the conditions of consent, assistance, and stopping a session in the comprehensibility and cognitive accessibility protocol.

International standards and their scope

International standards and guidance define the shared technical and methodological reference frame. Their legal effect depends on the jurisdiction, instrument, procurement rules, contract, or other source that adopts or references them. W3C documents, including WCAG, are not legal acts in themselves. The table below summarises the purpose and scope of the key international documents on which the methodologies rest.

Document Publisher and purpose Scope and status
WCAG-EM 2.0, COGA, ACT Rules Methodological documents of the W3C consortium: site conformance evaluation, cognitive accessibility, test rule format A Group Note, a Working Group Note, and a W3C Recommendation respectively, not international ISO standards
ISO 21801-1:2020 The international ISO standard on cognitive accessibility Current international standard
ISO 14289-1:2014 (PDF/UA) The international ISO standard for accessible tagged PDF documents Current international standard
ISO 24495-1:2023 (plain language) The international ISO standard for writing texts in plain (easy to understand) language Current international standard, published in June 2023
EN 301 549 The European Union harmonised standard (ETSI/CEN/CENELEC) for the accessibility of ICT products and services, applied in EU public procurement A European Union standard, not an international ISO standard

Russian national profile

The Russian materials in this section form one national profile among the jurisdictions cited in this document. Their use in a project is recorded with the applicable jurisdiction, the instrument that establishes any obligation, and the scope of voluntary or contractual adoption. None of them is an international standard, and a conformance claim against a national standard is not a conformance claim against WCAG.

National adoption and its degree of correspondence (IDT, MOD, or NEQ) are distinguished under GOST R 1.7-2014. A corresponding GOST R for ISO 24495-1:2023 is not identified in the cited sources; this is a limit of the documented mapping, not a claim that no such adoption could exist.

For the Russian profile, WCAG 2.2 has no separate GOST R reference in the cited materials; GOST R 52872-2019 was developed on the basis of WCAG 2.1. ISO 21801-1:2020 has an identical (IDT) GOST R ISO 21801-1-2022, approved by Rosstandart Order No. 1399-st of 29.11.2022. ISO 14289-1:2014 (PDF/UA) was considered when GOST R 70176-2022 was developed, without an IDT/MOD correspondence claim.

  • GOST R 52872-2019 (Russian-language source). Subject: accessibility of internet resources, applications, and interfaces in general. In the methodologies it is kept as a separate line of traceability, not identical to WCAG 2.2 AA.
  • GOST R 70176-2022 (Russian-language source). Subject: accessibility of PDF documents. The methodologies state separately that it does not prove the accessibility of a site interface or of a conversion process, and that conformance to PDF/A is not equal to conformance to PDF/UA.
  • GOST R ISO 21801-1-2022 (Russian-language source). Subject: general guidance on cognitive accessibility. In the methodologies it is used as a reference point, not as an independent measurable site checklist.
  • Government of the Russian Federation Resolution No. 102 of 07.02.2026 (Russian-language source), in force from 01.03.2026. A special mandatory profile for the official websites of state authorities, local government bodies, and organisations subordinate to them, in respect of accessibility for people with visual disabilities, and not a general rule for all sites and all kinds of limitations.
  • List of instructions of the President of the Russian Federation No. Pr-248 of 07.02.2025, item 9 (Russian-language source). The Ministry of Digital Development, Communications and Mass Media of Russia was instructed to present proposals on adapting Russian software and Russian information resources for use by people with disabilities (deadline 01.07.2025). The instruction sets a goal, not a technical profile: it does not determine a standard, a conformance level, or an assessment procedure. The methodologies are offered as a contribution to solving the task set, not as its official execution.
  • Ministry of Labour of the Russian Federation Order No. 647n of 14.11.2025 (Russian-language source), entering into force on 01.09.2027. It is not yet in force at the date of the methodologies, so its content is used only as a source of the project idea of an adaptation cycle for plain text, and not as a verified effective normative text.

National and regional practices taken into account in the methodologies

Besides the international methodological basis (WCAG 2.2, WCAG-EM 2.0, ACT Rules, COGA, see the section above), the experience of specific national digital accessibility regimes was taken into account when the methodologies were prepared. The practices, their source, and the element borrowed are listed below, by the methodology in which they were included. These examples can inform projects elsewhere. Their legal requirements, operational targets, and transferable practices remain distinct; applicability is established for each product.

In section A (sites and web applications) of the assessment methodology

  • Norway, Uutilsynet, "Forenklet kontroll og statusmåling med nettsteder". The principle of a separate regulation for simplified automated screening, and of the order of checks for regular monitoring of a portfolio of sites of one owner, was taken. Such a regulation does not replace the conclusion on a specific site.
  • Finland, Laki digitaalisten palvelujen tarjoamisesta 306/2019, §§ 8, 10d-10e. By analogy, the approach to a documented exemption from requirements (for example, disproportionate burden) was taken: the grounds are recorded in the assessment passport, and the assessor reflects the fact of the stated exemption itself, without confirming its justification as a fact.
  • Germany, BIK BITV-Test methodology. The following rule was taken: the scope of testing in the assessment passport is determined by the customer, while the final composition of the structured and random sample within the already agreed scope is determined by the assessor and is not agreed with the customer page by page. Following the same pattern, an annually updated reference list of versions of browsers, operating systems, and assistive technologies was introduced, together with mandatory independent review of the conclusion when conformance with the AA profile is claimed, or when the conclusion is used for an accessibility mark or a register.
  • France, RGAA portal, "Évaluation de la conformité". The rule for counting the result of a criterion across the sample was taken into account: a criterion is met at sample level only if it is met on all sample units where it applies; it is applicable if it applies on at least one sample unit.
  • Norway, Uutilsynet guide on user testing. The planning rule for user research was taken: at least one participant for each substantially different interaction model in a critical process, with the composition expanded until no new classes of barriers appear.
  • Estonia, TTJA, 2024 report on digital accessibility of the public sector; Norway, Uutilsynet, "Slik fører vi tilsyn med nettsteder og apper"; United Kingdom, GOV.UK, report on accessibility monitoring of public sector websites and applications for 2022-2024. The reference point of the cited national monitoring regimes on remediation plan deadlines was taken into account: about 5 working days for the first written response, and about 8-12 weeks for full remediation of a defect, tied to the severity of the defect, as an example of practice and not as a rule of the methodology.
  • France, RGAA portal, "Déclaration d'accessibilité". The model of three mutually exclusive final statuses of a conclusion (conforms, partially conforms, does not conform), each necessarily accompanied by a full list of non-conformities, was taken.
  • Finland, Traficom, procedure for checking conformance with the Act on Digital Services; Denmark, Digitaliseringsstyrelsen, "Overordnede resultater for 2024". The principle of checking the site's accessibility statement separately in the conclusion was taken into account: its presence, the date of the last review, the consistency of the stated status with the test results, and a working feedback channel.
  • Estonia, TTJA, overview of regular accessibility monitoring; Denmark, Digitaliseringsstyrelsen, "Monitorering og tilsyn"; Spain, Observatorio de Accesibilidad Web, monitoring report. The principle of sample rotation during regular monitoring of a portfolio of sites of one owner was taken into account: some objects are repeated to compare dynamics, some are updated to cover new areas, and no site remains unchecked for longer than the period agreed in the monitoring passport.

In the development methodology for accessible websites

  • Singapore, GovTech, Digital Service Standards Control Catalog and Accessibility playbook. The model of tagging the requirements register by component type or interface area (shared design system components, page templates, content, documents and media, third-party components) was taken, so that the designer and the developer see only the slice of the register relevant to them.
  • Finland, Selkokeskus, procedure for granting the plain language mark selkotunnus. The model of independent expert review of text comprehensibility for documents of critical processes was taken: the expert is not the author of the text under review, a representative of the target group takes part in the assessment, and a protocol listing the reworked passages is produced as the outcome.
  • Australia, AHRC, "Standards and guidelines for digital accessibility", in the wording of the national plain language standard AS ISO 24495.1:2024. The direct reader success criterion, that the reader found the needed information, understood it correctly, and was able to apply it to complete the task, was taken as the basis of the check of text comprehensibility; formal readability metrics remain only a reference point for the author.
  • Finland, Laki digitaalisten palvelujen tarjoamisesta 306/2019, § 10. By analogy, the response deadline of the support service for an accessibility barrier report was taken: a substantive response no later than two weeks, with a possible extension of another two weeks with notification of the reason. This is a project response target and does not replace the deadlines established by legislation on citizens' appeals.
  • Australia, DTA, Digital Service Standard v2.0, criterion 3 "Leave no one behind", in the wording of Intopia. The requirement of a backup channel for reporting an accessibility barrier, one that does not coincide with a potentially problematic element of the main channel, was taken.
  • Australia, AHRC, "How to provide equal access to digital goods and services". Two practices were taken: a mandatory register of known accessibility barriers with status, owner, and deadline as part of the handover package of a product to another team or contractor, and a supplier conformance declaration against the WCAG criteria (an example of a conformance report comparable in purpose to the VPAT format) as a qualification condition for the purchase of a third-party component.
  • Australia, DTA, Digital Inclusion Standard. The model of a single passport for a shared component of the website and the mobile application of one product was taken, with separate fields where the platform implementation really differs.
  • United Kingdom, GOV.UK Design System, "Accessibility strategy". The requirement to name in the component passport the specific assistive technologies on which the component was actually tested, rather than a general wording such as "tested with a screen reader", was taken.
  • Estonia, TTJA, 2024 report on digital accessibility of the public sector, section 2.2.3. The principle of the boundary of the contractor's area of responsibility was taken: the mandatory accessibility profile covers the screens and functions that fall within the subject of the specific contract, and not the whole product of the supplier.

In the comprehensibility and cognitive accessibility protocol

  • Spain, UNE 153101:2018 EX and UNE 153102:2018 EX. The requirement of mandatory validation of an "easy reading" text by a participant with difficulties in reading or understanding who has not previously edited that text, and not only an internal check by an editor, was taken as a condition for recognising a version as ready.

The practices listed above are not transferred verbatim. Numeric thresholds, deadlines, and weights from a specific jurisdiction are identified as jurisdiction-specific or replaced by an independent project proposal where the source does not establish a general rule. Each listed practice is limited to the scope of its cited source.

What is the authors' own

Not everything in the methodologies is taken from the documents above. The authors added some rules themselves, where the standards are silent or leave the choice to the implementer. So that a reader can always distinguish a norm from an authorial rule, such paragraphs in the methodology texts begin with a "Project proposal" badge on a coloured background. For example, the rule on rounding in random sampling of pages in section A.3 of the assessment methodology and the requirement to prepare a needs profile before design starts in section 3 of the development methodology are marked in this way. The full list of such paragraphs is visible directly in the texts of the methodologies by that badge; the origin of the ideas behind them is described below. In the check protocols the same role is played by the "project boundary" field in the criterion card.

The source of the idea for most of the paragraphs with the "Project proposal" badge can be traced: some descend directly from international W3C documents, some from the Russian draft order of the Ministry of Labour on plain language, and some are additionally supported by the practice of specific national and regional regimes, in particular Norway and Germany, see the section above. Two rules, the rounding in random sampling of pages and the requirement of a regression check of a shared component when changes are made, are independent engineering decisions of the project: no analogue was found for them in the international documents and national regimes studied. The methodology names the source next to each badge where a source is identified; where no source is identified, the paragraph remains an authorial proposal without an invented reference.

A rule with the badge is not an international or Russian normative requirement. It becomes applicable only when the responsible jurisdiction, customer, contract, procurement rule, or internal governance instrument gives it that effect. In all other cases it is a recommendation of the authors, which can be accepted or rejected.