Reading your own markup is a poor way to judge it, because you already know what everything is meant to be. These checks look at what the page actually produces rather than at what you intended, and together they take about fifteen minutes.
Check one: the heading outline
Use an extension or the accessibility panel to list the headings as an indented outline. Read it on its own.
It should summarise the page coherently. Look for skipped levels, for more than one level one heading, for headings used to make text large, and for sections with no heading at all. If the outline reads as nonsense, the structure is wrong regardless of how the page looks.
Check two: the landmarks
List the landmark regions. A well structured page has a banner, one or more navigation regions, a main, possibly a complementary region, and a contentinfo.
Two failure patterns are common. An empty list means the page is built from generic containers and offers no shortcuts. A long list of unlabelled navigation landmarks means the nav element has been applied to every group of links, which dilutes it. Multiple main elements is a straightforward error.
Check three: the accessibility tree
The accessibility panel in browser tools shows the tree assistive technology reads. Click through the interactive elements and read what each one reports.
Every control should have a meaningful name and an appropriate role. A button announced as button with no name is an icon control missing a label. An element with no role that responds to clicks is a div doing a button's job. A name that does not match the visible text will break voice control.
Check four: turn off the CSS
Disable the stylesheet and read the page from top to bottom. This is the fastest structural test available, because without styling the only thing giving the page shape is its markup.
The result should read as a sensible document: a title, headings introducing sections, lists that look like lists, content in a logical order. If it collapses into an undifferentiated wall of text, or if the order makes no sense, the structure was being carried entirely by CSS.
Check five: use the keyboard only
Put the mouse aside and tab through the page. Confirm that you can reach every interactive element, that the focus indicator is always visible, that the order matches the visual layout, and that you never get stuck.
Try the actual tasks: open the menu, complete the form, dismiss the dialog. Focus problems that are invisible in code review show up within seconds this way, and a surprising number of otherwise well built pages fail here.
Check six: run an automated checker
An automated tool catches missing alt attributes, empty links, contrast failures, duplicate ids, missing form labels and invalid attribute combinations. These are worth fixing and are quick to find.
Be clear about the limits. Automated testing catches a minority of accessibility issues, commonly estimated at around a third. It cannot tell you whether alt text is useful, whether a heading describes its section, or whether a custom widget makes sense. A clean report means the obvious problems are gone, not that the page is accessible.
The questions to ask about the markup itself
Alongside the tooling, a few questions catch what tools miss. Is every div there because no meaningful element fits, or because it was quicker? Is every clickable thing a button or a link? Does every list of items use list markup? Are tables data rather than layout? Does the source order match the reading order?
Fixing in order of value
Not everything is equally important. Interactive elements come first, because a div acting as a button excludes people entirely. Then headings and landmarks, which restore navigation. Then labels and alt text, which restore meaning. Then the remaining structural improvements, which are worth doing and rarely block anyone.
Working in that order means the largest problems disappear first, which matters if the audit turns up more than can be fixed at once.
Do it as you build
Auditing at the end produces a long list and a temptation to defer it. Running the heading outline and the keyboard pass on each page as it is finished takes two minutes and finds problems while the markup is still fresh, which is when they are cheapest to fix.