How AI can respect accessibility by default

Accessibility is about making sure people can use a website regardless of how they experience it: through a screen reader, with a keyboard instead of a mouse, with low vision, colour blindness, a tremor, or simply on a small phone in bright sunlight. It is not an add-on for a minority. Many accessibility practices make sites better for everyone.

The field rests on a large body of human work. Disabled people, advocates, developers and designers have spent many years documenting barriers and how to remove them. The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the best-known result: a detailed, carefully debated set of criteria that much of the industry uses as its reference.

This is an area where AI design tools have a real opportunity. Many accessibility practices are consistent, rule-based and easy to forget when you're working quickly. A tool can apply them every time. But some parts depend on meaning and context, and those still need a human.

What a tool can handle by default

When an AI design tool is built thoughtfully, a lot of good practice can be baked into how it generates pages. These are the kinds of things it can get right without being asked.

Proper structure

Screen readers and other assistive technologies rely on the underlying structure of a page: which text is a heading, which is a list, where the navigation is, where the main content begins. A tool that generates clean, semantic markup, with headings in a logical order and regions properly marked, gives assistive technology what it needs to help people navigate.

Colour contrast

Text needs enough contrast against its background to be readable by people with low vision, and by anyone looking at a screen in poor conditions. WCAG sets out specific contrast ratios; for normal body text at its AA level, the minimum is 4.5 to 1. A tool can check its colour choices against these thresholds automatically, which is far more reliable than judging by eye.

Readable type

Comfortable default text sizes, sensible line spacing and reasonable line lengths help people with dyslexia, low vision and anyone reading on a phone. These are long-established typographic practices that a tool can apply consistently.

Keyboard access and visible focus

Some people navigate entirely by keyboard. Every link, button and form field needs to be reachable in a logical order, and the currently focused element needs a clear visible outline. Designers sometimes remove focus outlines because they look untidy; a tool can keep them, styled to fit the design.

Labelled forms

Form fields need labels that are properly connected to them, not just placeholder text that disappears when you start typing. This is a simple pattern to apply consistently and a frequent source of problems on hand-built sites.

Comfortable touch targets

Buttons and links that are too small or too close together are hard to tap accurately, especially for people with limited dexterity. Generous sizing and spacing can be part of the default design.

Respecting motion preferences

Some people experience discomfort or dizziness from animation. Operating systems let users ask for reduced motion, and a site can honour that setting by toning down or removing non-essential movement.

What still needs you

Defaults can only go so far. Some of the most important accessibility work depends on understanding what your content means, and that's your job.

Meaningful alternative text

Images need short text descriptions for people who can't see them. A tool can prompt you for them or suggest a starting point, but only you know why an image is there. A photo of your shop front might need "The bakery's blue door on Market Street"; a decorative texture might need no description at all. Good alt text describes the purpose of the image in context, not just its contents.

Clear link and button wording

"Click here" and "Read more" tell a screen reader user very little when they hear a list of links out of context. "Read our refund policy" or "See the spring timetable" are much clearer. Review your links and buttons with this in mind.

Plain language

Accessibility includes cognitive accessibility. Short sentences, common words and clear explanations help people with learning disabilities, people reading in a second language, and people who are tired or distracted. A tool can help simplify text, but you decide what you actually mean.

Colour alone

If you ask for something like "show available dates in green and booked ones in red", remember that some people can't distinguish those colours. Make sure there's also a text label or icon so the meaning doesn't depend on colour alone.

Video and audio

If you include video, it needs captions; audio content benefits from a transcript. These depend on your content and need to be produced or checked by you.

Your own design requests

Sometimes an accessibility problem comes from a request. Pale grey text on white, very thin fonts, text placed over busy photographs: these can all look elegant and be hard to read. If a tool pushes back gently or adjusts your request to keep contrast acceptable, that's it doing its job.

A practical accessibility check

You don't need specialist software for a useful first check. Before publishing, try these:

1. Use the keyboard. Press Tab repeatedly from the top of the page. Can you reach every link and button? Can you always see where you are?
2. Zoom in. Set your browser zoom to 200 percent. Does the content still fit and read sensibly?
3. Read your headings alone. Do they make a sensible outline of the page?
4. Review your images. Does each meaningful image have a description that explains its purpose?
5. Read your links out of context. Would each one make sense on its own?
6. Check in bright light. Look at your site on a phone outdoors. Is all the text easy to read?
7. Look for colour-only meaning. Is anything communicated only through colour?

For a more thorough review, free automated checkers can catch many technical issues, though they can't judge everything, and nothing replaces feedback from disabled people who use assistive technology every day.

Defaults as a form of respect

When accessibility depends on everyone remembering to do it, it often gets skipped. When it's built into the defaults, it happens quietly on every page. That's one of the most valuable things an AI design tool can do: carry the hard-won knowledge of accessibility practitioners into projects that might otherwise never benefit from it.

For complex services, or where accessibility is a legal or contractual requirement, an audit by a specialist is the right step. For everyday sites, sensible defaults plus your own careful attention to meaning will make your site welcoming to far more people.