> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/features-and-advanced-setup/accessibility.md).

# Accessibility

What Avante handles for accessibility on its own, what depends on your settings, content and apps, and how we handle accessibility reports.

An accessible storefront is not produced by the theme alone. What a visitor using a keyboard or a screen reader actually experiences is the sum of several layers, and the theme is only one of them.

<table><thead><tr><th width="250">Layer</th><th>Who controls it</th></tr></thead><tbody><tr><td>Theme markup and behaviour</td><td>Us</td></tr><tr><td>Colours, font sizes, contrast</td><td>You, in theme settings</td></tr><tr><td>Image alt text, link wording, heading order</td><td>You, in your content</td></tr><tr><td>Pop-ups, reviews, chat and other app widgets</td><td>The app vendor</td></tr><tr><td>Custom code added to the theme</td><td>Whoever wrote it</td></tr><tr><td>Checkout</td><td>Shopify</td></tr></tbody></table>

## What Avante handles

Avante is published in the Shopify Theme Store, which means it is built and reviewed against Shopify's accessibility requirements for themes. In practice the theme takes care of:

* A **skip to content** link, visible on focus, so keyboard users can jump past the header.
* **Keyboard operation** of navigation, dropdowns and drawers, including closing them and returning focus where it came from.
* **Visible focus** on interactive elements.
* Markup that lets assistive technology announce what a control is and whether it is open — menus, drawers and dialogs carry the appropriate roles and state.
* **Alt text support** on every image field, so what you write in Shopify is what gets announced.

{% hint style="info" %}
Accessibility work continues release by release. If an accessibility report was run against an older version of Avante, update the theme before acting on it — part of what it lists is likely to be already fixed.
{% endhint %}

## What depends on you

{% hint style="warning" %}
These cannot be solved by any theme, because the theme does not own them:

* **Colour contrast.** Theme settings let you pick any palette, including combinations that are hard to read. Check text against its background, and also buttons, icons and borders.
* **Alt text.** Decorative images can be left empty; images that carry meaning need a description.
* **Heading order.** Section headings should descend logically, not be chosen for their size.
* **Link and button wording.** “Read more” repeated twenty times tells a screen reader user nothing.
* **Font size and tap targets.** Very small type or tightly packed controls are a settings choice.
  {% endhint %}

## Apps and custom code

App widgets inject their own markup into your storefront, and a theme update cannot change how they behave. A pop-up that traps focus, or a chat bubble that cannot be dismissed with the keyboard, is fixed by the app vendor — the same goes for code an agency added to the theme.

If you are not sure which layer a problem belongs to, a quick test is to switch to an unmodified copy of Avante with the apps disabled and repeat the exact steps.

## If you receive an accessibility report

Accessibility audits are often sent to merchants as a list of findings about the whole storefront. Send it to us with your store URL and theme version, and we will tell you which items are ours.

* Findings that turn out to be **deviations of the theme** from Shopify's accessibility requirements we fix for you, and they go into the next release.
* Findings that belong to your settings, content, an app or custom code we will point out, and we can quote the work if you would like us to do it.
* A **full audit of your storefront** — going through every page, every app and all of your content — is a separate paid service, not part of theme support.

{% hint style="info" %}
We cannot certify a storefront as compliant with any particular standard, because most of what that would cover is outside the theme. What we can do is make sure the theme layer holds up its end.
{% endhint %}


---

# 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://staylime.com/docs/avante-themes/features-and-advanced-setup/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.
