Free scan

November 17, 2026

Easy checks for web accessibility: a first review you can do yourself

Easy checks for web accessibility let you get a rough idea of whether a page addresses the basics, without being an expert. The W3C publishes them as “Easy Checks – A First Review of Web Accessibility”: most of them work in any browser and cover the page title, image text alternatives, headings, contrast, text resizing and keyboard access. The W3C is upfront about their limits: they cover just a few accessibility issues and are designed to be quick and easy rather than definitive, so a page that passes them may still have significant barriers. Below you will find how to run each check, what an evaluation tool adds, and what no tool can decide for you.

Easy check 1: the page title

The page title appears in places such as the browser tab and the window title bar. To read it, hover over the tab, look at the window title bar, or open the bookmark dialog (Ctrl+D on Windows, cmd+D on Mac).

Check that the title briefly and accurately describes the page and distinguishes it from other pages on the site. As a best practice, the W3C suggests putting the unique information first, for example “About Acme Web Solutions” rather than a generic prefix repeated on every page. This relates to WCAG success criterion 2.4.2 (Level A).

Image text alternatives

Every informative image needs appropriate alternative text (the alt attribute). Purely decorative images should have a null alt (alt="").

This check shows where automation ends and judgement begins: a tool easily flags an image with no alt attribute, but you must decide whether the text provided is appropriate. The related criterion is WCAG 1.1.1 (Level A).

Headings and basic structure

Check that the page has at least one heading, that text which looks like a heading is marked up as one, and that anything marked up as a heading really is a section heading. Ideally the outline starts with an h1 and does not skip levels, although the W3C notes these are not strict requirements. The W3C HTML Validator shows the outline when you enable its Outline option; if it reports 0 headings, none are marked up. Related criteria: WCAG 1.3.1 (A), 2.4.6 (AA) and 2.4.10 (AAA).

The W3C also suggests a basic structure check: view the page with no images, no styles and linearized into one column, roughly as a screen reader user or someone with low vision might experience it. The reading order should still make sense, images should be replaced by useful alt text and sections should have clear headings. In the W3C Before and After Demonstration (BAD), the article headlines on the inaccessible home page are hard to find once linearized, because they are not marked up as headings.

Color contrast

Normal-size text needs a contrast ratio of at least 4.5:1 against its background. In the W3C demo, dark gray text on a light gray background reaches only 3.76:1 and falls short. Related criteria: WCAG 1.4.3 (AA) and 1.4.6 (AAA).

Resize text to 200%

Increase the text size to 200% using text-only zoom. The W3C deliberately leaves out full-page zoom for this check because it often hides text layout problems. In Firefox, choose View > Zoom > Zoom Text Only, then press Ctrl (or cmd) and plus about four to six times. In Safari, hold the option key and choose View > Make Text Bigger, or press option+command+plus. Chrome requires an extension.

Then check that the text actually gets bigger, that nothing overlaps or is cut off, that controls remain usable and that sentences do not require horizontal scrolling. Text inside images does not resize, so flag it. Related criteria: WCAG 1.4.4 (AA) and 1.4.5 (AA).

Keyboard access and visible focus

Click in the address bar, set the mouse aside, and move through the page with Tab and Shift+Tab. Use the arrow keys within menus and Enter or Space to select. On a Mac, first enable keyboard access to all controls in the system Keyboard preferences. Related criteria: WCAG 2.1.1 and 2.1.2 (A), 2.4.3 (A) and 2.4.7 (AA).

Forms, moving content and media

In forms, every field needs a label (linking it to the field with label, for and id is a best practice rather than a strict requirement). Required fields should be indicated by more than color alone, for example an asterisk in the label; instructions and expected formats, such as a date format, should appear before they are needed; and error messages should be specific and keep the data already entered. To test errors, submit the form with blank or malformed fields.

Content that moves automatically for more than five seconds should be possible to pause, stop or hide. Check that nothing flashes more than three times per second; if something does, further evaluation is needed. Audio that plays automatically should stop after 3 seconds or offer controls to pause, stop or adjust the volume. For videos, look for the CC button: if it is missing, there are no captions. The W3C stresses that automatic captions are not sufficient for accessibility because they are not accurate enough.

What an evaluation tool adds, and its limits

The W3C describes evaluation tools as software programs or online services that help determine whether web content meets accessibility guidelines. They help you quickly identify potential issues, can be used in all phases of design and development, provide fully automated checks and assist manual review. Some check one page at a time, others scan entire websites.

Their limits are explicit: tools cannot check all accessibility aspects automatically, human judgement is required, and they can sometimes produce false or misleading results. In the W3C's words, evaluation tools cannot determine accessibility, they can only assist in doing so. Nor should you rely more on what tools say than on the real-life experience of the site's users.

When choosing one, the W3C lists features such as the tool's purpose (automated testing, help with manual testing or simulating the user experience), the type of product it evaluates, the standards it supports (most tools support WCAG), its scope (a single page or groups of pages) and its support for ACT Rules. A team may also gain from combining several tools to meet each member's needs at each stage.

Frequently asked questions

What are the W3C easy checks for web accessibility?

They are a first review covering the page title, image alt text, headings, contrast, text resizing to 200%, keyboard access, forms, moving content and multimedia. Most work in any browser; some rely on online tools such as WAVE or the W3C HTML Validator.

What is the minimum contrast ratio for accessible text?

For normal-size text, the contrast ratio with the background needs to be at least 4.5:1. The related WCAG criteria are 1.4.3 (AA) and 1.4.6 (AAA).

Is an automated accessibility checker enough?

No. According to the W3C, tools cannot check all accessibility aspects automatically, can produce false or misleading results, and can only assist in determining accessibility. Human judgement is required.

How do I test a website with the keyboard?

Set the mouse aside and move through the page with Tab and Shift+Tab. Check that every control can be reached, that you can leave every element, that the order is logical and that the focus is clearly visible.

If a page passes the easy checks, is it accessible?

Not necessarily. The checks cover just a few issues, and a page that passes them may still have significant barriers. For example, they do not cover links, data table markup or reliance on color.

Further reading on Conformly

Sources

This article relies on the official sources listed at the end of the page.