Captions, alt text and plain-language rewrites are now quick to make. How to use AI for accessibility, and what still needs a person.
An accessible website or document is one that people can use whatever their ability: with a screen reader, a keyboard only, low vision, without sound, or while reading in a second language. It is also simply clearer for everyone.
AI has made several accessibility tasks much faster. It hasn’t made them automatic.
Where AI genuinely helps
- Captions and transcripts for videos and recorded events, produced in minutes rather than hours.
- First drafts of alt text, the short descriptions that screen readers read out for images.
- Plain-language rewrites of dense policies, forms and instructions.
- Spotting likely issues in code, like missing labels on form fields or buttons with no name.
Where a person still matters
Alt text depends on purpose. AI can describe a photo of your clinic’s front desk. Only you know whether it is there to show the space is wheelchair accessible or just to look welcoming, and that changes what it should say. Decorative images should have no description at all.
Captions need checking for names, technical terms and anything said over background noise.
Automated checkers catch some problems. Many others, like a confusing order of steps in a booking form or a menu that traps keyboard users, only show up when a person actually tries to use the site.
Use AI to get the first draft done. Test with real people to know it works.
The tools are improving too
The tools developers use are getting more accessible themselves. In July, Anthropic added a screen reader mode to Claude Code that replaces the visual terminal interface with plain, linear text for screen readers such as VoiceOver and NVDA.
A short checklist for your site
- Can you complete a booking or order using only the keyboard?
- Does every form field have a visible label?
- Is text readable against its background, including on photos?
- Do videos have captions?
- Do images have useful descriptions, or none if they are decorative?
- Does the page still make sense when zoomed to 200%?
We build websites to WCAG 2.1 AA, the widely used standard, and test with keyboards and screen readers before launch.
Sources
From the DYOL blog. Photo by Matthew Moloney on Unsplash.
Keep reading
All posts
What the 2026 developer survey says about how software gets built
Most developers now use AI every day, and most only trust it when they can check it. What Stack Overflow’s survey tells business owners hiring developers.

How a little code changes a whole workday
Software doesn’t have to be big to matter. Small, well-placed tools remove the steps people repeat a hundred times a week.

Off-the-shelf or custom software? A simple way to decide
Buy what fits, build what doesn’t. Five questions that help a small business choose, and the common mistakes in both directions.
A free 20-minute conversation, then an honest assessment. You’ll know what it costs and how long it takes, in writing, at a fixed price.
Or email lloyd.delacruz@outlook.com. We reply within 24 hours.
