Accessibility preflight
Tick what is true of your app or website today. Everything stays in this browser tab. This is a local planning aid: not an audit, not automated testing, not a certification and not a quote.
Working notes
Short practical notes, filterable by service.
- DESIGN
Contrast first, colour second
Pick text and background pairs that read clearly, then choose accents. Repainting later is costlier.
- WEB
Forms that forgive
Keep what someone typed when submission fails. Losing a long message is the fastest way to lose a visitor.
- MOBILE
Test with large text on
Turn system text size up before calling a screen finished. Clipped labels show up immediately.
- RELEASE
Write the release order down
Who uploads, who checks the listing, who answers the first support email. Decide before the day.
- SUPPORT
Describe the problem in three lines
What you expected, what happened, and what you were doing just before. It halves the back-and-forth.
- DESIGN
Name the empty state
A list with nothing in it should say why and what to do next, not show a blank box.
- WEB
One h1, then order
Headings are a table of contents for screen reader users. Skipping levels makes the page harder to scan.
- SUPPORT
Keep a list of accounts
Know which email owns your domain, your hosting and your app store accounts. Recovery is far easier.
- MOBILE
Permissions with reasons
Ask for camera or location at the moment it is needed, with a sentence explaining why.
- RELEASE
Privacy text must match behaviour
If the app collects nothing, say so; if it collects something, describe it accurately.