Thirty points you can check without prior knowledge. Tick off what your website already gets right. The ticks are stored only in your browser; nothing leaves your device. The list does not replace a full WCAG audit; it is the practical core for everyday work, the points where most websites fail.
0 of 30 points checked
Perceivable
Switch images off in the browser or use WAVE: does the message survive?
Check the source: decoration should be skipped by the screen reader.
Put the colour values into WebAIM's Contrast Checker instead of guessing.
Button borders, icons and charts need measurable contrast too.
Do a greyscale test: do you still understand errors, links and status?
Watch once without sound: do you understand everything?
The content must be readable as well, not only audible.
Ctrl and Plus up to 200 percent: nothing overlaps, nothing disappears, no sideways scrolling.
Try to select the text: what cannot be selected is an image.
Operable
Put the mouse away and go through the page with Tab and Enter only.
During the Tab test you must always see where you are.
You can leave every dialog, menu and banner with the keyboard.
First press of Tab on the page: does a skip link appear?
The focus must not jump criss-cross over the page.
Test on the phone with your thumb, not at the desktop with a mouse.
Fast flashing can trigger seizures and is off limits.
Enable reduced motion in the operating system: does the page calm down?
Forms and sessions must not throw anyone out under time pressure.
Understandable
Look for the lang attribute in the html element of the source code.
Read the browser tab: does it say where you are?
One H1 per page, no skipped levels; WAVE shows the structure.
A link must make sense without the sentence around it.
Click the label: if the cursor jumps into the field, it is connected.
Submit the form incorrectly on purpose and read the message.
Menu items change neither place nor order.
Robust
Buttons are button, links are a, lists are ul: spot-check the source.
Browsers should be able to fill in name, email and address.
What native HTML can do needs no ARIA; wrong ARIA does harm.
Success and error messages need an aria-live region.
Listen to your homepage with VoiceOver or NVDA: order, links and headings make sense.
Everything ticked? Then your website is in better shape than most. The moves for the open points are explained in my guide. What an audit with blind testers looks like is shown in the BSVSH case study. And if you would like support: accessible web design is exactly my subject.
