Status: annex to the accessibility assessment methodology, a draft for discussion and piloting. This is not an approved standard, a normative legal act, or a certificate.
Why protocols are needed and how to use them
This annex sets a single procedure for the D-01 to D-20 checks of Section D "Methodology for assessing the accessibility of digital resources". The methodology defines inventory, sampling, safe conditions, configurations, evidence, and severity. This file defines the assessor's actions at each step of the selected process.
Each applicable check ends with exactly one status:
- pass: the conditions of the card are fulfilled at all applicable steps and states of the selected process variant;
- failure: at least one confirmed applicable instance of non-compliance was found;
- NA: the function or state is absent throughout the process under test, and the reason is recorded;
- not tested: applicability or the result could not be established because a permitted test environment, role, state, channel, or sufficient evidence was missing. This status is not counted as a pass.
A minimum record contains the process ID and variant, the role, the configuration, the test set, the step and state, the action, the expected and actual result, the focus before and after, the address or channel, the date, the assessor, and a link to the evidence. Secrets, one-time codes, payment details, and personal data are not included in the evidence. The automatic signal from D.6 does not replace a manual conclusion.
A normative reference shows the basis for the check. W3C explanatory documents are used for interpretation and do not create a new mandatory requirement. The "Project boundary" field separates the requirement of the source from a stricter project rule. Such a rule acts as a Project proposal only after it is included in an adopted profile.
Protocols
D-01. Completeness of the path and its states
- Applicability: every selected process and every included role or outcome variant.
- Preconditions: a frozen process register, the schema of the selected path, permitted roles and test states, a known expected result.
- Steps and parameters: start from the declared entry point; record every page, state, channel, and transition up to the outcome; repeat the applicable branches of success, error, correction, back, cancel, expiry, renewal, and re-entry; compare the actual path with the schema and the register.
- Pass/failure: passes if the whole selected path and the applicable branches have been checked, and every web page of the process is included in full; fails if the claim of a pass rests on a single screen or excludes a mandatory step.
- NA/not tested: NA does not apply to the selected process; an individual branch may be NA only on confirmed absence. Not tested if the branch exists but is not safely reachable.
- Minimum evidence: a path map with step numbers, addresses or channels, states, transitions, and outcomes; reasons for NA and untested branches.
- Normative reference: WCAG 2.2, conformance requirements 2 and 3, WCAG-EM, step 3.c.
- Project boundary: the composition of additional branches beyond the full web process is determined by the sampling in D.3 and marked there as a Project proposal.
D-02. Keyboard operation
- Applicability: all interactive steps, elements, dialogs, and ways out of the web part of the process.
- Preconditions: the initial state of the step, a keyboard or equivalent input interface, a mouse disconnected, known non-standard key combinations.
- Steps and parameters: traverse the process with sequential navigation and standard activation keys; open and close dialogs, lists, and calendar controls; perform back and cancel; check that all actions are reachable, that there is no trap, and that focus movement can be restored without a reload.
- Pass/failure: passes if all functionality is available from the keyboard and every component can be exited by the usual or an announced method; fails on an unreachable action, an invisible active element, a loop, or a trap.
- NA/not tested: NA only for a process with no web interface and no keyboard method; not tested if the appearance of the resource or the device is not provided.
- Minimum evidence: the key and focus sequence, the step, the element, the expected and actual action, a capture of the visible focus, or a record of a trap.
- Normative reference: WCAG 2.1.1, 2.1.2.
- Project boundary: automatic passing of a sequence confirms only the observed route; manual checking of all functions remains mandatory.
D-03. Order and movement of focus
- Applicability: pages and components with several elements, a step change, a dynamic update, an error, a dialog, or a back action.
- Preconditions: a known visual and logical sequence, a screen reader, keyboard input.
- Steps and parameters: record the order of sequential navigation; trigger the forward and backward transition, open and close a dialog, cause a permitted error and a dynamic update; after each action determine the active element, its name, role, state, and context; check the return of focus to the initiator or to a place where continuation is clear.
- Pass/failure: passes if the order preserves meaning and operability and the transfer of focus does not hide the change and does not return the user to the beginning without reason; fails on a skip, an unexpected jump, a loss of focus, or a programmatically indeterminate element.
- NA/not tested: NA for a step without focusable elements and dynamic transitions; not tested without the required state.
- Minimum evidence: a table of "action, focus before, focus after, expected place, actual place", and the programmatic name, role, and state.
- Normative reference: WCAG 2.4.3, 4.1.2.
- Project boundary: the specific point of transfer of focus is not prescribed if meaning and operability are preserved.
D-04. Steps, back action, and cancel
- Applicability: multi-step processes, wizards, questionnaires, and sequences with saved or changed data.
- Preconditions: a known number or logic of steps, safe test data, permitted back and cancel actions.
- Steps and parameters: at each step determine the title, the position in the process, and the available actions; move forward, then backward; check the preservation of valid data and of focus; trigger a cancel before the final action and check the warning, the result, and the possibility to continue.
- Pass/failure: passes if the current step and its purpose are clear, back and cancel are available, and data loss is announced in advance; fails on an unclear position, an irreversible transition without a warning, or an unavailable cancel where one is promised.
- NA/not tested: NA for a single-step process without back and cancel; not tested if a cancel produces an external consequence and no test environment is available.
- Minimum evidence: captures of two adjacent steps, the sequence of actions, the state of the input before and after the back action, the warning text, and the outcome of the cancel.
- Normative reference: WCAG 2.4.6, Making Content Usable: make each step clear, let users go back.
- Project boundary: the step indicator, the available back action, and the data loss warning apply as a Project proposal if they do not follow from the adopted profile or from the nature of the declared function.
D-05. Labels and instructions
- Applicability: input fields, selections, upload, confirmation, and groups of elements with a format or a constraint.
- Preconditions: the empty state of the step, the programmatic representation of the elements, known data rules.
- Steps and parameters: before input, determine the accessible name of each field, its requiredness, format, units, permitted range, and the link between a common instruction and the group; compare the programmatic and the visible label; check that a placeholder is not the only source of a permanent instruction.
- Pass/failure: passes if the purpose and the constraints are available before the action and programmatically linked to the field where a link is necessary; fails on a missing, wrong, disappearing, or unlinked label.
- NA/not tested: NA for a step without user input; not tested if the data rules are unknown and cannot be established safely.
- Minimum evidence: the step and the field, the visible label, the accessible name, the instruction, the requiredness, and the programmatic link.
- Normative reference: WCAG 3.3.2, 2.5.3.
- Project boundary: the project does not prescribe a specific placement of the label if the link and the clarity are confirmed.
D-06. Detecting and describing errors
- Applicability: fields and actions for which the service is able to detect an input error.
- Preconditions: permitted anonymised values for empty, malformed, and constraint-violating input; a prohibition on final submission outside the test environment.
- Steps and parameters: trigger each safe error; identify the erroneous field and the message; read the message visually and with a screen reader; check the textual description of the cause, a known correction hint, the preservation of valid fields, and a successful correction.
- Pass/failure: passes if the error is marked by text, is linked to the field, and contains a known correction suggestion, except in cases of a security risk or of purpose; fails on a single colour, a generic phrase without a field, a disappearing message, or a loop with no way to correct it.
- NA/not tested: NA if input and detectable errors are absent; not tested for an error that cannot be triggered safely.
- Minimum evidence: the class of the test value without its content, the field, the message, the programmatic link, the focus, the correction, and the result.
- Normative reference: WCAG 3.3.1, 3.3.3.
- Project boundary: a requirement to disclose protective rules is not introduced if the hint creates a confirmed security risk. The preservation of correctly entered fields is a Project proposal if it does not follow from the adopted profile.
D-07. Status messages
- Applicability: loading, searching, filtering, saving, submitting in the test environment, waiting, success, warning, and error that do not move the focus.
- Preconditions: an observed initial state, a screen reader, a permitted action, a known expected result.
- Steps and parameters: cause the change using only the keyboard; do not move the focus manually; record the text that appears and the programmatic role of the region; check the timely announcement of the result, the number found, the progress, and the error; repeat with a rapid sequence of changes.
- Pass/failure: passes if the message is programmatically determinable with a suitable role or property and is available to assistive technology without a mandatory focus move; fails if the change is visible but not announced, or if the announcement does not match the state.
- NA/not tested: NA in the absence of applicable dynamic messages; not tested if the action has an external consequence and no test environment is available.
- Minimum evidence: the action, the focus before and after, the text, the programmatic role or property, the time of appearance, and the actual output of the assistive technology.
- Normative reference: WCAG 4.1.3.
- Project boundary: a focus move is not required solely for the sake of a message; if a change requires continuation in a new context, the order is assessed under D-03.
D-08. Time limits and extension
- Applicability: sessions, steps, codes, and operations with a time limit set by the content.
- Preconditions: a known duration, a permitted test environment or a safe short test value, the reference point, and the warning and expiry states.
- Steps and parameters: measure the time; establish the way to switch off, configure, or extend it; wait for the warning; check that it is given at least 20 seconds in advance and that extension is available through a simple action at least ten times, if no exception to the criterion applies; check the state after expiry.
- Pass/failure: passes when the applicable variant of WCAG 2.2.1 or a confirmed exception is fulfilled; fails on expiry without available control, or on the loss of the possibility to complete the task.
- NA/not tested: NA without a time limit set by the content, or with a documented exception; not tested if the term cannot be reproduced safely.
- Minimum evidence: the source and the duration of the limit, the warning time, the available action, the number of extensions, the state of the data, and the justification for the exception.
- Normative reference: WCAG 2.2.1.
- Project boundary: a long wait is not replaced by an assumption; without a measurement the status is "not tested".
D-09. Warning about loss and preservation of entered data
- Applicability: steps with entered data that may be lost on exit, cancel, transition, or expiry.
- Preconditions: an anonymised set with distinguishable fields, permitted back action and expiry, or a test environment.
- Steps and parameters: fill in the test fields; go back, exit, cancel, and reproduce the expiry following the permitted scenario; record the warning and the available options; continue or re-enter; compare the preserved fields and the state of the step.
- Pass/failure: passes if the loss is explicitly announced in advance and valid data is preserved, or if the user knowingly confirms the refusal; fails on unexpected loss, or on the impossibility to continue without re-entering the data where preservation is allowed.
- NA/not tested: NA without entered data, or when preservation is prohibited by a confirmed security requirement; not tested without a permitted state.
- Minimum evidence: a list of the classes of filled fields without the values, the action, the warning, the chosen option, and the state after the back action or the re-entry.
- Normative reference: WCAG 2.2.5 (level AAA).
- Project boundary: the loss warning and the preservation apply as a Project proposal beyond the AA profile; secrets and expired data are not preserved.
D-10. Absence of repeated input
- Applicability: information already entered by the user earlier in the same process and requested again by the service.
- Preconditions: a map of the fields by steps, anonymised distinguishable values, information on essentiality and security constraints.
- Steps and parameters: enter the information at the first step; reach each repeated request; check the automatic filling or the possibility to select a previous value; determine whether the case falls under an essential, protective, or expired exception.
- Pass/failure: passes with automatic filling, selection, or a confirmed exception; fails if the same valid information has to be entered again without an acceptable reason.
- NA/not tested: NA without repeated requests, or with a confirmed exception; not tested if a further step is unreachable.
- Minimum evidence: the step and field numbers, the fact of a match of information without recording the value, the available mechanism, and the justification for the exception.
- Normative reference: WCAG 3.3.7.
- Project boundary: the comparison must not preserve the entered content in a log or a capture.
D-11. Accessible authentication
- Applicability: sign-in, re-entry, recovery, and identity confirmation at a web step.
- Preconditions: a permitted test account, all declared sign-in methods, the possibility to complete and reset an attempt safely.
- Steps and parameters: list each cognitive function test, including memorisation, transcription, and problem solving; traverse the primary and the alternative methods; check that pasting is permitted and that the assistance mechanisms work; for an exception, confirm the recognition of an object, personal content, or essentiality.
- Pass/failure: passes if there is no cognitive test, or if a criterion-conforming alternative, an assistance mechanism, or a permitted exception is available; fails if the only path requires a non-permitted test.
- NA/not tested: NA for a process without authentication; not tested without a test account or a sign-in method.
- Minimum evidence: the sign-in method, the function under test, the available alternative or assistance, the possibility to paste, the result, and the justification for the exception.
- Normative reference: WCAG 3.3.8.
- Project boundary: the assessment of resilience and identity verification is not part of the protocol.
D-12. CAPTCHA and alternatives
- Applicability: a check intended to distinguish a human from an automated system, including at sign-in and recovery.
- Preconditions: a permitted display state, all offered alternatives, a screen reader, and a keyboard.
- Steps and parameters: establish an accessible text description of the purpose; open each alternative; traverse it without a mouse and with a screen reader; check different types of perception; separately establish whether a cognitive function test remains the only authentication path.
- Pass/failure: passes if the non-text content indicates the purpose, alternatives exist for different constraints, and authentication conforms to 3.3.8; fails on a single visual, audio, or cognitive task with no permitted path.
- NA/not tested: NA without a CAPTCHA; not tested if it appears irregularly and no permitted state is provided.
- Minimum evidence: the invocation state, the description of the purpose, the list of alternatives, the keyboard path, the programmatic output, and the result.
- Normative reference: WCAG 1.1.1, 3.3.8.
- Project boundary: a single audio alternative does not prove conformance with accessible authentication; both criteria are checked.
D-13. One-time codes
- Applicability: entering a code from a message, an application, a device, or another channel.
- Preconditions: a test recipient, a permitted code without real data, and known validity period, number of attempts, and reissue method.
- Steps and parameters: obtain a test code; move between the channels; paste the code in full; with separate fields, check the automatic carry-over and the correction; check the labels, the format, the countdown, the reissue, the expired-code error, and the return to the process.
- Pass/failure: passes if the code can be pasted or carried over by a supported mechanism without mandatory transcription, if the fields and the error are available, and if the validity period and the reissue are clear; fails when pasting is prohibited, digits are lost, the countdown is unavailable, or there is a loop without recovery.
- NA/not tested: NA without a one-time code; not tested without a test channel or a permitted issuance.
- Minimum evidence: the channel without the recipient address, the number and the type of fields, the fact of pasting without the code value, the validity period, the reissue, the error, and the outcome.
- Normative reference: WCAG 3.3.8, Understanding 3.3.8.
- Project boundary: the W3C explanation is informative; the mandatory conclusion is bound to the normative text of 3.3.8 and to the adopted profile.
D-14. Re-authentication and continuation
- Applicability: a process that requires re-authentication after expiry, an increase of the trust level, or a transition.
- Preconditions: a test environment, a test account, a filled-in draft, a permitted way to trigger re-authentication.
- Steps and parameters: reach the control step with test data; trigger the re-authentication; complete it in an accessible way; determine the page, the step, the focus, and the preserved data after the return; complete the safe part of the process.
- Pass/failure: passes if the re-authentication is available, the context is clear, and the entered information is preserved, except for a confirmed security constraint; fails on a return to the beginning, loss of valid data, or an unavailable way to continue.
- NA/not tested: NA without re-authentication; not tested without a test environment or a test account.
- Minimum evidence: the step before the sign-in, the reason and the method of sign-in, the step and the focus after, the list of preserved classes of fields, and the constraints.
- Normative reference: WCAG 2.2.5 (level AAA).
- Project boundary: application in the base D set is a Project proposal beyond the AA profile.
D-15. Prevention of significant errors
- Applicability: a legal obligation, a financial operation, a change or deletion of data managed by the user, a submission of a response to an assessment.
- Preconditions: a test environment or a cancellable test operation, a known consequence, anonymised data, a prohibition on a real action.
- Steps and parameters: reach the last safe step; check for the presence of at least one mechanism: reversibility, detection and correction of errors, or review, confirmation, and correction before completion; check the content of the summary and the availability of each correction.
- Pass/failure: passes with one of the three mechanisms of the criterion across the whole applicable action; fails on irreversible completion without a check or without an available confirmation.
- NA/not tested: NA without the listed consequences; not tested if the final mechanism cannot be observed without a real operation and no test environment is available.
- Minimum evidence: the type of consequence, the last safe step, the summary, the available corrections, the prevention mechanism, and the status of the final action.
- Normative reference: WCAG 3.3.4.
- Project boundary: a real legal or financial action is not performed for the purpose of testing.
D-16. Consistent help
- Applicability: the set of web pages of the process on which at least one help mechanism from the list of WCAG 3.2.6 is repeated.
- Preconditions: all pages of the selected process, the list of contacts, the contact mechanisms, and the self-service and automated help.
- Steps and parameters: on each page record the presence and the relative order of the repeated mechanisms; traverse the links with the keyboard; check the purpose, the accessible name, and the preservation of the context on return.
- Pass/failure: passes if the repeated mechanism is placed in one relative order, except for a change initiated by the user; fails on an unpredictable movement or a substitution of the purpose.
- NA/not tested: NA if none of the mechanisms of the criterion is repeated; not tested if a page of the process is unreachable.
- Minimum evidence: a matrix of pages, mechanisms, and relative order, the focus sequence, and the result of the navigation.
- Normative reference: WCAG 3.2.6.
- Project boundary: the criterion does not require creating help where none exists; the consistency of the existing mechanisms is checked.
D-17. File upload
- Applicability: selecting, dragging, capturing, replacing, deleting, or sending a file.
- Preconditions: a test environment, safe test files of a permitted and a non-permitted type and size, and the absence of personal data.
- Steps and parameters: before the selection, establish the permitted formats, the size, and the number; select a file with the keyboard without a mandatory drag and drop; observe the progress and the result; trigger an error in a permitted way; replace and delete the file; check the labels, the focus, the messages, and the preservation of the remaining data.
- Pass/failure: passes if the constraints are known in advance, all actions are available from the keyboard, the file is named unambiguously, and the progress, the success, and the error are available programmatically; fails on drag and drop as the only method, an unclear constraint, or an unannounced result.
- NA/not tested: NA without upload; not tested without a test environment, or if even a test file would leave the system.
- Minimum evidence: the file properties without content, the selection method, the focus sequence, the constraints, the messages, the replacement, and the deletion.
- Normative reference: WCAG 3.3.2, 3.3.1, 4.1.3, 2.5.7.
- Project boundary: the preliminary list of constraints, the replacement, and the deletion of the file are a Project proposal in the part not established by the adopted profile. The file content and the storage security are not assessed; the document is assessed separately under Section B.
D-18. The result in an accessible form
- Applicability: a final page, a status, a reference, a receipt, a decision, a notification, or an electronic document.
- Preconditions: a safe test result or an already published example, a known purpose, and a known availability period.
- Steps and parameters: complete the permitted test-environment path or open the example; find the result with the keyboard and a screen reader; check the title, the status, the date, the way to obtain it again, and the link to the original process; for a document, run the applicable checks of Section B or check an equivalent accessible version.
- Pass/failure: passes if the result is reachable, unambiguously named, clear, and available in the adopted format; fails on an unreachable link, an unclear file, an unavailable mandatory document without an equivalent version, or the disappearance of the result without a warning.
- NA/not tested: NA for a process without a separate result; not tested if the result is created only by a real submission and no test environment is available.
- Minimum evidence: the final step, the name and the purpose of the result, the link or the way to obtain it, the applied Section B, and the status of the document.
- Normative reference: WCAG 2.4.4, Section B of the methodology.
- Project boundary: obtaining the result within the same process and the equivalent version are a Project proposal in the part not established by the adopted profile. The legal force of the result and the retention period are established outside the accessibility protocol.
D-19. Transition between resources and return
- Applicability: a transition to another domain, site, application, device, document, or channel with a subsequent continuation or return.
- Preconditions: all permitted components of the transition, a test role, and the initial state with an anonymised context.
- Steps and parameters: record the resource and the focus before the transition; activate the transition with the keyboard; establish the warning, the target, the way to continue, and the re-entry; complete the safe part; return by the standard method; compare the step, the context, and the valid data.
- Pass/failure: passes if the change is clear, the target is reachable, the context and the valid data are preserved, and continuation and return do not require an unreachable action; fails on an unexpected channel, a dead end, a loss of context, or an unavailable re-entry.
- NA/not tested: NA without transitions; not tested if the external resource, the application, or the test role is unavailable.
- Minimum evidence: both sides of the transition, the addresses or channels, the warning, the focus, the re-entry, the state before and after, and the return path.
- Normative reference: WCAG 2.2, conformance requirement 3.
- Project boundary: the warning about the change, the preservation of the context, and the standard return apply as a Project proposal beyond the boundary of the web process.
D-20. Notifications and confirmations in other channels
- Applicability: a message, a call, an application, a device, or another channel needed for a code, a status, a confirmation, or a result.
- Preconditions: a test recipient and a permitted channel, known delivery time, purpose, and repeat method.
- Steps and parameters: before the transition, establish which channel is used and when; receive a test message; check the meaning without relying only on colour, position, sound, or any other single type of perception; follow a safe link or enter a code under D-13; request a repeat; check the return to the original process.
- Pass/failure: passes if the channel, the timing, and the action are clear, the message is available to alternative perception, the repeat is possible, and the user returns to the required context; fails on a single inaccessible signal or the absence of a safe repeat.
- NA/not tested: NA without another channel; not tested without a test recipient or permitted delivery.
- Minimum evidence: the type of channel without the address, the moment of the request and of the delivery, the available content, the action, the repeat, and the state after the return.
- Normative reference: WCAG 1.3.3, 1.4.1.
- Project boundary: the timing, the repeat, and the preservation of the context are a Project proposal; the work of the telecom operator is outside the scope of the assessment, but an actual delivery failure is recorded as a limitation.
