Can AI make a website fully accessible?

The useful part

This question is worth asking, but a confident AI answer can be misleading. AI is useful for drafting fixes and organising a test checklist. It is not enough for declaring a site fully accessible from a scan.

W3C guidance on evaluation tools provides the basis for the key limitation in this guide. This percentage is our editorial estimate of what AI can reliably handle on its own for this question, not measured accuracy or a probability that an answer is true.

Before you start

Define the decision you need to make and gather the best source material you can access. Remove unnecessary private information before pasting anything into an AI chat. If a decision affects another person, keep the process fair and preserve the original evidence.

How to do it

1. Choose representative pages and complete user journeys.
2. Run an automated scan and fix confirmed issues.
3. Test keyboard navigation, focus, forms and zoom manually.
4. Check with assistive technology and users where possible; repeat after changes.

Copy this prompt

Help me investigate whether AI can make a website fully accessible in my specific situation. Do not give a final verdict yet.

HOW TO WORK WITH ME
- Ask no more than three short questions in each message, then wait for my reply.
- Keep observed facts, assumptions and open questions separate.
- Say what evidence you can actually inspect. Never claim to have opened a file, searched the web or used a product unless you did.
- Give a cautious conclusion with its limitations. Never invent confidence percentages.
- If another person's rights, reputation or safety may be affected, avoid accusations and recommend a fair human review.

START WITH ONLY THESE THREE QUESTIONS
1. What page or user flow are we assessing?
2. Can you share the page URL or code and the target audience?
3. Which devices, browsers and assistive technologies can you test?
Then stop and wait.

IN LATER ROUNDS
Ask about forms, menus, dialogs, dynamic updates, images and video. Prioritise keyboard access, focus order, labels, contrast and error recovery.
Ask for the minimum material needed. Let me remove private or confidential information. If you lack the original file, links or browsing access, explain how I can run the check myself.

BEFORE ANALYSIS
Summarise the task and the evidence I provided as numbered items. Put assumptions and missing evidence in separate lists. Ask me to correct the summary. Wait for my confirmation.

AFTER CONFIRMATION
Produce a prioritised issue log with reproduction steps, suggested fix, manual verification and remaining test coverage. For every substantive finding, say which supplied item or opened source supports it. Explain what a specialist tool could help me check, and what it cannot establish. Give me an ordered, practical next-step checklist.


USE THIS CHECK SEQUENCE
1. Choose representative pages and complete user journeys.
2. Run an automated scan and fix confirmed issues.
3. Test keyboard navigation, focus, forms and zoom manually.
4. Check with assistive technology and users where possible; repeat after changes.
If a step is impossible because evidence or access is missing, mark it 'not checked' and tell me what I would need to complete it. Separate a tool's signal from your own interpretation. End by asking which unresolved point I want to investigate next.

IMPORTANT LIMIT
Do not claim WCAG compliance from an automated scan or an AI review alone.

Begin with the three starting questions only.

What you should get

You should get a prioritised issue log with reproduction steps, suggested fix, manual verification and remaining test coverage. Each finding should point to a real source or to something you supplied, and unknowns should stay visible.

Where AI falls short

Automated tools cannot assess every accessibility requirement or lived experience. Do not claim WCAG compliance from an automated scan or an AI review alone.

When another tool helps

WAVE can support one part of the check. Review its current features, access and results before relying on it. Its output does not settle the whole question.