Full Glossary

Web Accessibility

Web accessibility is the practice of removing barriers for people with disabilities. The widest and most common application of web accessibility focuses on providing access to those with limited vision, hearing, and motor function.

In the United States, web accessibility is governed by Section 508 of the Rehabilitation Act of 1973; in Europe, it is governed by Directive 2016/2102. Recommended web accessibility guidelines are outlined within the WCAG (Web Content Accessibility Guidelines).

Related Chapter Sections:

  • Writing for Accessibility

    Chapter 12: Write for People and Machines

    Writing for accessibility – much like writing for search engine optimization – boils down to writing clear, scannable, well-structured content.

  • Policy, Standards, and Workflow

    Chapter 23: Plan for Post-Launch Operations

    Rules, policies, and paths for success: a website runs only as smoothly as those who create systems to ensure success.

  • Front-End in Action

    Chapter 19: Implement the Design

    So, what does all of this front-end development and server ops look like in action? And why does it matter to the end user? The answer is in compatibility, accessibility, and performance.

  • Inputs and Outputs

    Chapter 13: Develop the Graphic and Interface Design

    Inputs and outputs for Chapter 13: Develop the Graphic and Interface Design.

  • Writing for Readability: Plain Language and Scannability

    Chapter 12: Write for People and Machines

    Different people possess different levels of reading comprehension, which means for your message and goals to reach the widest range of people, they must be written in a way that's clear to all.

  • Writing for Machines

    Chapter 12: Write for People and Machines

    Finally, there's one audience you can never please — because they care only for data: search engines and screen readers.

  • Content Strategy: Creating Usable, Useful Content

    Chapter 9: Develop a Strategy for Your Content

    The practice of creating usable, useful content? That's content strategy, and it's what helps ensure your site is built to serve the needs of your users.

  • Testing the Site

    Chapter 22: Test and Launch the Site

    There are three axes that a QA issue can turn on when testing the site: public vs. private, absolute vs. partial, and uncontained vs. contained.

  • Accountability, Authority, and Change

    Chapter 23: Plan for Post-Launch Operations

    A new website or web project is a clear signal for change: who will be accountable, who will have authority to make changes, and what levels of adoption will be required.

  • The Content: Maintaining and Creating Content That Works

    Chapter 24: Maintain and Improve

    The steps to maintaining content focus on carving out attention and setting up useful systems of review.