Mobile Application Check Protocols

  • Version: 0.1.1
  • Date: 17 October 2026
A phone supports a simple tap, magnification and an external switch.

Download the document (DOCX)

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 these protocols are needed and how to use them

This annex sets a single procedure for checks V-01 to V-22 of Section V "Accessibility assessment methodology for digital resources". The methodology defines the object of assessment, the inventory, the sample, the device matrix, evidence, and severity; this file defines the actions of the assessor on each selected screen and state.

Every card ends with exactly one overall status: pass, fail, NA, or not tested. If a card contains several conditions, an internal sub-result is recorded for each condition first, and then a single aggregation rule is applied:

  1. any applicable failure gives the overall result "fail";
  2. if there are no failures but at least one applicable sub-result is not tested, the overall result is "not tested";
  3. if at least one applicable sub-result passes, the rest either pass or carry a justified NA, the overall result is "pass";
  4. an overall NA is acceptable only when all sub-results have a confirmed NA.

Thus the combination NA + pass gives one overall pass, NA + fail gives one overall fail, and not tested + pass gives one overall "not tested". Multiple failures are retained as separate sub-results and evidence, but they do not create multiple overall card statuses.

A minimal result record always contains the identifier and version of the application, the platform and device model, the configuration, the screen and state IDs, preconditions, steps, expected and actual result, date, assessor, and an evidence link. A static signal and an accessibility tree dump do not replace a manual step and the actual output of a screen reader.

A route with a screen reader covers one task in two ways: exploration by touch and a sequence of gestures. Both ways are performed from the initial state to a confirmed result and include the applicable loading, empty result, error, correction, success, system transition, and return cases. The screen reader version, its significant settings, and the voice language are recorded for a run. The expected result is specified through the accessible name, role, state, value, and actions, the focus position, and the outcome of the operation, and not through a single verbatim synthesizer phrase. For applicable elements, the six base component cards are used, and the general sequence is set by the manual checks guide.

An assessor run through these cards is a manual check, even when a real screen reader is used. User evidence is recorded separately according to the Comprehensibility and Cognitive Accessibility Protocol in a session with a person for whom the configuration is familiar. An automated signal, an expert route, and participant observation are not combined into a single result.

A normative reference shows the basis of the check. WCAG2ICT is an informative note on the application of WCAG to non-web software. A reference to a G protocol means that its procedure is applied with the mobile specificity of Section V.5. The "Project boundary" field separates the condition of the source from a stricter project rule.

Protocols

V-01. Accessible name, role, state, value, relationships, and actions

  • Applicability: every meaningful control, information object, and composite component.
  • Preconditions: screen in the initial and modified state, screen reader, accessibility tree dump.
  • Steps and parameters: separately traverse the elements by touch exploration and by sequential navigation; compare the visible label with the accessible name; check the role, state, value, relationships, and list of actions; change a value or state and repeat both routes; perform the applicable protocol G-01.
  • Pass/fail: passes if the properties are accurate, sufficient, and updated in time, and every available action can be performed; fails if a name, role, state, value, relationship, or action is missing or false.
  • NA/not tested: NA is impossible for an interface with user components; not tested when the state or tree is unavailable and the actual output also cannot be observed.
  • Minimum evidence: screenshot, tree node before and after, structured record of name, role, state, value, and available actions, focus position, and the action performed; an audio recording or verbatim transcript is additional evidence for this configuration.
  • Normative reference: EN 301 549 V4.1.1, 11.5.2, WCAG 4.1.2.
  • Project boundary: the presence of a non-empty property by itself does not prove its accuracy; the final conclusion is always manual.

V-02. Reading order, focus, and virtualized content

  • Applicability: screens with two or more elements, scrolling, lazy loading, a dialog, or dynamic updates.
  • Preconditions: expected semantic sequence, screen reader, states before and after the transition.
  • Steps and parameters: traverse the screen forward and backward; scroll and load the next portion; open and close a dialog; trigger an update, an error, and a return; record the focus before and after; perform the applicable protocols G-02 and G-04.
  • Pass/fail: passes if the order preserves meaning, hidden and empty objects are excluded, lazily loaded content is reachable, and the focus after a change is predictable; fails on a skip, a loop, a jump, a loss, or a landing on an invisible object.
  • NA/not tested: NA only for a state with a single inactive information object; not tested if a dynamic state cannot be triggered safely.
  • Minimum evidence: numbered sequence, names, roles, states, and available actions along the route, screenshots before and after, tree fragments, and focus position; a narration recording is added when needed to supplement these data.
  • Normative reference: WCAG 1.3.2, 2.4.3, EN 301 549 V4.1.1, 11.5.2.13-11.5.2.15.
  • Project boundary: an identical tree order and visual layout are not mandatory if the actual sequence preserves meaning and operation.

V-03. Complex gestures and a single-pointer alternative

  • Applicability: an action with multiple touch points, a directional swipe, path drawing, or another trajectory-based gesture.
  • Preconditions: list of gestures from B.2, initial state, and description of the expected function.
  • Steps and parameters: perform each gesture in the ordinary way; find and perform the alternative with a single tap, press, or another single-pointer action without a trajectory; check both screen readers; establish whether the gesture belongs to the platform or to an assistive technology.
  • Pass/fail: passes with an equivalent single-pointer alternative or with proven essentiality of the gesture; fails if the application function is available only through a complex gesture.
  • NA/not tested: NA when such gestures are absent; not tested if the state or device does not allow reproduction.
  • Minimum evidence: recording of the gesture and of the alternative, the result of each path, and the justification of the exclusion if one is applied.
  • Normative reference: WCAG 2.5.1, EN 301 549 V4.1.1, 11.2.5.1.
  • Project boundary: screen reader system gestures are not counted as application gestures.

V-04. Pointer cancellation

  • Applicability: an action with a single tap, press, long press, or pointer release.
  • Preconditions: a safe state in which the action can be repeated or undone.
  • Steps and parameters: touch the target and move the pointer outside its boundary before releasing; check the moment of execution; if the action executes on touch, check undo or reversal; separately explore press-and-hold and repeat.
  • Pass/fail: passes if the action completes on release with a possibility to abort, or is otherwise available to undo or reverse, except for the precise exception; fails on irreversible execution on touch without an exception.
  • NA/not tested: NA when there is no pointer control; not tested if the action is irreversible and no approved test stand is available.
  • Minimum evidence: recording of the touch, movement, and release, the state before and after, the undo mechanism or the justification of the exception.
  • Normative reference: WCAG 2.5.2, EN 301 549 V4.1.1, 11.2.5.2.
  • Project boundary: the check does not require performing a real legal, financial, or otherwise irreversible action.

V-05. Dragging and an alternative without dragging

  • Applicability: sorting, moving, a slider, a map, range selection, or another function with dragging.
  • Preconditions: safe test data and the initial position of objects.
  • Steps and parameters: perform the drag; find a control with a single pointer that does not require dragging, for example selecting an object and a separate position command; perform it; check the screen reader and the applicable protocol G-12.
  • Pass/fail: passes with an equivalent single-pointer method without dragging or with a precise exception; fails when dragging is the only method.
  • NA/not tested: NA without dragging; not tested without a safe state or a possibility to restore the data.
  • Minimum evidence: recording of both methods, the initial and final position, accessible names, and actions.
  • Normative reference: WCAG 2.5.7, EN 301 549 V4.1.1, 11.2.5.7.
  • Project boundary: a platform action that the application has not changed is not attributed to the application.

V-06. Target size and spacing

  • Applicability: every pointer target, including icons, switches, list rows, map areas, and invisible touch areas.
  • Preconditions: physical device, screenshot at the original scale, a tool for measuring target boundaries.
  • Steps and parameters: measure the actual active area and the spacing to neighbouring targets; map platform-independent units to CSS px; for each target smaller than 24 x 24 CSS px check one of five exceptions: sufficient spacing, an equivalent target of at least 24 x 24 CSS px in the same application, a target within a line of text, a size set by the platform and not changed by the application, or a specific size that is essential or prescribed; compare the static layout with the observed area.
  • Pass/fail: passes if the actual area is at least 24 x 24 CSS px or a confirmed exception applies; fails if the area is smaller without an exception.
  • NA/not tested: NA without pointer targets; not tested when it is impossible to establish the activation area or the unit correspondence.
  • Minimum evidence: screenshot with boundaries and dimensions, the unit mapping factor, neighbouring targets, and the exception applied.
  • Normative reference: WCAG 2.5.8, EN 301 549 V4.1.1, 11.2.5.8.
  • Project boundary: WCAG2ICT, 2.5.8 is used as an informative note on unit correspondence. A stricter minimum from the platform recommendations is a Project proposal and is recorded as a separate profile.

V-07. Text enlargement and reflow

  • Applicability: screens with text, labels, fields, messages, and buttons.
  • Preconditions: initial state at the normal size; the text enlargement configuration; a way to obtain a content area 320 CSS px wide, and for horizontally scrollable content a height of 256 CSS px.
  • Steps and parameters: perform two tests separately. Text enlargement: traverse the same screens and actions at up to 200 percent enlargement, if the platform supports it, and at the maximum system size. Reflow: set an area 320 CSS px wide for vertically scrollable content or 256 CSS px high for horizontally scrollable content, then check the loss of information and functions and the need for scrolling in two dimensions; exclude only parts for which a two-dimensional layout is essential. In both tests check fields, errors, buttons, and the on-screen keyboard; perform the applicable protocol G-09.
  • Pass/fail: text enlargement passes if the text enlarges and stays readable without loss of content and functions. Reflow passes if at 320 CSS px in width or 256 CSS px in height there is no loss of information and functions and no unintended two-dimensional scrolling. A failure is recorded separately for the unfulfilled sub-result.
  • NA/not tested: text enlargement receives NA only for a state without text; reflow receives NA only for a part with an essential two-dimensional layout. If the platform or the test stand does not allow reaching 320 CSS px in width or 256 CSS px in height, the reflow sub-result has the status "not tested", and the nearest size may be recorded only as an additional observation.
  • Minimum evidence: separate paired screenshots and setting values for enlargement; the area size in CSS px, the scroll direction, and a record of the preserved or lost function for reflow.
  • Normative reference: WCAG 1.4.4, 1.4.10, EN 301 549 V4.1.1, 11.1.4.4, 11.1.4.10 and 11.7.
  • Project boundary: the static text size in the package is a selection signal, not a final failure.

V-08. Portrait and landscape orientations

  • Applicability: an application on a device designed for orientation change.
  • Preconditions: the same screen and data, automatic rotation enabled.
  • Steps and parameters: open the screen in portrait orientation, move to the control element, and rotate the device; repeat in the opposite direction; check content, functions, focus, keyboard, and preservation of entered data; separately check the claimed exception.
  • Pass/fail: passes if both orientations are available without loss of content and functions, or a specific orientation is essential; fails on a software prohibition or a loss without essentiality.
  • NA/not tested: NA only for hardware that is not designed for orientation change, or for an absent function; a proven essential orientation is a pass with a justified exception; not tested if rotation is blocked by an external device policy.
  • Minimum evidence: screenshots of both orientations, the state before and after, manifest data as an additional signal, and the justification of the exception.
  • Normative reference: WCAG 1.3.4, EN 301 549 V4.1.1, 11.1.3.4.
  • Project boundary: a portrait design is not evidence of the essentiality of portrait orientation.

V-09. Device motion and an accessible alternative

  • Applicability: shaking, tilting, rotation, camera or user motion that triggers a function.
  • Preconditions: physical device, list of motion functions, and safe test data.
  • Steps and parameters: trigger the function by motion; find and perform the control through the interface; disable the reaction to motion if it does not relate to a supported accessibility function; repeat the action.
  • Pass/fail: passes with an equivalent interface control and the possibility to disable the reaction, except for the criterion's exceptions; fails when motion is mandatory without an alternative or disabling.
  • NA/not tested: NA when there are no motion functions; not tested on an emulator or without the required sensor.
  • Minimum evidence: recording of the motion, the alternative, and the setting, and the outcome of each path.
  • Normative reference: WCAG 2.5.4, EN 301 549 V4.1.1, 11.2.5.4.
  • Project boundary: vibration as feedback is checked separately and is not counted as motion control.

V-10. Contrast and independence from colour

  • Applicability: text, icons, graphics, field borders, focus, and selected, error, and disabled states.
  • Preconditions: screenshots without a system filter overlay, known colours or measurable pixels, and all significant states.
  • Steps and parameters: measure the contrast of normal and large text; large text is taken to be at least 18 pt, or at least 14 pt in bold. Check significant non-text graphics, borders, and component states; for text check the exceptions for logos and incidental text; for non-text elements check the exceptions for inactive or platform-set unchanged components and for essential graphical presentation; enable the claimed colour modes; hide the colour channel and establish whether the meaning remains; perform the applicable protocol G-10.
  • Pass/fail: passes if normal text and images of text have a ratio of at least 4.5:1, large text at least 3:1, and visual information needed to distinguish components, states, and graphical objects at least 3:1 against adjacent colours, or a precise exception is applied; colour is not the only means of conveying meaning. Fails at a lower ratio without an exception or on a loss of meaning without colour.
  • NA/not tested: NA only for an absent kind of content; not tested if the background or state cannot be reliably reproduced.
  • Minimum evidence: screenshot, colour pairs, ratio calculation, state, and the non-colour signal.
  • Normative reference: WCAG 1.4.1, 1.4.3, 1.4.11, EN 301 549 V4.1.1, 11.1.4.1, 11.1.4.3 and 11.1.4.11.
  • Project boundary: system inversion does not remedy insufficient initial contrast in the application.

V-11. Notifications, errors, progress, and status messages

  • Applicability: loading, filtering, results, saving, an error, a background operation, a system notification, and an in-app notification.
  • Preconditions: an approved state in which each message can be triggered safely.
  • Steps and parameters: trigger the message; use the tree and the accessibility service to establish whether its text or other content is programmatically determined without a focus shift; separately, with the screen reader enabled, record the accessible properties, the actual announcement, and the focus; perform an action that changes or dismisses the message and re-check the tree, the focus, and the announced state; open a system notification and check the action and the return; perform the applicable protocol G-07.
  • Pass/fail: the normative sub-result passes if the status message is programmatically determined so that assistive technology can present it without receiving focus; fails on a visual-only message or an unjustified focus shift. The actual announcement is recorded as a separate integration sub-result and does not by itself replace the check of programmatic determinability.
  • NA/not tested: NA for a specific absent kind of message; not tested if triggering it requires a prohibited operation.
  • Minimum evidence: accessible properties and the state of the message before and after the action, a screenshot, the tree node, the focus before and after, and a system notification where applicable; a narration recording is additional evidence for the specific configuration.
  • Normative reference: WCAG 3.3.1, 4.1.3, EN 301 549 V4.1.1, 11.4.1.3 and 11.5.2.15.
  • Project boundary: the actual announcement is useful for integration and user checks, but a failure of a single configuration is not automatically a failure of EN 11.4.1.3 without a check of programmatic determinability.

V-12. Labels, instructions, errors, and correction of a form

  • Applicability: text fields, switches, selection, upload, search, and other forms.
  • Preconditions: empty, filled, error, and corrected states, and safe de-identified data.
  • Steps and parameters: compare the visible and the programmatic label; check the required flag and the format before input; trigger an error; navigate to it with the screen reader; correct the value, resubmit the form, and check the state of the field, the message, and the focus after the error is cleared and after success; perform the applicable protocol G-14.
  • Pass/fail: passes with a persistent label, sufficient instructions, a programmatically associated error, and an accessible correction, if after the correction the previous error is no longer presented as active, the remaining data is preserved, and the successful outcome is detectable; fails on a label that is only a placeholder, a name mismatch, an unassociated or outdated error, data loss, or an inaccessible result.
  • NA/not tested: NA without forms; not tested if a server-side error cannot be triggered safely.
  • Minimum evidence: the state of the field and the error before and after the correction, accessible properties, the focus, the result of the resubmission, and the success state; narration supplements the structured record.
  • Normative reference: WCAG 2.5.3, 3.3.1, 3.3.2, 3.3.3.
  • Project boundary: a message does not have to have a single wording if it accurately identifies the error and the available way to correct it.

V-13. Input purpose, obscured focus, and redundant entry

  • Applicability: fields with supported purposes, author content that can obscure the focused component, and multi-step processes that request previously entered data again.
  • Preconditions: a clean test state, approved de-identified data, the on-screen keyboard, and platform autofill.
  • Steps and parameters: for each supported field, check the programmatically determinable purpose. Open the on-screen keyboard and other author content that overlays, move the focus across fields and actions, and check that the focused component is not completely hidden. In a multi-step process, reach already entered details again and check autofill or the selection of these details, as well as the exceptions for essentiality, security, and the initial invalidity of the data.
  • Pass/fail: the separate normative sub-results pass if the purpose of a supported field is programmatically determinable, the focused component is not completely hidden by author-created content, and previously provided data is not required to be entered again without a precise exception. A failure is recorded for the specific unfulfilled requirement.
  • NA/not tested: NA separately for absent fields with applicable purposes, absent overlay content, or an absent repeat request; not tested without safe data or platform support for the technology.
  • Minimum evidence: the field, the programmatic purpose, the keyboard type, the autofilled value without its secret content, and the final transition.
  • Normative reference: WCAG 1.3.5, 2.4.11, 3.3.7, EN 301 549 V4.1.1, 11.1.3.5, 11.2.4.11 and 11.3.3.7.
  • Project boundary: WCAG2ICT, 1.3.5 is used as an informative note. The system on-screen keyboard belongs to the platform; only overlay created or changed by the application is attributed to the application. Project proposal: the specific on-screen keyboard type and the convenience of autofill are recorded as observations, but they do not constitute a separate normative failure.

V-14. Timing, motion, and flashes

  • Applicability: sessions, one-time actions, disappearing messages, carousels, animation, blinking, and automatically updating content.
  • Preconditions: a known limit, a safe session, a timing tool, and screen recording.
  • Steps and parameters: for each limit check the advance disabling, a setting of at least ten times, a warning of at least 20 seconds with a simple extension of at least ten times, or a precise exception for a real-time event, essentiality, or a limit longer than 20 hours. For motion, blinking, or scrolling that starts automatically, lasts more than five seconds, and runs in parallel with other content, check the pause, stop, or hide if the effect is not essential; for auto-updating content also check the control of the frequency. Review all sliding intervals of one second; with more than three flashes, measure the general and red thresholds. Perform the applicable protocol G-13.
  • Pass/fail: passes if for each limit one normative branch is fulfilled, applicable motion and updating are controllable, and the interface does not create more than three flashes in any one second or the flashes are below the general and red thresholds. Fails on an unfulfilled condition or an exceeded threshold.
  • NA/not tested: NA separately for absent time limits, motion, or flashes; not tested if the waiting or the action cannot be performed on the approved test stand.
  • Minimum evidence: timestamps, the warning, the extension action, the state before and after, a recording of the motion, and the result of the flash measurement.
  • Normative reference: WCAG 2.2.1, 2.2.2, 2.3.1, EN 301 549 V4.1.1, 11.2.2.1-11.2.2.2 and 11.2.3.1.
  • Project boundary: preservation of entered data after a timeout beyond the requirements of the criterion is a Project proposal and is assessed separately.

V-15. Accessible authentication

  • Applicability: sign-in, registration, recovery, a one-time code, a biometric step, and re-authentication.
  • Preconditions: an approved test account, a secure code channel, and protocols D-09 to D-12.
  • Steps and parameters: traverse each step with the screen reader; check paste and autofill; establish the presence of a cognitive test. For each such test check at least one permitted branch: a different authentication method without a cognitive test; a mechanism of assistance during it; recognition of objects; recognition of non-text content previously provided by the user themselves. Check the error, the return, and the repeat; perform the applicable protocols of Section D.
  • Pass/fail: passes if every cognitive test satisfies at least one of the four permitted branches and the whole process is accessible; fails on an inaccessible mandatory step or a cognitive test without an alternative, an assistance mechanism, object recognition, or personal non-text user content.
  • NA/not tested: NA without authentication; not tested without an approved account or a secure way to obtain the code.
  • Minimum evidence: numbered steps without secrets, accessible properties, the branch chosen for each cognitive test, errors, and the outcome.
  • Normative reference: WCAG 3.3.8, EN 301 549 V4.1.1, 11.3.3.8.
  • Project boundary: the procedures of Section D apply additionally. A successful sign-in does not confirm the preservation of accessibility in the further authorized process.

V-16. External keyboard

  • Applicability: an application on a platform and device with support for an external keyboard.
  • Preconditions: a connected keyboard, visible focus, a list of critical functions.
  • Steps and parameters: without touching the screen, traverse the navigation and the scenarios; open and close a dialog; enter and correct text; check navigation, activation, and the return; check single-character shortcuts; perform protocols G-03 and G-11 with the mobile specificity.
  • Pass/fail: passes if all functions that do not depend substantially on a trajectory are available, the focus is visible, and there are no traps; fails on an unreachable action, an invisible focus, or a trap.
  • NA/not tested: NA only with a documented absence of platform support; not tested without a compatible keyboard.
  • Minimum evidence: the key sequence, the focus per step, a recording of the scenario, and any conflict found.
  • Normative reference: WCAG 2.1.1, 2.1.2, 2.1.4, 2.4.3, 2.4.7, EN 301 549 V4.1.1, 11.2.1.1-11.2.1.2, 11.2.1.4, 11.2.4.3 and 11.2.4.7.
  • Project boundary: the external keyboard focus and the screen reader focus are recorded separately.

V-17. Switch control

  • Applicability: an application on a platform with system switch control.
  • Preconditions: configured sequential scanning, one or more switches, a critical scenario.
  • Steps and parameters: start scanning; traverse each element forward and backward in an accessible way; open the actions menu; activate, change the value, and return; check a modal dialog, scrolling, and a virtualized list.
  • Pass/fail: passes if every needed element is reached in a meaningful order, the highlight is distinguishable, the action is performed, and the state is available; fails on a skip, a loop, an inaccessible action, or a loss of the highlight.
  • NA/not tested: NA with a documented absence of the platform function; not tested without a configured input device.
  • Minimum evidence: a recording of the scanning, the order, the highlight, the action, and the state before and after.
  • Normative reference: WCAG 2.1.1, 2.4.3, 2.4.7, 4.1.2, EN 301 549 V4.1.1, 11.2.1.1, 11.2.4.3, 11.2.4.7 and 11.5.2.
  • Project boundary: the requirement to check system switch control in the minimum matrix is a Project proposal.

V-18. System accessibility settings

  • Applicability: all applications that are not isolated from the platform.
  • Preconditions: configurations of the screen magnifier, contrast or inversion, enlarged text, and reduced motion.
  • Steps and parameters: traverse the same scenario in each configuration. Sub-result 11.6.2: check whether the application disrupts the normal operation of a documented accessibility function and whether such disruption was explicitly requested by the user during the work. Sub-result 11.7: check compliance with the user's preferences for documented functions and separately justify the essentiality of any deviation. Perform the applicable protocol G-08.
  • Pass/fail: sub-result 11.6.2 passes if there is no disruption or if it was explicitly requested by the user; the essentiality exception does not apply here. Sub-result 11.7 passes if the preferences are respected or if it is proven that the deviation is essential for the application function. A failure is recorded for the specific sub-result.
  • NA/not tested: NA only for a specific function absent on the platform; not tested without the required device or setting.
  • Minimum evidence: the setting values, paired screenshots or recordings, the actual behaviour, the user's request for the 11.6.2 exception, or a separate essentiality justification for 11.7.
  • Normative reference: EN 301 549 V4.1.1, 11.6.2 and 11.7.
  • Project boundary: the expectation of compliance with an undocumented setting is not introduced without an adopted additional profile.

V-19. System dialogs, permissions, and return

  • Applicability: camera, microphone, geolocation, files, notifications, external settings, and other system requests.
  • Preconditions: a reset permission, an explanation of the purpose, and the states of consent, refusal, and a repeated request.
  • Steps and parameters: reach the function without the permission; open the system dialog; choose consent and refusal in separate runs; go to the settings if necessary; return and check the focus order and the absence of an unexpected change of context. Separately record the responsibility of the platform for its own dialog. With the project profile enabled, check the explanation of the purpose before the request, and after a refusal and a return check the absence of a dead end and the preservation of the context, data, and focus. Perform protocols G-06 and G-07.
  • Pass/fail: the normative sub-results pass if the application preserves the meaningful focus order and does not cause a change of context on focus or on a change of value alone. The accessibility of the system dialog is assessed as a property of the platform and is not attributed to the application. Project proposal: a clear explanation before the request, the absence of a dead end after a refusal, and the preservation of the context, data, and focus form a separate project sub-result only when the profile is enabled.
  • NA/not tested: NA without permissions and system transitions; not tested if a device policy blocks a change of the permission.
  • Minimum evidence: the screen before the request, the system dialog, both outcomes, the focus order, and the state after the return; the project conditions are recorded separately from the normative ones.
  • Normative reference: WCAG 2.4.3, 3.2.1, 3.2.2, EN 301 549 V4.1.1, 11.2.4.3, 11.3.2.1 and 11.3.2.2.
  • Project boundary: the conditions of comprehensibility, of the absence of a dead end, and of data preservation are wider than the listed normative clauses and are a Project proposal. The responsibility of the application and of the platform is not combined into a single normative result.

V-20. Embedded web views

  • Applicability: web content embedded in the application, including sign-in, help, payment, and external content inside the container.
  • Preconditions: a known boundary between the native and the web layer, approved addresses, and the applicable protocols of Section A.
  • Steps and parameters: start on the native screen; switch to the web view; perform the applicable A procedures for the content and match each sub-result with the exact normative clause of EN 11.x; check the container, the heading, the traversal, the keyboard, the return, the opening of an external application, and the preservation of the context; repeat with the screen reader.
  • Pass/fail: passes if the content meets the applicable normative requirements of Section 11 of EN 301 549, checked by the A procedures, the container meets the applicable B cards, and the boundary does not break the control and the context; a failure is recorded against the exact clause 11.x without double counting under Section 9 of EN 301 549.
  • NA/not tested: NA without web views; not tested without a network, a role, or approved access.
  • Minimum evidence: the address or a stable content identifier, the layer boundary, the focus sequence, the results of the applicable A checks, and the return.
  • Normative reference: the applicable exact normative clauses EN 301 549 V4.1.1, 11.1-11.4, as indicated for each sub-result.
  • Project boundary: the informative EN 11.0 defines the scope, and WCAG2ICT explains the transfer of web criteria, but they are not a normative basis for the result. Section A is used as the verification procedure for web semantics; the embedded view remains part of the B result and is not counted twice.

V-21. Audio and video

  • Applicability: recorded and live audio, video, synchronized media, and an embedded player.
  • Preconditions: a known language and the full set of declared alternatives. Project proposal: the sample includes at least one accessible instance of each identified kind: recorded audio without video, recorded video without sound, recorded synchronized media, and live media; the completeness of the instances is determined by B.3.
  • Steps and parameters: check the transcript, subtitles, audio description, or media alternative separately according to the applicable criterion; control playback by touch, by screen reader, by external keyboard, and by switches; change the orientation and the subtitle text size.
  • Pass/fail: passes if every required alternative is available, synchronized, and controllable; fails on a missing alternative or inaccessible control.
  • NA/not tested: NA separately for an absent kind of media; not tested with an unavailable broadcast, track, or state.
  • Minimum evidence: a media fragment, the kind of alternative, timestamps, the controls, and a recording of their use.
  • Normative reference: WCAG 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5.
  • Project boundary: each alternative receives a separate result; the presence of subtitles does not replace an audio description and vice versa.

V-22. Error prevention, confirmation, reversal, and redundant entry

  • Applicability: a legal, financial, payment, or other significant action, a change or deletion of user data, and a multi-step form.
  • Preconditions: an approved test stand, reversible test data, known consequences, protocol G-19, and the applicable checks of Section D.
  • Steps and parameters: enter the data; proceed to the confirmation; check the review and the correction; cancel or reverse the action; return to the previous step; reuse already entered details; check the erroneous and the interrupted variants without a real irreversible outcome.
  • Pass/fail: passes if the applicable error prevention condition is fulfilled, the action is available to confirm or cancel, and redundant entry is not required without an exception; fails on an irreversible outcome without protection or on mandatory redundant entry.
  • NA/not tested: NA without significant actions and redundant entry; not tested without an approved test stand or a reversible scenario.
  • Minimum evidence: the steps up to the confirmation, the review, the correction, the cancellation, the state of the data, and the reason for stopping before the prohibited action.
  • Normative reference: WCAG 3.3.4, 3.3.7, EN 301 549 V4.1.1, 11.3.3.4 and 11.3.3.7.
  • Project boundary: the procedures of Section D apply additionally. The test does not require a real payment, submission, or deletion; a result that is safely unreachable receives the status "not tested".

Result matrix

The overall result for the application contains, for each "platform + application version" pair, the list of the checked screens and states, the result of V-01 to V-22, the configuration, the evidence, and the limitation. A failure in at least one claimed configuration is not averaged with a pass in another. A general conclusion is allowed only within the platforms, devices, versions, roles, and scenarios actually checked.