Tables and accessibility

A basic accessibility check

Review language, headings, landmarks, link text, image alternatives, and keyboard access before calling an HTML page complete.

Accessibility is part of writing correct HTML. You can catch many problems with a short manual review before you ship a page.

Start with the document itself:

  • does html have the correct lang?
  • is there a descriptive title?
  • is there one clear main heading?
  • do heading levels form a logical outline without skipped levels?
  • is the unique page content inside main?

Then check the content:

  • do links describe their destination out of context?
  • does every informative image have useful alt text?
  • do decorative images use alt=""?
  • are tables used for data, with proper header cells?
  • do form controls have associated labels?

Finally, put the mouse aside. Press Tab and move through the page with the keyboard only. You should always see where focus is. Every interactive control should be reachable and activatable.

Automated accessibility tools are useful, but they cannot judge whether alt text communicates the right information or whether a heading truly describes its section. Use tools after a thoughtful HTML review, not instead of one.

The goal is not to memorize every possible rule on day one. Start with meaningful native elements, then test how the page actually works for keyboard navigation and screen readers.

Run this checklist on your personal page before you call it done. Most issues you find will be fixable in the HTML itself without any JavaScript.

Quick check

Result

You got of right.

Lesson completed