NormflussDocument accessibility platform

Standard

Document accessibility

Document accessibility is the practice of building a document so that people with disabilities can perceive, navigate, and understand its content using assistive technology — screen readers, braille displays, screen magnifiers, and voice-control software. An accessible document conveys the same information, structure, and functionality to someone who cannot see the page, cannot use a mouse, or reads through synthetic speech as it does to a sighted reader looking at the visual layout.

The distinction that matters is between how a document looks and how it is structured underneath. A PDF or Word file can look perfectly readable on screen while being meaningless to a screen reader, because the visual appearance (a bold line that looks like a heading, columns that read left-to-right, a scanned image of text) carries no machine-readable meaning. Accessibility is about the invisible layer: the tags, the reading order, and the semantic structure that tell assistive technology what each part of the document actually is.

An accessible document is a Tagged document with a complete and correct logical structure. In practice that means headings are marked as headings (not just large text), lists and tables are marked up so their relationships survive, the reading order is defined explicitly rather than inferred from position, every meaningful image carries alternative text describing it, the natural language of the content is declared so speech synthesis pronounces it correctly, and decorative elements are marked as artifacts so they are skipped rather than read aloud. For documents with forms, fields must be labelled and operable by keyboard.

Document accessibility is governed by two complementary standards. WCAG (the Web Content Accessibility Guidelines) describes the accessible outcome in format-agnostic terms, while PDF/UA (ISO 14289) specifies precisely how those outcomes must be engineered into a PDF file. Legally, accessible documents are increasingly required: in the EU the European Accessibility Act reaches many customer-facing business documents, and public-sector bodies across Europe and the UK must publish accessible documents under web-accessibility rules. Accessibility is not an all-or-nothing badge — it is measured against specific, testable technical criteria, some of which a machine can verify and some of which need human judgement.

How Normfluss checks for it

Normfluss checks a document against the technical criteria that underpin accessibility: it confirms the file is tagged, verifies the structure tree is complete and correctly nested, checks reading order, and detects missing alternative text, untagged content, an undeclared language, and improperly marked decorative elements. The machine-testable criteria are automated; judgement calls such as whether alt text is meaningful or the reading order makes sense are routed to human review. Every check is recorded, so the result is a signed evidence record of exactly what was tested — conformance within a stated scope, not a legal-compliance determination.

Frequently asked questions

What are accessible documents?
Accessible documents are files built so that people using assistive technology — screen readers, braille displays, magnifiers, voice control — can read and understand the same content a sighted reader sees. That depends on the document's underlying structure (tags, reading order, alternative text, declared language), not just how it looks on screen.
What is document accessibility?
Document accessibility is the practice of structuring a document so its meaning survives for assistive technology. A file can look readable yet be inaccessible if its headings, tables, reading order, and images carry no machine-readable meaning underneath.
What are the four types of accessibility?
Accessibility is commonly grouped by the barriers it addresses: visual (blindness, low vision, colour perception), auditory (deafness, hard of hearing), motor (limited dexterity, keyboard-only use), and cognitive (learning, attention, memory). WCAG's four principles — Perceivable, Operable, Understandable, Robust — map guidance across all of these.
How do I know if a document is accessible?
You check it against the technical criteria that underpin accessibility — whether it is tagged, has a correct reading order, provides alternative text for images, declares its language, and structures headings, lists and tables correctly. Automated tools verify the machine-checkable criteria; the rest, such as whether alt text is meaningful, need human review. A free automated check is the fastest way to see where a document stands.

Related