You can learn a lot about a page in ten minutes with only a keyboard and your own eyes. Zoom in, press Tab, scan the headings, look at the images, squint at the colors and read the links. If something fails, you know where to start.
The W3C publishes a set of these checks, called Easy Checks. This page puts the ones that need no special software into one short routine. Most steps point to a longer guide for the fix.
What this check can and cannot tell you
The W3C says Easy Checks are designed to be quick and easy rather than exhaustive. Its own warning is plain: a page could seem to pass these checks and still have significant barriers. More extensive testing is needed to judge a page fully.
So treat this as a first pass. It finds common, visible problems. It does not give a pass mark.
Run it on the page the way a reader meets it: the live version, in a normal browser window, with no special settings. A draft on your own screen can hide problems that a visitor will see at once.
The ten-minute plan
| Minutes | Check | What to do | You pass if |
|---|---|---|---|
| 1 | Page title | Read the browser tab | The title says what the page is and differs from other pages |
| 2 | Zoom | Press Ctrl or Cmd with + five times | Text wraps, nothing hides, no sideways scrolling for paragraphs |
| 2 | Keyboard | Press Tab again and again | You can see where you are, and you reach every link and button |
| 1 | Headings | Scan the page for section titles | They read like a table of contents, in order |
| 1 | Images | Look at each picture | Each one has a purpose, and a description if it carries meaning |
| 1 | Contrast | Lower your screen brightness | All text is still easy to read |
| 1 | Link text | Read the links without the sentences around them | Each link says where it goes |
| 1 | Notes | Write down what failed | You have a short list |
Set a timer. If a step runs long, write the problem down and move on. You can dig deeper later.
Zoom, keyboard and headings in detail
Zoom. The W3C check starts with a fairly narrow browser window. Press Ctrl or Cmd with + five times, which should reach 200%. All the text should wrap and stay in the visible area. Text should not hide behind other text or images. A menu that turns into an icon is fine. The zoom guide covers fixes.
Keyboard. Visible keyboard focus is the marker that moves as you tab through a page. The W3C check asks whether every interactive element has an obvious visual style when it is selected. Press Tab once on a freshly loaded page. The W3C describes a skip link as the first interactive element, which lets keyboard users jump to the main content. If one appears, use it and see where you land.
Headings. The W3C compares headings to a table of contents. Its questions are useful on any page:
- Does the page have headings at all?
- Does the page start with a main heading?
- Are any levels skipped?
- Does any text look like a heading but not work as one?
- Does the heading text match what follows?
The fourth question is hard to answer by eye, because a bold line can pass for a heading. The headings guide covers real headings in detail.
Images, contrast and link text
Images. The W3C defines alt text as a short description that conveys the purpose of an image. You cannot read it by looking, so use the tool your software offers, or check the file's picture settings. The W3C's Easy Checks have a separate page for this one. See writing alt text for what a good description looks like.
Contrast. The W3C describes contrast as the difference between adjacent colors, usually text and background. Dim the screen and scroll the page. Pale gray text on white is often the first thing to disappear. For exact numbers, use a checker and read what the contrast numbers mean.
Link text. Read only the links, one after another. "Click here" and "read more" tell a reader nothing out of context. The link text guide shows how to fix them.
Writing down what you found
A note that says "seems fine" helps nobody. Write what failed, where, and at what setting.
Before: The page looks okay but feels hard to use.
After: At 200% the menu overlaps the first paragraph. Tab skips the search button. Two links say "read more". The page title is the same as the home page.
Four lines like these are enough to hand to whoever edits the page. Sort the list when you are done. Put the problems that stop someone from reading or reaching content first, and the polish last.
If you have a phone nearby, run the zoom and link steps there too. Sideways scrolling and tiny buttons show up fast on a small screen. The phone text guide covers those. If the page is a PDF, the PDF guide has its own list of fixes.
If the writing itself is the problem, long sentences and hard words are easier to spot with help. The Easy-Read Editor can point you toward the places to simplify.
Common mistakes
- Treating a pass as proof. The W3C says a page can pass and still have barriers.
- Checking only at normal size. Many problems show up only at 200%.
- Clicking instead of tabbing. Using a mouse hides keyboard problems.
- Skipping the notes. Without notes, nothing gets fixed.
- Checking only the home page. Titles and headings go wrong deeper in the site.
- Fixing everything at once. Start with the failures that block reading.
FAQ
Do I need special software?
Not for most steps. You need a browser or document, a keyboard and your own judgment. For images and exact contrast numbers, a tool helps.
How often should I run this?
Run it whenever a page changes in a big way, and before you publish anything new.
Does it work on documents as well as web pages?
Zoom, headings, images, contrast and link text all apply to documents too. The keyboard step applies to anything you open on screen.
What if the page fails one step?
Fix that step first and run the check again. Most steps link to a guide with the details.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Easy Checks - A First Review of Web Accessibility Checked November 19, 2026
- Zoom Levels - Easy Checks Checked November 19, 2026
- Headings - Easy Checks Checked November 19, 2026
- Visible Keyboard Focus - Easy Checks Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.