Pick a page that asks someone to do something: apply, register, submit a document, or contact an office. Read it from the point of view of someone who does not know your institution’s terminology.
W3C’s writing guidance recommends informative page titles, meaningful headings and links, clear instructions, and concise content. These practices help people understand and navigate information. They are a starting point, not a complete accessibility assessment. Read the W3C guidance.
Try the page out loud
Ask a colleague to explain what the reader should do next using only the page. If the explanation depends on something your colleague knows from working there, add the missing context to the page.
Replace institutional shorthand
“Submit to the relevant office” leaves the difficult part to the reader. Name the office and the route to it. Expand an abbreviation the first time it appears. If two audiences follow different processes, label each path before presenting its instructions.
Check the journey, not just the page
Follow the next link on a phone. Does it lead to the promised information? Is the academic year clear? If a document must be completed elsewhere, explain what the reader should prepare and where to get help.
Use these boxes during your review, or print the guide. Selections are not saved.
Instead of “Contact us for further details,” name the team and the question it handles: “Ask Admissions about the documents required for your application.”
Sources & further reading
Sources checked September 19, 2026. The exercises and recommended next steps are The School Guru’s editorial suggestions. Check the linked authority for current requirements and institution-specific applicability.