All insights
Websites

Your Homepage Probably Fails These 6 Accessibility Checks

20 Nov 2026 · 7 min read

Every year, the team at WebAIM runs automated accessibility tests on the homepages of the top one million websites. The 2026 results are out, and they're a useful reality check: 95.9% of those homepages had detectable failures against the Web Content Accessibility Guidelines (WCAG), with an average of 56.1 errors per page. That's up from 51 errors per page in 2025.

Here's the useful part for a small business. Six error types made up 96% of all the errors found. They're also some of the easiest to spot yourself. Below is a six-check self-audit you can run on your own homepage in about 12 minutes, with a note on who usually fixes each one.

What you should take away

Open your homepage in an accessibility checker such as WAVE, look for the six error types below, and write down what you find. Most fixes sit with whoever manages your website theme or content, and many take minutes once someone knows where to look. A clean result is a good start, and a full accessibility review still needs a person testing the site.

What the WebAIM numbers measure

WebAIM used its WAVE tool to test one million homepages in February 2026. The report is clear that it only counts errors software can detect automatically. In WebAIM's words, the absence of detected errors does not indicate that a page is accessible or conformant. So treat these six checks as the common, findable problems, and a starting point for your site.

The six most common error types, with the share of homepages that had each one:

  1. Low contrast text: 83.9%
  2. Missing alternative text on images: 53.1%
  3. Missing form input labels: 51%
  4. Empty links: 46.3%
  5. Empty buttons: 30.6%
  6. Missing document language: 13.5%

Before you start: two minutes of setup

Go to wave.webaim.org, enter your homepage address and run the test. WAVE shows your page with small icons on each issue and a summary panel listing errors by type. WebAIM also offers browser extensions for Chrome, Firefox and Edge, which help with pages behind a login. Keep a note open with three columns: the check, what you found, and who will fix it.

The six-check self-audit

1. Low contrast text (about 2 minutes)

What it is: text that's too close in colour to its background, such as light grey on white or white on a pale photo. WCAG asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.

How to check: in WAVE, look for "Very low contrast" errors and note each flagged item. To test a specific pair of colours, enter them in WebAIM's contrast checker. Then look at your page on a phone outdoors. If you squint to read it, so will your customers.

Who fixes it: whoever controls your theme colours. On Shopify, Squarespace or Wix that's often a theme setting. On a custom site, it's your designer or developer.

2. Missing image alt text (about 2 minutes)

What it is: alternative text is the short description a screen reader reads aloud in place of an image. WebAIM found 16.2% of all homepage images had none.

How to check: look for WAVE's "Missing alternative text" errors. Then ask one question of each image that carries meaning: does the description say what a customer needs to know? "Team photo" helps less than "Our three plumbers outside the Ipswich workshop". Images that are pure decoration can use empty alt text, so screen readers skip them.

Who fixes it: usually you or whoever edits your content. Most website builders have an alt text field in the image settings.

3. Unlabelled form fields (about 2 minutes)

What it is: a form field without a proper label, so a screen reader announces "edit text" and leaves the visitor guessing. Placeholder text inside the box tends to disappear once someone starts typing, so it works best alongside a label.

How to check: look for WAVE's "Missing form label" errors on your contact, quote or newsletter form. A quick hands-on test: click the visible label text above a field. On a well-built form, the cursor jumps into the field.

Who fixes it: your developer, or the settings in your form builder. Many form plugins have a "show label" option that's been switched off for looks.

4. Empty links (about 2 minutes)

What it is: a link that a screen reader can only announce as "link". These are often icon links, such as social media logos in the footer or a logo image that links home without alt text.

How to check: look for WAVE's "Empty link" errors and click the icon to see where it sits on your page. Footers and headers are the usual spots.

Who fixes it: your developer or theme settings. The fix is a short text label or alt text on the icon, such as "Instagram" or "Home".

5. Empty buttons (about 2 minutes)

What it is: a button that shows only an icon, so a screen reader announces it as just "button". Think of the magnifying glass for search, the three-line menu icon, the cart icon or the X that closes a pop-up.

How to check: look for WAVE's "Empty button" errors. Imagine a visitor who uses a screen reader trying to open your menu on a phone: they'll hear "button" and little else. Each icon button should announce what it does, such as "Open menu" or "Search".

Who fixes it: your developer. It's usually a small change to the theme code.

6. Missing page language (about 1 minute)

What it is: a setting in the page code that tells screen readers which language to speak. It helps the voice pronounce your words correctly.

How to check: WAVE flags "Language missing or invalid". You can also right-click your page, choose View Page Source, and look at the first few lines for something like <html lang="en"> or lang="en-AU".

Who fixes it: your developer. It's typically a single line in the site template.

Copy this audit record

  • Date checked and page tested (start with the homepage).
  • Contrast: number of WAVE contrast errors, and which colours.
  • Alt text: images missing alt text, and images with unhelpful descriptions.
  • Form labels: which form, which fields.
  • Empty links: which icons, and where on the page.
  • Empty buttons: which icons, and what each one does.
  • Page language: present or missing.
  • Owner for each fix, and a date to check again.

When you send the list to your developer, include the WAVE results link and a screenshot for each item. Our guide on reporting website problems so they get fixed faster has a simple template for this.

Limits to keep in mind

These six checks cover what software can find. Plenty of barriers need a person to spot them, such as whether a page works with a keyboard alone, whether headings make sense, or whether a checkout can be finished with a screen reader. Our 15-minute website launch check includes a keyboard test you can add to this audit. Automated tools can also flag items that turn out fine on review, so check each one before asking for a fix. Once your homepage is done, run the same audit on your contact page and your most visited service or product page.

The Australian picture

The Disability Discrimination Act 1992 makes disability discrimination unlawful in areas of public life. In April 2025 the Australian Human Rights Commission published its Guidelines on equal access to digital goods and services to help organisations meet their obligations when they provide goods and services online. The Commission says the guidelines are guidance rather than law, and suggests organisations seek independent legal advice about their own compliance. This article is general information. For your specific obligations, talk to a qualified adviser.

Takeaway

Most accessibility errors on the web come from the same six problems, and you can find them on your own homepage in about 12 minutes. Write them down, assign each one, and check again once the fixes are live. It's one of the quickest ways to make your site easier for every customer to use.

Want a hand fixing what your audit finds? Contact Maud Digital and we'll go through the list with you.

Source note: This original Maud Digital guide uses figures from WebAIM's The WebAIM Million 2026 report, which tested one million homepages with automated tools in February 2026; WebAIM's WAVE and contrast checker; the W3C's WCAG 2.2 contrast guidance; and the Australian Human Rights Commission's guidelines linked above. It is a first-pass self-audit; a complete accessibility or legal review goes further. AI-assisted research and drafting were reviewed, edited and adapted by Maud Digital.

General information to help you decide, based on public sources at the date shown. For legal, tax or compliance questions about your business, speak with a qualified adviser.

let's talk

Want technology decisions like these made for you?

book a discovery call