> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion.md).

# 3.2 Accessibility and inclusion

Build services that are usable and equitable for all.

Accessibility is important because it allows services to give equal access to all citizens, comply with legal requirements, foster inclusivity, enhance user experience, avoid discrimination, and contribute to government credibility, cost savings, innovation, and international reputation.

## 3.2.1 Test for accessibility

There could be significant interdependencies between UI components for different accessibility requirements. The World Wide Web Consortium and Web Accessibility Initiative have developed standards for considering the needs of developers ([WCAG, ATAG, UAAG](https://www.w3.org/WAI/fundamentals/components/#guidelines)), authoring tools, accessibility evaluation tools, and guidelines on how to make user agents (browsers, browser extensions, media players, readers) accessible to users.

[Test for accessibility](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion/3.2.1.1-test-for-accessibility.md)

## 3.2.2 Test your service with diverse users

[Involve a diverse user group in the design](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion/3.2.2.1-involve-a-diverse-user-group-in-the-design.md)

[Support multiple languages](broken://pages/GcroQ26ytWxsLXJvgOnt)

[Foster a culture of inclusion](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion/3.2.2.3-foster-a-culture-of-inclusion.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.2-accessibility-and-inclusion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.