Accessibility report for w3.org

November 9, 2026 · 4 pages checked

7 problems found by the automated checker (3 that can stop some visitors completely), and 1 thing it couldn't decide that need a person to look. Start with the first few: they're sorted by how much they get in visitors' way.

Automated checks only find some problems. On W3C's demonstration site they found about a quarter of the barriers W3C's experts documented, so the checks by hand at the end matter as much as this list. This report is a starting point, not a legal or compliance audit.

Fix these

Images are missing alternative text

Blocks some visitors 122 elements on 4 pages

People using screen readers may hear the file name read out, or hear nothing useful, when they reach these images. That makes the page noisy and confusing.

Where

How to fix it

  1. Open each image's settings in your page editor and find the field for alternative text (alt text).
  2. If the image shows something meaningful, such as a logo or a photo, write a short description of what it shows.
  3. If the image is only decoration, like a border or spacer, mark it as decorative or leave the alt text empty on purpose. Many site builders have a 'decorative' option.
  4. If these images come from your theme or template, check the theme's settings, or remove images you no longer need.

…and 117 more like these.

Checker rule image-alt · WCAG 1.1.1 · plain-language explanation by Claude, checked by code

Radio buttons have no labels

Blocks some visitors 11 elements on 1 page

People using screen readers hear only 'radio button' with no words, so they can't tell what each choice means. People who have trouble clicking small circles also can't click a label to pick an option.

Where

How to fix it

  1. Find the form or question with these round choice buttons in your page editor.
  2. Give each choice its own visible text, such as '1', '2' or the answer it stands for, and make sure the text is linked to its button as that choice's label.
  3. If your form tool has a label or 'option text' field for each choice, fill it in rather than typing loose text next to the button.
  4. Preview the page and click the text beside each button. If the button gets selected, the label is connected.

…and 6 more like these.

Checker rule label · WCAG 4.1.2 · plain-language explanation by Claude, checked by code

Dropdown menus have no label

Blocks some visitors 5 elements on 4 pages

People using screen readers hear only 'combo box' or 'menu' with no hint of what it's for. They can't tell what choices they are picking.

Where

How to fix it

  1. Find each dropdown in your page or form editor and look for a label, title or 'field name' setting.
  2. Add a short label that says what the dropdown is for, such as 'Choose a country' or 'Go to page'.
  3. If your builder only shows a placeholder or nearby text, make sure it is set as the field's actual label, not just text placed next to it.
  4. Save, then check the page again.

…and 3 more like these.

Checker rule select-name · WCAG 4.1.2 · plain-language explanation by Claude, checked by code

Links with no text for screen readers

Makes things hard 19 elements on 4 pages

People using screen readers hear only 'link' with no name, so they can't tell where it goes. People who navigate by keyboard are also affected.

Where

How to fix it

  1. Open each image link's settings and add alt text (a short description) to the image, such as the page it goes to.
  2. Use the same words as the picture shows. For example, if the image says 'News', the alt text should say 'News'.
  3. If your site builder lets you, use real text links or buttons for the menu instead of pictures of words.
  4. For the small arrow link, add alt text that says where it goes, such as 'More news'.

…and 14 more like these.

Checker rule link-name · WCAG 2.4.4, WCAG 4.1.2 · plain-language explanation by Claude, checked by code

Text color too faint against background

Makes things hard 10 elements on 2 pages

People with low vision or who read in bright light may struggle to read this text. Words blend into the background and are easy to miss.

Where

How to fix it

  1. Find the text in your editor and open its color settings, or the style settings for that section.
  2. Make the text darker, or make the background lighter, so the two stand out more from each other.
  3. If the text color was set by hand, remove it or reset it to the site's default text color.
  4. Run the checker again to see if the text now passes. The goal is a contrast of at least 4.5 to 1.

…and 5 more like these.

Checker rule color-contrast · WCAG 1.4.3 · plain-language explanation by Claude, checked by code

Small links are hard to tap or click

Makes things hard 8 elements on 4 pages

People who have trouble using a mouse precisely, or who tap on a phone or tablet, may miss these links or hit the wrong one. The links are only 20px tall and sit close to other links.

Where

How to fix it

  1. Find the 'Report' links and open their style or button settings. Look for size, padding, or spacing options.
  2. Make each link at least 24px tall and 24px wide. Adding padding around the text is the easiest way.
  3. Add more space between each 'Report' link and the links or buttons next to it.
  4. Save, then view the page on a phone to check that the links are easy to tap.

…and 3 more like these.

Checker rule target-size · WCAG 2.5.8 · plain-language explanation by Claude, checked by code

Page language is not set

Makes things hard 4 elements on 4 pages

People using screen readers may hear the page read aloud in the wrong accent or language, which can make it hard or impossible to understand. Translation tools can also guess wrong.

Where

How to fix it

  1. Open the site's general or language settings and choose the main language of your site.
  2. In WordPress, this is usually in Settings under General, called Site Language. Squarespace and Wix have a similar language or region setting in the site's settings.
  3. If you can't find a language setting, check whether your theme or template has an update, or ask whoever built it to add the language to the page code.
  4. Save, then run the checker again to confirm the problem is gone.

…and 3 more like these.

Checker rule html-has-lang · WCAG 3.1.1 · plain-language explanation by Claude, checked by code

Check these by eye

The checker couldn't decide these, often text over a picture or a background it can't measure.

Text color may be hard to read

Makes things hard 9 elements on 4 pages

People with low vision or color blindness, and anyone viewing the screen in bright light, may struggle to read this text if it doesn't stand out from the background. The checker could not decide on its own because there is a background image, so a person needs to look.

Where

How to fix it

  1. Look at each piece of text listed here on your live page and check whether it is easy to read against the picture behind it.
  2. If it is hard to read, change the text color or the background in the site's design or style settings so they differ strongly (dark on light, or light on dark).
  3. If the text sits on a photo or pattern, try a plain solid color behind the text, or a simpler image.
  4. Check again with a contrast checker tool, or ask someone else to read the text on the page.

…and 4 more like these.

Checker rule color-contrast · WCAG 1.4.3 · plain-language explanation by Claude, checked by code

Check these by hand (about 10 minutes)

No automated tool can test these. They follow W3C's Easy Checks.

  1. Use the keyboard only (WCAG 2.1.1)
    Put the mouse away and press Tab to move through the page. You should be able to reach every link, button and form field, and use each one with Enter or the space bar.
  2. See where you are (WCAG 2.4.7)
    While you press Tab, there should always be a visible outline or highlight on the thing you're on.
  3. Skip the menu (WCAG 2.4.1)
    The first press of Tab should offer a 'Skip to main content' link, so keyboard users don't tab through the whole menu on every page.
  4. Page titles (WCAG 2.4.2)
    Look at the title in the browser tab. Each page's title should say what that page is, not just the organization's name.
  5. Headings (WCAG 1.3.1)
    Text that looks like a heading should be set as a heading in your editor (Heading 2, Heading 3), not just made big and bold.
  6. Form labels and instructions (WCAG 3.3.2)
    Every form field (donate, volunteer, newsletter) needs a visible label, and required fields or formats should be explained in words.
  7. Not by color alone (WCAG 1.4.1)
    If something is shown only with color (required fields in red, a link only in a different color), add a word or symbol too.
  8. Text in pictures (WCAG 1.4.5)
    Event flyers and graphics with words in them can't be read by screen readers or resized. Put the key details (date, place, how to sign up) in the page text too.
  9. No surprises (WCAG 3.2.2)
    Choosing from a drop-down or clicking into a field shouldn't jump to another page or open a new window by itself.

Pages checked

Checks: axe-core 4.14.0, WCAG 2.x Level A and AA rules. Made with access-check.