Website Accessibility Basics for Small Websites

Website accessibility basics: remove barriers from real tasks

Website accessibility basics are about whether people with different disabilities can perceive content and complete the site's real tasks. Review the homepage, a representative content page, navigation, and the primary form or purchase path. A checklist is useful only when it includes the journey a visitor came to complete.

The Web Content Accessibility Guidelines provide a shared standard for accessibility requirements. A small-site baseline can find obvious barriers and improve the product, but it is not a substitute for a complete evaluation or a claim of conformance.

Test keyboard access and visible focus

Use Tab and Shift+Tab to move through the entire page, Enter and Space to activate controls as appropriate, and Escape to close menus or dialogs. Every interactive item should be reachable in a logical order, operable without a mouse, and identified by visible focus.

Watch for focus trapped inside a component, focus that disappears behind a sticky header, menus that open only on hover, and custom controls that look clickable but are not keyboard-operable. After a dialog closes, focus should return to a sensible place.

Use headings, landmarks, links, and buttons correctly

Give each page a descriptive title and use headings to describe a logical outline rather than to create visual sizes. Identify repeated page regions with appropriate semantic elements or landmarks so assistive-technology users can navigate efficiently.

Use links for navigation and buttons for actions. Link text should make sense in context and repeated controls should have consistent names. Semantic HTML provides behavior and meaning that a styled generic element does not automatically gain.

Give images and non-text content useful alternatives

The W3C images tutorial explains that alternative treatment depends on the image's purpose. An informative image needs concise text that conveys its meaning. A decorative image should usually be ignored by assistive technology. A functional image needs an alternative that describes the action, and a complex chart may need a longer explanation.

Do not repeat a nearby caption in the alternative text or begin every description with 'image of.' Confirm that icons, diagrams, audio, and video do not carry essential information in only one sensory form. Provide captions, transcripts, or text explanations when the content requires them.

Build forms with labels, instructions, and recoverable errors

Every field needs a persistent programmatic label. Placeholder text is not a label because it disappears and may have weak contrast. Group related controls, explain required formats before submission, and identify required fields without relying on color alone.

When validation fails, identify the affected field, explain the problem in text, and move or announce focus so the message can be found. Preserve valid entries. Test the form with a keyboard and at increased zoom, including the confirmation and any email or payment step.

Review contrast, zoom, reflow, motion, and media

Check text, icons, focus indicators, and meaningful graphics against their backgrounds. Then zoom the page and narrow the viewport. Content should reflow without forcing horizontal scrolling for ordinary reading, hiding controls, or covering text with fixed elements.

Do not communicate status by color, sound, position, or motion alone. Provide controls for motion or media that starts automatically, avoid unnecessary flashing, and make pause and volume controls keyboard accessible.

Combine automated tools with human evaluation

Automated checks can find missing alternatives, some naming problems, invalid relationships, and certain contrast failures. They cannot reliably decide whether an alternative is useful, a heading outline makes sense, focus order is logical, or an error message helps a person recover.

Use automation as a repeatable filter, then perform keyboard, zoom, screen-reader sampling, and task-based human review. W3C describes its Easy Checks as a first review rather than a complete assessment. Record what was tested, by whom, when, and which limitations remain.

Make accessibility a repeatable small-site review

At launch, review representative templates and every critical journey. During maintenance, repeat the keyboard and zoom passes after navigation, forms, dialogs, templates, or third-party embeds change. Recheck new content for heading order, link purpose, image alternatives, captions, and plain-language instructions.

Assign an owner, log barriers by impact, and provide a monitored feedback route for visitors. Publish an accessibility statement that describes the real approach and known limitations without promising a level that has not been evaluated.

• Keyboard-test navigation and the primary task.
• Review page titles, headings, links, buttons, and landmarks.
• Check images, forms, contrast, zoom, reflow, motion, and media.
• Record unresolved barriers, an owner, and a retest date.