
A photo story can look correctly arranged while a screen reader encounters captions and images in a different sequence. Review the page's underlying document order together with the visual order. Repair the source structure where the sequence changes the story's meaning, then check the actual reading experience at each responsive layout.
Key Takeaways
- A visually numbered story can still have a different underlying sequence.
- Keep each image with its own caption and relevant description.
- Check reading order and interactive focus order separately.
Write down the story before inspecting the layout
List the intended sequence using stable image names and short caption identifiers. For a preparation, ceremony and reception sequence, record which text belongs to each photograph. This gives the reviewer a reference independent of the designer's arrangement.
Not every arrangement requires one rigid order. W3C's Meaningful Sequence explanation distinguishes sequences that affect meaning from independent content that can have several correct orders. A chronological story has stronger ordering requirements than unrelated portfolio tiles. Decide what the sequence communicates before declaring every visual difference a failure.
Compare the visual story with the document
Ask the implementer to inspect the document object model, or DOM, and identify the image-caption groups in source order. Compare that with the wide page and the narrow page. CSS can reposition content without changing its underlying order, so dragging a visual card in a design file does not establish the published reading sequence.
The W3C C27 technique describes matching DOM and visual order as one sufficient approach. It is a technique, not a requirement to use one particular layout system. The delivered result must preserve the meaningful relationships.
Test the complete image-caption groups
- Read through the story using the intended screen reader and browser combination.
- Note which image description, caption and surrounding text are encountered together.
- Compare the announced sequence with the approved story list.
- Repeat at the narrow layout, where columns may become a single stream.
- Check any links or controls with keyboard navigation as a separate pass.
Do not use a successful Tab sequence as proof that all ordinary text reads correctly. Conversely, correct reading order does not prove that interactive controls receive focus in a usable order. Avoid positive tabindex values as a shortcut for repairing a structurally scrambled story.
Keep format-specific repairs in their own source
The Acrobat catalog guide addresses PDF regions and tags. Those controls do not repair a website's DOM. If the same story is delivered as both a page and a PDF, check both outputs rather than transferring one approval to the other.
The comic reading-order guide helps define intended narrative flow. For a website, the additional responsibility is ensuring that software can expose that flow. The guide to descriptions for images covers the content of descriptions; descriptions alone cannot restore a broken sequence.
Accept a saved revision, not an attractive screenshot
Consider a proposed wedding story where all three photos appear above all three captions in source order. The grid looks paired on a desktop, but the spoken sequence separates every caption from its image. Grouping each photograph with its caption addresses a different problem from merely adding visible numbers.
Save the corrected page revision and repeat the reading pass. Record the tested layout, browser and assistive technology. Accept only when the story remains understandable in the actual reading sequence and each caption retains its intended relationship. This documentation-based checklist does not certify the entire website's accessibility.
Related tasks
- Why Does a Screen Reader Read My Photo-Catalog Caption Before the Wrong Image?
- How Do I Stop Readers from Following My Comic Panels and Speech Balloons in the Wrong Order?
- Should I Use My Generation Prompt as Alt Text for an AI Image?
Sources and scope
- WCAG Understanding Meaningful Sequence: Official documentation for the interaction requirements and scope discussed above.
- WCAG Technique C27: Official documentation for the interaction requirements and scope discussed above.
Documentation-based guidance. The scenarios and acceptance steps are proposed; no production interaction test, certification, search-volume measurement or AI-citation result is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.