Short answer
Web accessibility means a site can be used by everyone, including people with disabilities. W3C’s WCAG standard defines it through four principles and three levels, A, AA and AAA. You can check keyboard use, text size, contrast, alt text and form labels without writing code.
Push the mouse to the edge of your desk, open your own site and move through it with the Tab key alone. If the focus vanishes somewhere in the menu, if a drop-down cannot be chosen from by keyboard, or if you never reach the “Send” button on the contact form, the site is closed to some visitors. Web accessibility is the check for exactly that: whether a site can be used by everyone, including people with visual, hearing, motor or learning difficulties. There is a short definition in the accessibility glossary entry too.
This guide covers the checks you can make today without code, and what to tell whoever builds the site. What pages a company site needs is in what a company website needs, and the ordering process is in commissioning a website; we do not repeat either here. Legal obligations are not the subject of this guide either; we only report the standard as W3C writes it.
What WCAG is and what its four principles say
WCAG (Web Content Accessibility Guidelines) is the international web accessibility standard published by W3C. Version 2.0 came out in December 2008, 2.1 in June 2018 and 2.2 on 5 October 2023. WCAG 2.2 has 13 guidelines, all grouped under four principles: perceivable, operable, understandable and robust. Each guideline has testable “success criteria”, and the criteria are split into three levels: A, AA and AAA.
Conforming to WCAG means meeting those criteria. In W3C’s conformance document, level A is the minimum; level AA requires meeting both the A and AA criteria, and level AAA requires all three. The summary for the robust principle is to maximise compatibility with current and future user tools. The figure below sets the four principles beside the guideline lines from W3C’s summary page and the checks in this guide.
W3C itself says WCAG is a technical standard rather than an introduction to accessibility. That is why we follow the method on W3C’s “Easy Checks” page below. The same page says these checks are designed to be quick, and that a page could pass all of them and still have significant barriers.
Seven checks you can make today
Here is the whole set at a glance. The table shows what each check asks for and what counts as a pass.
| Check | How you look | Counts as a pass |
|---|---|---|
| Keyboard | Put the mouse down; move with Tab and Shift+Tab | Every link, button and form is reachable; focus is visible |
| Text size | Raise the text size to 200% | Text does not vanish or overlap; no horizontal scrolling |
| Contrast | Measure text against its background | At least 4.5:1 for normal-size text |
| Alt text | Display each image’s alt text | Informative images have an equivalent text |
| Headings | Open the page’s heading outline | There are headings and their order makes sense |
| Form labels | Inspect each field; trigger an error | Every field has a label; the error message is clear |
| Page title | Read the title in the tab | Short, describes the page, differs from other pages |
1. Keyboard and visible focus
Click the address bar, put the mouse aside and press Tab; Shift+Tab goes back, arrow keys work in drop-downs, and Enter or Space selects. W3C looks for these things: can you Tab to every link, form field, button and media player control; can you Tab away from each element; does the order follow the reading order; and is the focus visible at every step. Focus getting caught in a media player with no way out is called a “keyboard trap”.
2. Raise the text to 200%
In W3C’s method the text size is raised to 200%; in Firefox there is a “Zoom Text Only” option, and Chrome needs an extension. Look for these things: does all the text get larger, does anything get cut off, does a heading overlap the main text, do buttons and form fields stay usable, and do you have to scroll sideways to read a sentence. Text embedded in an image does not get larger; W3C names this as a common problem.
3. Measure contrast
WCAG success criterion 1.4.3 (level AA) asks for a contrast ratio of at least 4.5:1 between normal-size text and its background, and at least 3:1 for large text. Text in a logo and purely decorative items have no requirement. You can pick the text and background colours in a contrast tool and read the ratio; W3C notes that this method is accurate but measures one item at a time. Light grey text on a light grey background is the typical failure.
4. Read the alt text
Every image that carries information needs a text equivalent, its alt text. For an image that is a button, the alt text describes the function, not the look: for a search button you write “search”, not “magnifying glass”. An image that is only decoration, one people do not need to know about, gets empty alt text. You do not need to write “image” or “button” in the alt text, because the screen reader says that anyway. A tool can find alt text that is missing; whether the text is appropriate is for you to judge by seeing the image in context. The alt text glossary entry has the short definition.
5. Pull out the headings
Any text that looks like a heading should really be marked up as one; keyboard and screen reader users move around a page by its headings. Open the heading outline from a browser extension or developer tools: is there a heading, is every text that looks like a heading in the list, does the order make sense. According to W3C, a page ideally opens with a single main heading similar to the page title and does not skip levels; these are not absolute requirements.
6. Try the forms
Every form field needs a visible label, correctly tied to the field, so that keyboard, voice input and screen readers work and clicking the label selects the field. Marking a required field only in red is not enough; add a sign such as an asterisk. Now trigger an error: leave a required field blank or type a badly formed phone number. Does the message say what is wrong and how to fix it?
7. Look at the page title
Read the title in the tab, or listen to it with a screen reader. It is the first thing a screen reader says on a new page, so trying a screen reader is easiest to start here. It should be short, describe the page and differ from the site’s other pages. W3C recommends putting the important information first: “About Acme Web Solutions” rather than “Acme Web Solutions, Inc. | About Us”.
What automated tools catch and what they miss
Scanning tools save time, and some can scan a whole site. W3C is still blunt: tools cannot check every aspect of accessibility automatically, human judgement is needed, they sometimes give false or misleading results, and they cannot determine accessibility, only assist in doing so. So do not treat a scan score as a substitute for how the site is really used.
| Topic | A tool can find | A person decides |
|---|---|---|
| Alt text | Alt text that is missing altogether | Whether the text describes the image correctly |
| Contrast | The ratio of colour pairs in the page | Whether the listed pairs are really visible on the page |
| Headings | An outline of the marked-up headings | Whether every heading-like text is marked up and the order makes sense |
The rows rest on the wording of W3C’s check pages: automated tests find missing alt text, while a person judges whether it is appropriate. In contrast tables some tools can list colour pairs that are not actually on the page. Keyboard and focus checks are done by hand.
Common mistakes
- Trusting the scan. The report comes back clean but the form cannot be sent by keyboard. W3C advises against relying on tool results over the real experience of users.
- Putting text inside an image. The words on a campaign banner do not grow when text is enlarged.
- Closing the media player to the keyboard. Focus goes in and cannot get out.
- Removing the focus outline. The “ugly” frame is deleted in the design, and a keyboard user cannot tell where they are.
- Making a heading only with large type. If text that looks like a heading is not marked up, a screen reader user cannot move around the page.
- Showing required fields by colour alone. The difference vanishes for people who do not tell the colours apart.
- Writing long alt text for decoration. It adds unimportant detail; a decorative image should get empty alt text.
- Leaving accessibility to the end. A fix added just before launch often cannot cure problems that came from the design. Speed works the same way: measure first, then fix, as in how to speed up a website.
What to write in the brief for whoever builds the site
Writing “make it accessible” in a brief is not enough; you need sentences that can be checked. You can write:
- Target standard and level: “WCAG 2.2, level AA.” You choose the level; AA covers the A criteria too.
- Contrast in the design: colour pairs for text and background approved in the design file; 4.5:1 for normal text, 3:1 for large text.
- Keyboard: the whole menu, forms, pop-ups and media player usable with Tab, with visible focus.
- Structure: headings marked up, a distinctive title on every page, form field labels tied to their fields.
- Content management: an alt text field visible when an image is added in the admin panel, left empty for decoration.
- Evidence at handover: an automated scan report plus the results of the seven checks above, with the pages they were run on.
Asking for these as separate items in the proposal also shows which checks the builder already applies. What a proposal should contain is listed in commissioning a website; how Detmore builds sites is on the web and software page.
Common questions
Is web accessibility the same as WCAG?
No. Accessibility is the goal: a site that everyone can use. WCAG is the standard W3C publishes for that goal, made of testable criteria. WCAG is a technical document; W3C offers separate introductory pages for beginners.
What do levels A, AA and AAA mean?
The success criteria are sorted into three levels. A is the minimum; conforming at AA means meeting both the A and AA criteria, and conforming at AAA means meeting all three. Which one to aim for is a decision you write into the brief.
Is an accessibility plugin or automated scan enough?
No. W3C says tools cannot check everything, sometimes give wrong results and cannot determine accessibility on their own. A scan is a good start and a regular check; for keyboard use, text size and whether alt text is appropriate, someone has to look.
One step you can take alone today
For your home page and your contact page, separately: put the mouse down and Tab through until you send the form, then raise the text to 200% and check that buttons and fields are still visible and usable. Write each problem you find on a list with the page name and one sentence. That list is the first accessibility brief you give whoever builds your site.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.