The answer in two paragraphs
When someone asks you to “make it accessible”, ask which person, task and barrier they have in mind before choosing a solution. Accessible can mean easy to find, reach, use or understand. An explanation that needs clearer language is a different problem from a document that cannot be navigated, a classroom resource that has no usable alternative format or a venue that someone cannot enter.
A helpful response is: “What does the person need to do with it, and what is stopping them now?” Then ask which change would make the task possible and how the person will confirm that it works. Do not begin by requesting someone’s medical history or guessing their abilities. The conversation is about removing barriers to participation, not requiring personal disclosure.
Quick summary: identify the user and their actual task; name the barrier rather than a label; offer concrete choices such as clearer wording, a different format, accessible controls or a reachable place; respect preferences and confidentiality; test the chosen solution with the people who use it; never claim accessibility is complete just because one box was ticked.
Did you know? Accessible is not just one technical property
Cambridge Dictionary records several ordinary uses of accessible, including information that can be obtained, places that can be entered or reached, technology that people can use, and explanations that are easy to understand. That range is why the instruction “make it accessible” often hides more than one possible reader job.
The W3C Web Accessibility Initiative recommends involving users in understanding barriers and evaluating solutions. It does not mean that a user must prove a diagnosis before receiving an effective resource. The person closest to the task may be able to explain what does and does not work better than a distant observer can guess.
A practical barrier–option–test conversation
Start by identifying the action: “Do you need to read the instructions, complete the form, watch the explanation or participate in the discussion?” The action matters because the same file can be readable for one purpose and unusable for another. A person may be able to view a slide but unable to enter text into the form linked from it.
Ask next about the barrier: “Is the main difficulty finding the information, understanding the wording, using the controls or getting the resource in a workable format?” These questions give the other person language for the problem without naming or diagnosing them. Do not force the choice into a single category if several barriers coexist.
Offer an option, not an assumption: “Would a short text version, structured document, audio explanation or guided walk-through help you complete the task?” Then check with an actual attempt: “Can you find the question, respond to it and tell what happens next?” Accessibility is not demonstrated by the sender saying it should be fine.
Fictional classroom dialogue: the graph is visible but not usable
Teacher: “I have put the graph on the screen. Is that accessible now?”
Student: “I can hear the explanation, but I can’t get the exact values from the image in the worksheet.”
Teacher: “Would a small data table with the values and a verbal explanation of the trend let you answer the question?”
Student: “Yes. Please also say which axis and unit each value belongs to.”
Teacher: “I’ll provide the data and check that you can answer the task from it.”
This invented dialogue does not imply that a data table alone makes every graph accessible. It shows how a teacher can identify the missing task information and check the result. The school may need other formats or supports for different students. The important repair is moving from “Can you see it?” to “Can you use the information to do the task?”
Fictional home dialogue: simple words versus complete meaning
Parent: “The letter should be more accessible. It is full of school terms.”
Student: “Would a short plain-language explanation help, or do you need the full letter in another language?”
Parent: “I want to understand what is required, what is optional and when I must respond.”
Student: “Let’s keep those details exact, explain unfamiliar terms, and ask the sender if any instruction remains unclear.”
This home scenario is fictional. The task is not to erase every technical term. It is to make the decision understandable without removing important conditions. An accessible summary should never convert a suggestion into a requirement or replace an important date with the vague word soon.
Fictional workplace dialogue: a PDF is not necessarily usable
Project lead: “I’ve uploaded the PDF, so it is accessible to everybody.”
Colleague: “The link opens, but I cannot move through the questions properly with my current reading setup. Do we have a structured version?”
Project lead: “I can provide an alternative format and check the headings, field labels and reading order. Would you be willing to test the task?”
Colleague: “Yes. I need to locate question four and enter an answer without losing my place.”
This exchange separates access to a link from use of its contents. It is not a technical claim that any particular PDF conforms to a standard. The project lead recognises a user-reported obstacle and agrees to test the actual task. A published file may still need changes, and one successful test does not certify all possible use cases.
Fictional community dialogue: a reachable venue
Organiser: “The workshop is accessible because the notice is available online.”
Participant: “I can read the notice, but I need to know whether I can reach the room using the route I use.”
Organiser: “Thank you. I will verify the entrance and route with the venue rather than assume the website is enough. Is there specific access information you would like confirmed?”
Participant: “Please confirm the usable entrance and whether the room can be reached from it.”
Here accessible refers to a physical route, not vocabulary or document format. No speaker should invent a guarantee about an actual building. The conversation ends with an action to verify details from an appropriate source and communicate them accurately.
Why the conversation breaks down
English compresses several meanings into the adjective accessible. A requester may think of comprehension, while a designer thinks of visual contrast and an administrator thinks of the login permissions. Each is addressing a real dimension, but none may address the reader’s actual obstacle. The repair is to convert the vague quality into the task that is failing.
The process resembles concept checking in language teaching. Asking “Do you understand?” often produces a yes that reveals very little. Asking a learner to locate a heading, restate a condition or complete a sample action gives a more meaningful check. The British Council specifically recommends concept questions and demonstrations rather than relying entirely on yes-or-no reassurance.
A second issue is power. A student, parent or employee may not wish to describe a personal difficulty in front of a group. Offer a private route to request a change. The task-focused question “Which part of the activity is hard to complete?” is often more respectful and more useful than “What condition do you have?”
Accessible language is not merely shorter language
Shorter can help, but a shortened explanation that removes necessary exceptions may be less usable than a well-organised longer one. Try headings, one action per sentence, named references instead of vague pronouns, examples tied to the task and definitions for unfamiliar terms. Where precise technical vocabulary is necessary, explain it rather than silently changing it.
For multilingual readers, ask whether a translation, bilingual key terms or a spoken explanation is needed. Avoid assuming that someone prefers a language because of their name or appearance. If an official decision depends on exact wording, preserve the original conditions and verify the translation rather than offering an unreviewed summary as a substitute.
Usable formats and participation options
A document may need a structured text format, clear headings, labels for controls, logical navigation, meaningful descriptions of essential images or a suitable alternative to time-limited speech. A meeting may need written questions in advance, an alternative to speaking on camera, a chance to respond later or clearer turn-taking. A place may need reliable route and entrance information.
These are examples, not a complete accessibility checklist. The right combination depends on the task and the people involved. A request to change the format should not automatically authorise changes to the message’s meaning. Preserve the relevant facts, and test the result. W3C guidance on involving users can help teams see why direct feedback matters.
An accessible choice should also be a genuine choice. A person who asks for a text version should not have to accept an unrelated recording, and someone who needs an accessible physical route should not be told that a website description solves the problem.
Register: one method, different settings
With a classmate: “Which part can’t you use? Want the instructions written differently or shown another way?” With a parent: “Would you prefer a clearer explanation, a different language or the full notice with key actions highlighted?” In an organisation: “Please identify the task, observed barrier, proposed change and how we will verify successful use.”
The professional version is more explicit because responsibilities are distributed across teams. The casual version is shorter and easier to say. Both are better than “It is accessible now, isn’t it?” when the speaker has not tested the user’s experience. Do not turn every request into a questionnaire; ask one or two questions that materially change what will be delivered.
Mistakes that produce false confidence
One mistake is equating a successful download with a usable document. Another is treating larger text as the only form of access. A third is replacing complex information with an inaccurate summary. A fourth is assuming that one person’s preferred method works for everyone. A fifth is treating someone who reports a barrier as the cause of the problem rather than investigating the task and environment.
Another error is claiming compliance or completion simply because a tool produced an automatic score. Technical checks are valuable but do not replace review of actual content and tasks. Conversely, a person’s difficulty should not be treated as proof that every part of a product fails. State what has been tested, what has been fixed and what remains to be checked.
Diagnostic questions
Ask yourself: Who needs to use this, and for what purpose? What step fails? Is the barrier about reach, discovery, language, navigation, interaction or timing? What change is possible without losing important meaning? Have we asked the user rather than guessed? Is a private channel appropriate? Can the person complete a meaningful sample task after the change?
If the recipient says only “It’s inaccessible,” start with a bounded question such as “Which step were you trying to complete when you got stuck?” Avoid demanding an exhaustive account. The person asking for help may have already made several attempts. Make the next exchange easier, not harder.
Retrieval practice with new scenarios
Exercise one: a school handout opens on a phone, but the parent cannot identify which action is required. Write a question that separates a language problem from navigation. Exercise two: a video is provided for a class task, but one learner cannot access essential spoken information. Name two possible alternatives to discuss and one question that checks whether they help.
Exercise three: a staff member says the venue is accessible, but the organiser has not verified the entrance route. Write a careful response that avoids inventing details. Exercise four: a PDF is readable visually but cannot be used to complete a form with a particular setup. What exact action should be tested after a revised format is provided?
Exercise five: a teacher asks “Does everyone understand?” and receives silence. Replace the question with one that checks a specific concept or action without publicly targeting an individual. Explain why the revised question offers more evidence. These exercises test task-focused communication, not proficiency with any one software product.
Check your response for three ingredients: the user’s task, the suspected barrier and a verifiable next action. A vague promise to make everything better does not satisfy the exercise.
Four-week application plan
In week one, practise sorting requests for accessible into reach, availability, comprehension and use. In week two, role-play the school and home conversations while keeping every date and requirement accurate. In week three, test a fictional form or slide with another learner and ask for a specific problem rather than a general rating. In week four, return to the first exercise and see whether your question now leads to a testable solution faster.
Parents can invite children to explain which words, layout or response step are confusing. Teachers can vary format and checking questions and offer private routes for support. Students can practise asking for a workable alternative without revealing private information. Team leaders can record the user task, change, verification and remaining limits, without making unsupported claims of full accessibility.
Frequently asked questions
Does accessible always mean easy to understand? No. It can also mean reachable, obtainable or usable, including for people with disabilities.
Should I ask someone to disclose a diagnosis before making a change? Do not assume that is necessary. Focus on the task, barrier and preference, and handle any personal information appropriately.
Is a simpler summary enough? Only if it preserves the information needed for the task. Sometimes a full alternative format is necessary.
Can one accessible format work for everyone? Not necessarily. Ask about the task and verify that the available options meet the relevant needs.
How do I know whether the change worked? Ask the user to attempt a meaningful step and tell you what remains difficult. One test provides evidence about that task, not universal certification.
What is the shortest repair question? “What do you need to do with it, and what is stopping you?”
Sources and reader guidance
Cambridge Dictionary explains the various meanings of accessible. W3C’s Web Accessibility Initiative provides guidance on involving users in design and evaluation. British Council describes checking learner understanding through specific tasks. The scenarios here are fictional demonstrations, not reports of tested outcomes, and they do not certify a particular file, venue or service.
Verified sources: Cambridge Dictionary: accessible; W3C Web Accessibility Initiative: involving users; British Council: concept checking. For the language-learning role of understanding and use, see eduKateSG: What Is Vocabulary?.