> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/compliance-protections/required-compliance/web-accessibility-ada-compliance.md). # Web Accessibility & ADA Compliance Explains what web accessibility and ADA compliance mean for your store and the accessibility features built into Recart popups. Learn what web accessibility and ADA compliance mean for your store — and the accessibility features Recart builds into your popups and forms. Recart popups and forms are built with accessibility in mind — so more of your customers can engage with them, and you can feel confident about the experience you're putting in front of your shoppers. Here's what that means and what's built in for you. ### What is **Web Accessibility & ADA Compliance** "Web accessibility" means making your store's content usable by everyone, including people with disabilities — for example, customers who navigate with a keyboard instead of a mouse, or who use a screen reader. When it comes to accessibility, two terms come up a lot: * **ADA (Americans with Disabilities Act)** is a U.S. civil rights law that protects people with disabilities from discrimination. It increasingly applies to digital experiences like websites, but it doesn't spell out specific technical requirements. * **WCAG 2.2 (Web Content Accessibility Guidelines)** is the technical standard that defines *how* to make web content accessible. It's published by the W3C and is the most widely adopted standard in the world. Its "AA" level is the one most commonly treated as the benchmark for ADA. ### What it means for you An accessible popup is one more of your customers can actually use — which means a wider audience for your offers and a better experience for everyone who visits your store. Recart builds these accessibility features directly into your popups and forms, so you get the benefit automatically, without extra setup on your end. We design our popups and forms with accessibility in mind and are continually working toward WCAG 2.2 AA. It's an ongoing commitment, and we keep enhancing these features over time. ### What Recart has implemented We've built a range of accessibility features directly into your popups. Here's what's in place and what each one means for your shoppers: | What's built in | What it means for your shoppers | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Focus moves into the popup when it opens | Keyboard and screen-reader users are taken straight to the popup, instead of having to hunt for it on the page. | | Keyboard-friendly exit | Shoppers can move through and close the popup using the keyboard alone — they never get "stuck" inside it. | | Clear focus highlighting | As keyboard users move through the popup's buttons and links, the focused element is highlighted so they can see where they are. | | Focus returns when the popup closes | Once the popup is dismissed, shoppers are returned to exactly where they left off on your page. | | Announced to screen readers | Popups identify themselves to assistive technology, so screen-reader users know one has appeared. | | Image alt text | Images in your popups include an alt text field to fill out that screen readers can read aloud. | | Errors are announced, not just shown | When there's a problem with a form entry, the error is conveyed to screen readers, not shown only on screen. For example: “Please enter a valid email” is also read out. | | Easy-to-use controls | Close buttons and calls-to-action are sized to be simple to tap or click, including on mobile. | | Never relies on color alone | Important cues, like flagging an invalid field, are shown with more than just color, so the meaning comes through for everyone. | Accessibility isn't a one-and-done project for us — it's something we keep working on. We're committed to making your popups and forms as accessible as they can be, and we're continually improving them as standards evolve, so your store stays in great shape for every shopper who visits. If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) We'd be happy to help! --- # 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://help.recart.com/compliance-protections/required-compliance/web-accessibility-ada-compliance.md?ask=&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.