Accessibility and human agency

Home Learn Accessibility and human agency

In short

AI can make information easier to use when a person can understand, control, correct, or decline the help. Accessibility includes the ordinary interface around the AI, not only the generated answer. Agency means the person still has a meaningful choice.

Why it matters

A tool can produce a helpful plain-language explanation and place it behind an unreadable form. It can also make a confident choice for someone who wanted options. The practical question is whether a person can reach the information, understand what the system changed, and choose how much help to accept.

How it works

Start with the task and the people who will use it. Provide clear labels, keyboard navigation, visible focus, readable text, and a way to correct input. W3C’s Web Content Accessibility Guidelines 2.2 describe ways to make web content more perceivable and operable. They apply to the surrounding experience regardless of whether the words are written by a person or generated by AI. Test the interface with the people and assistive approaches relevant to the setting; an automated checker can identify some issues but cannot speak for every user.

AI may offer another format, a shorter explanation, or a draft response. Give the person a way to see the original and choose among formats. State when a transformation is approximate or a key detail is uncertain. Do not make the easier-looking output the only available path. UNESCO’s 2021 ethics recommendation emphasizes human oversight and dignity. In an everyday tool, that means a person can ask for a different explanation, reject an unwanted transformation, and reach another route when the assistant fails.

Look at the entire journey. Can someone start without a mouse? Does a screen reader announce the result and the action buttons in a sensible order? Can a user pause speech or edit a generated message before it goes anywhere? If the result summarizes an important notice, can they inspect the exact source and deadline? A feature meant to help should not take away the original information or quietly act for the person.

Example

Illustrative example: this scenario is invented.

Sam, 19, looks at a public museum’s volunteer guide. They ask an assistant for a short explanation of the shift options. The page still offers the original guide and accessible controls for changing text size. Sam notices that one shift includes a break condition the summary left out. They open the original, correct their understanding, and choose an option themselves. The assistant has helped them get oriented while leaving the decision and source within reach.

Sam can also move through the controls with a keyboard and request a longer explanation. Those options make the help adaptable without requiring them to accept one simplified answer.

What it doesn’t mean

A generated audio version isn’t automatically accessible to everyone. A plain-language summary can omit a condition. Giving the user a choice on paper is weak if the alternative route is hard to reach. Good design includes the controls, content, and human support path together.

Try it

Choose a short public museum description. Ask any assistant for a simpler version, then compare names, dates, exceptions, and meaning with the original. On paper, list how a page should let someone switch back and edit the result. No personal account or private material is needed.

Keep going

Sources

Share this page