Website Accessibility: Practical Checks for Forms and Navigation

Website Accessibility: Practical Checks for Forms and Navigation

You can find most serious accessibility problems in a website's forms and navigation in about an hour, with nothing more than a keyboard, the browser's zoom and a careful eye. Put the mouse aside and try to use the menu and send the contact form with the Tab key; check that every field has a visible label; make a deliberate mistake and see how the error is explained; zoom the page to 200%. These checks don't replace a full evaluation against the Web Content Accessibility Guidelines (WCAG), but they catch the problems that most often stop people from contacting you or buying.

Why start with forms and navigation

Forms and navigation are where visitors stop reading and start doing, and where common errors cluster. WebAIM's 2026 analysis of the home pages of the top one million websites, carried out in February 2026, detected WCAG failures on 95.9% of them. Missing form input labels were found on 51% of home pages, empty links on 46.3% and empty buttons on 30.6%. The most common problem of all, low-contrast text, appeared on 83.9%.

There is a legal side as well. According to AccessibleEU, the EU's accessibility resource centre, the European Accessibility Act applies to products and services placed on the market after 28 June 2025, including e-commerce and banking services, and the related European standard EN 301 549 refers to WCAG 2.1. Whether and how the Act applies to your business depends on the national law that transposes it, so check with a legal adviser. The checks below are worth doing either way, because they make forms easier for everyone.

Check 1: Use the site with the keyboard only

Click into the browser's address bar, then press Tab repeatedly. Shift+Tab goes back, Enter activates links and buttons, Space ticks checkboxes, and the arrow keys move between radio buttons and through dropdowns.

  • Can you always see where you are? W3C's Easy Checks describe keyboard focus as a visible indicator that moves as you tab through the page. If it disappears, the browser's outline has probably been removed in CSS. web.dev advises styling the focus indicator rather than removing it, with a contrast ratio of at least 3:1.
  • Does the order make sense? Focus should follow the visual order of the page. Jumps from the header to the footer and back often come from positive tabindex values, which web.dev advises avoiding.
  • Is there a skip link? The first Tab on a page should reveal a "Skip to main content" link, so keyboard users can bypass the menu.
  • Is the focused element hidden? WCAG 2.2 added criterion 2.4.11 Focus Not Obscured (Minimum), Level AA: the focused element must not be completely hidden by author-created content such as a sticky header, a cookie banner or a chat widget.
  • Can you get back out? Open the menu, a dropdown and any pop-up, then close them using only the keyboard. If focus gets stuck, that is a serious barrier.

Check 2: Navigation and links

  • Every link and button has a text name. An icon-only link – a phone, a magnifying glass, a social network logo, a menu icon – gives a screen reader nothing to announce unless it has a text alternative.
  • Dropdown menus work without a mouse. Submenus that open only on hover lock out keyboard and touch users.
  • Link text says where it goes. Ten links called "Read more" mean nothing when a screen reader lists the links on a page.
  • Pages have meaningful titles and headings. Easy Checks notes that page titles are the first thing screen readers read and help people know where they are, and that headings should reflect the page's structure, because screen reader users often navigate by them.
  • Help is in the same place on every page. WCAG 2.2 criterion 3.2.6 Consistent Help (Level A) asks that help mechanisms repeated across pages – contact details, a contact link, a chat – appear in the same relative order.
  • Targets are big enough. Criterion 2.5.8 Target Size (Minimum), Level AA, sets 24×24 CSS pixels as the minimum for pointer targets, with some exceptions.

Check 3: Form labels and instructions

  • Every field has a visible label that stays visible while typing. web.dev's accessibility course says labels must be visible at all times and accurately describe the field. Placeholder text inside the field is not a label.
  • Labels are connected to their fields in the code, so that a screen reader announces the label when the field gets focus. A quick test: click the label text. If the cursor doesn't jump into the field, the connection is probably missing.
  • Required fields are marked in text – for example "(required)" in the label – not only by colour. Required fields are one of the form checks in Easy Checks.
  • Related fields are grouped – an address, or a set of radio buttons – with fieldset and legend, so the question for the group is clear both visually and to assistive technology.
  • Format rules are explained up front – date formats, password rules – not only after an error.
  • Autocomplete attributes such as autocomplete="email" tell browsers and assistive technology what each field is for, which helps screen reader users and people with cognitive and reading difficulties.

Check 4: Errors, confirmation and logging in

Submit the form empty, then again with a wrong email address.

  • The field with the error must be clearly identified and the error described in text – web.dev's course is explicit about this. "Invalid input" is not enough; "Enter an email address, such as name@example.com" is.
  • Colour alone, such as a red border, doesn't tell everyone what is wrong.
  • Everything the visitor typed is still there after the error.
  • Success is confirmed with a clear message, not just an empty form.
  • Nothing submits or changes the page by itself when a field receives focus or a value is chosen, unless people were warned first.
  • In multi-step processes, don't ask for the same information twice. WCAG 2.2's Redundant Entry criterion (3.3.7, Level A) asks that information already entered is filled in automatically or available to select.
  • For logins, WCAG 2.2's Accessible Authentication (Minimum) criterion (3.3.8, Level AA) says a login step must not require a cognitive function test unless an alternative or a helping mechanism is offered. Letting password managers fill in the fields and allowing paste helps here.

Check 5: Zoom and contrast

Press Ctrl (Cmd on a Mac) and + until the browser shows 200%. According to W3C's Easy Checks, all text should still be readable, nothing should be hidden behind other text or images, and you shouldn't need to scroll sideways to read the content. A menu collapsing into an icon at that size is fine. Then look at contrast: light grey text on white, text over photos and pale placeholder text are typical problems. A free contrast checker will tell you whether a pair of colours passes.

One-hour checklist

CheckHowPasses if
Keyboard navigationTab through the header, menu, page and footerFocus is always visible, the order is logical, nothing traps you
Skip linkFirst Tab on the page"Skip to main content" appears and works
MenusOpen submenus with the keyboard and on a phoneEvery item can be reached
Icon links and buttonsCheck with a screen reader or browser toolsEach one has a text name
LabelsClick each labelThe cursor moves into the field
Required fieldsRead the formMarked in text
ErrorsSubmit empty and wrong dataField identified, error explained, data kept
ZoomZoom to 200%Readable, no sideways scrolling
Page titlesLook at the browser tabsEach title says what the page is

What automated tools can and can't tell you

Free browser extensions and testing tools quickly find missing labels, empty links and low contrast – the kinds of issues in WebAIM's figures. They can't tell you whether a label makes sense, whether the focus order is logical or whether an error message actually helps. W3C itself says its Easy Checks cover only a few issues and that a page that passes them may still have significant barriers. For an online shop, a booking system or anything with legal requirements, plan a proper evaluation, ideally including people who use assistive technology.

Fixing labels, focus styles and error messages is often a matter of days, not a redesign. If you would like us to go through these checks on your site, or build accessibility into a new website from the start, get in touch. Our company website checklist covers the other basics, and if you are commissioning a new site, put the accessibility level you expect into your website brief.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.