You’ll end up with pages that pass the accessibility checker as you finish them, instead of a rework pass on publish day.
You’ll need
- The project open in Studio or Flow, on the page you are working on.
- The Check accessibility status button in the editor’s actions strip.
Improving Accessibility explains the tools. This page is the workflow: where accessibility belongs in the rhythm of building a page, so the checker finds nothing new on publish day. The core habit is simple: describe as you place, check as you finish each page.
As you place each element: give it a description
The cheapest accessibility work is the work done while the element is still selected. Every element takes a description under Properties → Accessibility:
- Aria label is a short description of what the element is or does.
- Alt — for image-type elements (images, logos), what readers hear instead of seeing the picture. Write it when you place the image, not later.
- Role marks the semantic role for text elements (Paragraph, Heading 1–6) so assistive technology announces the document structure. Pick the level that matches the visual heading; see Setting the Text Type (Heading Levels) for why the two should agree.
Two placements deserve extra care:
- Rows that carry anchors: when a row is the target of an anchor link, give it a human-readable name in the row settings; unnamed rows read as anonymous jumps to a screen reader. See Naming Rows and Creating Anchor Links.
- Color pairs: when styling text on a background, keep the contrast ratio at or above 4.5:1 (the checker’s threshold). Choosing an accessible pair now saves a rework pass later.
When a page is done: run the checker
- In the editor actions strip, click Check accessibility status; the button carries a ! marker whenever the current page has findings.
- Read the findings list. Each pairs a plain-language summary with the technical detail, e.g. “Background and foreground colors do not have a sufficient contrast ratio” with the computed ratio and expected minimum (4.5:1), or “Image elements do not have [alt] attributes”.
- Click a finding: Studio selects the affected element on the canvas. Fix it (adjust colors, add the missing description) and run the check again until the page comes back clean.
Do this per page as you finish it, not once at the end: the findings list stays short and each fix is a thirty-second edit on a page you still have in your head.
Before you publish: read it like assistive technology
- Accessible preview: Preview options → Accessible version shows the project the way screen-reader users will get it. If a page reads badly there, no amount of visual polish fixes it. See Previewing Your Project.
- Viewer version: Project Settings → Viewer Settings offers a View version choice between Standard and Accessible, configurable per device type; decide which devices get which version before launch.
- Publish output: every publish produces a link to the accessible version alongside the standard one; share it wherever accessibility matters. See Publishing and Sharing Your Studio Project.
Flow projects: same habit, same button
The Flow editor’s canvas toolbar carries the same Check accessibility status button with the same ! marker; run it per page there too. The underlying content is shared, but each edition is checked as rendered, and a clean flipbook page can still have findings after the Flow reflow.
The tool reference lives in Improving Accessibility; for the reading-side checks (including testing the accessible version on a real device), see Testing your publication on mobile devices.
If it doesn’t work
- The page comes back clean but still reads badly in the accessible preview. The checker finds the mechanical class (contrast, missing alt, structure gaps) and cannot tell you that an alt text is wrong. Fix the description itself.
- Flow pages show findings after a clean flipbook check. Each edition is checked as rendered; run the same button in the Flow editor.