> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/site-quality/accessibility.md).

# Accessibility

Build more accessible websites with Elements

Designing with accessibility in mind ensures your website works for everyone, including people with visual, auditory, cognitive, and motor impairments. It’s not just good practice; in many regions, it’s also a legal requirement.

This chapter covers how to create accessible websites using Elements. We’ll walk through key principles, recommended techniques, and how Elements helps you meet common accessibility standards like WCAG 2.1 and the upcoming European Accessibility Act (EAA).

From using semantic HTML and alt text, to managing contrast and keyboard navigation, we’ll give you pointers on how to build sites that are inclusive, usable, and compliant, without compromising on design.

While not exhaustive, the following checklist covers the most important steps to help you build a more accessible website from the start:

### Structure & Semantics

* Use proper heading levels (h1, h2, h3, etc.) in logical order
* Structure content with semantic HTML (e.g. \<nav>, \<main>, \<section>)

### Text & Contrast

* Ensure sufficient colour contrast between text and its background
* Avoid using colour as the only way to convey information
* Use readable font sizes and line heights

### Images & Media

* Add meaningful alt text to all images
* Provide captions or transcripts for videos and audio content where possible
* Avoid autoplaying media with sound

### Forms & Interactivity

* Label all form inputs clearly and associate them with their controls
* Ensure error messages are clear and accessible

### Responsiveness & Layout

* Use responsive layouts that adapt to different screen sizes and zoom levels
* Avoid fixed pixel sizes for text or important layout elements

### Testing & Validation

* Use accessibility checkers like [WAVE](https://wave.webaim.org/), or Lighthouse (in Chrome DevTools) to audit your pages
* Test with keyboard-only navigation
* Try screen reader testing (VoiceOver on macOS is a good starting point)

### Legal & Compliance

* Aim for [WCAG 2.1 Level AA](https://www.w3.org/TR/WCAG21/) compliance
* If you sell products or services in the EU, ensure you comply with the [European Accessibility Act (EAA)](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/union-equality-strategy-rights-persons-disabilities-2021-2030/european-accessibility-act_en).


---

# 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://docs.realmacsoftware.com/elements-docs/site-quality/accessibility.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.