A practical WCAG 2.2 checklist for flipbooks and digital catalogs. Check contrast, alt text, reading order, keyboard access, focus visibility, target size and captions, with tables, real examples and a step-by-step workflow for publishing accessible catalogs.
A beautiful catalog that a shopper cannot read, tab through or hear is a catalog that loses sales. Roughly one in six people lives with some form of disability, and that includes low vision, color blindness, motor limits, deafness and cognitive differences. This WCAG 2.2 checklist for flipbooks and digital catalogs turns the standard into concrete checks you can run before every publish. If you build page-turning publications with Flipbooks AI, you can apply every step below to your next release.
WCAG 2.2 is the current version of the Web Content Accessibility Guidelines from the W3C. It builds on 2.0 and 2.1, so everything you already did still counts. The new criteria focus on mobile, keyboard users and people who struggle with fine motor control. That matters a lot for flipbooks, because page-flip interactions, hotspots and zoom controls are exactly where accessibility breaks.
Legal pressure is real. The European Accessibility Act, the ADA in the United States and many national laws point to WCAG as the measuring stick, and most reference level AA. Beyond the legal angle, accessible catalogs are simply easier for everyone to use. Larger tap targets help people on phones. Good contrast helps people reading outdoors. Captions help people watching in a quiet office.
WCAG groups every rule under four ideas, often shortened to POUR:
Nine criteria were added. The ones that hit flipbooks hardest are below.
| New criterion | Level | What it means for a catalog |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A sticky header or cookie banner must not hide the focused control |
| 2.5.7 Dragging Movements | AA | Page flips and sliders need a single-click alternative |
| 2.5.8 Target Size (Minimum) | AA | Buttons and hotspots should be at least 24 by 24 CSS pixels |
| 3.2.6 Consistent Help | A | Help links stay in the same place on every page |
| 3.3.7 Redundant Entry | A | Do not ask for the same information twice in a form |
| 3.3.8 Accessible Authentication | AA | Password protected flipbooks must allow paste and password managers |
💡 Criterion 4.1.1 Parsing was removed in 2.2, so you no longer need to worry about it. Focus your time on the new items above.
Work through these nine checks in order. Each one has a pass condition you can test in a few minutes.
Product photos, lookbook spreads and diagrams all need alt text. Describe what the image shows and why it matters, not just the file name. Skip decoration with an empty alt value.
Normal text needs a contrast ratio of at least 4.5:1 against its background. Large text (18 pt or 14 pt bold) needs 3:1. User interface parts, such as button borders and focus rings, also need 3:1. Text laid over a photo is the usual offender in catalogs, so add a solid or semi opaque panel behind it.
| Element | Minimum ratio | Common catalog failure |
|---|---|---|
| Body text | 4.5:1 | Light gray text on white |
| Large headings | 3:1 | White title over a bright photo |
| Buttons and icons | 3:1 | Pale outline on a pale page |
| Focus indicator | 3:1 | Thin default ring on a colored band |
⚠️ Never rely on color alone. A red price and a green price look identical to many readers, so add a label such as "Sale" or an icon.
A screen reader follows the order of the underlying document, not the visual layout. If your PDF source was exported with tags in the wrong order, a two column spread may be read left to right across both columns. Fix this in the source file before you convert it.
Every action must work without a mouse. That means turning pages, zooming, opening the table of contents, playing media and closing dialogs.
Sighted keyboard users need to see where they are. A clear focus ring with 3:1 contrast is the baseline. WCAG 2.2 adds that the focused item must not be fully hidden behind sticky bars, chat widgets or cookie notices. Test this by tabbing while the browser window is small, since overlays cover more of the page there.
Hotspots on product images are often tiny dots. Make them at least 24 by 24 CSS pixels, and aim for 44 by 44 on touch screens. Provide space between neighbors so a thumb does not hit two at once. If a user can drag a corner to flip a page, they must also be able to click a visible "Next page" button.
If your catalog embeds product videos, add synchronized captions. Provide a text transcript for audio only content. Nothing should autoplay sound for more than three seconds without a way to pause it. Moving content that lasts more than five seconds, like a looping banner, needs a pause control.
Use real headings in a logical sequence, short paragraphs and plain wording. Spell out abbreviations on first use. Label links with their destination, so "Download the spring price list" replaces "Click here".
Lead forms inside a flipbook need visible labels, error messages that say what went wrong and no repeated questions. For password protected publications, WCAG 2.2 requires that people can paste or use a password manager, and that you do not force a puzzle or memory test as the only way in.
Different publications fail in different places. Use this table to decide where to start.
| Catalog type | Biggest risk | First fix |
|---|---|---|
| Fashion lookbook | Text over photos, missing alt text | Add contrast panels and descriptive alt text |
| Product price list | Dense tables, tiny type | Use real table headers and larger type |
| Restaurant menu | Allergen icons with no text | Add text labels beside every icon |
| Annual report | Charts without data | Add summary text and data tables |
| Training manual | Videos without captions | Caption and add transcripts |
A furniture retailer found that its sofa hotspots were 12 pixels wide. After resizing them to 44 pixels and adding labels, mobile shoppers stopped missing the tap, and the support inbox saw fewer "I cannot open the details" messages.
A hotel group discovered that its brochure used pale gold text on cream. Switching to a dark brown that hit 7:1 made the room descriptions readable in bright lobby light and on small phones.
A school office published a newsletter flipbook with unlabeled photos. Adding alt text took ten minutes per issue and gave blind parents access to the same updates as everyone else.
Accessibility starts in the source document, then carries into the viewer. This workflow keeps both sides in check.
Create your file in a layout tool that supports tagged PDF export. Add alt text, set the document language, use real heading styles and check the tag order. Run a built in accessibility checker before you export.
Sign in or create an account, then drop the PDF into the PDF to Flipbook Converter. Conversion keeps text selectable, which screen readers and browser zoom depend on. For product listings, the Digital Catalog Maker is a good starting point, and the Product Catalog tool fits large inventories.
Open the branding settings and pick colors that pass 4.5:1 for text and 3:1 for buttons. Choose a page effect that is subtle, and keep a visible next and previous button on screen. Add your logo, but keep it away from small body text.
Embed videos and audio, then upload caption files and place transcript links on the same page. Mobile responsive layouts help, but test them with real taps, not only with a desktop browser resized.
Share a direct link, or follow the steps in the Embed Flipbook on Website tool. Give the embed frame a descriptive title so screen readers announce what it contains. If you use password protection, check the login flow against criterion 3.3.8. Offer a downloadable accessible PDF as a fallback for readers who prefer it, which the offline download option makes easy.
On the Professional plan, analytics and lead generation show which pages people leave and which forms they abandon. A page with a sudden drop may hide an accessibility barrier. See pricing plans for the full feature list. Every plan publishes with no watermarks, and Standard and above allow unlimited flipbooks, so you can fix and republish as often as you need.
✅ Best practice: keep a one page accessibility statement linked from your catalog, with a contact address for reporting problems. It satisfies good practice in many regions and builds trust.
No automatic scanner catches everything. Automated tools find roughly a third of issues, so pair them with manual checks.
| Tool or method | What it checks | How often |
|---|---|---|
| Browser accessibility audit | Contrast, missing labels, alt text | Every release |
| Screen reader (NVDA, VoiceOver) | Reading order, announcements | Every release |
| Keyboard only run | Focus, traps, shortcuts | Every release |
| Zoom to 200 percent | Reflow and clipped text | Monthly |
| Phone touch test | Target size and gestures | Every release |
| Real user feedback | Everything the tools miss | Quarterly |
Accessible catalogs reach more buyers, reduce legal risk and look cleaner for everyone. Work through the nine checks, record what you fixed and republish with confidence. When you are ready, get started for free on Flipbooks AI, browse all flipbook tools to match your content type, and compare pricing plans to pick the level that fits your catalog volume.
