Status: draft for discussion and piloting. This document is not an approved standard, a legal instrument, or evidence of compliance with legislation. Before approval, it must be piloted on live websites with the participation of users.
1. Purpose and scope boundaries
The methodology sets out a working process for creating and developing websites and web applications that can be used independently by people with different perception profiles and with limitations in vision, hearing, movement, speech, attention, memory, comprehension, and learning. It is intended for owners of digital products, customers, analysts, designers, content authors, developers, testers, and support services.
The object of the methodology: web pages, interface states, complete user processes, embedded web components, documents, and media assets reachable through the site. The methodology applies to the web part of any digital product, whatever the country of the owner, the country of the users, the country of the hosting, and the applicable legal system. A desktop or mobile application is assessed under its applicable platform methodology, not by assuming that web requirements transfer automatically.
Two capabilities of the product must be considered separately:
- accessibility of the site's own user interface;
- the ability of the site to create, receive, transform, publish, or export accessible content.
For example, a web editor may have accessible buttons but produce a document with no heading structure and no text alternatives. In that case the interface is accessible but the result of the work is not. The reverse situation is equally unacceptable.
The methodology does not assign a legally mandatory conformance level. The applicable profile is determined separately for each product and for each assessment: by the jurisdiction in which the site and its owner operate, by the customer, by the site category, by the contract or procurement instrument, and by the date of the assessment. For a cross-border service, record every applicable jurisdiction and the instrument that makes a requirement binding. A standard may also be adopted voluntarily or through a contract, including outside its country of origin. Citing a standard or WCAG does not by itself establish a legal obligation. The methodology therefore describes a universal digital product and a way of working that can be applied in any jurisdiction, and the national profiles in section 2 are examples of one possible legal basis, not a baseline.
1.1. Scope of application
The object of the methodology, the boundary against desktop and mobile applications, the separation of the two capabilities of the product (interface accessibility and the ability to produce accessible content), and the absence of an assigned legally mandatory conformance level are described in section 1. The methodology applies to any digital product with a web part, in any jurisdiction: the applicable jurisdiction, the contract or procurement instrument, and the voluntary target profile are fixed for each product at stage 0, and the national profiles in section 2 are examples whose applicability must be established for the product.
1.2. Terms and definitions
- Critical process - a process from entry to a confirmed result for which the WCAG complete process requirement applies; examples: registration, sign-in and account recovery, product search, filling in and submitting an application, uploading and signing a document, payment, contacting support, changing personal data (stage 0).
- Needs profile - a description of the functions, usage conditions, and barriers of a specific critical process, including devices, assistive technologies, level of digital experience, language, stressful conditions, and the cost of an error, prepared instead of a list of diagnoses (section 3).
- Requirements passport - a document that records, for a single requirement, the source, applicability, testable condition, pages, states, and components, verification method, expected result, owner, and control stage (template 9.1).
- Shared component - a design system component consumed by several product teams; a change to a shared component is treated as a change to all of its consumers (stage 8).
- Design system - a library of reusable components that keeps accessibility requirements next to the component itself rather than in a separate checklist (stage 8).
- Conditional acceptance - a release decision taken with non-critical deviations from project proposals, with an owner, a deadline, and a way of informing users defined by the owner; it does not apply to an unimplemented success criterion when the release claims conformance to WCAG (section 8).
- Project proposal - a requirement that this methodology introduces in addition to the adopted WCAG profile; a customer may make it mandatory in a technical specification, a contract, a design system, or an internal regulation (section 2.3).
- Jurisdiction - a legal system relevant to the product, its owner, or its users. A cross-border product may require more than one legal profile; applicability is established from the relevant instrument, not from the interface language.
- Legally applicable profile - requirements that apply to a specific site by virtue of verified legal grounds in the applicable jurisdiction, a contract, or procurement documentation; it is recorded with the jurisdiction and the date on which applicability was checked (stage 0).
- Voluntary target profile - a higher or wider set of requirements that the owner adopts in order to develop the product, for example WCAG 2.2 AA plus additional COGA proposals (stage 0).
- Accessible alternative - an equivalent way, in terms of result, to obtain content or complete a process when the main option cannot be made accessible, or cannot be made accessible yet (stages 4 and 9, section 8).
- Technology baseline - the recorded versions of browsers, devices, and assistive technologies on which product compatibility has been verified (stage 5).
- Supplier conformance declaration against WCAG success criteria - an annex to a contract for a third-party component, listing the applicable success criteria of the target profile and the status of each of them (stage 9).
- WCAG (Web Content Accessibility Guidelines) - the web content accessibility guidelines developed and maintained by the W3C consortium; this methodology uses version WCAG 2.2.
- W3C (World Wide Web Consortium) - an international consortium that develops standards and recommendations for the web, including WCAG.
- WAI (Web Accessibility Initiative) - an initiative (programme) of the W3C consortium that leads the development of WCAG, WAI-ARIA, and related accessibility documents.
- COGA (Cognitive and Learning Disabilities Accessibility Task Force) - a working group of the W3C consortium on cognitive accessibility; it produces advisory, non-mandatory additions to WCAG for people with cognitive and learning disabilities.
- WAI-ARIA (Accessible Rich Internet Applications) - a specification of the W3C consortium for marking up dynamic interfaces (roles, states, and element properties) that helps screen readers work.
- Levels A, AA, AAA - the three levels of WCAG conformance in increasing order of strictness; the methodology targets level AA, for which all applicable level A and level AA success criteria must be met.
- Assistive technologies (AT) - software and devices that a person with a disability uses to work with the site: screen readers, screen magnifiers, alternative input devices, and similar tools.
- ISO - the International Organization for Standardization, which publishes international standards, including in accessibility; an international standard is not by itself a legal instrument in any jurisdiction unless it has been adopted or referenced by applicable law, a contract, procurement instrument, or technical specification. Adoption or reference does not automatically make every provision mandatory: the applicable source must be checked for its scope and binding effect.
- GOST R ISO - the designation of a Russian national standard adopted on the basis of an international ISO (or ISO/IEC) standard, with the degree of correspondence indicated: identical (IDT), modified (MOD), or non-equivalent (NEQ); an identical standard (IDT) means that the text of the GOST R fully matches the international one. This designation identifies the national adoption; the project records separately whether and why it applies.
- PDF/UA (ISO 14289-1) - the international standard for accessible tagged PDF documents; its scope concerns the document format. In the Russian national example, it was taken into account when GOST R 70176-2022 (Russian-language source) was developed.
- PDF/A (ISO 19005) - a family of international standards for the long-term archival storage of PDF documents; it does not concern accessibility and is not the same as PDF/UA.
1.3. Reference framework and national profiles
The international reference framework is provided by WCAG 2.2 and COGA. National laws and standards are identified by origin, scope, edition, and the basis for their use. The Russian materials below are one national profile among others; they do not define the general scope of this methodology.
- WCAG 2.2, W3C Recommendation.
- Making Content Usable for People with Cognitive and Learning Disabilities (COGA), W3C Working Group Note.
- GOST R 52872-2019 (Russian-language source).
- GOST R 70176-2022 (Russian-language source).
- GOST R ISO 21801-1-2022 (Russian-language source).
- Government of the Russian Federation Resolution No. 102 of 07.02.2026 (Russian-language source).
- Ministry of Labour of the Russian Federation Order No. 647n of 14.11.2025 (Russian-language source).
The methodology is advisory in nature, is not a legal instrument, and does not establish mandatory requirements. Whether an individual requirement is binding depends on the applicable jurisdiction, contract, procurement instrument, or technical specification and must be checked against its own scope.
2. Basis and levels of requirements
The draft distinguishes three layers that must not be mixed: testable WCAG success criteria, advisory guidance, and project proposals. National legal and standards grounds form a fourth layer, kept apart from the first three: they are recorded with the relevant jurisdiction, adoption basis, and scope.
2.1. Testable WCAG success criteria
WCAG 2.2 is a W3C Recommendation and contains testable success criteria at levels A, AA, and AAA. WCAG itself warns that even AAA conformance does not cover the needs of all people, especially in the area of cognitive, language, and learning differences. A claim of conformance at level AA is possible only when all level A and level AA success criteria are met, together with all five conformance requirements: full level, full page, full process, support for accessibility-supported ways of using technologies, and non-interference of non-conforming technologies.
A W3C Recommendation is a technical standard, not a legal instrument. It has no automatic legal force in any jurisdiction and becomes binding only where the applicable law, a contract, a technical specification, or a procurement instrument adopts or references it. The scope of that binding must be read from the source that creates it.
2.2. Advisory COGA guidance
Making Content Usable for People with Cognitive and Learning Disabilities is a W3C Working Group Note. Its goals and patterns complement WCAG and are not required in order to claim conformance to WCAG. In this draft they are used as a source of requirements for practical cognitive accessibility: comprehensibility, predictability, error prevention, attention support, reduced memory load, help, and personalisation. A Working Group Note is advisory material: it carries no legal force of its own in any jurisdiction and is used here as a source of requirements for the target profile, not as a legal ground.
2.3. Project proposals
All requirements that this methodology introduces in addition to the adopted WCAG profile are marked with the words "Project proposal". A customer may make them mandatory in a technical specification, a contract, a design system, or an internal regulation. Such binding applies within the project and does not turn a proposal into an international or national normative criterion in any jurisdiction.
2.4. National profile example: the Russian legal and standards profile
This subsection records one national profile as an example of how legal and standards grounds are described for a single jurisdiction. It is not the general basis of the methodology, and the requirements of this methodology apply to a product in any jurisdiction.
In the project passport the Russian profile is recorded as separate lines with the date on which applicability was checked. Government of the Russian Federation Resolution No. 102 of 07.02.2026 (Russian-language source) takes effect on 01.03.2026 and forms 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. It cannot be extended to all sites, to other groups of owners, or to all kinds of limitations without a separate legal basis.
GOST R 52872-2019 (Russian-language source) has accessibility of internet resources, applications, and interfaces as its general subject. GOST R 70176-2022 (Russian-language source) concerns the accessibility of PDF documents and does not prove the accessibility of a site interface or of a transformation process. Conformance to PDF/A does not mean conformance to PDF/UA. GOST R ISO 21801-1-2022 (Russian-language source) gives general guidance on cognitive accessibility, but it is not by itself a measurable site checklist. None of these standards is identical to the WCAG 2.2 AA profile, so the project keeps a separate mapping for each of them.
Ministry of Labour of the Russian Federation Order No. 647n of 14.11.2025 (Russian-language source) takes effect on 01.09.2027. At the date of this version it is not in force. It can be taken into account as a future basis for plain-language texts, but not as an effective mandatory requirement and not as a replacement for checking the annex to the order once it enters into force.
The Russian profile illustrates how to record a national legal and standards context. Apply the same method to the examples in section 2.5: identify the applicable instrument, distinguish legal duties from voluntary targets, and retain separate mappings when editions or scopes differ.
2.5. Other national profiles cited in this document
The national materials below provide additional examples. Their origin does not make them universal legal requirements; their practices may inform projects elsewhere, with applicability and any adaptation recorded explicitly. They are cited as models for a single practice: a plain language procedure, a service standard, a procurement condition, a handover register, or a monitoring report.
- Australia: the Australian Human Rights Commission, "Chapter 3 | Standards and guidelines for digital accessibility" (2025) describes the AS ISO 24495.1:2024 plain language national standard; the Australian Human Rights Commission, "Chapter 2 | How to provide equal access to digital goods and services" (May 2025) describes the supplier conformance declaration in procurement and the register of barriers at handover. The Digital Inclusion Standard of the Digital Transformation Agency applies to websites and applications alike, and criterion 3 "Leave no one behind" of the Digital Service Standard v2.0 is reported by Intopia (15 February 2024).
- Singapore: the GovTech Singapore, Digital Service Standards Control Catalog and the Accessibility playbook describe the service design requirements applied in Singapore.
- Finland: the procedure for awarding the selkotunnus plain language mark of the Selkokeskus plain language centre and Laki digitaalisten palvelujen tarjoamisesta 306/2019, Section 10, are Finnish materials; its response deadlines are cited as a Finnish example, with legal applicability assessed separately.
- Estonia: the TTJA annual report on the digital accessibility of the public sector for 2024, section 2.2.3, describes the practice applied in Estonia for the boundary of the responsibility of a contractor within a contract.
- United Kingdom: the GOV.UK accessibility statement and the GOV.UK Design System, "Accessibility strategy" are used here as examples of an honest structure and of a published accessibility strategy; any legal obligations mentioned in them require a separate applicability check.
3. Target needs profile
The team starts not from a list of diagnoses, but from functions, usage conditions, and barriers. One person may simultaneously use magnification, a keyboard, captions, and a simplified presentation, and a need may be permanent, temporary, or situational.
| Area of needs | Typical barriers | Project answers |
|---|---|---|
| Low vision and colour perception | Low contrast, clipping when magnified, meaning conveyed by colour alone | Contrast, scaling and reflow, independence from colour, visible focus |
| Deafness and reduced hearing | Meaning only in audio, no captions or transcript | Accurate captions, text alternative for audio, visual notifications |
| Motor limitations | Operation requires a mouse, dragging, or precise pointing | Full keyboard operation, sufficient target sizes, alternative to gestures and drag and drop |
| Speech | Voice is the only way to enter or confirm information | An equivalent non-voice channel, compatibility with alternative input |
| Attention and sensory sensitivity | Autoplay, flashing and high-contrast or high-frequency content, superfluous notifications, unexpected transitions | Control of motion, limits on flash rate and area per WCAG 2.3.1, stopping of updates, calm composition, predictability |
| Memory and executive functions | Long process, repeated entry, loss of progress, timeout | Step-by-step process, data retention, clear progress, contextual help |
| Reading, language, and comprehension | Jargon, metaphors, complex instructions, overloaded pages | Literal language, short meaningful blocks, examples, summaries, and illustrations |
Project proposal. Before design starts, the team prepares a needs profile for three to five key processes. It records not only user groups, but also devices, assistive technologies, level of digital experience, language, stressful conditions, and the cost of an error. The number of research participants is chosen according to the diversity of risks and the maturity of the product. This document does not establish a universal normative quota.
3.1. Reconciling differing needs
Sufficient contrast of text and elements does not require a saturated palette, decorative motion, or a brighter screen. A calm composition can preserve distinguishability and a visible focus. Non-visual perception is supported by correct structure, element names, text alternatives, keyboard operation, and compatibility with assistive technologies; colour and magnification settings serve other needs. Within a single group, including people with autism spectrum disorder, preferences may differ, and one person may combine several needs. A profile is not assigned automatically by diagnosis. Basis: W3C WAI on vision and ways of accessing content.
Project proposal. Where a difference in needs is identified, the team provides an accessible choice of presentation: for example, changing colours, reducing motion, or hiding optional distractions. The choice must not remove content, functions, labels, or the focus indicator. The switch, the saving of the choice, and the return to the default are checked with a keyboard and assistive technologies. Sound and motion are not turned on as a mandatory cue without a way to control them.
For the default presentation the applicable contrast requirements still hold. The W3C explanation of WCAG 1.4.3 allows user-chosen combinations with lower contrast if a mechanism is available for returning to the required values. This condition belongs to that success criterion and does not cancel any other requirement. The chosen colours and the absence of distractions are checked separately. The mere presence of a light or dark theme does not prove that the interface is usable, and reduced motion does not replace the check for flashes.
4. Management and roles
The product owner is responsible for scope, process priority, the remediation budget, and the release decision. The customer or requirements owner fixes the target WCAG profile, additional rules, and permitted exceptions. The accessibility specialist translates the profile into testable criteria, advises the team, and checks the evidence. The researcher organises the safe participation of people with disabilities. The designer is responsible for states, navigation, readability, and component behaviour. The content author is responsible for plain language, structure, alternatives, and media. The developer provides semantics, operability, compatibility, and resilience. The tester reproduces scenarios and regressions. The support service receives requests through an accessible channel and passes recurring barriers to the product owner.
One person may combine roles, but the decisions must remain distinguishable. The author of a component does not close their own critical defect without an independent check. User testing does not replace the WCAG check, and the WCAG check does not replace user testing. Such a combined approach matches the W3C position that standard-based evaluation and research with users must be combined: Involving Users in Evaluating Web Accessibility.
Organisational maturity and the accessibility of a specific product version are assessed separately. Distributed roles, training, budget, policy, and supplier management show that the organisation can manage accessibility sustainably, but they do not replace the checking of pages, components, states, and release processes. A successful check of one release also does not prove maturity of continuous work. For organisational self-assessment, the W3C Accessibility Maturity Model in Group Note status and the draft resource Accessibility Roles and Responsibilities Mapping can be used as planning tools; the result of product acceptance is recorded separately, under stage 6.
5. Development process
Stage 0. Defining scope and critical processes
The owner records domains and subdomains, language versions, authorised and public zones, adaptive presentations, embedded third-party services, document types, and media assets. For each release the exact version or build date is stated.
Critical processes are described from entry to a confirmed result. Examples: registration, sign-in, and account recovery; product search; filling in and submitting an application; uploading and signing a document; payment; contacting support; changing personal data. Under the WCAG complete process requirement, an individual step cannot be declared accessible if another mandatory step of the process does not meet the target level.
Stage results: a scope map, a list of technologies, a register of critical processes, a needs matrix, the target WCAG level, and a list of project proposals. For each risk the affected groups, the owner, the resolution deadline, the temporary workaround, and the closure criterion are stated. A risk without an owner and a deadline counts as unplanned.
Two different fields must be kept in the project passport:
- legally applicable profile: requirements that apply to a specific site by virtue of verified legal grounds in the applicable jurisdiction, a contract, or procurement documentation, recorded with the jurisdiction and the date on which applicability was checked;
- voluntary target profile: a higher or wider set of requirements that the owner adopts in order to develop the product, for example WCAG 2.2 AA plus additional COGA proposals.
If the legally applicable profile refers to another edition of a standard, the team does not substitute WCAG 2.2 for it. The team keeps both mappings and shows the differences. The voluntary target WCAG 2.2 AA is not declared a universal legal obligation, and the legal grounds are checked for each applicable jurisdiction, including cross-border use.
Stage 1. Requirements and readiness criteria
Each requirement contains: the source; applicability; the testable condition; pages, states, and components; the verification method; the expected result; the owner; the point of verification. The wording "make it accessible" is not a requirement.
Project proposal. The requirements register is additionally tagged by component type or interface area from a closed list: shared design system components, page templates, content, documents and media, third-party embedded components. Such tagging does not replace the link to a specific WCAG success criterion and does not apply to requirements that concern the whole site rather than one component type. It lets the designer at stage 3 and the developer at stage 5 see only the slice of the register that belongs to their current task instead of a single monolithic list of requirements. Model sources: Digital Service Standards Control Catalog and the Accessibility playbook published by the Usability & Accessibility GovTech team. In that guidance the requirements are grouped by interface component and separated into checklists for design, development, and testing.
A minimal working profile is usually built around WCAG 2.2 A and AA, but the final profile is determined by the customer taking account of the law and the contract. For each success criterion the team uses the normative text of WCAG as the source of the requirement. The Understanding WCAG and Techniques for WCAG materials help to understand and implement the criteria, but they are not normative in themselves and do not cover all permissible ways.
Requirements and acceptance scenarios are traced to the annex "WCAG 2.2 A/AA check protocols". It contains 55 current A/AA success criteria, separate decisions on applicability, pass, fail, NA, and "not checked". The removed 4.1.1 and the AAA criteria 2.2.6 and 2.5.6 are not part of this profile.
Project proposal. For critical services, the applicable COGA patterns are added to the mandatory development profile, even when they do not follow from WCAG. A refusal to apply a particular COGA pattern must be accompanied by a short justification and by the result of a check with target users.
Stage 2. Information architecture and user paths
The architecture offers several ways to find an important section, except in cases where the page is a step of a process. This supports WCAG 2.4.5. Headings and labels describe the topic or purpose in line with WCAG 2.4.6. Repeated navigation keeps its order, and identical functions are identified consistently: WCAG 3.2.3 and 3.2.4.
Project proposal. The most important actions are visible on the first meaningful screen, and the path to them is not masked by advertising or secondary cards. A long task is split into understandable steps; before starting, the user sees the required data, an approximate content of the stages, and the consequences of submitting. This builds on the COGA goals "help find what is needed", "help focus", and "do not rely on memory".
Stage 3. Designing screens and components
All components are designed at least in these states: default, hover, keyboard focus, selected, disabled, loading, success, warning, and error. For a modal window, menu, tabs, disclosure blocks, autocomplete, and tables, the keyboard model and focus behaviour are specified. The ARIA Authoring Practices Guide can be used as a reference of proven interaction patterns, but the implementation must be tested in a real technology environment.
For each significant transition the mock-up and the specification name the initial state, the action, the state after the action, the focus position, the visual and programmatic change, and the path back or for correction. An error is designed together with its removal: after correction the previous message and the erroneous state are no longer presented as current, the correct data is retained, and the successful result stays discoverable. Practical routes for a button, a form, a modal dialog, tabs, a disclosure, and a loading state are given in the catalogue "Accessible components: six base cards".
Key design constraints:
- meaning is not conveyed by colour alone: WCAG 1.4.1;
- contrast of normal text is at least 4.5:1, of large text at least 3:1: WCAG 1.4.3;
- important graphical objects and component states have a contrast of at least 3:1: WCAG 1.4.11;
- text is enlarged to 200% without loss of content or function: WCAG 1.4.4;
- content reflows at a viewport width of 320 CSS pixels without two-dimensional scrolling, except for permitted exceptions: WCAG 1.4.10;
- the focus is visible and not completely hidden by author content: WCAG 2.4.7 and 2.4.11;
- the pointer target size conforms to WCAG 2.5.8, and dragging has a single-pointer alternative per WCAG 2.5.7.
Project proposal. In complex and stressful processes a calm composition is applied: no decorative motion by default, no artificial scarcity, no pressing timers, and no competing calls to action. The user can hide secondary content, stop motion, and return to an interrupted task. This is a project application of COGA, not a separate WCAG success criterion.
Stage 4. Content, documents, and media
A page has the correct language per WCAG 3.1.1, and passages in another language are marked per 3.1.2. Headings reflect the structure, lists are lists, and tables have determinable header and cell relationships in line with WCAG 1.3.1. Meaningful images receive an equivalent text alternative, and decorative ones create no noise: WCAG 1.1.1.
Project proposal. Authors use common and literal words, short sentences, and separate instructions, expand abbreviations, explain the consequences of actions, and give a short summary of long material. These decisions are based on the COGA Design Guide and are checked with people for whom comprehension and memory are a source of barriers.
Project proposal. For documents of critical processes, the list of which is fixed in the requirements passport, the team organises an independent expert review of text comprehensibility. Minimum conditions for such a review: the expert is not the author of the text under review, a representative of the target group takes part in the assessment, and the outcome is recorded in a protocol listing the reworked passages. Model source: the selkotunnus plain language mark procedure of the Finnish plain language centre Selkokeskus.
Project proposal. The comprehensibility check for the text of a critical process is oriented not only to formal features of the text (sentence length, number of syllables), but also to a direct success criterion for the reader: they found the needed information, understood it correctly, and were able to apply it to complete the task. Formal readability metrics are used as a guide for the author while writing, not as independent evidence of comprehensibility at acceptance. The result of such a check is documented as a finding with the user's task and the specific question or place in the text where the reader stumbled. The model of the criterion is described in the Australian Human Rights Commission account of the AS ISO 24495.1:2024 plain language national standard (AHRC, "Standards and guidelines for digital accessibility"); the direct ISO 24495-1 standard page on iso.org did not open at the time of the edit, so this account, and not the text of the standard itself, is the primary source.
Recorded video has accurate synchronised captions per WCAG 1.2.2. Meaningful visual information is conveyed by audio description or a media alternative in line with the applicable criteria 1.2.3 and 1.2.5. Live streams are accompanied by captions for level AA per 1.2.4. Autoplay of sound and motion are controlled per 1.4.2 and 2.2.2.
A downloadable document is treated as part of the user path. It must have a meaningful name, a language, a title, a reading order, semantic headings, lists and tables, text alternatives, accessible form fields, and sufficient contrast. If the format or a specific document cannot be made accessible, an equivalent accessible version is provided, directly reachable from the same page. This does not release the page and the mandatory process from the WCAG requirements for the full page and the full process.
Stage 5. Implementation
The developer prefers native HTML elements and adds ARIA only for semantics that the chosen technology lacks. All functions are available through the keyboard interface per WCAG 2.1.1, the focus does not get trapped per 2.1.2, and the focus order preserves meaning per 2.4.3. A visible label is part of the accessible name of the element per 2.5.3.
Programmatically determinable name, role, value, and state are provided per WCAG 4.1.2. Loading, error, addition, and completion messages are conveyed to assistive technologies without mandatory movement of the focus per 4.1.3. The support technology baseline records the versions of browsers, devices, and assistive technologies on which compatibility has been verified. WCAG requires reliance on accessibility-supported ways of using technologies, but it does not set a universal list of products and versions: the definition of accessibility supported.
Forms contain permanent visible labels and the necessary instructions per WCAG 3.3.2. An error is identified by text per 3.3.1, and a known means of correction is suggested per 3.3.3. For legally significant, financial, and data-changing operations, a check, confirmation, or reversal applies per 3.3.4. Data already entered is not requested again without a provided exception per 3.3.7. Authentication must not require a cognitive test without an alternative or a help mechanism per 3.3.8.
Stage 6. Verification and acceptance
Acceptance includes three independent layers:
- automated checks for machine-detectable features;
- manual checks of all applicable success criteria, states, and complete processes;
- user checks of critical scenarios with people with different needs.
An automated result is not a certificate and does not prove accessibility. The rules for automated and manual checking must state the scope of applicability, the expectation, and the procedure. The ACT Rules Format 1.1, published as a W3C Recommendation on 5 February 2026, can be used to describe them.
Each defect contains the exact page and state, preconditions, steps, expected and actual result, source of the requirement, configuration, evidence, and the impact on the user. Criticality is determined by the loss of function and the impact, separately from level A, AA, or AAA.
For each run the product version and build, the OS version, the browser and its version, the assistive technology and its version, the language, the viewport size, the zoom level, the input method, the system motion and contrast settings, the date, the result, and a link to the evidence are recorded. A product name without a version is not enough.
The manual route with an assistive technology runs the task from the agreed starting point to the confirmed result, including loading, empty result, error, correction, success, closing, and return, if they are part of the process. Checking a single element in isolation does not replace an end-to-end route. Observations are recorded through the accessible name, role, state, value, and actions, the focus position, and the actual result. The verbatim phrase of a synthesiser may be attached as diagnostic evidence of a specific configuration, but it cannot be set as a universal reference for all programs and versions. Working sequences are collected in the manual check guidance.
The result of the expert route, the record of the automated check, and the testimony of a user research participant are kept as different types of evidence. An expert using a screen reader is not a research participant merely because of the tool chosen; user testimony is an observation of a person for whom that configuration is familiar, carried out per section 7.
Authorised scenarios are performed only on an approved test stand or with an explicitly issued test role. The fixture contains the role and rights, anonymised test data, a way to obtain the initial state without passing a password to the researcher, the session lifetime, MFA or CAPTCHA conditions, the reset procedure, and the owner of the cleanup. Recordings and screenshots mask personal and payment data. After the check, temporary accounts and data are revoked or cleaned up by the responsible owner.
Stage 7. Release and support
A release is accepted if the scope and the version are recorded, the critical processes have been checked in full, there are no open blocking defects, the remaining risks have an owner and a deadline, and support is ready to receive a request through an accessible means. A conformance claim is made only within the scope that was really checked and only when all the WCAG conformance claim requirements are met. A sampled audit usually does not allow a claim of conformance for the whole site.
Accessibility statement
Project proposal. The site owner publishes a clear accessibility statement as a permanent point of contact with users and a report on the known state of the product. W3C WAI recommends naming the applicable standard, giving a contact point for reporting problems, describing known limitations, the measures taken to ensure accessibility, and the verified environments. A link with a stable name, "Accessibility" or "Accessibility statement", is placed in the footer of every page and, where needed, in the help section.
The statement contains:
- the exact scope: domains, applications, sections, versions, and exclusions;
- the applicable standard and the target level, without extension to an unchecked scope;
- the real grounds for the conclusion: the type of check, the pages and processes covered, the verified configurations, and the date of the last check;
- known barriers in language a user can understand, their impact, an accessible workaround, the owner of the fix, and the date of the next review;
- a clear accessible contact point for reporting a new barrier and for requesting information in another format;
- the publication date, the owner of the statement, and the planned review date.
The statement is updated after a substantial change to the product, a new check, or a change in a known barrier. The GOV.UK statement serves as an example of an honest structure: it limits the scope, lists specific problems, explains how to request another format, and gives check and review dates. The applicable duty to publish a statement is established separately for the product; the example informs its structure.
An accessibility statement is not a certificate and does not amount to confirmation of full WCAG conformance. The absence of errors in an automated check does not confirm complete processes, manual scenarios, and the behaviour of real assistive technologies. If the evidence is insufficient for a conformance claim, the verified facts, the known limitations, and the improvement plan are published without a statement of full conformance.
After the release the team monitors requests, repeats the check of changed components and related processes, and updates the technology baseline on schedule. Any change to the design system, authentication, the editor, the payment process, or the media player triggers a targeted accessibility regression.
The author or editor of the material is responsible for fixing a barrier in the content and for re-checking the published version. The support service records the product version, the role, the task, the way of interaction, the state before and after the action, the result obtained, and an accessible way to make contact; it then links the request to the defect and the owner. Support does not require a person to reproduce the verbatim phrase of an assistive technology if the purpose of the element, the action, and the observable result already allow the barrier to be reproduced.
Project proposal. The support service confirms receipt of a report about an accessibility barrier and gives a substantive response no later than two weeks from the report; if more information must be collected or an alternative format prepared, the deadline is extended by another two weeks with the requester notified of the reason and the new deadline. If the requested accessible format or workaround cannot be provided, the requester receives a short written explanation of the refusal. These deadlines are an internal norm specifically for reports about accessibility barriers; they do not replace the response deadlines for requests established by applicable legislation, including the legislation on citizens' appeals in the jurisdictions where it applies. Model source: Laki digitaalisten palvelujen tarjoamisesta 306/2019, Section 10.
The fallback channel for reporting a barrier, which does not depend on the potentially problematic element of the main channel, is recorded in a separate field of template 9.5, "Support card", and stays available even when the main channel is technically unavailable to a person with the same barrier. Model source, in an account of an official standard: Digital Transformation Agency (Australia), Digital Service Standard v2.0, criterion 3 "Leave no one behind", as reported by Intopia.
Project proposal. When a product is handed over to another team for maintenance, or when a contractor changes, the new performer receives the register of known accessibility barriers with their status (resolved, in progress, risk accepted), the owner, and the deadline, as a mandatory part of the handover package, alongside access rights and infrastructure documentation. For each risk with the status "risk accepted", the date of the review of the decision is stated as well. Model source: AHRC, "How to provide equal access to digital goods and services", section "Accessibility and risk management".
Stage 8. Design system and reuse management
The design system keeps accessibility requirements next to the component rather than in a separate checklist that the developer does not see. For each component the allowed roles and HTML elements, the states, the accessible names, the keyboard model, the focus rules, the contrast, the target size, the messages, and the limits of application are published. The demonstration page includes not only the normal state but also long text, an error, loading, the disabled state, scaling, and a narrow screen.
A change to a component is treated as a change to all of its consumers. The library owner notifies the teams about incompatible changes and provides a migration. A product team does not modify a component locally without registering the difference, otherwise the library evidence stops describing the real behaviour.
Project proposal. If the same visual component or interaction pattern is used at the same time on the site and in the mobile application of the same product, the component passport (template 9.3) is kept as a single document for both implementations, with separate fields where the implementation really differs for each platform. A single component passport cannot be used as evidence of conformance for the mobile application: the mandatory application profile is still determined separately, and only the register of requirements for the shared component is kept unified. Model source: the Digital Inclusion Standard package of the Australian Digital Transformation Agency, applied to websites and applications alike.
Project proposal. A shared component is admitted to the library only after a manual check of the keyboard, focus, name, role, value, and dynamic messages in at least two substantially different configurations. For complex widgets the ARIA APG patterns are used, together with a separate check of actual compatibility. An APG example is treated as a starting point, not as ready evidence of conformance. The component passport (template 9.3, field "Verified configurations") names the specific assistive technologies on which the component was actually checked, rather than a general wording such as "checked with a screen reader", and is updated on every significant change of the component together with the version of the technology baseline recorded at stage 5. The list records only the fact of the check, is not a recommendation to procure a particular assistive technology, and does not replace the needs profile of the target group. Model source: GOV.UK Design System, Accessibility strategy.
Stage 9. Third-party components and procurement
The site owner is responsible for the user process as a whole, even if an individual step is provided by an external supplier. Before procuring or embedding a widget, the supplier provides a description of keyboard operation, the supported assistive technologies, the known limitations, the remediation process, and an accessible support channel. The team checks the component on its own page, because styles, the container, focus, and integration code are able to change its behaviour.
Project proposal. If a supplier or contractor maintains a site under a contract and part of its functions falls outside the subject of that contract, the mandatory accessibility profile applies exactly to those screens and functions that relate to the performance of that contract, and not to the supplier's entire digital product. The customer fixes the boundary of the perimeter in the technical specification with a named list of screens, pages, or APIs, rather than with a general wording such as "the whole service". Such a boundary narrows the contractor's zone of responsibility for specific elements, but it does not release the site owner from responsibility for the accessibility of the user process as a whole, nor for an accessible alternative where part of the process stays outside the contractor's perimeter. Model source: TTJA annual report on digital accessibility of the public sector of Estonia, section 2.2.3.
Project proposal. The procurement documentation for a third-party component, widget, or ready-made solution is accompanied by the supplier conformance declaration against WCAG success criteria (the international analogue: a VPAT-format accessibility conformance report): a list of the applicable success criteria of the target profile, the status of each of them (supports, partially supports, does not support, not applicable), a short explanation, and the tested configuration. The presence of such a declaration is a qualification condition of the procurement and a mandatory annex to the contract, not a separate point in the scoring of bids. If the supplier is small and does not prepare a declaration itself, the customer or their accessibility specialist may fill it in after their own quick check of the component. Model source: AHRC, "How to provide equal access to digital goods and services", the section on procurement.
If a third-party component blocks a critical process, a mention of the supplier in the risk register is not enough. An accessible alternative, a replacement of the component, or a prohibition of the release is required. When conformance is claimed, the rules on the full page and on non-interference are taken into account, and not only the authorship zone of the team.
Stage 10. Editorial control
A page template may comply with the requirements, yet editorial material creates new barriers every day. Therefore the publishing system checks the presence of a page title, the heading structure, image alternatives, meaningful link text, the language, and captions. A warning explains the correction, and a bypass of a mandatory check is registered with its reason.
Short instructions are created for authors by material type: news, a long guide, a table, a chart, a form, a video, and a document. The WAI Tutorials on images, tables, structure, and forms serve as a reference point. Before publishing important material the author checks the linear order, magnification, links, captions, and the accessible version of an attachment. A periodic sample of published content reveals systemic errors of guidance and templates.
6. Special acceptance cases
A dynamic window is checked from the moment it opens until the return to the original context: accessible name, announcement, movement of focus inside, containment of focus while modal, closing, return of focus, and the absence of access to the background. A table is checked both as a visual object and as a sequence of headers and cells. An editor is checked for producing an accessible result: heading structure, alternatives, language, lists, tables, and preservation of semantics on export.
For a form, the hint before input, the format, the required state, autofill, the error, the error summary, the retention of correct data, repeated entry, confirmation, and cancellation are checked separately. The detailed grounds and examples are collected in the materials Understanding 3.3.2, Understanding 3.3.7, and Understanding 3.3.8.
Video is checked for the accuracy, synchronisation, and completeness of captions, not only for the presence of a track. Audio description must convey meaningful visual information that is missing from the main audio track. For the player, the accessible buttons, the keyboard, the focus, the volume control, the track selection, and the absence of uncontrolled autoplay are checked. Practical explanations are given in the WAI Audio and Video Media section.
7. Checks with users
The composition of participants is determined by the risks of the scenario. For a site with documents and forms, people are needed who use a screen reader, magnification, a keyboard or alternative input, captions, a simplified presentation, and memory or attention support strategies. One participant does not represent the whole group. Participants perform real tasks in their familiar configuration, and the researcher does not suggest an interface solution before the barrier is recorded.
The protocol includes informed consent, an accessible format for the materials, the possibility of a break, a convenient communication channel, and compensation for participation on agreed terms. Recording of audio, video, or the screen, the composition of the data collected, the retention period, deletion, and the right to withdraw consent are agreed separately. The team prepares in advance the participant's familiar technology, support, a safe stop, and the absence of a real payment or data disclosure. The moderator ends the task at any sign of discomfort, a risk of data loss, or a request from the participant, offers help, and conducts the debrief. After the session the participant keeps an accessible support contact. What is observed is the achievement of the result, errors, returns, unexpected help, understanding of the consequences, and subjective load. A successful completion and the reason why a user refused to continue are equally important.
Project proposal. The cycle of adapting plain-language text includes identifying the needs and the composition of the team, adapting, an expert assessment with the participation of a representative of the target group, reworking, and an additional reading by other people. This cycle uses the content of the published annex to Order No. 647n (Russian-language source) as a project recommendation. The details in the header of the accessible DOCX annex are not filled in, the order is not yet in force, and the number of participants in such a protocol is not considered a sufficient research sample.
Cognitive scenarios, consent, support, stopping, and the observation form are moved to the annex "Plain language and cognitive accessibility protocol". Its results complement the WCAG check and do not by themselves change the WCAG conformance level.
Project proposal. For an early prototype, at least one person is involved for each substantially different interaction model present in the critical scenario. For the release decision the composition is extended until new sessions stop revealing new classes of blocking barriers. This is a planning rule, not a statistical norm and not proof of representativeness.
8. Release acceptance criteria
The decision is taken by the product owner on the conclusion of the accessibility and testing specialists.
- Acceptance: the target profile is met in the declared scope; the critical processes have been passed; the evidence is reproducible.
- Conditional acceptance: only non-critical deviations from project proposals; the owner, the deadline, and the way of informing users are defined. Conditional acceptance does not apply to an unimplemented success criterion if the release is going to claim conformance to WCAG.
- Release prohibition: there is a barrier that prevents the target group from starting, continuing, or completing a critical process, creates a risk of data or security loss, or violates a criterion that is mandatory for the project without an accessible alternative.
No single accessibility percentage is calculated. It hides the difference between a decorative non-conformance and the impossibility of submitting an application. The decision relies on criteria, processes, groups of needs, severity, and evidence.
9. Templates
Templates 9.1-9.5 are used, when the document package is formatted, as annexes No. 1-5 to the methodology.
9.1. Requirements passport
Identifier:
Title:
Status: WCAG / contractual / Project proposal
Profile: legally applicable / voluntary target
Jurisdiction and scope of the requirement:
Source and direct link:
Scope of application:
User need:
Testable condition:
Expected result:
Verification methods:
Pages, states, components:
Owner:
Control stage:
Related risks and exceptions:
9.2. User scenario
User goal:
Starting point and preconditions:
Device and interaction method:
Steps and branches, including erroneous data:
Expected confirmed result:
How the user understands progress and the consequences:
Possibility of cancellation, return, and recovery:
WCAG requirements:
Additional COGA proposals:
Success criteria of the user check:
9.3. Design component passport
Component and version:
Purpose:
Visible states:
Accessible name, role, value, description:
Keyboard model and focus order:
Behaviour with a screen reader and with magnification:
Contrast and target size:
Behaviour on reflow and when the spacing of the text changes:
Errors, statuses, loading:
Support for reduced motion and personalisation:
Examples of acceptable and unacceptable use:
Verified configurations:
Related criteria and evidence:
9.4. Release acceptance sheet
Product, version, date:
Scope of acceptance and exclusions:
Legally applicable profile, jurisdiction, and its basis:
Voluntary target profile:
Target WCAG profile:
Critical processes and results:
Manual check:
Automated check:
User check:
Open defects by severity:
Risks of third-party components:
Accessible support channels:
Decision: acceptance / conditional acceptance / prohibition
Responsible for the decision:
Date of the next check:
9.5. Support card
Channel and working hours:
Accessible ways to make contact:
Fallback channel for reporting a barrier (without using the problematic element):
What information to ask the user for:
Deadline for the first response:
Route for a blocking request:
Temporary accessible workaround:
Related defect and owner:
Date of the check of the fix with a user:
10. Main sources
The sources are listed in one numbered list. Items 1-7 and 17-21 are international or internationally used materials; items 8-10 are Russian national materials; items 11-16 are national materials of Australia, Singapore, Finland, and Estonia. National materials are identified by origin and cited as examples. Their legal or contractual applicability and the scope of any voluntary adoption are recorded for each product.
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Recommendation of 12 December 2024.
- W3C, WCAG 2.2 Conformance Requirements.
- W3C, Making Content Usable for People with Cognitive and Learning Disabilities, Working Group Note of 29 April 2021.
- W3C WAI, Involving Users in Evaluating Web Accessibility.
- W3C, Accessibility Conformance Testing Rules Format 1.1, Recommendation of 5 February 2026.
- W3C WAI, Tutorials.
- W3C WAI, ARIA Authoring Practices Guide.
- Government of the Russian Federation, Resolution No. 102 of 07.02.2026 (Russian-language source), effective from 01.03.2026 within the scope established by it.
- Rosstandart, official cards for GOST R 52872-2019, GOST R 70176-2022, and GOST R ISO 21801-1-2022 (Russian-language sources).
- Ministry of Labour of the Russian Federation, Order No. 647n of 14.11.2025 (Russian-language source), takes effect on 01.09.2027.
- Australian Human Rights Commission, "Chapter 3 | Standards and guidelines for digital accessibility" (2025), as regards the AS ISO 24495.1:2024 plain language national standard.
- Australian Human Rights Commission, "Chapter 2 | How to provide equal access to digital goods and services" (May 2025), as regards the supplier conformance declaration in procurement and the register of barriers at handover.
- GovTech Singapore, Digital Service Standards Control Catalog and Accessibility playbook.
- Tarbijakaitse ja Tehnilise Järelevalve Amet (Estonia), annual report on the digital accessibility of the public sector for 2024.
- Selkokeskus (Finland), procedure for awarding the selkotunnus plain language mark.
- Finland, Laki digitaalisten palvelujen tarjoamisesta 306/2019, Section 10.
- GOV.UK Design System, "Accessibility strategy".
- Digital Transformation Agency (Australia), Digital Inclusion Standard.
- Intopia, Andrew Arch, "Australia's Digital Service Standard gets an upgrade" (15 February 2024), an account of the official Digital Service Standard v2.0 of the Digital Transformation Agency, criterion 3 "Leave no one behind".
- W3C, Accessibility Maturity Model, Group Note of 4 November 2025.
- W3C WAI, Accessibility Roles and Responsibilities Mapping, draft resource on the distribution of roles and responsibilities, edition of 24 July 2025.
Links and source statuses were checked on the date of this version of the document. They should be checked again when the methodology is revised.
