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 connected decisions: how a document is structured, how controls behave, how focus moves, how images and media are explained, and how changes are reviewed before and after publication.
This neighborhood brings together URLMD articles on accessibility foundations, semantic HTML, navigation, interaction, forms, media, testing, 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, browsers, and assistive technologies. Understanding those differences helps connect an accessibility requirement to the experience it is intended to support.
These articles introduce accessibility, the technologies people use, and the standards and organizations that provide a shared framework for accessible web work.
- 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.
- WHATWG, W3C, and WAI: How Web Standards and Accessibility Guidance Relate — An orientation to organizations and standards work that shape modern websites.
- Section 508 Compliance as a Cornerstone of Inclusive Web Design — An entry point into accessibility requirements in the United States federal context.
Standards help define what to evaluate, but accessibility is not exhausted by conformance language. The continuing question is whether people can perceive the information, understand the interface, operate its controls, and recover when something does not go as expected.
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 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.
- Source Order vs. Visual Order in Accessible Web Layouts — Understanding why the order represented in the document should remain meaningful when visual layout changes.
- 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 roles, names, states, and relationships to that representation. ARIA can communicate additional interface meaning when native HTML is not sufficient, but assigning a role does not create keyboard behavior, focus management, or a complete interaction.
- 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.
Semantics and behavior should tell the same truth. A control’s element, accessible name, visual presentation, keyboard operation, and resulting behavior should support the same basic understanding of what the control is and what will happen when someone uses it.
Navigation, focus, and interaction
A usable interface helps people understand where they are, reach the next control, recognize what kind of action is available, and receive useful feedback after acting. Keyboard operation, meaningful links, predictable focus, clear navigation, and understandable state changes all contribute to that continuity.
Moving through pages and controls
- Keyboard Navigation Best Practices — Supporting operation through logical focus order, visible focus, and expected keyboard behavior.
- Focus Management: Preserving Context in Dynamic Interfaces — Managing focus when content changes, dialogs open, errors appear, or an interaction moves someone into a new interface state.
- Skip Links and Bypass Navigation — Providing a direct route past repeated content to the primary page region or another useful destination.
- 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 resource.
- 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.
Controls and changing interface states
- Links and Buttons: Choosing the Right Element and Writing a Clear Accessible Name — Choosing controls according to whether someone is navigating to a resource or performing an action.
- Accessible Dialogs: Focus, Context, Escape, and Return — Preserving orientation when a dialog temporarily changes the active boundary of an interface.
- Loading States: How Interfaces Communicate While Work Is in Progress — Explaining what is happening while an interface waits for a task to finish.
- Interface Feedback: Communicating Results, Errors, and State Changes — Helping people understand what happened after an action and what they can do next.
Zoom, reflow, and adaptable presentation
- Zoom, Reflow, and Text Resizing in Accessible Web Design — Preserving readable content and operable interfaces when people enlarge text or change the visual presentation.
Review an interaction as a sequence. A person needs to discover the control, understand its purpose, reach it, operate it, perceive the result, and continue or return. Accessibility is experienced across these transitions, not only at individual elements.
Forms, images, tables, 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, recording, or video may carry meaning that needs another 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, requirements, 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 make the necessary information available in forms people can perceive and use.
Engineering, testing, and maintenance
Accessibility needs a place in everyday website work: component design, content editing, template changes, testing, publishing, and maintenance. A correction becomes more durable when the team understands its cause and carries the relevant check into future work.
- Accessibility Engineering — Approaching accessibility as part of the technical work of building and maintaining websites.
- Testing Accessibility with Assistive Technology — Using representative technologies and tasks to investigate how an interface is actually exposed and operated.
- 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 reviewed and checked.
Combine different forms of evidence
Automated checks and markup validation can identify some problems. Keyboard review, zoom and reflow testing, screen reader testing, and complete task walkthroughs reveal other barriers. Feedback from disabled people and people who regularly use assistive technologies contributes experience that an automated rule cannot reproduce.
No single tool or test represents accessibility as a whole. Findings should remain connected to the affected content, component, workflow, and user task so that corrections address causes rather than only individual reports.
Return as the website changes
As content and interfaces change, return to representative tasks: navigating the page, bypassing repeated content, reading at increased zoom, opening and closing a dialog, 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 without becoming identical to them. Clear document structure can support human navigation, assistive technology, browser interpretation, search, and retrieval. A dependable publishing workflow helps preserve that structure as a website 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.
These relationships are useful, but accessibility should not be justified only by secondary benefits such as search visibility or machine interpretation. Its central concern remains whether people can perceive the content, understand the interface, and complete the tasks the website offers.
Continue into the Retrieval Neighborhood to explore how information is found and used, or the Workflow Neighborhood to explore how work is organized, reviewed, and carried forward.