Recognize the barrier and the task it blocks
An accessibility problem is often easiest to describe through the task you were trying to complete. Perhaps a form cannot be used with a keyboard, a button has no readable label, captions are missing from an instructional video, or text becomes difficult to read when enlarged. You do not need to know the technical cause before reporting it. Explaining what you tried and what happened gives the service provider a useful starting point.
Note whether the problem stops you entirely or makes the task harder. For example, “I could not submit the application because I could not reach the Continue button using the keyboard” is more useful than “the app is broken.” If the task is time-sensitive, look for another contact method while preparing your report. Reporting a barrier and asking for help with the immediate task can happen at the same time.
Collect details without making the report complicated
Write down the page or screen name, the action you attempted, and the result. Include the device type, browser or app, and any accessibility tool that matters to the problem, such as a screen reader, voice control, or keyboard navigation. You can also mention whether the same issue happens each time. These details help the provider find and test the barrier, but it is fine to leave out information you do not know.
If a screenshot would clarify the issue, check it before sharing. Screenshots can reveal account names, messages, addresses, or other private information. Crop or cover details that are not needed. Never send a password, a one-time code, or complete payment information to explain an accessibility problem. If the barrier appears only after you sign in, describe the steps leading to it rather than sharing your login details.
Find a contact route you can use
Look for an accessibility, help, support, or feedback link in the website footer, app settings, or service provider’s contact page. If the available form is itself inaccessible, use another listed option, such as email or telephone, when possible. You can also tell the provider that its usual reporting route is part of the problem.
Send the report to the organization that runs the service, rather than assuming your device maker or browser provider controls the page. If you are unsure who runs it, describe the service and the screen where the problem occurs to the most relevant support team you can reach. Keep a copy of your message and any reply so that you do not have to reconstruct the issue later.
Write a clear request and ask for an alternative
A useful report can be brief: “I am trying to book an appointment on the Schedule page. When I use the Tab key, keyboard focus skips the Choose a time control, so I cannot select a slot. I am using a laptop and a web browser. Could you help me complete the booking and pass this issue to the team responsible for the website?” This states the goal, location, barrier, and help needed without guessing at a fix.
If you need access to information or a service now, ask for a usable alternative, such as assistance by phone, an accessible document, or another way to complete the form. Say which contact method works for you. You may also ask the provider to confirm it received the report and to let you know what happens next. A provider may need more detail to reproduce an issue, but you can ask why particular personal information is needed before sending it.
Follow up and keep the conversation useful
If you do not receive a helpful response, reply to your original message or use another published support route. Restate the task you cannot complete, refer to your earlier report, and ask about an alternative way forward. If the provider offers a workaround, try it only if it is practical and comfortable for you; a workaround that requires someone else to use your account may not meet your needs.
Accessibility reports are most useful when they describe a reproducible barrier, but not every problem behaves the same way on every device. If the provider says it cannot reproduce the issue, you can offer one or two additional details, such as the screen where it starts or the order of actions you took. You have already contributed something valuable by explaining where access failed. The goal is both to complete your task and to give the provider information it can use to improve the service.
