Follow the content in source order
Begin with the page title and read the headings in sequence. They should describe the document without relying on visual size alone. Keep the main content before optional related links. Use a visible page title rather than an extra hidden heading added only for search engines.
Try a complete keyboard route
Use Tab to move from the skip link through the navigation and into the content. Check that focus is visible, links activate predictably, and interactive controls have meaningful labels. If a menu expands, verify that it can also be closed and that it does not trap focus. Test the actual page rather than assuming a framework handles these details.
Explain images according to their purpose
An informative diagram needs text that communicates its useful information. A logo that links home needs an accessible name for that action. Pure decoration can use an empty alternative. Do not repeat an entire nearby caption in alternative text when the repetition adds no meaning.
Let content adapt to narrow screens
Use flexible columns and allow labels and long URLs to wrap. Give wide tables a local scrolling region rather than allowing the entire document to overflow. Increase text size and confirm that controls remain reachable. A small screenshot alone does not establish that the page works with keyboard or assistive technology.
Record problems as reproducible tasks
For each issue, write the page, the action, the observed result, and the expected result. For example: on the comparison page, tabbing from the search field should reach the first link without entering hidden controls. Retest after a fix. These checks are a starting point, not a claim of formal accessibility conformance.
Reference framework
Use the W3C accessibility guidance to develop a broader review appropriate to your site.
W3C Web Accessibility Tutorials