Accessible websites help people find information, understand content, and complete tasks using the ways of reading and interacting that work for them. That experience depends on many connected decisions: how a document is structured, how a control behaves, how an image is explained, and how changes are reviewed before and after publication.
This neighborhood brings together URLMD articles on accessibility foundations, semantic HTML, navigation, forms, media, and ongoing engineering practice. Start with the foundations for an introduction, or move directly to the part of a website you are building or reviewing.
Understanding accessibility
People encounter websites through different combinations of vision, hearing, movement, cognition, devices, and software. Understanding those differences helps connect an accessibility requirement to the experience it is intended to support. These articles introduce the subject, the technologies people use, and the shared framework for evaluating web accessibility.
- Web Accessibility: Building Websites People Can Perceive, Navigate, and Use — A starting point for understanding accessibility across content, navigation, and interaction.
- Assistive Technologies and How They Help People Use the Web — An introduction to technologies that support different ways of accessing and operating websites.
- Understanding WCAG: The Foundation of Web Accessibility — The principles and guidelines that give accessibility work a common technical framework.
Structure and semantics
HTML gives a document meaning beyond its appearance. Headings identify topics, landmarks distinguish page regions, and lists express groups or sequences. Using the appropriate elements helps preserve those relationships when someone navigates with assistive technology or experiences the page in a different presentation.
- Semantic HTML: Foundations, Structure, and Meaning — The foundation for choosing elements according to the content and purpose they represent.
- Heading Hierarchy: How to Structure Web Content Clearly — Organizing headings so readers can recognize the page’s topics and their relationships.
- HTML Landmarks Explained: Structuring Meaningful Regions of a Webpage — Identifying major regions so people can move between navigation, primary content, and supporting information.
- HTML Lists: Choosing the Right Structure for Web Content — Selecting list structures that communicate how items belong together.
- Common Semantic HTML Mistakes and How to Correct Them — A practical companion for reviewing markup and correcting unclear or inappropriate structure.
How structure reaches assistive technology
Browsers expose information about a page through an accessibility tree. Native HTML contributes to that representation, while ARIA can express additional names, states, and relationships. The markup and the behavior must agree: assigning a role does not supply keyboard interaction or focus management.
- Accessibility Tree Explained — An introduction to the representation browsers expose to assistive technologies.
- How Semantic HTML Shapes the Accessibility Tree — A closer look at how choices in document markup contribute to that representation.
- Understanding ARIA: Accessible Rich Internet Applications — The role of ARIA in communicating interface meaning to assistive technology.
- When ARIA Is Unnecessary: Let Native HTML Do the Work — Recognizing when an appropriate HTML element already provides the semantics needed.
Navigation and interaction
A usable interface helps people understand where they are, reach the next control, and recognize what happened after an action. Keyboard operation, meaningful links, predictable navigation, and clear feedback all contribute to that continuity.
- Keyboard Navigation Best Practices — Supporting operation through logical focus order, visible focus, and expected keyboard behavior.
- Navigation Design Principles — Organizing navigation so people can identify useful destinations and move through a website.
- Anchor Text: Making Links Understandable in Context — Writing link text that helps readers understand a destination or action.
- Anchor Links and Fragment Identifiers: Accessible In-Page Navigation for Long Documents — Connecting links to locations within a page so readers can move directly to relevant sections.
- Loading States: How Interfaces Communicate While Work Is in Progress — Explaining what is happening while an interface waits for a task to finish.
Review an interaction as a sequence. A person needs to discover the control, understand its purpose, operate it, and receive useful feedback. Each step deserves attention, including error conditions and the route back to the task.
Forms, images, and media
Different kinds of content need different accessibility decisions. A form asks someone to provide information. A table communicates relationships between values. An image or recording may carry meaning that needs an alternative presentation. Begin with what the content is doing, then choose the structure or alternative that preserves its purpose.
Forms and tabular information
- Form Design Best Practices for Clear, Accessible Web Forms — The broader design decisions that make a form understandable and usable.
- Accessible HTML Forms: Labels, Instructions, Errors, and Keyboard Support — The implementation details that connect form controls with their names, guidance, and feedback.
- HTML Tables: Structure, Accessibility, and Practical Use — Structuring tabular content so headers and data communicate their relationships.
Images, audio, and video
- Accessible Images and Alternative Text — Choosing text alternatives according to an image’s meaning and role in the surrounding content.
- Captions, Transcripts, Audio Description, and Accessible Media Alternatives — Understanding the different alternatives used to make audio and visual information available.
Review alternatives alongside the original content. Useful alternative text depends on context, and different media alternatives preserve different parts of an experience. The goal is to give people access to the information they need in a form they can use.
Engineering, review, and maintenance
Accessibility needs a place in everyday website work: component design, content editing, template changes, testing, and maintenance. A correction becomes more durable when the team understands its cause and includes the relevant check in future work.
- Accessibility Engineering — Approaching accessibility as part of the technical work of building and maintaining websites.
- Reviewing a Web Form from Start to Finish — A focused review workflow for following a form through a complete user task.
- Web Standards Quality Assurance — Connecting standards with the broader practice of checking website quality.
- HTML Validation Workflow: From Report to Verified Correction — Moving from reported markup problems to corrections that have been checked.
Standards and responsibility
Standards help define what to evaluate. Review also needs to examine how the website works for people. Automated checks and markup validation can identify some problems; manual interaction testing and feedback from people who use assistive technologies help reveal barriers those checks miss.
Section 508 Compliance as a Cornerstone of Inclusive Web Design provides a separate entry point into accessibility requirements in the United States federal context.
As content and interfaces change, return to representative tasks: navigating a page, reading at increased zoom, completing a form, recovering from an error, and using media alternatives. Carry the findings into the next revision, with clear responsibility for addressing barriers.
Connections to retrieval and workflow
Accessibility connects to other parts of website practice. Clear document structure can support both human navigation and machine interpretation. A dependable publishing workflow helps preserve that structure as a site grows.
- Accessibility and Retrieval-Awareness — Exploring the overlap between accessible content structure and the interpretation of information by retrieval systems.
- Machine-Readable Structure vs. Human-Readable Structure — Examining the relationship between what people perceive and what software can interpret.
- Content Governance: Maintaining Quality as Websites Grow — Connecting publishing decisions with ongoing responsibility for content quality.
Continue into the Retrieval Neighborhood to explore how information is found and used, or the Workflow Neighborhood to explore how work is organized and reviewed. Within this neighborhood, the central question remains whether people can understand the content and complete the tasks the website offers.