Built with WCAG 2.2 AA as the target

Accessibility infrastructure for publications

For catalogs with accessible publishing enabled, Creavim generates semantic HTML and two tagged PDFs alongside the visual publication. Heading structure, alternative text, reading order and media alternatives flow from the same content source into each output.

A visual publication and an accessible reading experience. Generated from the same catalog.

Accessibility belongs in the publishing infrastructure

Content being visible on a screen does not make it perceivable or usable for every reader. When heading structure, reading order, image descriptions and media alternatives are not machine-readable, assistive technologies receive an incomplete version of the publication.

01

Visual position does not carry meaning on its own

Screen readers follow semantic structure rather than page geometry. Creavim translates headings, regions, links and content order into real HTML elements in the accessible edition.

02

No parallel copy of the content

The visual publication and accessible edition are generated from the same catalog data. Content is not rebuilt in a separate system, reducing drift between versions and avoiding a second publishing workflow.

03

Access is a measure of publishing quality

Semantic structure, keyboard operation, alternative text and captions are more than technical conformance items. They allow more people to read and use the publication independently.

One source, two reading experiences

The flipbook is the visual publishing surface, preserving page composition, transitions, zoom and interactive hotspots. The accessible edition transforms the same content into semantic, linear HTML for screen readers, keyboard navigation and narrow screens.

Both editions link directly to each other. Catalog, page and section titles become real heading levels, while forms, quizzes and product request lists retain their functionality in the accessible edition.

Accessible PDF (tagged)

When a catalog with the accessible edition enabled is published, two tagged PDFs are generated automatically: a linear reading edition and a print edition that keeps the page design. Heading structure, alternative text, reading order and the document language are embedded in the tag tree of both files, and the text is real text you can select and search.

Readers can download the linear reading PDF from the link at the top of the accessible edition or from the download dialog. Publishers manage both the linear reading and design-preserving print PDFs from the Accessibility tab of the Share dialog.

Accessible publishing tools

Semantic HTML edition

Content reflows into one column with landmarks, real heading levels, a skip link and page navigation. It remains readable at 400 percent browser zoom without horizontal scrolling.

How it works

Alternative text management

Provides alternative text fields and decorative-content flags for images. Gallery items and virtual tours support individual text alternatives.

How it works

Multilingual video captions

Supports WebVTT caption files and multiple languages for the same video. Missing captions are identified during pre-publish checks.

How it works

Reading order control

An initial reading order is derived automatically from the page layout. Block order remains configurable per page for complex compositions.

How it works

Pre-publish accessibility checks

When accessible publishing is enabled, required issues such as missing alternative text or captions block publication. Preflight takes you to the relevant page and block.

How it works

Keyboard operation and announcements

Controls expose clear names and states, while page changes are announced to screen readers. The viewer does not intercept assistive technology navigation shortcuts.

How it works

Contrast against the rendered background

Contrast is measured against what actually renders behind the text, not just the block fill. For text over an image, the editor samples the area under the type and evaluates it against WCAG thresholds; where no machine can decide, the author confirms readability and that confirmation is recorded.

How it works

The standards we check against

Standards-based rules in Publication Check are tied to the relevant clauses in the official documents below. Readability warnings without a fixed standards criterion are kept separate as product recommendations.

A new rule cannot pass the release pipeline until it cites its standards clause or is explicitly classified as a product recommendation; the rule set ships with the product.

  • WCAG 2.2 (Level A, AA)W3C Recommendation

    Web content: the flipbook and the accessible edition. Levels A and AA.

  • ISO 14289-1 (PDF/UA-1)ISO

    Tagged PDF structure: headings, lists, tables, alternative text, language, links.

  • Matterhorn Protocol 1.1PDF Association

    The test protocol for PDF/UA: 31 checkpoints, 136 failure conditions.

  • EN 301 549 V3.2.1ETSI / CEN / CENELEC

    European Union accessibility requirements: web (cl. 9), documents (cl. 10), software (cl. 11).

  • ATAG 2.0W3C Recommendation

    The authoring tool standard: the editor itself and how it helps authors produce accessible content.

  • ARIA Authoring Practices GuideW3C WAI

    Behaviour patterns for components such as dialogs, galleries and sliders.

  • PDF/UA-1 validationveraPDF · structural checks

    Reference catalog outputs are rebuilt through the production pipeline and revalidated from scratch in CI when code changes.

  • Screen reader walkthroughsVoiceOver · NVDA

    The flipbook and the accessible edition are read page by page in real Safari on macOS and in automated runs on Windows; every spoken phrase is captured as a transcript.

  • Automated scansaxe · CI

    Publishing surfaces and this page are scanned with axe in desktop and narrow-screen scenarios in CI.

This work is not an independent conformance certification. The final result also depends on publisher decisions such as heading structure, the accuracy of alternative text and reading order. Creavim provides the authoring controls for those decisions and a validation layer that identifies required issues before publishing.

How accessible publishing works