Accessibility
Page has a title for screen readers
a11y.document-title
Why this matters
The title is what appears in the browser tab, in bookmarks, and as the headline of your search result. It is also the first thing a screen reader announces on arrival.
Who fixes it
You can, usually
Roughly how long
Minutes
Care needed
Low risk to change
How to fix it
Add a unique, descriptive <title> to every page.
On your platform
WordPress
The search-result title in your SEO plugin, which is also what a screen reader announces. If no SEO plugin is installed, WordPress falls back to the post title plus the site name, so a missing title means the theme's `<head>` is not calling `wp_head()`.
Shopify
The title in the search engine listing section of the product, page or collection — and Online Store → Preferences for the home page.
Drupal
The Metatag module's title pattern on the content type, or the page title on the node itself.
Joomla
The Browser Page Title on the menu item or article's Page Display tab.
How we score it
Failing this check takes up to 8 points off your accessibility score. It is a fact about your site rather than a measurement, so it reads the same on every scan until you change something.
Does your site pass this one?
This check runs on every scan, along with the other 106. Free, no account, and you see the evidence for each result.
Check my siteOther accessibility checks
- Accessibility check completedThe accessibility pass runs inside a real browser, and a few things can stop it: a content security policy that blocks our script, or a page that never finishes loading. When that happens the accessibility section is marked unchecked rather than passed, because finding no problems and being unable to look are not the same result.
- Buttons have readable labelsA button with no readable label is announced to a screen reader as nothing more than 'button'. This usually happens when the button contains only an icon. If the unlabelled one is a menu toggle or an Add to Basket, the site becomes unusable rather than merely awkward.
- Form fields are labelledA form field without a label gives a screen reader user no indication of what to type into it. Placeholder text is not a substitute — it vanishes the moment somebody starts typing. On a contact or checkout form this is the difference between an enquiry and a visitor who leaves.
- Headings run in orderScreen reader users navigate by jumping between headings. When levels are skipped, that outline stops matching the page and becomes confusing to move through.
- Images have descriptions for screen readersSomeone using a screen reader hears nothing where these images are. If any of them are product photos, logos or buttons, that part of the page simply does not exist for them.
- Links have readable textA screen reader announces these as just "link", with nothing to say where they go. Icon-only links, such as social media buttons, are the usual cause.