Desktop software test protocols

  • Version: 0.1
  • Date: 23 September 2026
  • Status: appendix to the assessment methodology, a draft for discussion and piloting. It is not an approved standard, a normative legal act, or a certificate.
The keyboard focus route connects a toolbar, a list and a desktop application dialog.

Download the document (DOCX)

Why protocols are needed and how to use them

This appendix sets a single procedure for tests G-01-G-29 of Section G "Desktop software" of the "Methodology for assessing the accessibility of digital resources". The methodology defines the object, the inventory, the sample, the configurations, the evidence, the severity, and the limits of the conclusion. This file defines the actions of the assessor in the selected window, mode, or scenario.

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

  1. any applicable failure gives the final result "fail";
  2. if there are no failures, but at least one applicable sub-result was not tested, the final result is "not tested";
  3. if at least one applicable sub-result passed, the others passed or have a justified NA, the final result is "pass";
  4. a final NA is admissible only when all sub-results have a confirmed NA.

Thus, the combination NA + pass gives one final pass, and NA + fail gives one final fail. A pass means that all applicable conditions of the card are fulfilled for the entire selected unit. A partial NA is not recorded as a second card status. "Not tested" applies when access, state, configuration, or evidence is insufficient and is not counted as a pass.

The minimum record contains the version and build of the application and of the platform, the configuration, the sampling unit, the initial state, the steps, the input, the expected and the actual result, the date, the assessor, and a link to the evidence. Accessibility tree inspection does not replace manual testing. The normative reference shows the basis, and the "Project boundary" field separates the operationalization and the project proposal from a direct requirement of the source.

Protocols

G-01. Name, role, state, value, relationships, and actions

  • Applicability: all interactive objects and the programmatically significant parts of the selected windows.
  • Preconditions: the platform accessibility tree inspector, a screen reader, the states before and after the change.
  • Steps and parameters: successively obtain the role, name, description, state, value, relationships, boundaries, and the list of actions; change every available state and value; perform the action through ordinary input and through the programmatic interface.
  • Pass/fail: passes if the information is accurate, changes synchronously, and the actions available to the user are programmatically operable; fails on a missing, false, or outdated property, or an unavailable action.
  • NA/not tested: NA only for an object with no interactive or semantic meaning; not tested without access to the platform programmatic interface.
  • Minimum evidence: an accessibility tree excerpt before and after the action, a snapshot of the object, the command and the result.
  • Normative reference: EN 301 549 V4.1.1, 11.5.2.5-11.5.2.17, WCAG 2.2, 4.1.2.
  • Project boundary: pronunciation by the screen reader without verification of the programmatic properties is insufficient.

G-02. Virtualized content and invisible objects

  • Applicability: editors, grids, trees, and lists that load or reuse objects while scrolling.
  • Preconditions: a set larger than the visible area, a known beginning and end, the tree inspector, and a screen reader.
  • Steps and parameters: traverse the content forward and backward beyond the screen; jump to the beginning, the middle, and the end; trigger the loading; check the hierarchy, the text ranges, the position, the count, and the focus.
  • Pass/fail: passes if all logical objects are reachable, the order is stable, the information is not duplicated, and the focus is not lost; fails on a skip, a false repetition, or a loss of context.
  • NA/not tested: NA for a fully static small view; not tested without a sufficiently large set.
  • Minimum evidence: a log of the transitions with identifiers and positions, tree excerpts before and after the loading.
  • Normative reference: EN 301 549 V4.1.1, 11.5.2.9-11.5.2.10, 11.5.2.13.
  • Project boundary: the requirement to cover objects outside the visible area is a scenario-based operationalization of general programmatic properties.

G-03. Keyboard and absence of traps

  • Applicability: all functions, windows, dialogs, menus, and modes.
  • Preconditions: mouse and touch input are not used; the documented non-standard keys are known.
  • Steps and parameters: traverse each function by sequential and by direct navigation; activate, modify, and close elements; enter and exit each composite component; repeat in the reverse direction.
  • Pass/fail: passes if all the functionality is available from the keyboard and every component can be exited by the usual or by a pre-announced method; fails on an unreachable action or a trap.
  • NA/not tested: NA only for an action that essentially requires a continuous input path; not tested in the absence of the required mode.
  • Minimum evidence: the sequence of keys, focus, and result; a log of the trap or of the unreachable action.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.1-11.2.1.2, WCAG 2.2, 2.1.1, 2.1.2.
  • Project boundary: the list of functions is taken from the inventory of D.2, and not only from the main path.

G-04. Visibility, order, and stability of focus

  • Applicability: all windows with several elements, with scrolling, with pop-up areas, or with updates.
  • Preconditions: keyboard navigation, normal and increased zoom, a known meaningful order.
  • Steps and parameters: record the full order forward and backward; check the visibility and the overlap of the focus; trigger an update, a loading, and a change by a co-author; continue from the previous position.
  • Pass/fail: passes if the order preserves the meaning, the focus is visible and not fully hidden, and an update does not move it without reason; fails on a jump, a skip, an overlap, or a reset.
  • NA/not tested: NA for a window without focusable objects; not tested without the required dynamic state.
  • Minimum evidence: the order table, a focus snapshot, a record of the position before and after the update.
  • Normative reference: EN 301 549 V4.1.1, 11.2.4.3, 11.2.4.7, 11.2.4.11, 11.5.2.13.
  • Project boundary: the absence of a reset of the working context on update or on collaborative change is a Project proposal and is tested only if the corresponding function falls within the scope.

G-05. Menus, panels, ribbons, and complex elements

  • Applicability: menus, ribbons, tabs, panels, trees, lists, expandable items, and similar composite components.
  • Preconditions: a list of components, the keyboard, a screen reader, and the tree inspector.
  • Steps and parameters: enter the component, determine its name and role; move through the child objects; expand and collapse; change the selection; invoke a command; exit and return.
  • Pass/fail: passes if the structure, the current position, the selection, the expansion state, and the available commands are determinable and operable; fails on a function that is visually available but programmatically hidden.
  • NA/not tested: NA for an absent component type; not tested without a state in which it is available.
  • Minimum evidence: a log of keys and messages, a tree excerpt with the structure and the states.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1, 11.4.1.2, 11.5.2.5-11.5.2.17.
  • Project boundary: the names of specific component types are a scenario-based application of the general requirements, and not separate clauses of the standard.

G-06. Dialogs and focus transfer

  • Applicability: modal and non-modal dialogs, confirmation panels, and system selection controls.
  • Preconditions: a known initiator, the initial focus, and the expected continuation after closing.
  • Steps and parameters: open the dialog with the keyboard; establish the first and the active elements; traverse the content; check the boundaries of the modal focus; close by confirmation, by cancellation, and by a system command.
  • Pass/fail: passes if the opening is announced, the focus lands in a logical place, does not leave the modal area, and after closing returns to an understandable context; fails on a loss of control or of context.
  • NA/not tested: NA for a unit without a dialog; not tested if a safe opening is unavailable.
  • Minimum evidence: the focus before, after opening, and after closing, a log of the traversal, a tree excerpt.
  • Normative reference: EN 301 549 V4.1.1, 11.2.4.3, 11.5.2.13-11.5.2.15.
  • Project boundary: the choice of the first element, the retention of the focus in the modal area, and the return to the initiator or to the logical continuation are a scenario-based operationalization of the project.

G-07. Notifications, states, errors, and progress

  • Applicability: saving, search, import, export, collaboration, errors, and long-running operations.
  • Preconditions: safe data for the success and the error cases, a screen reader, an accessibility event log.
  • Steps and parameters: trigger the start, the progress, the completion, and the error; do not move the focus manually; check the programmatic message, the link between the error and the object, the cause, and the way of correcting it.
  • Pass/fail: passes if a significant change is made available in time without unnecessary focus movement, and the error is understandable and linked to the place of correction; fails on a visual-only signal or an unclear error.
  • NA/not tested: NA for a unit without state changes; not tested if the state cannot be triggered safely.
  • Minimum evidence: a record of the event, the time, the message, the focus, and the related object.
  • Normative reference: EN 301 549 V4.1.1, 11.3.3.1-11.3.3.3, 11.4.1.3, 11.5.2.15, WCAG 2.2, 4.1.3.
  • Project boundary: the set of events is taken from the inventory and includes the applicable collaborative changes.

G-08. System accessibility settings

  • Applicability: all windows and modes of the application, except for a documented isolated interface with a justified exception.
  • Preconditions: the baseline configuration, and separate configurations for high contrast, for system colors, for increased text, for the cursor, for the pointer, and for reduced motion.
  • Steps and parameters: change one system setting at a time, restart the application only if this is documented; traverse the mandatory windows; compare the text, the controls, the motion, and the functions.
  • Pass/fail: passes if the application does not break the platform functions and follows the documented settings under the applicable conditions; fails when it ignores them without justification, or when a function is lost.
  • NA/not tested: NA for a setting that does not exist on the selected platform; not tested without permission to change the system.
  • Minimum evidence: the value of the setting, the snapshots before and after, the platform version, and the list of the windows tested.
  • Normative reference: EN 301 549 V4.1.1, 11.6.2, 11.7.
  • Project boundary: reduced motion is mandatory here only as a documented platform accessibility feature; otherwise it is tested as a project proposal.

G-09. Scaling and reflow without loss of functions

  • Applicability: all visual windows, dialogs, and editors.
  • Preconditions: the normal zoom; an increase of the text to 200 percent or to the platform limit, if the limit is lower; a measurable content area for reflow. For vertically scrollable content a width equivalent to 320 CSS px is specified; for horizontally scrollable content a height equivalent to 256 CSS px is specified. In an environment without CSS, the definition of a CSS pixel is used through a visual angle of 0.0213 degrees, and the recalculation method is recorded.
  • Steps and parameters: test the text enlargement and the reflow separately. Increase the text to the selected limit and traverse the mandatory scenarios. Then obtain an area of 320 CSS px in width or of 256 CSS px in height by changing the content zoom, the window size, the resolution, or by means of the platform; check the clipping, the overlap, the commands, the messages, the focus, and the need for scrolling in two dimensions. For each part with two-dimensional scrolling, record whether a two-dimensional layout is necessary for the use or for the meaning; acceptable examples include a map, a diagram, a video, a presentation, a complete data table, and an interface in which a panel and the content must be visible at the same time.
  • Pass/fail: passes if, with enlarged text, the information and the functions are preserved, and if in the reflow configuration there is no loss of information or of functions and no required scrolling in two dimensions, except for the justified parts with a necessary two-dimensional layout. Fails on a hidden command, an inaccessible message, an overlap without a workaround, a loss of a function, or unjustified two-dimensional scrolling.
  • NA/not tested: NA does not apply to a visual application. If the platform does not allow reaching 320 or 256 CSS px, the reflow result has the status "not tested" with the actual nearest size and the reason; the minimum supported window size does not replace the normative threshold.
  • Minimum evidence: the display, zoom, and area parameters in CSS px or a calculated equivalent, the snapshots, the list of two-dimensional exceptions with the justification, and the step that cannot be completed.
  • Normative reference: EN 301 549 V4.1.1, 11.1.4.4, 11.1.4.10, WCAG 2.2, 1.4.4.
  • Project boundary: 400 percent is only a way to obtain 320 CSS px from an initial area of 1280 CSS px, or 256 CSS px from 1024 px. A claim of 400 percent zoom is admissible only for a configuration that was actually tested.

G-10. Contrast and conveyance of meaning

  • Applicability: text, meaningful boundaries, states, icons, charts, and highlighting.
  • Preconditions: the WCAG 2.2 AA profile, normal and high contrast, a colorimeter, a list of the states. Text is considered large at not less than 18 points, or at not less than 14 points in bold, with an equivalent size for other scripts.
  • Steps and parameters: measure the contrast of the normal text, of the large text, and of the required non-text elements; check the exceptions of the profile; switch the color off or apply the system colors; determine whether the name, the state, and the distinguishability are preserved without color.
  • Pass/fail: passes if the normal text has a ratio of not less than 4.5:1, the large text not less than 3:1, and the components, the states, and the graphical objects required for distinguishability not less than 3:1 against the adjacent colors, taking the exceptions of WCAG 2.2 into account; color is not the only visual means of conveying information, an action, a request for a response, or a distinction. Fails on a lower ratio without an exception, or on a loss of meaning without color.
  • NA/not tested: NA for a non-visual object; not tested if the color is produced by an external inaccessible source.
  • Minimum evidence: a snapshot, the color coordinates, the ratio calculation, and a description of the meaning lost.
  • Normative reference: EN 301 549 V4.1.1, 11.1.4.1, 11.1.4.3, 11.1.4.11, WCAG 2.2, 1.4.1.
  • Project boundary: the interface contrast and the contrast of the generated content are recorded separately. The prohibition on using only shape or position acts as a Project proposal if the state is not otherwise determined programmatically.

G-11. Character key shortcuts and conflicts

  • Applicability: all single-character and composite commands of the application.
  • Preconditions: a command registry, the system and the auxiliary combinations of the selected configuration.
  • Steps and parameters: find the combination in the interface or in the documentation; invoke the commands with the focus in different areas; check the disabling, the remapping, or the restriction of the single-character commands; for the other declared combinations, check the available way of remapping or the documented resolution of the conflict; match the combinations against the platform and the assistive technology, reproduce each conflict, and check the result after the resolution.
  • Pass/fail: passes if the combinations are discoverable, the single-character commands are controllable, and a conflict with a critical platform or assistive technology command can be eliminated by remapping, by disabling, or by an available alternative command. Fails on an accidental activation, a hidden combination, an unresolvable conflict, or the loss of a critical command.
  • NA/not tested: NA for an application without such commands; not tested without a selected assistive technology.
  • Minimum evidence: the table "command, context, combination, conflict, setting, result".
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.4, 11.6.2, WCAG 2.2, 2.1.4.
  • Project boundary: the discoverability and the full conflict matrix for all the combinations go beyond the requirement for single-character commands and are a Project proposal.

G-12. Alternative input, dragging, and target size

  • Applicability: pointer actions, dragging, resizing, separators, and small targets.
  • Preconditions: an inventory of the actions, the keyboard and the selected alternative input, the zoom with the recalculation into CSS px.
  • Steps and parameters: perform each drag with the keyboard and with a single pointer without dragging; measure each target smaller than 24 x 24 CSS px and the spacing around it; for each small target check one of the five exceptions: sufficient spacing, an equivalent element of not less than 24 x 24 CSS px in the same application, the target is inside a line of text, the size is set by the platform and is not changed by the application, or a specific size is necessary or prescribed. Separately, by the project rule, repeat the other precise actions with the selected alternative input.
  • Pass/fail: the normative part passes if the dragging has a keyboard method per EN 11.2.1.1 and a single-pointer non-dragging method per EN 11.2.5.7, except for an essential dragging or an action of a lower layer, and each target is of not less than 24 x 24 CSS px or has a documented exception EN 11.2.5.8. Fails on the absence of a required alternative, or on an insufficient size without an exception. Project proposal: any other action passes without precise movement in the selected configuration.
  • NA/not tested: NA for a unit without pointer actions; not tested without an applicable alternative input configuration.
  • Minimum evidence: the action, the alternative sequence, the target sizes, and a snapshot.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.1, 11.2.5.7-11.2.5.8, WCAG 2.2, 2.5.7, 2.5.8.
  • Project boundary: the standalone requirement "without precise movement" does not follow from EN 11.2.5.7-11.2.5.8 and is tested as a Project proposal. Voice and switch input are added when there is an audience or a declared support for it.

G-13. Time, motion, and flashes

  • Applicability: timeouts, autosave with a limit, animation, blinking, automatic transitions, and updates.
  • Preconditions: the known intervals, the test state before the expiry, a means of recording the time and the frames, and the selected method of assessing the general flash and red flash thresholds.
  • Steps and parameters: for each limit check one branch EN 11.2.2.1: disabling in advance; a change of not less than ten times; a warning not less than 20 seconds in advance with a simple extension of not less than ten times; or one of the exceptions for a real-time event, for essentiality, or for a limit of more 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, the stop, or the hiding, if the effect is not essential; for an auto-refresh, also check the control of the frequency. Review the frame-by-frame recording in all the sliding intervals of one second; if there are more than three flashes, measure the general flash and red flash thresholds with the selected analyzer and save its settings.
  • Pass/fail: passes if for each limit one normative branch is executed, the applicable motion and refresh are controllable, and the interface does not produce more than three flashes in any one second, or the flashes are below the general flash and red flash thresholds. Fails on an unfulfilled condition, on a loss of data, or on an uncontrolled effect.
  • NA/not tested: NA in the absence of time, motion, and flashes; not tested if the waiting creates an external consequence.
  • Minimum evidence: a timeline with the selected branch or exception, the settings, a frame-by-frame recording of the effect, the number of flashes, and, if needed, a report of the analyzer on the thresholds.
  • Normative reference: EN 301 549 V4.1.1, 11.2.2.1-11.2.2.2, 11.2.3.1.
  • Project boundary: the local disabling of the optional motion applies as a project proposal, if the system setting is not covered by the source.

G-14. Text input and editing

  • Applicability: input fields and editors of text, of formulas, of notes, and of captions.
  • Preconditions: text in different languages and formats, a screen reader; for an editor of text data, a braille display with routing keys in the configuration from D.4.
  • Steps and parameters: in each editable area read by character, by word, by line, by paragraph, and by page, if the application divides the content into pages; move the caret; extend the selection; modify and undo the text and the formatting; check the announcement of the boundaries and of the attributes. Repeat the reading on the braille display, then, with the routing key of each control cell, move the caret to the corresponding character, including at the beginning, in the middle, and at the end of the line, and beyond the initially visible area.
  • Pass/fail: passes if the text, the formatting, the caret, and the selection are determinable and modifiable in the same ways that are available to the user, the braille output corresponds to the current range, and each tested routing key places the caret in the corresponding position without a loss of context. Fails on a lost position, a hidden change, an incorrect range, or incorrect routing.
  • NA/not tested: NA for a unit without text; not tested for the braille scenario, if it is applicable, when the device is absent.
  • Minimum evidence: the source text, the key sequence, the messages, and the editing result; for the braille scenario the table "area, line, display cell, expected and actual caret position".
  • Normative reference: EN 301 549 V4.1.1, 11.5.2.10, 11.5.2.13-11.5.2.14, 11.5.2.17.
  • Project boundary: the verification of the routing in all the editable areas is a project scenario for a reproducible verification of the text ranges. The absence of excessive speech noise is assessed as a practical obstacle, and not as a separate numeric requirement.

G-15. Text editor scenarios

  • Applicability: an application or a mode for editing text documents.
  • Preconditions: a document with headings, lists, links, a table with headers, with merging, and with nesting, an image, a bookmark, a footnote, a field, a comment, a revision, a revision conflict, a spelling or grammar problem, and a protected area.
  • Steps and parameters: traverse the headings, the lists, the links, the tables, the images, the bookmarks, the footnotes, and the fields; for the table determine the boundaries, the coordinates, the row and column headers, the merging, and the nesting; for the image or the object determine the type, the alternative, the decorative status, and the position. Find and replace text, go to a page and to each result. For a spelling or grammar problem obtain the type, the context, and the correction options without relying only on the underlining. Open a comment and a revision, create a revision conflict, determine the sides and the options, choose a resolution, and check the outcome. Traverse the fields in order, enter the protected area and the read-only area.
  • Pass/fail: passes if the listed structure and properties are available, the search and the navigation preserve a predictable context, the problem and the correction options are available not only visually, the comments, the revisions, and the conflict can be understood and resolved without a pointer, and the order of the fields and the restrictions of the protected mode are named. Fails on a flat reading, an unreachable object, a hidden result, an inaccessible resolution of the conflict, or an unclear protection.
  • NA/not tested: NA for an application without a text editor; an individual feature is NA only when its absence is confirmed.
  • Minimum evidence: the test document, a log of the navigation and the actions, the properties of the table and of the object, a record of the search and of the correction, the conflict before and after the resolution, the order of the fields, and tree excerpts.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.1, 11.5.2.
  • Project boundary: the list of the objects and of the operations is a scenario-based operationalization of the general requirements. The card tests the editor interface; the accessibility of the saved document is assessed separately per Section B.

G-16. Spreadsheet editor scenarios

  • Applicability: an application or a mode for electronic spreadsheets.
  • Preconditions: a workbook with several sheets, with custom row and column headers, with formulas, an error, a comment, a lock, a range, a filter, a chart with several series and categories, source data, a pivot table with a hierarchy, with totals, with groups, with filters, and with slicers, as well as conditional formatting.
  • Steps and parameters: traverse the grid, the rows, the columns, and the sheets; determine the address, the displayed value, the formula, the type, the format, the error, the comment, the lock, and the related custom headers of the active cell. Select a range, obtain its start, its end, and its size, expand and reduce it without a precise pointer, and check the message about the change. Modify a formula through the formula bar, the function wizard, the autocomplete, and a range reference; apply a filter and obtain its presence, its state, and its result without relying only on the color. For the chart obtain the name and the description, traverse the series and the categories, and match the points with the source data. For the pivot table traverse the fields and the hierarchies, expand a group, determine the totals, and change a filter and a slicer without a pointer.
  • Pass/fail: passes if the coordinates, the custom headers, and all the listed cell properties are available in time; the range announces the boundaries, the size, and the changes; the formula tools are available; the filter reports its state and its result not only by color; the chart exposes the series, the categories, and the link to the source data; the fields, the hierarchies, the totals, the groups, the filters, and the slicers of the pivot table are determinable and operable without a pointer. Fails on the loss of any significant property, structure, or command.
  • NA/not tested: NA for an application without a spreadsheet editor; a feature is NA when its absence is confirmed.
  • Minimum evidence: the test workbook, the sequence of the coordinates and of the messages, the properties of the range, of the formula, and of the filter, the trees of the chart and of the pivot table, and the matching of the series and of the categories with the source data.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.1, 11.5.2.6-11.5.2.17.
  • Project boundary: the full set of the properties of the active cell and of the specialized objects is a reproducible project scenario.

G-17. Presentation editor scenarios

  • Applicability: an application or a mode for creating and for showing presentations.
  • Preconditions: a presentation with slides, with text, with an image, with a table with headers, with a chart with series, categories, and source data, with notes, with animation, and with multimedia.
  • Steps and parameters: traverse the list of the slides, the current slide, and the hierarchy of the objects; determine the type, the name, the text, the alternative, the geometry, and the state of the selected object. Change the reading order; move, resize, rotate, align, and group the objects by a numeric or by a keyboard method. Read the table and the chart structurally, traverse the series and the categories, and open the source data without a visual analysis. Open the notes as a separate area, read them, and modify them. Start the show, read the content, control it, and finish it using only the keyboard and a screen reader.
  • Pass/fail: passes if the structure and all the listed properties are available, the order is modifiable, the precise operations have a numeric or a keyboard method, the table and the chart have a structural reading and access to the data, the notes are edited separately, and the show is fully controllable. Fails on an object, a property, an operation, or data that is visually available but programmatically hidden.
  • NA/not tested: NA for an application without presentations; an individual feature is NA when its absence is confirmed.
  • Minimum evidence: the test presentation, a record of the edit and of the show modes, the trees of the selected object, of the table, and of the chart, the numeric values of the geometry, and the access to the source data.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.1, 11.5.2.
  • Project boundary: the list of the objects and of the operations is a scenario-based operationalization of the general requirements. The accessibility of the created presentation is tested separately per Section B.

G-18. Documentation, help, and compatibility

  • Applicability: digital information about the product or the service, if it is provided; the documentation on the product or on the official site, if it exists.
  • Preconditions: access to the supplied and to the online documentation, a list of the declared features and configurations.
  • Steps and parameters: open the documentation with the keyboard only and with a screen reader; find the accessibility features, the ways of enabling them, the supported configurations, the limitations, and the way of obtaining support; perform one instruction.
  • Pass/fail: passes if the provided information is available in its format, and the existing documentation describes the accessibility features, their use, and the way of obtaining support; fails on an unavailable format, on the absence of the required information, or on an instruction that does not work.
  • NA/not tested: NA for a kind of information or of documentation that is not provided; not tested if the applicability or the official source cannot be established.
  • Minimum evidence: the address or the file, the sections found, the step of the instruction, and the actual result.
  • Normative reference: EN 301 549 V4.1.1, 12.1-12.3.
  • Project boundary: the presence of the documentation and the publication of a full compatibility matrix are a Project proposal; EN sets the requirements for the provided information and for the existing documentation.

G-19. Errors, undo, and confirmation

  • Applicability: input, deletion, overwrite, closing without saving, and other actions with a risk of loss.
  • Preconditions: safe test data, the known valid and erroneous values, a process with a repeated request of previously entered or user-provided information.
  • Steps and parameters: trigger an error; determine the object, the cause, and the correction. In the same process, reach the repeated request of previously entered or provided information and check the automatic filling or the available selection; separately check the exceptions for a substantial re-entry, for security, and for a loss of currency. By the project rule, correct the error without re-entering the other unchanged fields. Perform the undo; trigger a dangerous action and check the confirmation.
  • Pass/fail: the normative part passes if the error is named and correctable, and if the information requested again in the same process is filled automatically or is available for selection, except for the three exceptions of EN 11.3.3.7. Project proposal: the other unchanged fields are preserved, and the risky action is reversible or is confirmed before the result. Fails on an unclear error, on an unjustified re-entry, or on an undeclared loss.
  • NA/not tested: NA for a unit without input and without risk; not tested if the action cannot be performed safely.
  • Minimum evidence: the data at the first and at the repeated request, the way of the autofilling or of the selection, or the justification of the exception, the message, the related object, the undo or the confirmation, and the outcome.
  • Normative reference: EN 301 549 V4.1.1, 11.3.3.1-11.3.3.4, 11.3.3.7.
  • Project boundary: the preservation of the other unchanged fields and the confirmation of all the actions with a risk of data loss are a Project proposal and are not attributed to EN 11.3.3.7.

G-20. Built-in accessibility check

  • Applicability: a content creation tool able to detect at least one non-conformity with an applicable requirement of Sections 9, 10, or 11 of EN 301 549. A separate panel, a declared feature, or the name "accessibility check" is not required for the applicability.
  • Preconditions: for each supported type of text document, of spreadsheet, and of presentation in scope, a control file is prepared with a known machine-detectable problem, a warning, and an item that requires a manual check.
  • Steps and parameters: examine all the ways of detecting the problems: a separate check, the object properties, and the messages on editing, on saving, and on exporting. For each type of file run the available mechanisms from the keyboard; match what is found with the control set; distinguish the errors, the warnings, and the manual items, if the tool declares such categories; go to the object, obtain an explanation and a correction suggestion, correct it, and repeat the check.
  • Pass/fail: per EN 5.10.4 it passes if for each non-conformity that the tool is able to detect an accessible way of correction is proposed; fails on a detected problem without a correction suggestion, or on an inaccessible correction. Project proposal: a single mechanism covers all the three editor types in scope, clearly distinguishes the errors, the warnings, and the manual items, and allows going to the object. If this proposal is included in the pilot profile, the absence of any of the listed conditions gives a failure of the project profile.
  • NA/not tested: NA is admissible only after confirming, on the control files and in all the listed mechanisms, that the tool is not able to detect any applicable non-conformity. The absence of a separate or of a declared check function is insufficient for NA. Not tested applies without a control file of at least one type in scope, or with an unavailable state.
  • Minimum evidence: the control files by type, the list of the examined mechanisms, the list of the expected and of the found problems, a record of the correction suggestion, of the correction, and of the repeated result.
  • Normative reference: EN 301 549 V4.1.1, 5.10.4.
  • Project boundary: the completeness of a single mechanism across the editor types, the distinction of the automatic and of the manual items, going to the object, a single indicator, and the unobtrusive hints during the work are a Project proposal.
  • Applicability: editors of structured text, of tables, and of presentations.
  • Preconditions: a new file and a sample with headings, a list, a caption, an order, two languages, and a link.
  • Steps and parameters: assign each property with the keyboard only; read it through the application interface; save, open again, and check the resulting file per B-01-B-03, B-06, and B-09.
  • Pass/fail: passes if the properties are available to the author, are preserved, and are present in the result; fails on a purely visual formatting or on a loss of the semantics.
  • NA/not tested: NA for a format that by its purpose does not support a specific property; not tested without the possibility of examining the result.
  • Minimum evidence: the original and the saved files, the assignment commands, the properties before and after, and the results of the B checks.
  • Normative reference: EN 301 549 V4.1.1, 5.10.1-5.10.3.
  • Project boundary: Section B defines the accessibility of the result; this card tests the ability of the editor to create it.

G-22. Alternative text and complex graphics

  • Applicability: a tool for creating images, charts, and other non-text objects.
  • Preconditions: a simple image, a decorative object, and complex graphics with data.
  • Steps and parameters: assign a short alternative and the decorative status; for a complex object add an extended description or accessible data; save, open again, and check per B-05.
  • Pass/fail: passes if the properties are assigned in an accessible way, are distinguishable, and are preserved; fails on an inaccessible field, on a mixture of the alternative and of the decorative status, or on a loss of data.
  • NA/not tested: NA for a tool without non-text objects; not tested without a format that preserves the properties.
  • Minimum evidence: the files before and after, the properties of the objects in the interface, and the result of B-05.
  • Normative reference: EN 301 549 V4.1.1, 5.10.1-5.10.3.
  • Project boundary: the mandatory extended description or data table for the complex graphics is a project rule based on the nature of the information.

G-23. Creating semantic tables

  • Applicability: a tool that allows the creation of tables.
  • Preconditions: a simple table with headers, and a complex table with merges, with empty separator rows, with hidden data, and with a non-obvious reading order.
  • Steps and parameters: assign the rows and the columns as headers; check the relationships; create in turn a merge, an empty separator row, hidden data, and a non-obvious reading order; for each problem that the tool is able to detect, obtain a warning and a correction suggestion; save, open again, and perform B-04.
  • Pass/fail: passes if the semantics are assigned in an accessible way and are preserved; if the tool is able to detect a merge, an empty separator row, hidden data, or a non-obvious reading order, it offers a correction. Fails on a formatting that is available only visually, or on a detected problem without a correction suggestion.
  • NA/not tested: NA for a tool without tables; not tested without a supported output format.
  • Minimum evidence: the control tables, the properties, the warnings, and the result of B-04.
  • Normative reference: EN 301 549 V4.1.1, 5.10.1-5.10.4.
  • Project boundary: the mandatory warning about a complex table is a Project proposal; the list of the risky structures is defined by the project profile and by the document type.

G-24. Content contrast and accessible templates

  • Applicability: a tool with color settings, with palettes, or with templates.
  • Preconditions: a sample with an insufficient contrast, a gallery of templates, and a declared accessible template.
  • Steps and parameters: detect and correct the contrast; find the template in an accessible way; create a file from it; check the color independence and the applicable B-01-B-17.
  • Pass/fail: passes if a correction is proposed for the detected insufficient contrast, and, when templates exist, at least one of them is accessible, is marked, and supports the creation of accessible content; fails on a detected problem without a correction, or on the absence of such a template.
  • NA/not tested: for the contrast sub-result NA is admissible if the tool does not work with the color, or if it is not able to detect an insufficient contrast; for the templates sub-result NA is admissible if the tool does not provide templates. The final status is determined by the single rule at the beginning of the appendix: a partial NA does not become a status of the card. Not tested applies without a control file, or without an accessible template file, for the applicable sub-result.
  • Minimum evidence: the measurements, the path of the template selection, the created file, and the B protocols.
  • Normative reference: EN 301 549 V4.1.1, 5.10.4-5.10.5.
  • Project boundary: the marking of the template in the gallery and the passing by the created file of all the applicable checks of Section B are project rules.

G-25. Creating multimedia alternatives

  • Applicability: a tool that allows the insertion or the creation of audio and of video.
  • Preconditions: a short media item, the subtitle text, a transcript, and an audio description.
  • Steps and parameters: add and modify each applicable alternative; manage the time codes without a pointer; play back the result with a screen reader; save and open again.
  • Pass/fail: passes if the alternatives are created, edited, played back, and saved in an accessible way; fails on an inaccessible editor, or on a loss of a track.
  • NA/not tested: for each alternative an internal NA is admissible only when it is inapplicable to the selected kind of the material. A final NA is admissible for a tool without multimedia, or when all the alternatives are inapplicable; in the other combinations the final status is determined by the single rule at the beginning of the appendix. Not tested applies in the absence of material for an applicable alternative.
  • Minimum evidence: the original and the saved files, a record of the editing and of the playback, and the properties of the tracks.
  • Normative reference: EN 301 549 V4.1.1, 5.10.1-5.10.3.
  • Project boundary: the set of the alternatives is determined by the type of the material and by the adopted profile of the result.

G-26. Preserving the semantics on re-saving

  • Applicability: opening and saving existing structured files.
  • Preconditions: a control file with headings, with language, with links, with tables, with alternatives, with forms, and with other supported properties.
  • Steps and parameters: check the original file per B; open it, make a neutral change, save it in the same format, open it again, and repeat the same checks; compare the properties.
  • Pass/fail: passes if, under a restructuring or recoding transformation, the supported accessibility information is preserved where the output technology has equivalent mechanisms; fails on the loss of such a property.
  • NA/not tested: NA for a tool that does not open existing files; not tested without an approved control file.
  • Minimum evidence: the original and the re-saved files, the exact change, and a comparative B table.
  • Normative reference: EN 301 549 V4.1.1, 5.10.3.
  • Project boundary: each declared format is checked separately; the result of one format is not transferred to another.

G-27. Exporting an accessible result

  • Applicability: exporting or saving to another format, including PDF.
  • Preconditions: an accessible control source, a file with a known problem, a list of the formats that are able to lose the semantics, the export profiles selected in the profile passport, and the protocols of Section B. For the verification of PDF/UA the profile PDF/UA-1 (ISO 14289-1:2014) is fixed, and the control data are recorded: the tags, the language, the reading order, the alternative text, the headings, and the table structure.
  • Steps and parameters: select the format in an accessible way and, for the PDF in the pilot profile, the explicit profile PDF/UA-1; export the accessible source. Before each export to PDF and to any other format from the list with a risk of losing the semantics, run a check accessible from the keyboard; go to all the detected problems, correct them, or deliberately cancel the export. Repeat with a problem that the tool is able to detect, and check the correction suggestion. Examine the resulting file by the full applicable set of B-01-B-17; for PDF/UA-1 check the claim of the profile and all the control data with a validator and with the manual checks of Section B.
  • Pass/fail: the normative part passes if the export interface is accessible, the supported information is preserved where equivalent mechanisms exist, and a detectable problem receives a correction suggestion. Project proposal: the selected profile PDF/UA-1 is explicitly available and is confirmed on the result; the accessible check is performed before each potentially destructive export and allows correcting the problem or cancelling the export. The result of the file per Section B is recorded separately. Fails on the loss of supported properties, on a detected problem without a correction suggestion, on the absence of the selected profile, or on the skipping of the mandatory check before the export.
  • NA/not tested: NA for a tool without export; not tested if the format or the validator of the result is unavailable.
  • Minimum evidence: the source, the selected format and profile, the list of the risky formats, the record of the check before the export, the corrections or the cancellation, the exported file, the report of the PDF/UA-1 validator, and the full applicable B protocol.
  • Normative reference: EN 301 549 V4.1.1, 5.10.3-5.10.4, GOST R 70176-2022 only for the resulting PDF (a national example from Russia; include it in the project profile where applicable through law, contract or voluntary adoption).
  • Project boundary: the availability of an explicit PDF/UA-1 profile, the mandatory check before the export, and the passing of Section B are a Project proposal. GOST R 70176-2022 is not used as a requirement for the interface or for the conversion process; it relates to the resulting PDF.

G-28. Accessibility regression control

  • Applicability: the repeated testing of a changed version or build.
  • Preconditions: the baseline report, the list of the changes, the critical components, and the result files.
  • Steps and parameters: repeat the corrected defects; traverse the critical scenarios and the affected D checks; compare the accessibility tree; re-check the control export files per Section B.
  • Pass/fail: passes if the corrections are confirmed and there are no new defects in the declared matrix; fails if a defect returns or if there is a new loss of accessibility.
  • NA/not tested: NA for a first assessment without a baseline version; not tested if the previous build or the evidence is unavailable.
  • Minimum evidence: the matrix "version, change, scenario, configuration, previous and new result", the comparison files.
  • Normative reference: Section 8 of Part I of the methodology.
  • Project boundary: the mandatory release control matrix is a Project proposal, and not a separate requirement of the standard.

G-29. Built-in read aloud

  • Applicability: an application with a declared read aloud feature.
  • Preconditions: a document with structure, with a table, with an image, and with a change of the language; the screen reader enabled and disabled separately.
  • Steps and parameters: start and stop the reading from the keyboard; navigate through the text; change the speed and the voice, if declared; check the documentation. Separately enable each documented platform accessibility feature from the configuration, including the screen reader, and determine whether the reading breaks its normal operation and whether such a break was explicitly requested by the user. By the project rule, check the message of the reading position.
  • Pass/fail: passes if the declared feature is fully controllable, is documented, and does not break the documented platform accessibility features, except for a break explicitly requested by the user. Project proposal: the feature reports the reading position. Fails on unavailable commands, or on an unsolicited conflict.
  • NA/not tested: NA in the absence of the feature; its absence is not in itself a failure; not tested without test content.
  • Minimum evidence: a link to the documentation, the key sequence, and a record of the result in both configurations.
  • Normative reference: EN 301 549 V4.1.1, 11.2.1.1, 11.5.2, 11.6.2, 12.3.
  • Project boundary: the presence of a built-in reading is not a universal requirement and does not replace the compatibility with a screen reader. The message of the reading position is a Project proposal.