Rules
Part of Digital magazine accessibility guide: production practices
Digital magazine accessibility problems with practical fixes
Digital magazine accessibility problems and fixes for image-only pages, reading order, headings, alt text, tables, contrast, keyboard traps, media, and PDFs.
What to take away
- Fix the source file, then regenerate every output. A repaired PDF alone leaves the next issue with the same faults.
- Match the text alternative to the image's editorial job, not to what the file looks like.
- Plan reading order, keyboard order and visual order as one system before layout starts.
- Simplify a table or an interaction before attempting heavy remediation on it.
- Retest the reader journey after each correction, not only the file that was edited.
Digital magazine accessibility problems usually start as production shortcuts. A designer exports pages as flat images, styles a paragraph to look like a heading, or accepts auto-captions without editing. Fix the cause and the checker message clears on its own.
Choose a conformance baseline
Use WCAG 2.2 Level AA as the technical target for the edition, then confirm which legal requirements apply in each market. In the United States, assess the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act where applicable; in Europe, assess the European Accessibility Act (Directive (EU) 2019/882) and EN 301 549. Their scopes differ, so a WCAG target alone does not establish legal compliance.
Map practical checks to WCAG 2.2 success criteria: 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.4.3 Contrast (Minimum), 1.4.10 Reflow, 2.1.1 Keyboard, 2.4.7 Focus Visible, and 1.2.2 Captions (Prerecorded). For PDFs, check ISO 14289 (PDF/UA); for EPUB, use EPUB Accessibility 1.1 and publish a conformance statement with accessibility metadata, including an accessibility summary.
The issue is a stack of page images
A magazine exported page by page as JPEGs has no text layer, so search, selection, reflow and speech output all fail or lean on weak optical character recognition.
From page images to live text
- Page images: search and speech fail
- Return to structured manuscript or layout source
- Export live text with semantic structure
- No source: run recognition and correct every page
- Rebuild headings and reading order
- Verify against the visible edition
- Offer responsive HTML or reflowable edition
Return to the structured manuscript or the layout source and export live text with real structure. Where no source survives, run recognition, correct every page, rebuild headings and order, then compare the result against the visible edition. Offer a reflowable HTML or EPUB edition when a fixed page remains hard to use. For an EPUB, assess it against EPUB Accessibility 1.1 and document its accessibility metadata, including an accessibility summary.
Alt text that repeats the caption
A screen-reader user hears the same name and event twice, or listens to a decorative border described in full.
The W3C Web Accessibility Initiative's Images Tutorial separates several image types. It ties the text alternative to the image's purpose in context. The types are:
- informative
- decorative
- functional
- text-bearing
- complex
- grouped
- mapped
Classify first, then write the alternative or suppress the announcement.
- informative
- decorative
- functional
- text-bearing
- complex
- grouped
- mapped Classify first, then write the alternative or suppress the announcement.
Keep the caption for shared editorial context. Use alt text for visual information the caption does not carry. Give a functional icon the name of its action. Leave decoration with an empty alternative. For a complex graphic, add a nearby long description or a data equivalent.
Headings that are only visual styling
The page looks organized, but navigation tools report a flat block of text or an outline that makes no sense.
Mark section titles as real headings in a logical hierarchy. Set appearance in CSS or document styles. Do not skip a level to get a size you want. Check the announced heading list after export.
Reading order that follows columns incorrectly
Speech jumps from a feature into an unrelated sidebar, reads both columns line by line, or announces the footer before the article ends.
Set source order before positioning. In PDF, inspect the tag tree and order panels with assistive technology. In HTML or EPUB, keep the DOM order logical and use layout rules that do not change meaning. Put optional side material at a clear boundary.
A data table that loses its headers
Values are announced without the row or column that gives them meaning, most often after a format conversion.
The W3C Web Accessibility Initiative's Tables Tutorial explains that accessible tables separate headers from data cells and establish the relationship between them, with explicit associations for complex structures. It also warns that table markup is easily lost in conversion.
Rebuild real header cells, scope or associations, and a useful caption. Simplify nested or irregular tables. Test cell navigation in the delivered format. Use a list or prose when the content is not a data grid.
Color as the only signal
A chart key, a warning, a quiz result or a subscription status becomes unclear when color is not perceived as designed.
Add direct labels, patterns, symbols with text, or explicit status words. Under WCAG 2.2 AA criterion 1.4.3, text contrast must be at least 4.5:1 for normal text and 3:1 for large text; criterion 1.4.11 requires at least 3:1 contrast for visual information needed to identify controls or states and graphics needed to understand content. Review hover, selected, disabled and error states against the applicable criterion. For UK-specific duties, see the Equality Act guidance.
Text that clips when enlarged
Captions vanish, navigation overlaps, or a fixed spread needs panning in both directions.
Remove fixed heights around text, allow wrapping, and test reflow at narrow widths and high zoom. Where a format cannot adapt, provide an equivalent reflowable edition and disclose the limitation before download.
Keyboard focus that disappears or traps
A reader enters a menu, lightbox, paywall or player and cannot see focus or get back to the article.
Use native controls, logical source order, visible focus, and open-close behavior you have tested. Check WCAG 2.2 success criteria 2.1.1 (Keyboard) and 2.4.7 (Focus Visible), then move focus into a modal when it opens and return it to the control that opened it. Test forward and reverse navigation without a mouse.
Captions straight from automation
Names, technical terms, punctuation, speakers and meaningful sounds come through wrong or missing.
Edit captions against the final audio, synchronize them, identify speakers where it matters, and include relevant non-speech sound. For prerecorded synchronized video, check WCAG 2.2 criterion 1.2.2, Captions (Prerecorded). Add a transcript for audio and descriptions for essential visual information that sound alone does not carry.
A tagged PDF that passes and still reads badly
Tags exist, yet headings are wrong, decorative objects are announced, tables have no context, and links carry vague names.
Treat automated checking as inventory, not as a verdict. Inspect these accessibility and structure details by hand:
- tag roles
- order
- alternatives
- language
- title
- bookmarks
- links
- forms
- tables
Read representative pages with supported assistive technology such as NVDA, JAWS, VoiceOver or TalkBack, then repair the source where feasible and regenerate. For PDFs, use Acrobat Pro's Accessibility Checker or PAC (PDF Accessibility Checker); for HTML, use axe or Accessibility Insights for Web. Treat these tools as prompts for manual review, not as proof of conformance.
A worked check before release
Run this against one issue before the next one goes to press. Each line is a pass or a fail, not a score.
- Export the issue and confirm the text layer is live, selectable and searchable.
- Read the heading list aloud in the reading tool and confirm the outline matches the contents page.
- Tab through the whole issue without a mouse and confirm focus is always visible.
- Open every modal, lightbox and player, then close it and confirm focus returns to the trigger.
- Check each chart and data table with headers announced alongside the values.
- Zoom to 200 percent at a narrow width and confirm no caption or control is cut off.
- Play one captioned video and one audio piece end to end with sound off.
Common questions
Should a publisher repair the PDF or rebuild the source?
Rebuild the source when you can, because later issues and formats inherit the fix. Remediate the file directly when a deadline or a missing source makes that the responsible route, and record what changed so the next production cycle does not undo it.
Can an accessibility overlay fix a magazine viewer?
Do not assume it. Test the underlying content, the controls, the reading order and the assistive technologies readers actually use. An overlay sits on top of the problem rather than removing it.
Is a separate text-only version enough?
Not when it drops equivalent images, charts, media, navigation or interaction. The main edition should be accessible wherever it can be, with the text-only route as a fallback rather than the answer.
Which problem should be fixed first?
Start with anything that blocks access to essential content or a task. Then take the widespread high-impact barriers, and assign the source-process change that stops each one coming back next issue.
