This series is inspired by the excellent posters published on the GOV.UK Accessibility Blog. They were originally created for government services, but the advice applies everywhere - from e-commerce to healthcare to education.
Each part takes one of the posters, shares the official Do’s and Don’ts, and adds my own perspective on why it matters in practice.
I still remember the first time I opened a website that had dozens of unlabeled “button, button, button” announcements. I gave up after three clicks. Screen readers are brilliant tools, but they rely on developers giving them meaningful content. Without that, you’re essentially giving users a blank map.
Do’s and Don’ts for Screen Reader Users
Do
- describe images and provide transcripts for video
- follow a linear, logical layout
- structure content using HTML5
- build for keyboard use only
- write descriptive links and heading - for example, Contact us
Don't
- only show information in an image or video
- spread content all over a page
- rely on text size and placement for structure
- force mouse or screen use
- write uninformative links and heading - for example, Click here
Why it matters
Screen readers read from top to bottom. Clear headings, logical order, and proper HTML matter more than fancy layouts.
Takeaway: Don’t design for what you see on screen. Design for what someone hears.
The dos and don’ts of designing for accessibility are general guidelines, best design practices for making services accessible
https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/
unknownx500
/Passle/60211dc9e5416a0c14bc63d4/SearchServiceImages/2025-12-03-19-31-44-490-69309020a71bd983b528ca6c.jpg)
