# Accessibility

The Web Content Accessibility Guidelines (WCAG) break down accessibility into [four main principles](https://www.w3.org/WAI/standards-guidelines/wcag/glance/):

* **Perceivable**: Create content that can be perceived in different ways, for example, providing text alternatives for non-text content and content that can be perceived by assistive technologies like screen readers.
* **Operable**: Enable simple operation by making all functionality available from the keyboard, helping users navigate and find content, and giving users plenty of time to consume content.
* **Understandable**: Make text readable and understandable, make content appear in predictable ways, and help users avoid and correct mistakes.
* **Robust**: Maximize compatibility with current and future user tools.

[Inclusive design](https://www.codecademy.com/resources/docs/uiux/inclusive-design) focuses on designing for users of all demographics and abilities, while accessibility is specifically focused on designing for people with disabilities. Any product that doesn’t consider accessibility and equity may (whether intentionally or not) exclude a portion of the population who would otherwise find it useful.

### **Links:** <a href="#heading-resources" id="heading-resources"></a>

* [Codecademy: What is Digital Accessibility?](https://www.codecademy.com/article/what-is-digital-accessibility)
* [W3C: Web Content Accessibility Guidelines](https://www.w3.org/WAI/standards-guidelines/wcag/)
* [The A11Y Project](https://www.a11yproject.com/)
* [Interaction Design Foundation: What Is Accessibility?](https://www.interaction-design.org/literature/topics/accessibility)
* [UX Planet: A Primer to Web Accessibility for Designers](https://uxplanet.org/a-primer-to-web-accessibility-for-designers-2c548448c612)

<br>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rebo.vn/foundation/contents/accessibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.