What Is Web Accessibility?
Web accessibility means building websites that anyone can use — including people who navigate with a screen reader, a keyboard, voice control software, or other assistive tools. It is not a special feature you add on top. It is the result of writing good HTML from the beginning.
What accessibility means in practice
Section titled “What accessibility means in practice”An accessible website:
- Can be read aloud by a screen reader in a logical order
- Can be navigated entirely with a keyboard (no mouse required)
- Has images described in text for users who cannot see them
- Has forms that are labeled so users know what each field is for
- Has a heading structure that lets users jump to the section they need
- Has color contrast and text size that do not rely entirely on CSS (that comes later)
The Summit Trail Outfitters site you built in Modules 08 and 09 already has much of this in place — because you used semantic HTML, labeled forms, and proper heading hierarchy. This module makes those practices explicit and fills in the gaps.
Who benefits
Section titled “Who benefits”Accessibility is often framed as helping “disabled users,” but the population that benefits is much wider:
| User situation | Benefit |
|---|---|
| Blind or low vision | Screen reader can interpret the page |
| Motor impairment | Keyboard navigation works without a mouse |
| Cognitive or reading differences | Clear structure and headings reduce cognitive load |
| Temporary injury | A broken arm makes keyboard and voice control primary |
| Slow network | Descriptive alt text loads instead of a missing image |
| Voice assistant users | Semantic structure enables accurate voice control |
| Search engines | Bots read the page like a screen reader |
Accessibility improvements help all of these users — and they improve the experience for everyone else too. A page with clear heading structure and labeled forms is simply easier to use.
Assistive technologies
Section titled “Assistive technologies”Screen readers convert page content to speech or braille output. They navigate using headings, landmarks, links, and form labels. Without these, a screen reader user hears a wall of text with no structure.
Keyboard navigation allows users to move through a page using Tab, Enter, arrow keys, and other keyboard shortcuts — without touching a mouse. Every interactive element (links, buttons, form fields) must be reachable by keyboard.
Voice control software (like Dragon NaturallySpeaking) lets users click links and fill in forms by speaking. It relies on visible text labels and accessible element names to identify targets.
Why accessibility starts with HTML
Section titled “Why accessibility starts with HTML”Accessibility tools are built to read HTML. When HTML is semantic and well-structured, they work. When it is not, they break — and no amount of JavaScript or CSS can fully compensate.
This is the “HTML first” principle: before reaching for ARIA attributes, JavaScript focus management, or CSS workarounds, get the HTML right. Most accessibility requirements at this level are satisfied by using the correct semantic elements in the correct order.
What you will improve in this module
Section titled “What you will improve in this module”Over the next seven lessons, you will:
- Understand how semantic elements create accessible page structure
- Fix heading hierarchy issues across the Summit Trail Outfitters site
- Confirm landmark elements are used correctly on every page
- Review
alttext on every image - Audit form labeling across the Contact and Newsletter sections
- Learn what ARIA is and when (and when not) to use it
- Perform a final accessibility audit of the complete site
Beginner accessibility habits checklist
Section titled “Beginner accessibility habits checklist”These are habits to build from now on — not a one-time fix:
- Use semantic elements for their meaning, not their appearance
- Start every page with exactly one
<h1>and never skip heading levels - Every
<img>gets a descriptivealtattribute (oralt=""if decorative) - Every form field has an associated
<label> - Every
<audio>and<video>hascontrols - Every
<iframe>has a descriptivetitle - Never use a
<div>where a semantic element fits
- Web accessibility means anyone can use the page, regardless of how they navigate.
- Good HTML structure is the foundation — most accessibility requirements at this level are solved by correct semantics.
- Accessibility helps users with disabilities, temporary limitations, slow networks, and situational constraints.
- Screen readers, keyboard navigation, and voice control all rely on HTML structure to work.
- The Summit Trail Outfitters site will be audited and improved across this module.