Website planning

Accessibility First Checks an Owner Can Run (Not a Legal Guide)

Try keyboard, zoom, contrast, image, and form checks to find accessibility barriers. Know when a broader evaluation is needed.

Wild Article 024, 2026-11-19: Accessibility First Checks an Owner Can Run (Not a Legal Guide)

You can catch some common accessibility barriers on your own site by trying it with a keyboard, enlarging the page, checking text and image descriptions, and walking through a form. These are useful first checks, not a verdict that a site is accessible. The W3C’s Easy Checks explicitly says a page could seem to pass these checks and still have significant barriers.

Start with the pages that matter most to a customer: the home page, a service or product page, and the contact, booking, or checkout flow. Repeat on different page types, especially if their menus, pop-ups, or forms differ.

A practical first-pass checklist

1. Put the mouse aside

Use Tab to move through links, buttons, menus, and form fields; use Shift+Tab to go backward, Enter to follow a link, and Space or Enter to activate controls. Can you reach every action? Is there a visible highlight showing where you are? Does the order make sense? Can you open and leave menus or dialogs without getting stuck? W3C’s WCAG 2.2 Quick Reference includes keyboard access and visible focus criteria. This walk-through can expose problems, but it is not a full assistive-technology test.

2. Enlarge the page and check the structure

Zoom your browser to 200%. Look for text that overlaps, gets cut off, or disappears, and controls that become hard to use. Check whether each page has a useful title and whether section headings describe what follows. A heading should be a real heading in the page structure, not just larger or bold text. W3C’s Easy Checks explains why page titles and headings help people orient themselves, and WCAG 2.2 includes text resizing and reflow criteria. Treat zoom as a quick visual check, not a complete test of responsive behavior.

3. Review images for purpose, not just presence

If your site editor has an alternative-text field, look at the words for each important image. Ask what a person needs to understand from that image in this particular spot on the page. A useful description is concise and conveys the image’s purpose, not its file name or every visual detail. A linked or button image should describe the action or destination. A purely decorative image can have an empty alternative instead of a description. For a chart or diagram, a short label may not convey all the information, so provide the key information in page text too. The W3C Images Tutorial explains these different cases. As a practical habit, skip generic phrases like “photo of,” and do not repeat nearby text.

4. Look at contrast and color cues

Check text on the backgrounds where it actually appears, including buttons, navigation, and text over images. A contrast checker can help compare a foreground and background color; WCAG 2.2’s criterion for normal text is at least 4.5:1, with exceptions such as large text and logos. Don’t judge contrast by eye alone. Also check that color is not the only clue: a required field, error, or link should have another cue, such as a label, message, underline, or icon with text.

5. Try a form and any media

Find a contact or booking form. Can you move through it with the keyboard? Does every field have a clear label, and does the page explain which fields are required? If you can safely use a test or preview environment, try leaving a required field blank. A useful error says what needs attention and how to fix it, rather than relying only on red color. Avoid submitting a real order, payment, or booking just to test a live site. If the site has videos with spoken information, check that accurate captions are available; captions should convey speech and important sounds.

A simple tracking note helps turn observations into work: record the page, the step that caused trouble, what you expected, and what happened instead. This is a simple habit, not a formal W3C method. Fix clear content issues you control, then repeat the check after changes.

When to bring in an accessibility specialist

Get experienced help when a key task cannot be completed by keyboard; a menu, pop-up, booking widget, or checkout behaves unpredictably; form labels or error messages require code changes; or a screen reader is needed to confirm how a critical flow is announced. A specialist can also help when the site has many templates, third-party tools, PDFs, or video, or when you need a documented evaluation against a stated WCAG version and level. If you need advice about legal duties or risk, speak with a qualified attorney. A technical review is not legal advice.

When hiring, ask what pages and user journeys will be tested, whether the work combines automated scans with hands-on keyboard and screen-reader checks, which WCAG version and success criteria are in scope, how issues will be prioritized, and whether fixes will be retested. A scan can find some patterns; it cannot judge every image description or prove that a person can complete every task.

Limits of these checks

W3C's Easy Checks are preliminary, not a complete accessibility evaluation. Passing them does not establish compliance or show that every person can complete every task. Use the observations to prioritize a broader review when needed. Legal duties are outside this guide.

Evidence

Sources

  1. Easy Checks – A First Review of Web AccessibilityW3C WAI · Retrieved
  2. How to Meet WCAG (Quickref Reference)W3C WAI · Retrieved
  3. Images TutorialW3C WAI · Retrieved

A useful next step

Keep a useful record

Use the ownership checklist to organize the accounts and people involved in your site.

Open the ownership checklist