How to Create an Accessible Digital Publication
The complete guide to WCAG 2.2 AA for publishers - what it means and how to meet it.
How to Create an Accessible Digital Publication
Accessibility is not a feature you add at the end. It is a design decision that shapes how your content reaches every reader, including the estimated 1.3 billion people worldwide who live with some form of disability. For publishers, getting accessibility right is both an ethical responsibility and an increasingly common legal requirement.
This guide explains what WCAG 2.2 AA means for digital publications, what ZenFlip handles automatically, and what you need to do on your end to make your content truly accessible.
What WCAG 2.2 AA Means
The Web Content Accessibility Guidelines (WCAG) are published by the World Wide Web Consortium (W3C) and have become the global standard for digital accessibility. Version 2.2, released in October 2023, is the current standard.
WCAG has three conformance levels:
Level A - the minimum. Covers the most basic accessibility requirements
Level AA - the standard that most legislation references. Covers the needs of the majority of people with disabilities
Level AAA - the highest standard. Difficult to achieve for all content types but useful as a goal for specific contexts
When someone says a publication is "WCAG 2.2 AA compliant," they mean it meets all Level A and Level AA success criteria. This is the level ZenFlip targets.
The Four Principles
WCAG is organised around four principles. Every accessibility requirement falls under one of these:
1. Perceivable
Content must be presentable in ways that all users can perceive. This means:
Text alternatives for images (alt text)
Captions or transcripts for audio and video content
Sufficient colour contrast between text and background
Content that does not rely solely on colour to convey meaning
Text that can be resized up to 200% without losing functionality
2. Operable
The interface must be usable by everyone. This means:
Full keyboard navigation - every function must be accessible without a mouse
No keyboard traps - users must be able to navigate away from any component
Enough time to read and interact with content
No content that flashes more than three times per second
Clear focus indicators so keyboard users know where they are
3. Understandable
Content and interface behaviour must be predictable and comprehensible. This means:
Clear language appropriate for the audience
Consistent navigation patterns
Error identification and suggestions for forms and interactive elements
Labels and instructions for any input required from users
4. Robust
Content must work across a range of technologies, including assistive technologies. This means:
Valid, well-structured markup that screen readers can interpret
ARIA attributes used correctly where standard HTML is insufficient
Compatibility with current and reasonably future assistive technologies
What ZenFlip Handles Automatically
When you publish a flipbook on ZenFlip, the viewer and delivery layer handle many accessibility requirements for you:
Keyboard navigation. The ZenFlip viewer supports full keyboard control. Readers can turn pages, navigate to specific pages, toggle fullscreen, and access all viewer controls without a mouse. Tab order follows a logical sequence.
Screen reader support. The viewer announces page changes, button labels, and navigation landmarks to screen readers. ARIA labels are applied to all interactive elements.
Focus management. Visible focus indicators appear on all interactive elements. Focus is managed correctly when opening and closing overlays, dialogs, and the fullscreen viewer.
Responsive design. The viewer adapts to any screen size and supports text scaling. Readers can zoom in on content without breaking the layout.
Touch and gesture support. Mobile readers can swipe to turn pages and use standard pinch-to-zoom gestures.
Colour contrast in the viewer UI. All viewer controls, buttons, and navigation elements meet the minimum 4.5:1 contrast ratio required by WCAG 2.2 AA.
What You Need to Do
ZenFlip handles the viewer, but the content inside your publication is your responsibility. Here is what to focus on:
Colour Contrast in Your Content
Text in your PDF must have sufficient contrast against its background. WCAG 2.2 AA requires:
4.5:1 contrast ratio for normal text (under 18pt or 14pt bold)
3:1 contrast ratio for large text (18pt and above, or 14pt bold and above)
Common problems:
Light grey text on white backgrounds
Coloured text on coloured backgrounds (for example, orange text on a yellow background)
Text overlaid on photographs without a solid or semi-transparent background
Use a contrast checker like WebAIM's Contrast Checker (webaim.org/resources/contrastchecker) to verify your colour combinations before creating your PDF.
Document Structure
A well-structured PDF helps screen readers understand the hierarchy and flow of your content:
Use real headings in your authoring tool (Word, InDesign, Google Docs). Do not just make text larger and bold - use the heading styles (H1, H2, H3)
Use logical reading order - the content should make sense when read sequentially from top to bottom, left to right
Use lists for list content rather than manually typed bullets or dashes
Use tables for tabular data, not for layout purposes
Images and Alt Text
Every meaningful image in your publication should have alternative text that describes what the image conveys:
Be specific. "Bar chart showing Q3 revenue of $4.2M, up 12% from Q2" is better than "chart"
Be concise. One or two sentences is usually sufficient
Skip decorative images. Purely decorative borders, backgrounds, and spacers do not need alt text
Describe function, not just appearance. If an image is a link or button, describe where it goes or what it does
In most authoring tools (Word, InDesign, Google Docs), you can add alt text through the image properties dialog. This alt text carries through to the PDF if you export correctly.
Typography and Readability
Minimum 12pt font size for body text. Smaller text is difficult to read even for people without vision impairments
Avoid justified text where possible. The uneven word spacing can be difficult for readers with dyslexia
Use sufficient line spacing. WCAG recommends line height of at least 1.5 times the font size for body text
Limit line length. Lines of 60-80 characters are easiest to read
Language and Clarity
Use plain language appropriate for your audience. Avoid jargon where simpler words work
Define abbreviations on first use
Use active voice where possible. "The board approved the budget" is clearer than "The budget was approved by the board"
Break up long paragraphs. Shorter paragraphs with clear topic sentences are easier to scan and comprehend
Creating an Accessible PDF
The quality of your flipbook's accessibility depends significantly on the quality of the source PDF. Here are the key steps for each common authoring tool:
From Microsoft Word
Use built-in heading styles (Heading 1, Heading 2, etc.)
Add alt text to all meaningful images (right-click > Edit Alt Text)
Use the Accessibility Checker (Review > Check Accessibility) before exporting
Export as PDF using File > Save As > PDF (ensure "Document structure tags for accessibility" is checked)
From Adobe InDesign
Use paragraph styles consistently for headings and body text
Set the reading order in the Articles panel
Add alt text through Object > Object Export Options
Export as PDF using File > Export > Adobe PDF (Interactive or Print), with "Create Tagged PDF" checked
From Google Docs
Use heading styles from the toolbar
Add alt text to images (right-click > Alt text)
Export as PDF using File > Download > PDF
From Canva
Canva has limited accessibility features for PDF export
Use clear heading hierarchy in your design
Ensure strong colour contrast
Download as PDF Print for best quality
Testing Your Publication
After uploading to ZenFlip, take these steps to verify accessibility:
Keyboard test - navigate your flipbook using only the keyboard. Can you reach every page? Can you access all controls?
Screen reader test - if you have access to a screen reader (VoiceOver on Mac, NVDA on Windows), listen to how your content is read aloud. Does the reading order make sense?
Zoom test - zoom to 200% in your browser. Does the content remain usable?
Colour test - view your content in greyscale. Can you still understand all the information?
Legal Requirements
Accessibility is increasingly a legal requirement, not just a best practice:
United States - The Americans with Disabilities Act (ADA) and Section 508 require accessible digital content for government agencies and many private organisations
European Union - The European Accessibility Act (EAA), taking effect June 2025, requires accessible digital products and services
United Kingdom - The Equality Act 2010 and Public Sector Bodies Accessibility Regulations 2018
Australia - The Disability Discrimination Act 1992
India - The Rights of Persons with Disabilities Act, 2016
While ZenFlip provides an accessible viewer, you should consult with your legal team about your specific compliance obligations. The content you publish also needs to meet accessibility standards.
Resources
WCAG 2.2 specification - w3.org/TR/WCAG22
WebAIM contrast checker - webaim.org/resources/contrastchecker
PDF Accessibility Checker (PAC) - pdfua.foundation/en/pac
ZenFlip Accessibility Statement - zenflip.io/legal/accessibility
Summary
Creating accessible digital publications involves two layers: the delivery platform and the content itself. ZenFlip handles the platform layer, providing an accessible viewer with keyboard navigation, screen reader support, and responsive design. Your responsibility is creating content with proper structure, sufficient colour contrast, meaningful alt text, and clear language.
Start with the basics: structured headings, good contrast, and alt text on images. These three things alone make a significant difference for readers who rely on assistive technology.