HTML review checklist
A starting point for a public page. These checks do not cover all accessibility requirements or certify legal compliance.
Back to resources · Run a source-HTML preview
Review the source evidence
- Page title. Give the page a useful title that distinguishes its purpose.
<title>Contact the team | Example</title> - Page language. Set the document language to match its content.
<html lang="en"> - Image alternatives. Describe the information or function of a meaningful image. Use
alt=""for a purely decorative image. Review the context rather than adding a generic label to every image. - Form labels. Associate a useful label with the control.
<label for="email">Email address</label> <input id="email" type="email"> - Button names. Give the action a clear accessible name.
<button>Save changes</button>is a simple visible-text example. - Link names. Make the destination understandable in context.
<a href="/contact">Contact the team</a> - Frame titles. Describe the embedded content when a frame is used. A title does not establish that the embedded content itself is accessible.
If a source check has no matching elements, it was not tested. A JavaScript application may render content that is absent from the HTML a scanner receives.
Check the experience in a browser
- Complete important tasks using a keyboard, including opening menus, submitting forms and dismissing dialogs. Watch where focus moves and whether it stays visible.
- Review contrast, zoom, layout and information conveyed by color.
- Check form instructions, errors and feedback, including how assistive technology announces them.
- Review dynamic content, captions and the accessibility of third-party embeds.
- Include screen-reader evaluation and people with disabilities in a broader assessment.
These manual steps are outside ADAflags' seven source-HTML checks.
Give the developer a clear handoff
Record the page URL, the affected element, the task a user is trying to complete, the observed problem and the change you made. Keep the dated report and verify the result after the change.
Illustrative code examples need to be adapted to the actual page. The checklist is not a finding about your website.