In this article
A difficult page can create several different problems. Text may be uncomfortable to read, a control may not work with your input method, or a required document may be inaccessible in the form provided. Treating all three as “the website looks wrong” makes it harder to explain what needs to change.
This essay focuses on practical observation and communication. It does not assess disability, determine accommodations or certify the accessibility of university services. For formal access or accommodation needs, use the university’s current official process and the relevant course or program contacts.
Name the task that is blocked
Start with the activity rather than a broad judgment about the page. “I cannot move focus to the submit control using the keyboard” is more actionable than “the design is bad.” “The document text cannot be selected or read with my usual tool” identifies a different barrier from a small font.
State what you were trying to accomplish and what prevented it. You do not need to disclose a diagnosis to describe the behavior of a control. If a formal process requires personal information, provide it only through that approved process, not in a public comment or an unrelated support message.
Avoid claiming that every user will encounter the same problem. Your observation can be valid without being universal. A particular browser, document format or input method may be important context for the investigation.
Try preferences without accepting a broken workflow
Ordinary browser zoom, text settings or an approved reading tool may improve comfort. These are options to consider, not proof that the original service has met every accessibility obligation. A personal adjustment can help you continue reading while a barrier still deserves a report.
Do not install an unknown extension or upload a private document to a conversion website just because it promises an accessible version. The destination and the information involved matter. Ask for an approved alternative when the material is restricted or the tool’s handling of data is unclear.
If zoom makes a control disappear or forces an awkward sequence, note that behavior. The useful report explains both the setting and the blocked task. It should not blame you for using a reading preference or assume that returning to tiny text is an adequate resolution.
Separate the service from the material
A course platform may work while one uploaded document remains difficult to use. In that case, the material’s provider may need to supply an appropriate alternative. Conversely, a platform control can fail even when the document itself is readable. These questions can require different people.
The university Canvas help page identifies support resources for platform issues. Course-content questions also belong with the person responsible for the material. Ask each recipient the question within their role rather than hoping a single generic ticket will solve both.
If the barrier affects a deadline, communicate that fact promptly through the relevant course or official access channel. A technical report does not automatically create an extension or accommodation. The person authorized to decide the arrangement needs to know what work is affected.
Fictional case: a scanned reading
Imagine Lee receives a required reading that displays as images. Lee can open the file but cannot use the usual text-reading workflow. Describing the problem as “the file will not open” would send support toward the wrong issue. The file opens; its usable form is the question.
Lee asks the material’s provider for an appropriate alternative and explains the task that is blocked. If there is also a platform problem, Lee reports that separately with the service context. Lee does not upload the reading to an arbitrary conversion service or distribute it publicly to ask strangers for help.
The distinction keeps the request focused. An alternative version may address the immediate material issue, while a platform investigation addresses a different technical barrier. Neither should erase the other from the conversation if both remain unresolved.
Make the report reproducible, not invasive
Describe the sequence of controls, the input method and the point where progress stops. A short text account may be enough. If a recording or screenshot is requested, review it for private notifications, identifiers and unrelated course material before sending it through an approved route.
State any safe comparison you tried, but do not perform endless tests at the expense of the actual coursework. It is reasonable to say that you can provide more detail if support identifies the specific evidence needed. You are reporting a barrier, not volunteering to reverse-engineer the entire service.
When a change is offered, check the original task again. Can you now read the material or complete the intended action with your workflow? A reply saying “fixed” should be evaluated against the practical outcome, not merely the appearance of a different screen.
Keep a concise record of the next step and responsible contact. The most useful result is a workable path to the activity and a clear understanding of any remaining issue. This independent fieldbook can help frame that conversation, but it cannot provide official access determinations or inspect your course environment.
Sources and scope
Public pages reviewed November 9, 2026. The analysis and fictional cases are this publication’s own. No authenticated university account was inspected. Screen labels, service coverage and availability can change.
- University Canvas help: Canvas entry routes and separation of Canvas and video support.
- Campus IT support: Academic-role help desk, service status and support channels.