Why protocols are needed and how they relate to the methodologies
WCAG 2.2 states requirements, but does not say exactly how to check them: two assessors reading the same criterion may reach different conclusions. The protocols close that gap. For each of the 55 criteria at levels A and AA, the same reproducible procedure is described here: what the criterion applies to, what must be prepared, which steps to perform, what counts as a pass and what counts as a failure, when to record "not applicable" or "not checked", and what evidence must be retained. This is precisely what makes the results of different assessors comparable.
Where the protocols sit among the project documents:
- Accessibility Assessment Methodology for Digital Resources answers the question "what and in what scope to check": how to describe the scope, how to collect a sample of pages, which configurations and assistive technologies to use, how to maintain evidence, how to determine the severity of defects, and how to phrase the conclusion. Its section A.7 provides a basic route of 34 control checks for common risks of websites and web applications. When the assessor reaches manual testing against the standard (section 4.2), they open this document: the protocols provide full traceability across all 55 criteria, not only the frequent ones.
- Methodology for Developing Accessible Websites uses the protocols from the other side: requirements in the technical specification and acceptance scenarios are traced to criterion cards, so the customer and the contractor verify the result by the same procedure, and acceptance disputes are resolved against pre-agreed conditions.
- Automated testing relies on the same cards. Each criterion is marked by degree of automatability: software tools demonstrate violations for only part of the conditions, no criterion is fully confirmed by an automated tool, therefore the "pass" status is set by a human following the protocol.
How to read a card. The heading contains the criterion number, the name, and the level (A or AA). Then come eight fields: applicability; preconditions and fixture (what to prepare); steps and parameters; pass and failure conditions; when to record "not applicable" or "not checked"; minimum evidence; normative reference to the criterion text; the project boundary that separates the standard requirement from a stricter author rule. Checking one sampling unit against one criterion ends with one row in the results matrix (section 3) carrying one of four statuses and a link to the evidence.
1. Purpose and result rules
The register contains all 55 current success criteria at levels A and AA of WCAG 2.2. The removed criterion 4.1.1 is not included. Criteria 2.2.6 and 2.5.6 are at level AAA and are likewise not included. This protocol supplements the assessment methodology; its 34 items form the basic route, while this register sets out full A/AA traceability.
Each card applies to every relevant sampling unit, state, and full process. Statuses:
- pass: the normative condition is met in all checked applicable cases of the card;
- failure: at least one proven applicable case has been found that does not meet the condition;
- NA: the content or function to which the criterion relates is absent; the reason is mandatory;
- not checked: applicability or result has not been established, including because of an unreachable state or a missing configuration. This status is not counted as a pass.
Minimum evidence always includes the unit ID, a URL or a way to open the state, the version/build, the exact steps and data, the actual result, the status, the date, and the assessor. For visual measurement, the original colours, sizes, and viewport are retained; for keyboard testing, the key and focus sequence; for assistive technology, its exact version and the observed output; for code, a DOM fragment or a program structure. A screenshot by itself does not prove dynamics or screen reader output.
The "project boundary" field separates the normative WCAG condition from a stricter author rule. An author rule applies only after being included in a contractual or internal profile, and is marked as a Project proposal.
Abbreviations
- WCAG - Web Content Accessibility Guidelines, the accessibility guidance of the W3C consortium for web content; the protocols use version WCAG 2.2.
- Levels A, AA, AAA - three steps of WCAG conformance in increasing order of strictness of requirements; the protocols cover levels A and AA.
- NA - "not applicable": the content or function to which the criterion relates is absent on the unit under test.
- AT - assistive technologies: programs and devices used by a person with a disability to work with the site (a screen reader, magnification, and similar means).
- DOM - Document Object Model, the program tree of page elements that assistive technologies and test code see.
- CSS - Cascading Style Sheets, the language for describing page presentation; in the protocols it is used for units of measurement (CSS pixel) and viewport parameters.
- HTML - HyperText Markup Language, the markup language used to describe the structure of a page.
- CAPTCHA - a test that distinguishes a human from an automated program; in the protocols the presence of an accessible alternative to such a test is checked.
- MFA - multi-factor authentication: sign-in with additional confirmation in addition to a password.
- URL - the address of a page or state in the browser, a mandatory part of the minimum evidence.
2. Protocols
1.1.1 Non-text content, A
- Applicability: images, icons, charts, CAPTCHAs, image buttons, maps, and other non-text content.
- Preconditions/fixture: open all states; determine the purpose of each object and the presence of a text alternative in the accessibility tree.
- Steps and parameters: disable images or inspect the accessible name; match the alternative to the same purpose/information; check decorative, sensory, test, and CAPTCHA objects separately: for a CAPTCHA, make sure that a text description is given that defines and describes its purpose, and that at least one alternative CAPTCHA form is available on the page with a different output mode for another kind of sensory perception (for example, audio instead of distorted text).
- Pass/failure: passes if the equivalent fulfils the purpose and the special cases of the criterion are observed (for a CAPTCHA, a text description of the purpose and an alternative modality for another kind of perception); fails if significant information is lost, the name is wrong, decoration is announced as content, or a CAPTCHA lacks a text description of its purpose or an alternative modality.
- NA/not checked: NA only when there is no non-text content at all; not checked if the purpose of the object has not been established.
- Minimum evidence: the object, the context, the DOM/accessible name, and an explanation of equivalence.
- Normative reference: WCAG 1.1.1. Project boundary: the quality of a long description for target users is an additional check.
1.2.1 Audio-only and video-only (prerecorded), A
- Applicability: prerecorded audio without video, and prerecorded video without an audio track, except for a media alternative for text.
- Preconditions/fixture: the complete media material and access to all tracks/alternatives.
- Steps and parameters: watch or listen to the material in full; compare the prerecorded audio with the text alternative, and the silent video with the text or audio track conveying equivalent information.
- Pass/failure: passes with an equivalent alternative; fails if a significant sequence, speech, sounds, or visual events are omitted.
- NA/not checked: NA for synchronised audio-video and for a media alternative for text; not checked if the complete file is not available.
- Minimum evidence: timecodes, a link to the alternative, and a list of the information conveyed/omitted.
- Normative reference: WCAG 1.2.1. Project boundary: literary editing of the transcript beyond equivalence is additional.
1.2.2 Captions (prerecorded), A
- Applicability: prerecorded synchronised media with auditory information, except for a media alternative for text.
- Preconditions/fixture: the full clip, the captions track enabled, the ability to hear the original for comparison.
- Steps and parameters: play in full; by timecodes compare speech, speakers, and significant sounds with the captions; check synchronisation and that the captions can be turned on.
- Pass/failure: passes if all prerecorded auditory information is presented in the captions; fails if the track is absent or there are meaningful omissions.
- NA/not checked: NA for material without sound or for a media alternative for text; not checked without access to the audio/the full clip.
- Minimum evidence: URL, track, timecodes, and the exact omissions/distortions.
- Normative reference: WCAG 1.2.2. Project boundary: style and reading speed requirements beyond equivalence are additional.
1.2.3 Audio description or media alternative (prerecorded), A
- Applicability: prerecorded synchronised video, except for a media alternative for text.
- Preconditions/fixture: the full clip, the main track, the audio description and/or the media alternative.
- Steps and parameters: identify the significant visual information that is not present in the audio; check whether the audio description or the sequential media alternative conveys it.
- Pass/failure: passes if at least one permitted equivalent is present; fails if significant visual information is unavailable.
- NA/not checked: NA for a media alternative for text and for video with no untransmitted visual information; not checked without the full material.
- Minimum evidence: timecodes, a description of the visual event, and the corresponding fragment of the alternative.
- Normative reference: WCAG 1.2.3. Project boundary: at level AA the separate 1.2.5 requires audio description and is not replaced by a text media alternative.
1.2.4 Captions (live), AA
- Applicability: live synchronised media with sound.
- Preconditions/fixture: a permitted test broadcast or a real broadcast, a captions track, and a sound observer.
- Steps and parameters: record the boundaries of the event and the observed intervals; match speech and significant sounds against the live captions, including speaker changes. To reach a conclusion about an event, coverage of its whole interval is required. Checking individual fragments gives only a limited observation.
- Pass/failure: passes in the explicitly stated area if there are captions for all significant auditory information; the absence of required information is a failure. Success on individual fragments does not yield a pass for the whole broadcast; the uncovered remainder is recorded as not checked.
- NA/not checked: NA where there are no live broadcasts; not checked if the broadcast was not available and no test broadcast was conducted.
- Minimum evidence: date/broadcast, observation intervals, a recording with consent or a log of timecodes and omissions.
- Normative reference: WCAG 1.2.4. Project boundary: a numeric delay or accuracy norm is not introduced without an agreed profile.
1.2.5 Audio description (prerecorded), AA
- Applicability: prerecorded synchronised video, except for a media alternative for text.
- Preconditions/fixture: the full clip and an available audio description track.
- Steps and parameters: identify the significant visual events not conveyed by the main audio; enable the audio description and check that they are conveyed during appropriate pauses or in an extended version.
- Pass/failure: passes if the audio description covers all significant visual information; fails if the track is absent or there are meaningful omissions.
- NA/not checked: NA if all significant visual information is already present in the main track; not checked without the full clip.
- Minimum evidence: timecodes, the visual information, and the text/audio of the audio description.
- Normative reference: WCAG 1.2.5. Project boundary: a single text media alternative does not satisfy this AA criterion.
1.3.1 Info and relationships, A
- Applicability: visual structure, headings, lists, tables, captions, field groups, regions, and states.
- Preconditions/fixture: content in all states, the DOM, and the accessibility tree.
- Steps and parameters: match the structure/relationships conveyed visually against the HTML and program semantics; read linearly; check table header relationships, labels, fieldset/legend, and groups.
- Pass/failure: passes if information and relationships are programmatically determinable or available in text; fails if they are conveyed by presentation alone.
- NA/not checked: NA only where there are no structural/visual relationships; not checked if the program structure is unavailable.
- Minimum evidence: a visual fragment, the DOM/tree, and the specific lost relationship.
- Normative reference: WCAG 1.3.1. Project boundary: a preference for a specific HTML structure beyond the result is an author rule.
1.3.2 Meaningful sequence, A
- Applicability: content whose presentation order affects meaning.
- Preconditions/fixture: a page with styles disabled or in linear presentation, and the accessibility tree.
- Steps and parameters: determine the meaningful visual order; compare it with the DOM/reading order after linearisation and in a screen reader.
- Pass/failure: passes if the programmatically determinable order preserves meaning; fails if meaning or instructions change.
- NA/not checked: NA if the order does not affect meaning; not checked without access to the structure.
- Minimum evidence: the expected and actual sequences with a DOM fragment/output.
- Normative reference: WCAG 1.3.2. Project boundary: matching the DOM to the visual order is not required where the variants are equivalent.
1.3.3 Sensory characteristics, A
- Applicability: instructions that depend on shape, colour, size, position, orientation, or sound.
- Preconditions/fixture: all instructions and the corresponding elements.
- Steps and parameters: find sensory references; try to identify the object without perceiving the named characteristic; check for a text name or another non-sensory identifier.
- Pass/failure: passes if the instructions do not rely solely on a sensory characteristic; fails on a single reference such as "the button on the right".
- NA/not checked: NA where there are no such instructions; not checked if the related object is unavailable.
- Minimum evidence: the exact instruction, the candidate elements, and the missing identifier.
- Normative reference: WCAG 1.3.3. Project boundary: a ban on any sensory words beyond the "not only" requirement is additional.
1.3.4 Orientation, AA
- Applicability: web content on devices that support both portrait and landscape orientation.
- Preconditions/fixture: a mobile viewport/device, both orientations, without a system-level user lock.
- Steps and parameters: open each significant state in portrait and landscape; perform the function and check that there is no author-imposed lock.
- Pass/failure: passes if it works in both orientations or where a specific orientation is essential; fails with unjustified locking.
- NA/not checked: NA for an environment with no concept of orientation or where essentiality is proven; not checked without a suitable device/emulation.
- Minimum evidence: the device, the viewport, both orientations, and an explanation of the exception if it is applied.
- Normative reference: WCAG 1.3.4. Project boundary: optimising the layout in both orientations beyond preserving the function is additional.
1.3.5 Identify input purpose, AA
- Applicability: fields collecting information about the user with purposes from the Input Purposes for User Interface Components list, implemented by the supporting technology.
- Preconditions/fixture: a form with a test role, the DOM, and the autofill mechanism.
- Steps and parameters: match the meaning of each applicable field to the established token; check the program attribute and the actual recognition by the user agent.
- Pass/failure: passes if the purpose is programmatically determinable; fails if the value is missing, wrong, or ambiguous.
- NA/not checked: NA for fields outside the list or not relating to the user; not checked without access to the form/DOM.
- Minimum evidence: the field, the expected purpose, the actual attribute, and the recognition result.
- Normative reference: WCAG 1.3.5. Project boundary: mandatory autofill for every field is a separate rule.
1.4.1 Use of color, A
- Applicability: information, state, action, or distinction expressed by colour.
- Preconditions/fixture: all states, including errors, selection, charts, and links within text.
- Steps and parameters: view in greyscale/without colour differentiation; check for text, form, pattern, caption, or another additional cue.
- Pass/failure: passes if colour is not the only visual means; fails if the meaning disappears without colour.
- NA/not checked: NA without colour coding; not checked if a state is unavailable.
- Minimum evidence: the original state and the colourless rendering with the lost/retained meaning.
- Normative reference: WCAG 1.4.1. Project boundary: a specific palette or a mandatory icon beyond a second cue is additional.
1.4.2 Audio control, A
- Applicability: audio that plays automatically for more than 3 seconds.
- Preconditions/fixture: a clean session, sound enabled, default settings.
- Steps and parameters: load the page with no action; measure the duration; find a pause/stop independent of the system master volume, or volume control.
- Pass/failure: passes if the auto-audio lasts up to 3 seconds or the required control is available; fails with longer uncontrolled sound.
- NA/not checked: NA without auto-audio over 3 seconds; not checked without audio output.
- Minimum evidence: start time/duration and the control actions.
- Normative reference: WCAG 1.4.2. Project boundary: a full ban on autoplay is a stricter rule.
1.4.3 Contrast (minimum), AA
- Applicability: text and images of text, except for large text (from 18 points or from 14 points bold, or an equivalent size for Chinese/Japanese/Korean script) with a 3:1 threshold, text of inactive user interface components, purely decorative or invisible text, text over an image with significant other visual content, and text that is part of a logo or brand name.
- Preconditions/fixture: computed text/background colours in all states, the font size, and the font weight.
- Steps and parameters: measure colour pairs taking the actual background into account; the threshold is 4.5:1 for normal text; 3:1 for large text as defined by WCAG (from 18 points or from 14 points bold); separately assess the applicability of the exceptions: inactive component, pure decoration, invisible text, text over an image with significant other visual content, logo or brand name.
- Pass/failure: passes when the threshold is reached or an applicable exception holds; fails with a lower ratio.
- NA/not checked: NA only where there is no applicable text; not checked with an indeterminate dynamic background.
- Minimum evidence: the colours, the ratio, the text size/weight, the state, and the exception applied.
- Normative reference: WCAG 1.4.3. Project boundary: higher contrast may be a target setting, but it is not part of this AA criterion.
1.4.4 Resize text, AA
- Applicability: text, except for captions and images of text.
- Preconditions/fixture: a desktop browser, text/page zoom of 200%, all states.
- Steps and parameters: zoom to 200% without assistive technology; go through the functions, open dialogs and messages; look for clipping, overlapping, and unreachable elements.
- Pass/failure: passes without loss of content and function; fails when there is a loss due to the author implementation.
- NA/not checked: NA only where there is no applicable text; not checked if the user agent does not allow the required zoom.
- Minimum evidence: the browser, the original and 200% views, the lost element, and the function step.
- Normative reference: WCAG 1.4.4. Project boundary: reflow at a narrow width is assessed separately under 1.4.10.
1.4.5 Images of text, AA
- Applicability: images containing text that could have been presented as text.
- Preconditions/fixture: all images and stylised captions, plus a check of the possibility of an equivalent HTML/CSS.
- Steps and parameters: determine whether the image is used for a visual effect; check whether it is user-customisable or essential, including a logo.
- Pass/failure: passes with real text or an applicable exception; fails for an optional image of text.
- NA/not checked: NA without images of text; not checked when essentiality is unknown.
- Minimum evidence: the object, the string it contains, and the decision on the exception.
- Normative reference: WCAG 1.4.5. Project boundary: a ban on logos and essential images of text beyond the criterion is not permissible without a separate profile.
1.4.10 Reflow, AA
- Applicability: ordinary web content, except for parts that require a two-dimensional layout for use.
- Preconditions/fixture: a viewport of 320 CSS px wide for content with vertical scrolling (ordinary pages) or 256 CSS px high for content with horizontal scrolling (for example, vertical writing); 320 CSS px is equivalent to 400% zoom at an original screen width of 1280 CSS px.
- Steps and parameters: open all states, scroll, and perform the functions; check for the absence of simultaneous horizontal and vertical scrolling and of loss.
- Pass/failure: passes with one-dimensional scrolling and no loss, or with an applicable exception; fails where ordinary content requires two-dimensional scrolling.
- NA/not checked: NA only for fully excluded two-dimensional content; not checked without a specified viewport.
- Minimum evidence: the CSS viewport, the zoom, a screenshot/video, and the lost element or the justification for the exception.
- Normative reference: WCAG 1.4.10. Project boundary: a table may be excluded as a section, but the whole page does not thereby become an exception.
1.4.11 Non-text contrast, AA
- Applicability: visual information required to identify components/states and significant graphical objects, except for inactive components and graphics whose specific presentation is essential to conveying information (for example, logos, photographs).
- Preconditions/fixture: all states, computed adjacent colours, and magnification for thin lines.
- Steps and parameters: measure the contrast of required borders, indicators, states, and graphical parts; the threshold is 3:1 against adjacent colours; check the applicability of the exceptions: inactive user interface components and components whose appearance is determined by the user agent and not changed by the author; graphical objects whose specific presentation is essential to the information conveyed (for example, logos, photographs).
- Pass/failure: passes at 3:1 or with an exception; fails if a required cue is below the threshold.
- NA/not checked: NA without applicable visual information; not checked with an indeterminate background.
- Minimum evidence: the colours, the ratio, the element, the state, and why the cue is necessary.
- Normative reference: WCAG 1.4.11. Project boundary: decorative borders do not become mandatory solely because of this criterion.
1.4.12 Text spacing, AA
- Applicability: content in languages/scripts where the specified parameters apply.
- Preconditions/fixture: inject custom styles: line-height 1.5, 2 font sizes after a paragraph, letter-spacing 0.12, word-spacing 0.16.
- Steps and parameters: apply all four values at once; open the states and perform the functions; look for clipping, overlapping, and obscuring.
- Pass/failure: passes without loss of content or function; fails when there is a loss due to author styles.
- NA/not checked: NA only for text whose script the parameters do not apply to; not checked without the possibility to inject styles.
- Minimum evidence: the styles, the browser, before/after, and the specific loss.
- Normative reference: WCAG 1.4.12. Project boundary: the criterion does not require these spacings to be used by default.
1.4.13 Content on hover or focus, AA
- Applicability: additional content that appears on pointer hover or keyboard focus and disappears when they are removed.
- Preconditions/fixture: mouse and keyboard, all tooltips/menus/popovers.
- Steps and parameters: trigger hover and focus; check the possibility of dismissing without moving the focus/pointer, hovering the pointer over the appearing content and holding it until the trigger is removed or the user closes it; take the exceptions into account.
- Pass/failure: passes when dismissible, hoverable, and persistent all hold at the same time where they apply; fails if any condition fails.
- NA/not checked: NA without such author content; not checked without one of the input methods.
- Minimum evidence: the trigger, the key/pointer sequence, and the behaviour under each of the three conditions.
- Normative reference: WCAG 1.4.13. Project boundary: the appearance and animation time of a popover are regulated separately.
2.1.1 Keyboard, A
- Applicability: all functionality of the content.
- Preconditions/fixture: disable the pointer; start from the address bar/beginning of the document; prepare all roles and states.
- Steps and parameters: perform every function with the Tab, Shift+Tab, Enter, Space, arrow keys, and documented commands, without time-dependent movement; check the exception for a function requiring a path-based input.
- Pass/failure: passes if all functions are available through the keyboard interface; fails if a function is unreachable or requires imitating a mouse.
- NA/not checked: NA practically only in the absence of functions; not checked if a state is unreachable.
- Minimum evidence: the function, the starting point, the key sequence, and the point of blockage/success.
- Normative reference: WCAG 2.1.1. Project boundary: specific key combinations are set by the component and do not follow automatically from the criterion.
2.1.2 No keyboard trap, A
- Applicability: all components that take keyboard focus.
- Preconditions/fixture: keyboard, open modal windows, editors, iframes, and media players.
- Steps and parameters: enter the component with Tab/Shift+Tab or a provided key; exit in the standard way; if the method is non-standard, check for available instructions before entering.
- Pass/failure: passes if the focus can be moved out; fails if the user is trapped with no stated method.
- NA/not checked: NA without focusable components; not checked without access to the embedded content.
- Minimum evidence: the entry/exit sequence, the actual focus, and the instructions in the case of a non-standard method.
- Normative reference: WCAG 2.1.2. Project boundary: cyclic focus within a correct modal window is by itself not a trap if the window can be closed.
2.1.4 Character key shortcuts, A
- Applicability: shortcuts triggered by a single printable letter, digit, punctuation mark, or symbol without a modifier.
- Preconditions/fixture: a list of shortcuts and the components where they are active; voice input, if present.
- Steps and parameters: press each key outside and inside the target component; check the possibility of disabling it, remapping it with a modifier, or its being active only when the component has focus.
- Pass/failure: passes with one of the three mechanisms; fails for a global, unmanageable single-character invocation.
- NA/not checked: NA without such shortcuts; not checked without the full list/state.
- Minimum evidence: the key, the area of activity, and the result of disabling/remapping/focus.
- Normative reference: WCAG 2.1.4. Project boundary: a ban on all hotkeys is a stricter rule.
2.2.1 Timing adjustable, A
- Applicability: every time limit set by the content.
- Preconditions/fixture: the known duration, a test session, the data before the timeout, and all warnings.
- Steps and parameters: wait for the limit; check turning it off before it starts, setting it to at least ten times the default, or a warning at least 20 seconds in advance that can be extended by a simple action at least 10 times; check separately the stated exception of real-time, essential, or more than 20 hours.
- Pass/failure: passes with one permitted mechanism or a proven exception; fails with an uncontrolled limit.
- NA/not checked: NA without limits set by the content; not checked if the limit cannot be reproduced.
- Minimum evidence: the actual time, the warning, the extension actions, and the decision on the exception.
- Normative reference: WCAG 2.2.1. Project boundary: preserving entered data after the time has expired is a separate cognitive proposal.
2.2.2 Pause, stop, hide, A
- Applicability: automatically starting moving/blinking/scrolling content lasting longer than 5 seconds in parallel with other content, as well as automatically updating content.
- Preconditions/fixture: a clean load, a stopwatch, all carousels, animations, tickers, and updates.
- Steps and parameters: observe for more than 5 seconds; find the pause/stop/hide; for updates check the control of the frequency; assess the essentiality exception.
- Pass/failure: passes with the required control or essentiality; fails with distracting uncontrolled content.
- NA/not checked: NA without applicable movement/update; not checked if the duration or the control cannot be reproduced.
- Minimum evidence: the type, the time, the parallel content, and the control action.
- Normative reference: WCAG 2.2.2. Project boundary:
prefers-reduced-motionis useful, but by itself it does not replace all the conditions of the criterion.
2.3.1 Three flashes or below threshold, A
- Applicability: blinking content or content that rapidly changes brightness.
- Preconditions/fixture: the complete time segment, and the known sizes and colours of the flashes.
- Steps and parameters: determine the intervals with more than three flashes in any one second; where present, apply a validated analysis of the general and red flash thresholds.
- Pass/failure: passes with no more than three flashes or below both thresholds; fails on exceeding them.
- NA/not checked: NA without flashes; not checked without a reliable analysis of a potentially exceeding segment.
- Minimum evidence: video/frames, the time interval, and the threshold analysis result.
- Normative reference: WCAG 2.3.1. Project boundary: a full ban on flashes is a stricter rule.
2.4.1 Bypass blocks, A
- Applicability: sets of pages with repeated blocks.
- Preconditions/fixture: keyboard/screen reader, at least two pages of the same template.
- Steps and parameters: start from the beginning; use a skip link, regions, headings, or another mechanism; go directly to the main content and check the repetition.
- Pass/failure: passes if an available bypass mechanism is present; fails if the whole repeated block must be traversed each time.
- NA/not checked: NA for a page without repeated blocks/a set; not checked without a second page where repetition is disputed.
- Minimum evidence: the repeated block, the mechanism, the sequence, and the final focus/position.
- Normative reference: WCAG 2.4.1. Project boundary: the specific form of a skip link is not prescribed.
2.4.2 Page title, A
- Applicability: every web page/view for which the browser reports a title.
- Preconditions/fixtures: open the page and the significant SPA routes.
- Steps and parameters: read the programmatic title before and after navigation; compare it with the topic or purpose of the current view.
- Pass/fail: passes with a descriptive title; fails with an empty, generic, incorrect, or outdated title.
- NA/not tested: NA usually does not apply to a web page; not tested when the view is unavailable.
- Minimum evidence: URL/route, actual title, and topic/purpose.
- Normative reference: WCAG 2.4.2. Project boundary: the branding template and the title length are an editorial rule.
2.4.3 Focus Order, A
- Applicability: sequential navigation affects meaning or operation.
- Preconditions/fixtures: keyboard, all dynamic states, and modal dialogs.
- Steps and parameters: move forward/backward through all elements; open/close components; record the order, initial movement, and focus return.
- Pass/fail: passes if the order preserves meaning and operability; fails on an illogical jump, an unreachable element, or a loss of context.
- NA/not tested: NA without sequential navigation; not tested if part of a state is unavailable.
- Minimum evidence: numbered focus sequence and the point of failure.
- Normative reference: WCAG 2.4.3. Project boundary: exact correspondence with the visual order is not required as long as meaning is preserved.
2.4.4 Link Purpose (In Context), A
- Applicability: every link.
- Preconditions/fixtures: visible text, programmatically associated context, and the screen reader link list.
- Steps and parameters: determine the purpose from the link text alone or together with programmatically determinable context; check the exception for ambiguity for users in general.
- Pass/fail: passes when the purpose is determinable; fails with indistinguishable "read more" links without programmatic context.
- NA/not tested: NA without links; not tested when the target context is unavailable.
- Minimum evidence: text, accessible name, context, and target URL/action.
- Normative reference: WCAG 2.4.4. Project boundary: a unique link name without context belongs to AAA 2.4.9, not to this A criterion.
2.4.5 Multiple Ways, AA
- Applicability: searching for a web page within a set, except for a page that is the result or a step of a process.
- Preconditions/fixtures: set map, navigation, search, and list of related pages.
- Steps and parameters: for each substantial page, check at least two ways of finding it, for example navigation and search, a map, or links.
- Pass/fail: passes with two or more ways or the process-step exception; fails with only one way.
- NA/not tested: NA for a standalone page outside a set or a process step; not tested without a set map.
- Minimum evidence: the page and two reproducible paths, or the reason for the exception.
- Normative reference: WCAG 2.4.5. Project boundary: the specific two mechanisms are not prescribed.
2.4.6 Headings and Labels, AA
- Applicability: existing headings and labels of controls.
- Preconditions/fixtures: the page in all states, and the list of headings/labels.
- Steps and parameters: match each heading to the topic of its section, and each label to the purpose of the component; check the distinguishability of functions of the same kind.
- Pass/fail: passes if they describe the topic or purpose; fails with misleading/empty wording.
- NA/not tested: NA without headings and components that need a label; not tested when the purpose is unknown.
- Minimum evidence: text, the associated section/component, and an explanation of the discrepancy.
- Normative reference: WCAG 2.4.6. Project boundary: the criterion does not require adding headings everywhere; structural necessity is checked under 1.3.1.
2.4.7 Focus Visible, AA
- Applicability: any keyboard-operable interface.
- Preconditions/fixtures: keyboard, all focusable elements, and states.
- Steps and parameters: traverse the elements using only the keyboard; at each step visually identify the focus, including custom and built-in components.
- Pass/fail: passes if the operating mode has a visible focus indicator; fails if the current element cannot be seen.
- NA/not tested: NA without keyboard operation is practically inapplicable; not tested when a state is unavailable.
- Minimum evidence: the sequence, the element, and an image of the focus state or of its absence.
- Normative reference: WCAG 2.4.7. Project boundary: contrast is checked separately under the applicable 1.4.11; the enhanced requirements for the size of the indicator and for changes in its contrast belong to AAA 2.4.13 or to an additional profile.
2.4.11 Focus Not Obscured (Minimum), AA
- Applicability: elements that receive keyboard focus.
- Preconditions/fixtures: keyboard, sticky header/footer, banners, dialogs, and all viewports from the matrix.
- Steps and parameters: traverse all elements and check the visibility of the component itself, not only of an external indicator. For user-movable panels, assess the initial position. If the overlapping content was opened by the user, check the ability to reveal the component without moving focus to another element; take the criterion's notes into account.
- Pass/fail: passes if the component is not completely hidden by authored content, taking the criterion's notes into account. Absence of overlap gives a pass. Complete obscuring without an applicable condition from the notes gives a failure.
- NA/not tested: NA only if there are completely no elements that receive keyboard focus; not tested without access to the required state or viewport.
- Minimum evidence: viewport, element, sequence, and an image of the complete obscuring.
- Normative reference: WCAG 2.4.11. Project boundary: the requirement not to obscure the focus even partially belongs to AAA 2.4.12.
2.5.1 Pointer Gestures, A
- Applicability: functions that use multipoint or path-based gestures.
- Preconditions/fixtures: touch/pointer device, and a map of all gestures.
- Steps and parameters: perform a pinch, swipe, path drawing, or multi-finger gesture; find a single-pointer alternative without path dependence; assess essentiality.
- Pass/fail: passes with a single-pointer alternative or with essentiality of the gesture; fails when there is only one complex gesture.
- NA/not tested: NA without such gestures; not tested without a device/state.
- Minimum evidence: gesture, function, alternative action, and the essentiality decision.
- Normative reference: WCAG 2.5.1. Project boundary: the criterion applies to authored content, not to system gestures of the user agent.
2.5.2 Pointer Cancellation, A
- Applicability: functions operated by a single pointer.
- Preconditions/fixtures: mouse/touch, all buttons, and custom areas.
- Steps and parameters: press down inside, move outside, and release; check that the action happens on up, can be cancelled/reversed, or that down is required; to complete the check, verify the ability to cancel before up.
- Pass/fail: passes with one of the conditions of the criterion; fails with an irreversible unwanted activation on down.
- NA/not tested: NA without single-pointer functions; not tested without suitable input.
- Minimum evidence: down/up event, trajectory, the moment of activation, and the cancellation.
- Normative reference: WCAG 2.5.2. Project boundary: confirming every ordinary action beyond the criterion is not required.
2.5.3 Label in Name, A
- Applicability: components with a visible text label or an image of text.
- Preconditions/fixtures: visible label, computed accessible name, and voice input if present.
- Steps and parameters: compare the strings taking order/inclusion into account; say the visible label as a command and observe the element being selected.
- Pass/fail: passes if the accessible name contains the visible text; fails on a mismatch that impedes addressing.
- NA/not tested: NA for a component without a visible text label; not tested when the name is unavailable.
- Minimum evidence: visible string, accessible name, and the result of the voice command in the stated configuration.
- Normative reference: WCAG 2.5.3. Project boundary: exact string equality is desirable, but what is normatively required is the inclusion of the visible label.
2.5.4 Motion Actuation, A
- Applicability: functions triggered by device or user motion.
- Preconditions/fixtures: a device with a sensor, the feature enabled, and an alternative interface.
- Steps and parameters: trigger the motion; perform the same function through an interface component; switch off the motion response except for the supported accessibility interface; assess essentiality.
- Pass/fail: passes with an alternative and the ability to switch it off, or with the exception; fails when there is a single non-disablable motion.
- NA/not tested: NA without motion actuation; not tested without a suitable device.
- Minimum evidence: motion, function, the switch-off control, and the alternative.
- Normative reference: WCAG 2.5.4. Project boundary: visual animation is checked by other criteria.
2.5.7 Dragging Movements, AA
- Applicability: functions where the user drags an object from one point to another.
- Preconditions/fixtures: pointer, all drag states, and the alternative component.
- Steps and parameters: perform the drag; then reach the same result without dragging, with a single pointer, for example via buttons or by selecting a point; assess the applicability of the exceptions: essentiality of the dragging (without it the meaning or function changes) and functionality determined by the user agent (browser/OS) and not modified by the author, for example built-in scrolling or resizing the browser window.
- Pass/fail: passes with a single-pointer alternative without drag, with justified essentiality of the dragging, or when the functionality is determined by the user agent and not modified by the author; fails with a drag-only implementation made specifically by the author of the content.
- NA/not tested: NA without dragging movements; not tested without a state/device.
- Minimum evidence: start/end positions, function, the steps of the alternative, and the essentiality decision.
- Normative reference: WCAG 2.5.7. Project boundary: keyboard accessibility of the same function is additionally checked under 2.1.1.
2.5.8 Target Size (Minimum), AA
- Applicability: pointer targets.
- Preconditions/fixtures: CSS pixel sizes/coordinates, all states, and viewports.
- Steps and parameters: measure the target area as at least 24x24 CSS px; the geometric center of the target's bounding box determines the point of origin of the circle; for the spacing exception, build a circle of 24 CSS px in diameter with its center at the geometric center of the bounding box of each small target and check that it does not intersect another target or the same circle of another small target; check the applicability of the other exceptions: equivalent - the same function is available through another control on the same page that is at least 24x24 CSS px; inline - the target is in a line of text or its size is limited by the line height of non-target text; user agent control - the size of the target is set by the browser and is not modified by the author; essential - the specific presentation of the target is essential to the conveyed information or is required by law.
- Pass/fail: passes by size, spacing, or exception; fails with a target that is too small and too close to another.
- NA/not tested: NA without pointer targets; not tested when the geometry cannot be measured.
- Minimum evidence: sizes, the coordinates of neighbours, the state, and the exception applied.
- Normative reference: WCAG 2.5.8. Project boundary: 44x44 CSS px belongs to AAA 2.5.5 or to a project profile, not to this criterion.
3.1.1 Language of Page, A
- Applicability: every web page/view.
- Preconditions/fixtures: the main natural language of the content, the DOM, and a screen reader with language voices.
- Steps and parameters: determine the main language; check the programmatic value of the root element and the actual switch of pronunciation.
- Pass/fail: passes if the main language is programmatically determinable; fails with a missing or incorrect value.
- NA/not tested: NA usually does not apply; not tested if the main language cannot be established.
- Minimum evidence: main language, actual attribute, and the output of the stated AT.
- Normative reference: WCAG 3.1.1. Project boundary: translation quality is assessed separately.
3.1.2 Language of Parts, AA
- Applicability: phrases and passages in a language other than the main one, except for names, technical terms, words of indeterminate language, and common idioms or loanwords in common use.
- Preconditions/fixtures: a list of multilingual passages, the DOM, and AT with language voices.
- Steps and parameters: check the programmatic language designation of each applicable passage and the pronunciation; assess the exceptions.
- Pass/fail: passes with a correctly determinable language; fails with a missing/incorrect marking.
- NA/not tested: NA without applicable language changes; not tested with a disputed language/term.
- Minimum evidence: quotation of the passage, language, attribute, and AT result.
- Normative reference: WCAG 3.1.2. Project boundary: translation of the passage is not required by this criterion.
3.2.1 On Focus, A
- Applicability: any component that can receive focus.
- Preconditions/fixtures: keyboard, all elements, and initial states.
- Steps and parameters: move focus to each component without activation. For a discovered change, determine whether it changes context as defined by WCAG: user agent, viewport, focus, or content, in a way that could disorient a person who does not perceive the page as a whole. A routine content update without a context change is not to be treated as a failure.
- Pass/fail: passes if receiving focus does not initiate a context change; fails on any such automatic change.
- NA/not tested: NA without focusable components; not tested when a state is unavailable.
- Minimum evidence: the initial state, the focus sequence, and the context change that occurred.
- Normative reference: WCAG 3.2.1. Project boundary: an advance warning does not permit a context change on receiving focus.
3.2.2 On Input, A
- Applicability: components whose setting change may cause a context change.
- Preconditions/fixtures: forms, selects, toggles, and all value options; warning text before use.
- Steps and parameters: change each value without a separate activation. Establish the context change itself as defined by WCAG, as in the card of 3.2.1, and then check whether it was announced before the component was used. A result refresh or the appearance of an additional field is not by itself a context change.
- Pass/fail: passes with no automatic context change or with a warning before the component is used; fails with an unannounced change.
- NA/not tested: NA without input/context-change components; not tested when a branch is unavailable.
- Minimum evidence: component, value, the warning preceding it, and the actual change.
- Normative reference: WCAG 3.2.2. Project boundary: this condition differs from 3.2.1, where a warning does not create an exception.
3.2.3 Consistent Navigation, AA
- Applicability: repeated navigation mechanisms across a set of pages.
- Preconditions/fixtures: at least two pages/views of the set in the same relative order.
- Steps and parameters: compare the order of the repeated mechanisms; check a change initiated by the user.
- Pass/fail: passes with the same relative order or a user-initiated change; fails with an unexpected rearrangement.
- NA/not tested: NA without repeated navigation/set; not tested without a sufficient number of pages.
- Minimum evidence: the pages and the compared sequences.
- Normative reference: WCAG 3.2.3. Project boundary: identical appearance is checked separately.
3.2.4 Consistent Identification, AA
- Applicability: components with the same functionality across a set of pages.
- Preconditions/fixtures: a list of repeated functions, visible names, and accessible names.
- Steps and parameters: compare the identification of each identical function across pages and states.
- Pass/fail: passes with consistent identification; fails if the same function is named/designated so that it looks like a different one.
- NA/not tested: NA without repeated functions; not tested without access to the whole set.
- Minimum evidence: function, pages, visible labels, and accessible names.
- Normative reference: WCAG 3.2.4. Project boundary: different functions are not required to have identical identification.
3.2.6 Consistent Help, A
- Applicability: a set of pages where at least one help mechanism from the criterion repeats: contact with a person, a contact mechanism, self-service, or fully automated contact.
- Preconditions/fixtures: the pages of the set and all help mechanisms.
- Steps and parameters: compare the relative order of the help mechanism with respect to the rest of the page content (the order in the linear/serialized presentation, not only the visual position) across the pages of the set that have the same presentation (the same breakpoint, scale, and orientation); if the order was changed at the user's own initiative, check that this choice is preserved.
- Pass/fail: passes with the same relative order of the help mechanism among the rest of the content on pages of the same presentation, or with an order changed at the user's initiative; fails with a different relative order on pages of the same presentation.
- NA/not tested: NA without the listed help mechanisms; not tested without a set of pages.
- Minimum evidence: the pages, the help type, and the positions in the order.
- Normative reference: WCAG 3.2.6. Project boundary: the criterion does not require creating help where none exists; that can be a separate COGA rule.
3.3.1 Error Identification, A
- Applicability: automatically detected input errors.
- Preconditions/fixtures: test invalid/missing data for each validation rule.
- Steps and parameters: trigger an error, submit/leave the field via a real scenario; find the erroneous element and the text description of the error.
- Pass/fail: passes if the element is identified and the error is described in text; fails with color/icon only, a generic message without an identifiable element, or the absence of a description.
- NA/not tested: NA without automatically detected errors; not tested without a safe way to trigger an error.
- Minimum evidence: input, action, the erroneous element, and the exact message text.
- Normative reference: WCAG 3.3.1. Project boundary: automatic announcement by a screen reader requires a separate check under 4.1.3 and a specific configuration.
3.3.2 Labels or Instructions, A
- Applicability: content that requires user input.
- Preconditions/fixtures: an empty form, formats, requiredness, and non-standard constraints.
- Steps and parameters: before typing, check for the presence of a visible/accessible label and of the necessary instructions; enter boundary data without using a placeholder as the only sustainable source.
- Pass/fail: passes if the user receives the needed label or instruction; fails with an unknown purpose/format/requiredness.
- NA/not tested: NA without input; not tested when the form is unavailable.
- Minimum evidence: the field, the input requirement, and the label/instruction before typing.
- Normative reference: WCAG 3.3.2. Project boundary: a permanently visible hint is a useful project rule if the normative condition is otherwise already met.
3.3.3 Error Suggestion, AA
- Applicability: a detected input error with a known correction suggestion, if it does not endanger security or the purpose.
- Preconditions/fixtures: separate invalid values and known valid formats.
- Steps and parameters: trigger an error; check the specific correction suggestion and the possibility of applying it.
- Pass/fail: passes with an available suggestion or a proven exception; fails with a single "error" message without a known way to correct it.
- NA/not tested: NA when the correction is unknown or there is a risk to security/purpose; not tested if the error was not reproduced.
- Minimum evidence: input, message, known correction, and the decision on the exception.
- Normative reference: WCAG 3.3.3. Project boundary: the correction is not required to be applied automatically.
3.3.4 Error Prevention (Legal, Financial, Data), AA
- Applicability: legal obligations/financial transactions, changing or deleting user data in storage, and submitting test responses.
- Preconditions/fixtures: a safe stand, fictional data/payment, and all confirmation and cancellation steps.
- Steps and parameters: enter erroneous data and check the three permitted mechanisms: what was submitted can be undone; the data is checked for errors with the possibility to correct them; or the information can be reviewed, confirmed, and corrected before final submission. One fully implemented mechanism is sufficient.
- Pass/fail: passes when at least one of the three mechanisms is implemented. A single "Confirm" button without review and correction is not sufficient for the third mechanism. A failure is recorded if none of the mechanisms is implemented.
- NA/not tested: NA for transactions outside the listed categories; not tested without an authorized safe fixture.
- Minimum evidence: transaction type, test data, the steps of review/correction/cancellation, and the outcome without real damage.
- Normative reference: WCAG 3.3.4. Project boundary: double confirmation of every transaction beyond one permitted mechanism is additional.
3.3.7 Redundant Entry, A
- Applicability: information already entered or provided by the user and requested again in the same process.
- Preconditions/fixtures: the full process, test data, and forward/back transitions.
- Steps and parameters: enter the data at the first step; reach the repeated request; check the auto-fill or the selection of the previously entered value; assess the exceptions essential, security, or invalid.
- Pass/fail: passes with auto-fill/selection or an exception; fails when re-entry is mandatory.
- NA/not tested: NA without a repeated request in the process; not tested without the full process.
- Minimum evidence: the first and repeated fields, the steps, the behaviour, and the exception.
- Normative reference: WCAG 3.3.7. Project boundary: persistence between different processes or sessions is an additional rule.
3.3.8 Accessible Authentication (Minimum), AA
- Applicability: authentication steps.
- Preconditions/fixtures: an authorized test account, all MFA/CAPTCHA/recovery paths, a password manager, and pasting.
- Steps and parameters: go through each login and recovery step. Ordinary username, e-mail, or phone fields are not by themselves a cognitive function test: they are identifiers that are personal to the user and identical across sites; check that paste and autofill are not blocked in them. For the password and the one-time code - a cognitive function test as defined by the criterion - check for the presence of a mechanism that reduces the burden: password manager operation, permitted pasting, or autofill. If no such mechanism exists, check an alternative login method without a cognitive function test, or an exception permitted at the AA level: object recognition (without a text transcription) or recognition of personal content previously provided by the user to the site.
- Pass/fail: passes if the identifier field (name, e-mail, phone) has not blocked paste/autofill, or if a burden-reducing mechanism (password manager, paste) is available for the password/code, an alternative method without a cognitive function test, or a permitted exception (object recognition, recognition of personal content); fails with mandatory memorization, transcription, or computation without such a mechanism, alternative, or exception.
- NA/not tested: NA without authentication; not tested without an authorized fixture or a specific MFA branch.
- Minimum evidence: method, steps, available alternative/help, settings, and the result of the test login.
- Normative reference: WCAG 3.3.8. Project boundary: a blanket ban on all CAPTCHAs does not follow from the criterion; the security of the test account is mandatory under the assessment procedure.
4.1.2 Name, Role, Value, A
- Applicability: all interface components, especially custom widgets.
- Preconditions/fixtures: DOM, accessibility tree, the exact browser/AT version, and all states.
- Steps and parameters: for each component, check the programmatic name and role; the accessibility of values/states that the user can set; the ability to set them programmatically; the transfer of changes to user agents.
- Pass/fail: passes under all applicable conditions; fails with a missing/incorrect name, role, or state, or with inaccessible control.
- NA/not tested: NA without interface components is practically inapplicable; not tested without a state or programmatic structure.
- Minimum evidence: element, DOM/tree, actions, and the actual output of the stated AT.
- Normative reference: WCAG 4.1.2. Project boundary: one successful screen reader does not prove universal compatibility; the support matrix is set by the project.
4.1.3 Status Messages, AA
- Applicability: messages that inform about success, result, waiting, progress, or error without a context change.
- Preconditions/fixtures: the exact browser/screen reader version, the actions for all statuses, and the focus before triggering.
- Steps and parameters: trigger a message without moving focus; observe the accessibility tree and the AT output; check for a programmatically determinable role/property that allows the status to be announced without receiving focus.
- Pass/fail: passes if the status is programmatically determinable through a role or properties in a way that allows assistive technology to present it without receiving focus, with a supported way of using the technology. Failure: the required programmatic semantics are absent, or their unsuitability for such a presentation is proven. The silence of a single program does not by itself determine the result: check the settings, the moment of the update, and the support; if the cause is not established, leave the question open.
- NA/not tested: NA without status messages; not tested without reproduction or a stated AT configuration.
- Minimum evidence: the action, the initial/final focus, the status text, DOM/role/properties, and the supported way of use. The settings, the actual AT output, and the diagnosis of a detected incompatibility are recorded separately, if it is established.
- Normative reference: WCAG 4.1.3. Project boundary: the timing and the style of the announcement beyond sufficient programmatic determinability depend on the project profile.
3. Result Matrix
For each unit a row is kept for each of the 55 criteria, even if the status is NA. Grouping several criteria into a single observation is permissible only with a separate decision and evidence for each ID.
Unit ID and state:
Product version/build:
OS, version:
Browser, version:
AT, version:
Language, viewport, orientation, scale:
Input method and system settings:
Criterion and link to the normative card:
Applicability and basis:
Fixture/role/TTL:
Test data:
Sequence of keys/gestures/actions:
Expected normative result:
Actual result:
Status: pass / fail / NA / not tested
Minimum evidence and link:
Related defect/component/regression:
Project rule, if any:
Assessor and date:
A single proven defect of an applicable criterion on a page or within a full process inside the stated scope is sufficient to disprove full conformance of that scope to the stated level. It does not prove the inaccessibility of every element or every page. A successful result of a sample does not by itself usually give grounds to declare conformance of the whole site, which is to be taken into account together with the WCAG conformance requirements and the WCAG-EM 2.0 sampling assessment boundaries.
