A first accessibility check you can do yourself on any web page
Check page titles, images, headings, contrast, keyboard access and forms using W3C's preliminary guidance, without claiming full accessibility conformance.
You do not need to be technical to get a first idea of a page's accessibility. The W3C Web Accessibility Initiative's "Easy Checks" (https://www.w3.org/WAI/test-evaluate/preliminary/) gives step-by-step checks. W3C is clear about the limits: the checks cover a few issues, are quick rather than definitive, and a page could pass them and still have significant accessibility barriers. A more robust assessment is needed for a full evaluation.
The checks W3C lists
As read on 15 November 2026, the page carries a note that a draft new version of Easy Checks exists at https://www.w3.org/WAI/test-evaluate/easy-checks/. We read the older page, so check the newer one too. The older page lists these checks: page title, image text alternatives, headings, contrast ratio, resize text, keyboard access and visual focus, forms with labels and errors, and moving, flashing or blinking content. You can do most with any browser; some are easier with a browser extension, and W3C says it does not endorse particular tools. Its instructions name an extension and a toolbar for Internet Explorer 9 or later, which are dated, so we do not repeat the tool steps here.
Page title
W3C says page titles show in the browser tab or window bar, search results, bookmarks and screen readers, and that a screen reader speaks the title first when a user opens a page. Check that the title briefly describes the page's content and differs from the titles of other pages on the site. W3C says there is flexibility, and suggests putting the important, identifying words first (for example "About Acme Web Solutions" rather than "Acme Web Solutions, Inc. | About Us").
Image text alternatives ("alt text")
Alt text should carry the image's purpose and give an equivalent experience; it need not describe the picture (a search button's alt text should be "search", not "magnifying glass"). Check that every image has an alt attribute with appropriate text. W3C's guidance: images that inform need text; decorative images should have an empty alt=""; functional images such as buttons and linked images need text for the function; text inside an image, such as in a logo, belongs in the alt text; complex images such as charts get short alt text with the detail elsewhere; alt text need not say "button", "link" or "image of". W3C notes that automated tools can tell whether alt is missing, but only a person can judge whether the text is appropriate in context, and that appropriate alt text "is not an exact science".
Headings
Check that the page has at least one heading; that text that looks like a heading is marked up as one and that marked-up headings really are section headings; and that the hierarchy is meaningful. W3C says ideally the page starts with an h1 close to the page title and does not skip levels, but that these are not absolute requirements. It describes two views to check: an outline of the headings, and the page with heading markup shown. Compare the outline with how the page looks.
Contrast
W3C says to look for a contrast ratio of at least 4.5:1 for normal-size text. It describes three ways to check: a tool that tabulates ratios on the page, an eyedropper tool that tests one color pair at a time, and viewing the page in grayscale. It notes the first can show combinations not actually on the page, the second is accurate but tests one item at a time, and the third is imprecise and gives no ratio.
Resize text
Increase the text size in the browser and check that all text gets larger, nothing disappears or is cut off, content does not overlap, controls stay usable, and sentences do not need horizontal scrolling. W3C points out a common cause of failure: text provided as an image does not get larger.
Keyboard access
Put the mouse aside and press Tab to move through the page, Shift-Tab to go back. W3C's checklist: you can reach every link, field, button and media control; you can tab away from each (a "keyboard trap" is when focus gets stuck, often in media controls); tab order follows reading order; the element with focus is clearly visible; all functionality works without a mouse (hover-only actions are a common problem); and dropdown lists let you arrow through options without triggering an action.
Forms, labels and errors
W3C labels this section more complex than the others and says to skip it for now if it is too much. Checks it lists: every form control is keyboard accessible, including options in drop-down lists; every control has a label associated with it (the label element's for matching the control's id is its best practice in most cases, but W3C says it is not a requirement because a label can be associated in other ways, so a form that fails this check may still meet WCAG); labels sit to the left of text boxes and drop-downs and to the right of radio buttons and checkboxes in left-to-right languages; required fields are clearly indicated without relying on colour alone, with the indicator inside the label or legend; instructions come before they are needed; and required formats, such as dates, are in the label. On a form you own or are authorized to test, using harmless test data and avoiding real purchases or submissions, try leaving required fields blank or entering a badly formatted value and check that: the message is clear and specific and explains any required format; errors are easy to find (W3C says generally before the form rather than after it); and fields without errors keep the data you entered (best practice, not a requirement, with sensitive data such as card numbers as an exception).
Moving, flashing or blinking content
W3C's section lists carousels, ads, videos, stock tickers and scrolling news feeds as examples. It says people need to be able to control moving content, because some people read slowly or find moving objects hard to track, moving content can distract from other parts of the page, and flashing or blinking content can cause seizures in people with photosensitive epilepsy. Our fetch cut off partway through this section, so we do not report W3C's flash thresholds or its check steps. Read that section on W3C's page.
What a pass does and does not mean
A pass on these checks is not a conformance claim. Our own article on accessibility basics covers WCAG at a high level. Do not state on your site that a page is accessible or compliant on the basis of this checklist.
Limits
Based on W3C's older Easy Checks page as read on 15 November 2026. The tool-specific steps on it are dated and omitted. The moving, flashing and blinking section was cut off during our fetch, and the newer draft version of Easy Checks was not read. The contrast, resize text and keyboard summaries above come from the same page. These checks are quick and cover only a few issues; W3C says a page can pass them and still have significant barriers. Accessibility law varies by country and needs counsel.
By Omnistu.