Test Protocols for Electronic Documents

  • Version: 0.1
  • Date: 23 September 2026
  • Status: an appendix to the assessment methodology, a draft for discussion and piloting. This is not an approved standard, a normative legal act, or a certificate.
A document’s visual presentation is connected to its structure and reading order.

Download the document (DOCX)

Why protocols are needed and how to use them

This appendix sets a single procedure for the checks B-01 to B-17 of Section B "Accessibility Assessment Methodology for Digital Resources". The methodology defines the scope, inventory, sample, configurations, evidence and severity; this file defines the actions of the assessor for each selected unit.

Every applicable check ends with exactly one status:

  • pass: all conditions of the card are met across the whole checked area;
  • fail: at least one confirmed applicable case of non-compliance was found;
  • NA: the object or function is absent, the reason is recorded;
  • not tested: applicability or the result could not be established because the file, configuration, state or evidence was unavailable. This status is not counted as a pass.

The minimum result record always contains the document ID and checksum, the source page or the way the document was produced, the format and version, the number of the page, slide, sheet, section or object, the configuration, the steps, the actual result, the date, the assessor and a link to the evidence. An automatic signal from B.6 does not replace the steps of the card. If the format does not allow a specific technical step to be performed, the assessor applies an equivalent software representation and records the deviation.

The normative reference shows the basis of the check. WCAG2ICT is an informative explanation of the application of WCAG to non-web documents. The "Project boundary" field separates the condition of the source from a stricter project rule. Such a rule operates as a Project proposal only after it has been included in an adopted profile.

Protocols

B-01. Tagged structure and reading order

  • Applicability: documents with visual structure, several blocks, columns, insets, footnotes, floating objects or a traversal order.
  • Preconditions: the source file, a viewer or editor with access to the software structure, a screen reader; for PDF, access to the tag tree.
  • Steps and parameters: map every meaningful visual block to a software role; read the document sequentially with a screen reader and extract the text separately; check columns, captions, footnotes, headers and footers, floating objects and the keyboard traversal order. Use an automatic indication of the presence of a tag tree only to select the manual steps.
  • Pass/fail: passes if the structure is programmatically determinable, the logical sequence matches the visual sequence and decorative content does not interrupt reading; fails if structure is absent, the role is wrong, or the sequence changes meaning.
  • NA/not tested: NA only for a unit with no meaningful structure and sequence; not tested if the software representation or the required configuration is unavailable.
  • Minimum evidence: page and object, snapshot, fragment of the tag tree or of the properties, the actual reading sequence and the expected sequence.
  • Normative reference: WCAG 1.3.1, 1.3.2, PDF3, EN 301 549, clause 10.
  • Project boundary: a requirement for a specific set of tags beyond the necessary semantics is not introduced without an adopted profile standard.

B-02. Headings

  • Applicability: documents with visual titles for sections, chapters, slides or blocks.
  • Preconditions: the software structure, the heading navigation mode and the visual presentation.
  • Steps and parameters: compile the visual and the software hierarchies; navigate through all headings with a screen reader; check that the text describes the following section, that the levels reflect nesting, and that empty paragraphs and emphasised ordinary text do not stand in for headings.
  • Pass/fail: passes with programmatically identified descriptive headings and a consistent hierarchy; fails if a visual heading cannot be determined programmatically, a level distorts the structure, or a programmatic heading is empty.
  • NA/not tested: NA for a short document without sections; not tested without access to the software structure.
  • Minimum evidence: section or slide number, snapshot, list of headings with levels and a fragment of the structure.
  • Normative reference: WCAG 1.3.1, 2.4.6, PDF9.
  • Project boundary: a sequence with no skipped level is a recommended practice, but the result is determined by preservation of the relationships and comprehensibility of the hierarchy.

B-03. Lists

  • Applicability: bulleted, numbered, multilevel lists and enumerations that are visually presented as a list.
  • Preconditions: the visual and software representations, the possibility of linear reading.
  • Steps and parameters: match the list boundaries, the items, the markers, the numbers and the nesting; check the announced start, the number of items and the number of levels; make sure a number is not a separate unrelated paragraph and that ordinary paragraphs are not mistakenly included in the list.
  • Pass/fail: passes if the list and its items are programmatically determinable and the order and nesting preserve meaning; fails if the structure is conveyed only by spaces, characters or visual indentation.
  • NA/not tested: NA when there are no enumerations; not tested when the software structure is unavailable.
  • Minimum evidence: page, snapshot of the list, tree or properties of the items and the actual announcement.
  • Normative reference: WCAG 1.3.1, PDF21.
  • Project boundary: the choice of marker type and formatting beyond preservation of the relationships is not normalised.

B-04. Tables

  • Applicability: data tables and visual grids in which the position of a cell conveys a relationship.
  • Preconditions: the source table, the software structure, a screen reader; a known purpose for the headers.
  • Steps and parameters: identify the header rows and columns, the spans and the multi-level relationships; move through the cells with the keyboard and a screen reader; for each test cell, establish the available headers; check that a layout table is not declared as a data table and vice versa.
  • Pass/fail: passes if the cells, headers and relationships are programmatically determinable and preserve meaning; fails with missing headers, incorrect spans, a mixed order, or the use of spaces instead of structure.
  • NA/not tested: NA without data tables; not tested if a complex relationship cannot be established in the available configuration.
  • Minimum evidence: sheet or page, range, snapshot, fragment of the structure and a "data cell - declared headers" pair.
  • Normative reference: WCAG 1.3.1, PDF6.
  • Project boundary: repeating the header row when printing is a Project proposal if it is not required by the adopted profile.

B-05. Alternative text for images and diagrams

  • Applicability: images, schemas, charts, maps, formulas, icons and decorative graphical objects.
  • Preconditions: the visual object, its context, the software alternative and information about the purpose.
  • Steps and parameters: classify the object as meaningful, functional, complex or decorative; hide the image or read only the software representation; check the transfer of the same information or purpose; for a complex object, check the brief identification and the availability of the full description; make sure decoration is excluded from reading.
  • Pass/fail: passes with an equivalent alternative and correct handling of decoration; fails with an alternative that is absent, empty for a meaningful object, a file reference, duplicating the text, or semantically incorrect.
  • NA/not tested: NA without graphical objects; not tested if the purpose or the content cannot be established.
  • Minimum evidence: object and page, snapshot, the alternative text, a fragment of the software structure and an explanation of the equivalence.
  • Normative reference: WCAG 1.1.1.
  • Project boundary: the literary quality of the description beyond equivalent information is tested separately with users.

B-06. Document language and language of fragments

  • Applicability: all documents with natural language; a separate check of fragments where the language differs from the main one.
  • Preconditions: access to the language properties of the document and of the text, a screen reader supporting the languages used.
  • Steps and parameters: determine the actual main language; compare it with the programmatic default language; find phrases, quotes and blocks in another language; check their properties and the actual switch of pronunciation. Assess names, technical terms and words of undetermined language taking the WCAG exception into account.
  • Pass/fail: passes if the main language and the applicable fragments are programmatically determined correctly; fails if a language is absent, has a wrong value, or a differing fragment is not marked.
  • NA/not tested: NA for a document with no linguistic text; not tested without a configuration able to observe the programmatic language.
  • Minimum evidence: the document language property, the fragment and its property, the actual announcement in the stated configuration.
  • Normative reference: WCAG 3.1.1, 3.1.2, PDF16, PDF19.
  • Project boundary: a single format of language codes beyond programmatic determinability is not prescribed.

B-07. Document title

  • Applicability: documents whose format supports a programmatic title; a separate display step applies to PDF.
  • Preconditions: the document properties and the initial view settings of the PDF.
  • Steps and parameters: open the properties; check for a non-empty editable title describing the subject or purpose; compare it with the content; for PDF, establish whether the catalogue prescribes showing the document title instead of the file name, and observe the title bar of the viewer.
  • Pass/fail: passes with a descriptive programmatic title and, for PDF, a prescription to show it instead of the file name; fails with an empty, technical, outdated or non-displayed title.
  • NA/not tested: NA only if the format does not support a programmatic title; not tested if the properties are unavailable or the viewer does not allow the result to be observed.
  • Minimum evidence: file name, programmatic title, display property and a snapshot of the observed title.
  • Normative reference: EN 301 549, 10.2.4.2, PDF18.
  • Project boundary: matching the title to the file name is not required if the title describes the subject or purpose.

B-08. Bookmarks, table of contents and navigation

  • Applicability: long documents with sections for which sequential scrolling is not a sufficient way to find a place.
  • Preconditions: a visible table of contents, a bookmarks panel or another software navigation mechanism.
  • Steps and parameters: identify the main sections; go through every table of contents entry and a representative set of bookmarks with the keyboard; check the title, the hierarchy, the order, the target and the return; match the set against the headings and check the update after editing the document.
  • Pass/fail: passes with a working software means of navigating to the main sections and a consistent structure; fails with navigation absent in an applicable document, broken targets, substantial omissions or an incorrect order.
  • NA/not tested: NA for a short document that does not need additional navigation; not tested without the possibility to open the mechanism or the target.
  • Minimum evidence: the volume of the document, the list of entries, the source entry and the actual target, a snapshot or a record of the sequence.
  • Normative reference: WCAG 2.2 has no direct requirement for navigation inside a single document: criterion 2.4.5 applies to a set of pages or documents, and EN 301 549, 10.2.4.5 does not apply it to a single document. This check is a project proposal based on the advisory technique PDF2; a "fail" result under B-08 does not mean non-conformance with WCAG.
  • Project boundary: Project proposal: a document of 20 pages or more, or with three or more levels of structure, is considered long, unless the profile has set another threshold.
  • Applicability: external and internal links, links in the table of contents, email addresses and graphical links.
  • Preconditions: permitted access to the targets, a keyboard and a screen reader.
  • Steps and parameters: obtain the list of links; for each, check the accessible name and the software role and, for ambiguous texts, the surrounding context; navigate with the keyboard; compare the stated and the actual target; check the internal destinations and the distinction between adjacent links with identical text.
  • Pass/fail: passes if the purpose is clear from the name and the context, the link is reachable by keyboard and leads to the stated target; fails with an unclear purpose, a missing software role, an unreachable or wrong target.
  • NA/not tested: NA without links; not tested if an external target is temporarily unavailable and the purpose cannot be confirmed.
  • Minimum evidence: page and link text, accessible name, context, address or internal destination and the actual result of the navigation.
  • Normative reference: WCAG 2.4.4, PDF11.
  • Project boundary: a requirement for unique text for each link beyond sufficient context is additional.

B-10. Contrast

  • Applicability: text, images of text, borders and field states, meaningful parts of charts and other applicable graphics.
  • Preconditions: the source presentation without snapshot smoothing, a colour determiner, information about the size and weight of the text.
  • Steps and parameters: measure the foreground and background colours in the normal and applicable states; calculate the contrast; check ordinary and large text, form components and meaningful graphics separately; apply the exact exceptions of the criteria; check the high contrast mode by observation.
  • Pass/fail: passes with a ratio of at least 4.5:1 for ordinary text, 3:1 for large text and 3:1 for applicable components and graphics; fails with a lower ratio outside the exceptions.
  • NA/not tested: NA only for objects fully covered by the exceptions; not tested if the source colours or the size cannot be reliably established.
  • Minimum evidence: page and object, states, colour values, text size, the ratio calculation and the exception applied.
  • Normative reference: WCAG 1.4.3, 1.4.11.
  • Project boundary: machine extraction of the colour without visual confirmation is not sufficient evidence.

B-11. Text as text, not an image of text

  • Applicability: images containing text, including page scans, banners, captions in schemas and interface screenshots.
  • Preconditions: the visual presentation, the possibility to select, copy, zoom and change the rendering of the text.
  • Steps and parameters: identify the text fragments; attempt to select them character by character and to change the size or the formatting independently of the image; establish whether the particular presentation is essential or customisable; do not treat an invisible recognised layer as sufficient if the user still sees an unchangeable image of text.
  • Pass/fail: passes if text is used to convey the information or the essential/customisable exception has been applied; fails with an image of text and no permitted exception.
  • NA/not tested: NA without images of text; not tested if the original purpose of the presentation is unknown.
  • Minimum evidence: page, snapshot, the result of the selection and of the settings, the justification for the applicability of the exception.
  • Normative reference: WCAG 1.4.5.
  • Project boundary: logos and essential visual presentations are assessed under the exceptions of the criterion and are not banned by the project.

B-12. Fonts, text extractability and scans

  • Applicability: all documents with text, especially scans, non-standard fonts, formulas and documents with copy errors.
  • Preconditions: the source file, character-by-character selection, text extraction, a screen reader; for a scan, the visual original.
  • Steps and parameters: on each selected page, check for the presence of a text layer; copy representative fragments containing letters, digits, signs and tables; compare the characters, the order and the spaces; read with a screen reader; for a recognised scan, compare all critical text and a sample of the rest with the image.
  • Pass/fail: passes if the text is extractable and readable in the correct encoding and order, and the recognition does not change meaning; fails with an absent layer, substituted characters, a meaningless order or significant recognition errors.
  • NA/not tested: NA for a document without text; not tested if the file is damaged, protected, or the volume of recognition does not allow a justified conclusion.
  • Minimum evidence: pages, the source snapshot, the extracted fragment, the list of substitutions and the actual announcement.
  • Normative reference: WCAG 1.1.1, 1.4.5, PDF7 (the technique relates to 1.4.5 and 1.4.9).
  • Project boundary: automatic text detection reports only the presence of extractable characters and does not confirm the accuracy of the recognition.

B-13. Fillable fields and their labels

  • Applicability: interactive fields, toggles, check boxes, lists, buttons and submission or signing actions.
  • Preconditions: a safe copy or a permitted test environment, test data, a keyboard, a screen reader and a reset procedure.
  • Steps and parameters: go through all the elements with the keyboard only, forwards and backwards; for each, check the name, role, state, value, requiredness, format and instruction; fill in correct and erroneous values; check the error message, the correction, the saving of the data and the final action, without a real submission if it is irreversible.
  • Pass/fail: passes with a logical order, programmatic labels, accessible states, and entry and correction without a mouse; fails with an unlabelled field, a trap, a wrong order, an inaccessible error or a mandatory use of the mouse.
  • NA/not tested: NA without an interactive form; not tested if safe execution or the required configuration is absent.
  • Minimum evidence: object and page, the key and focus sequence, the programmatic name/role/value, the test data and the observed result.
  • Normative reference: WCAG 2.1.1, 3.3.2, 4.1.2, PDF10, PDF23.
  • Project boundary: an actual electronic signature, a payment or a legally significant submission is not performed without separate explicit permission.

B-14. Protection does not hinder assistive technologies

  • Applicability: documents with encryption, a password, a copying restriction, an electronic signature, a watermark or other protection.
  • Preconditions: a lawful way to open the document, the stated configuration, information about the file permissions.
  • Steps and parameters: record the type of protection and the software permissions; open the document in a permitted way; check reading, navigation, search, selection, filling in and access to the alternatives with a screen reader; do not bypass a password or a technical protection.
  • Pass/fail: passes if the protection does not block the applicable actions of an assistive technology; fails if a user who is entitled to open the document cannot read or use it because of the restrictions.
  • NA/not tested: NA when there is no protection; not tested without lawful access, a password or the stated assistive configuration.
  • Minimum evidence: the type of protection and the permissions, the configuration, the permitted steps and the specific blocked action.
  • Normative reference: EN 301 549, clause 10.
  • Project boundary: the absence of encryption is not a requirement in itself; the effect of the applied protection is what is assessed.
  • Applicability: a document for which the page offers a web version, another format or a corrected accessible alternative; also a document used as an alternative to web content.
  • Preconditions: the source page, the document and the stated alternative of the same revision.
  • Steps and parameters: find the link in both directions, if they are stated; compare the purpose, all essential text, tables, images, functions, language, date and version; check that the link is reachable with the keyboard and without an inaccessible preliminary step; apply the requirements of the corresponding version of WCAG to the alternative.
  • Pass/fail: passes if the alternative is reachable, equivalent, has the same language and currency, performs the same functions and meets the target level; fails with a hidden link, an incomplete, outdated or functionally unequal version.
  • NA/not tested: NA if the alternative is not stated and the document is checked directly; not tested if one of the versions is unavailable or its revision is unknown.
  • Minimum evidence: the page and both links, the versions and dates, a table of the differences in content and functions, the result of the reachability check.
  • Normative reference: WCAG, conformance requirements 1 and 4, G136.
  • Project boundary: Project proposal: if the alternative version is the only way of access, the link to it is placed next to the main link to the document and names the format explicitly.

B-16. Zoom, high contrast and reflow

  • Applicability: documents whose program and format support zoom, system colours or reflow; for the others, the available functionality and the limitation are recorded.
  • Preconditions: the configuration from B.4, the original scale, the high contrast mode or system colours, reflow or the narrowest supported width.
  • Steps and parameters: zoom to 200%; enable system colours; enable reflow or the minimum supported width; read and use representative pages, tables, images, links and the form; check for clipping, overlapping, loss of order, the need for two-dimensional scrolling and inaccessible elements.
  • Pass/fail: passes in the stated supported configuration without loss of content and function; fails with the loss or overlapping of applicable content, or the impossibility of an action because of the zoom or the display mode.
  • NA/not tested: NA for a specific capability that is objectively unsupported by the format and is not part of the adopted profile; not tested without the stated configuration. An NA for one capability does not remove the remaining steps.
  • Minimum evidence: the configuration, the scale and the width, the source and the modified snapshots, the object and a description of the loss or of the confirmed behaviour.
  • Normative reference: WCAG 1.4.4, 1.4.10, WCAG2ICT.
  • Project boundary: the methodology does not declare universal reflow support for every file format; the obligation is determined by the adopted profile and by the technical capabilities of the format.

B-17. Not only colour, shape or position

  • Applicability: documents with instructions, forms, tables, charts, legends, status or value highlighting.
  • Preconditions: the document in the configuration from B.4; a list of the places where colour, shape, size or position carry meaning.
  • Steps and parameters: find the instructions that refer to colour, shape or position ("fill in the fields marked in red", "see on the right"); check the required form fields, the highlighted values in tables, the lines and the areas of charts; view the document in shades of grey or with system colours; compare whether the same meaning is available in text or as a programmatic indication.
  • Pass/fail: passes if every such meaning is also conveyed by text, a label, a symbol or a programmatic indication; fails if the meaning is lost without the perception of colour, shape or position.
  • NA/not tested: NA when there are no places where colour, shape or position carry meaning; not tested without the possibility to view the document in a mode without colour.
  • Minimum evidence: the place in the document (page, object), a quotation of the instruction or a description of the highlighting, a snapshot in colour and without colour.
  • Normative reference: WCAG 1.3.3, 1.4.1.
  • Project boundary: the contrast of the colours themselves is checked in B-10; this check concerns only whether the meaning is conveyed in another way than by colour, shape or position.