Find Accessible Ways to Read, Write, Listen, and Communicate

Adapt the format to the person’s task while keeping the meaning intact.

A document may contain the right information in a form that is difficult for someone to use. Dense paragraphs, unclear links, uncorrected captions, or a scanned image of text can all create barriers.

AI may help reorganize a passage, draft a description, turn speech into editable text, or produce a script for listening. The useful starting point is the person’s task and preferred way of working. You do not need to ask someone to disclose a diagnosis before asking which format helps them.

Accessibility also depends on the interface and the final file. A clear rewrite does not establish that buttons work with a keyboard, that a document has a sensible reading order, or that a person can complete the task. Treat content adaptation and actual usability as connected checks.

Ask what the person needs to do

Start with a concrete request: find an appointment time, understand a set of instructions, compose a message, follow a video, or compare two options.

Then ask about preferred support. Someone may want larger text, concise numbered steps, audio with adjustable playback, an editable transcript, or both the original and a simpler explanation. Preferences can change with the setting and the task.

Use a prompt such as:

Adapt this information into short numbered steps and a separate read-aloud script. Preserve every date, time, location, requirement, exception, and contact instruction. Do not add facts. Explain unfamiliar terms briefly. Keep the original available for comparison. Ask about format preferences without requesting medical information.

W3C’s Web Accessibility Initiative recommends clear instructions, meaningful structure and links, and concise language appropriate to the context. These are useful foundations for adaptation, but they are only part of accessibility. W3C WAI: Writing for Web Accessibility

Preserve a small source exactly

Here is an original fictional event notice:

The repair club orientation takes place Saturday, November 14, 2026, from 9:00 to 10:00 a.m. at the community workshop. Enter through the west door. Bring your registration confirmation on paper or on your phone. Do not bring tools to orientation. If you cannot attend, contact the workshop office before 4:00 p.m. on Friday, November 13. The notice does not supply the office’s contact details or information about the entrance’s accessibility.

This exercise has several details a careless rewrite might lose: the end time, the choice of paper or phone, the instruction not to bring tools, and the conditional cancellation deadline.

An appropriate numbered version is:

Attend orientation on Saturday, November 14, 2026, from 9:00 to 10:00 a.m.
Go to the community workshop and use the west door.
Bring your registration confirmation. A paper copy or a copy on your phone is acceptable.
Leave your tools at home. Do not bring them to orientation.
If you cannot attend, contact the workshop office before 4:00 p.m. on Friday, November 13. The notice does not provide contact details; obtain them from the workshop’s verified information.

Add a separate unresolved note: “The notice does not say whether the west entrance meets your access needs. Ask the workshop about the route if needed.” Do not turn a direction into an assurance that the entrance is step-free.

Create a listening version without changing the task

A read-aloud script can use complete sentences and group related information:

Your repair club orientation is on Saturday, November fourteenth, twenty twenty-six. It starts at nine in the morning and ends at ten. Go to the community workshop and enter through the west door. Bring your registration confirmation, either on paper or on your phone. Do not bring tools. If you cannot attend, contact the workshop office before four in the afternoon on Friday, November thirteenth. The notice does not include the office’s contact details or information about the entrance’s accessibility.

This is a text script, not an audio file or a claim that audio was tested. If you use a reading tool, listen to the actual output and check the dates, times, and negation. Keep pause, replay, and a text alternative available where your chosen tool supports them.

For longer instructions, ask for short sections that a listener can replay. Avoid relying on “as shown above” or color alone to carry essential meaning. If the task involves a diagram, provide a description that explains the relevant relationship.

Review speech-to-text before sending

Dictation can help someone compose a message without typing every word. Begin with a private draft and inspect the transcription before sending it.

Pay special attention to names, numbers, and negation. “I cannot attend Friday” must not become “I can attend Friday.” A punctuation change can also alter the meaning of a request.

Ask an assistant to improve organization without changing intent:

Turn this dictated note into a clear message. Preserve the request and my level of certainty. Flag ambiguous words instead of guessing. Show the revised message for my review; do not send it.

A person may prefer an informal voice, regional expression, or direct wording. Do not assume that accessibility requires making everyone sound the same. The writer should be able to approve both the meaning and the tone.

Check captions and image descriptions against their sources

Captions should convey the speech and relevant non-speech audio needed to understand the content, synchronized with the media. Automated captions need review and correction; their presence alone is not evidence that the audio is represented accurately. W3C WAI: Captions and Subtitles

Review names, technical vocabulary, speaker changes, and meaningful sounds. A caption that changes “do not press” into “do press” can reverse an instruction. If the audio is unclear, mark that uncertainty and seek a better source rather than inventing a sentence.

For an image, explain its purpose in the surrounding content. A product photo, decorative flourish, map, and chart need different treatment. Ask an assistant to draft a description from the image and context, then compare it with the actual visual information. Do not accept inferred identities, emotions, or invisible details as observations.

For a chart, preserve its data and the comparison the reader needs to understand. A sentence such as “sales improved dramatically” does not replace the values, period, and units. Where useful, provide a data table alongside the description.

Test the actual task with the actual format

After adapting the fictional notice, ask a reader to find the orientation time, identify what to bring, and explain what to do if they cannot attend. Ask which part was difficult or unclear.

That is a proposed exercise, not a report of testing completed for this article. If you run it, record what happened and revise the specific obstacle. Avoid declaring a design universally accessible because one person completed one task.

For a website or application, inspect keyboard use, focus, labels, reading order, and the relevant assistive-technology experience through an appropriate evaluation process. W3C’s introductory checks explicitly describe themselves as a first review rather than a complete accessibility evaluation. Passing a few checks is useful evidence about those checks, not a comprehensive certification. W3C WAI: Easy Checks

Keep an alternative available. Editable text can be valuable when a formatted file behaves poorly in someone’s preferred tool. A person should not have to use AI simply to access essential information that could be provided directly.

For students: keep access and authorship clear

Students may use reading, dictation, captions, or other supports under course rules and accommodation arrangements. Ask the school’s relevant office or instructor about the appropriate process when needed. This article does not determine anyone’s entitlement or replace an agreed accommodation.

If an assignment assesses understanding, a format change may help you engage with the material. If it assesses a particular unaided performance, the permitted assistance needs to be clear. Preserve the distinction between changing access to a prompt and generating the assessed answer.

When producing work for classmates, include readable structure, meaningful links, corrected captions where applicable, and useful text alternatives. Ask about preferences without requiring people to reveal personal information to a group.

Practice: adapt and compare

Use the fictional orientation notice. Produce numbered text and a read-aloud script. Compare each version against a checklist containing the date, start and end times, location, entrance, confirmation options, tool restriction, and conditional deadline. Record the two details the source does not provide.

Completion check: Both versions preserve all required meaning and make missing information visible. A task-based review is planned or documented honestly. You can explain which barriers the adaptation addresses and which require further interface, document, or user evaluation.