Editorial team ยท

Put the mobile reading order on paper before moving the cards

Editorial cover: Put the mobile reading order on paper before moving the cards
AI-generated illustration.

On a laptop, a help page has instructions on the left and a booking card on the right. On a phone, the booking card lands above the steps that tell you what to bring. Put the page on four sticky notes. Moving those notes around will tell you pretty quickly which information people need first.

Write the order as a short story

In this example, the reader needs to know what the appointment is for, what to bring, and how to pick a date. Put the explanation first, then the checklist, then booking. A separate help link can sit by the booking form if that is where questions tend to come up.

Inspect the order in the page source or accessibility tree. Changing a grid position can move a card on screen while the underlying reading order stays the same. When the order affects meaning, align the source and the layout so both paths make sense.

Follow the form with the keyboard and listen through the content with a screen reader. The two checks answer different questions. Tab goes among controls, while reading commands let you hear the headings and text between them.

Give the flow a small test: ask someone to find what to bring and then open the date picker. If both steps arrive in a sensible sequence at phone width, the card arrangement supports the task.

One possible order for an appointment page
Step Block Question it answers
1 Appointment overview What am I booking?
2 What to bring Can I get ready for it?
3 Date picker Which slot works for me?
4 Help link Where do I ask a question?

Check that the browser tells the same story

  1. Plan the sequence
    • Write each main block on a card.
    • Arrange the cards in the order someone needs the information.
  2. Run the route in the browser
    • Read the headings and text from top to bottom.
    • Use Tab to check where the interactive elements land.

Questions and answers

Do columns have to disappear on mobile?
Use a layout that fits the screen and preserves the order needed to understand the content.
Does Tab reach every heading and paragraph?
Usually it moves among focusable controls. Use screen-reader reading commands for surrounding text.
What should I report if the two orders differ?
Record both sequences and explain where the difference changes meaning or interrupts the task.

W3C WCAG 2.2: Meaningful Sequence