Accessibility check

Page Lemon checks your published pages for common accessibility problems, such as photos without a description, buttons with no words or text that is hard to read, and your AI can fix them for you. It is an automated check: it finds common problems, not all of them, and it is not a full accessibility audit or a compliance certificate.

Last updated 19 October 2026 · View as Markdown

Say this to your AI

Or, after a change:

What your AI will ask you

• What each photo shows, in a few words, for the photos that have no description. Your AI should never guess what is in a photo.
• Whether a photo is only decoration (a pattern, a divider), so screen readers can skip it.
• Whether it may change a colour, when some text is hard to read against its background.
• Your yes before it publishes the fixes.

What to have ready

• A few words about each photo: who or what is in it ("Our bakery on Mill Road at opening time"). Nothing else to prepare.
• Nothing to install. The check runs on Page Lemon each time you publish.

What happens

1. Every time you publish, Page Lemon checks up to 40 pages and tells your AI the main problems, with a count. Nothing is ever blocked.
2. Your AI asks for the full list: each problem, the page it is on, the part of the page and how to fix it.
3. It shows you what it will change and asks you about anything only you know, such as what a photo shows. It publishes after your yes.
4. It offers a test: it runs the check again on the new version and tells you what's fixed and anything left.

You can also see the latest check in the app: open your site, then the Get found tab, then Accessibility. Ask your AI to fix these copies a message to paste into your AI.

What it checks

• Photos without a description (alt text), which screen readers read out to blind and partially sighted people.
• Links and buttons with no words, such as an icon on its own, which a screen reader can't name.
• Form fields without a label. A grey hint inside the box disappears when people type, so it doesn't count.
• Text that is hard to read against its background (low contrast), when both colours are set in your site's own styles.
• A missing page language or page title, sound or video that plays by itself, embedded maps or videos without a title, and zoom turned off on phones.
• Headings out of order, such as no main heading, or a small heading straight after a big one with a level skipped.
• Buttons and links too small to tap, when your site's styles make them smaller than 24 by 24 pixels.

Each problem names the WCAG 2.2 rule it relates to, where there is one. WCAG is the international guideline for accessible websites.

Good to know

• It is not a full audit. An automated check can't tell whether a description is accurate, whether the page makes sense with a keyboard alone, or whether text over a photo is readable. Try your site with your keyboard (the Tab key) and your phone's screen reader, and ask people who use them.
• It is not a certificate. Passing the check doesn't prove your site meets a law or a standard.
• What it reads: the pages and styles as you published them. Anything a script adds to the page later isn't checked.
• Big sites: up to 40 pages are checked each time, your home page first.
• Search engines like it too. Photo descriptions, a page language, one main heading and clear link text also help your pages in search. See Get found online.

If something looks wrong, see Fix a problem.

For AI assistants: the setup guide is at pagelemon.com/agents/accessibility.