Table of Contents

Accessibility Statement

The A11Y Project strives to be AA WCAG compliant.

The A11Y Project is committed to creating and maintaining an accessible, inclusive environment. It is a resource that is intended to be able to be used by everyone. This includes our audience, and also our contributors.

The standard we adhere to

The A11Y Project strives to be Web Content Accessibility Guidelines 2.1 (WCAG) AA compliant. The WCAG is an open standard for determining accessibility. AA compliance is considered good support for a website geared towards a global audience.

What we are doing

The following initiatives are how The A11Y Project goes about doing this. We are:

Guided by a Code of Conduct that outlines expected behaviors.
Capable of responding to Code of Conduct breaches, should they occur, via an incident response guide.
Using time-tested, stable and interoperable technology based on open standards to help ensure our content can be accessed by the widest range of devices as possible.
Running automated and manual checks to test for accessibility issues.
Working with daily assistive technology users to help verify our content works as intended.
Promoting and attributing resources and knowledge about digital accessibility.
Providing a free checklist to help others audit their content for accessibility issues.
Using clear, person-first, non-ableist language for our messaging.
Hosting our code on a public repository, allowing anyone with the interest and capability to inspect and modify it.
Striving to keep our interactions and user interface unambiguous and easy to understand.
Striving to keep our download size small and memory footprint light.
Supporting magnified and zoomed displays, as well as custom typefaces and themes potentially set by someone in their browser.
Maintaining a color palette with high contrast ratios values to keep content legible.
Using distinct, obvious focus states for all interactive elements.
Respecting expressed preferences for a reduced animation experience.
Providing open, structured guidance on how to contribute, with provisions for individuals who may be unwilling or unable to use our preferred workflows.

Accessibility features

In addition to semantic HTML, these features are set up specifically to work with assistive technology:

Distinct, descriptive page titles.
Ordered headings to construct a logical document flow.
Landmark areas to describe overall sections of the page.
Unique, descriptive names for links, buttons, and other interactive controls.
Skiplinks have been placed to help people navigate past content that repeats from page to page.
Alternative descriptions for non-text content.
Titles for content embedded via iframe elements.
Removing repetitive, redundant links to the same destination from the Accessibility Tree.
Small amounts of ARIA to help address gaps in assistive technology support.

Technical specifications

We rely on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

These technologies are relied upon for conformance with the accessibility standards used.

Known issues

A list of known long-term issues and false positives is available. In addition, short-term issues being actively worked on are available on our Issue tracker.

We ask

If you discover an accessibility-related issue, please let us know. We take these issues extremely seriously and will fix them as fast as possible. We will also include you in the process, if desired.

You can submit an accessibility issue by:

How you can help

We'd love it if you got involved! Here's what you can do:

Let us know if you have an accessibility need that hasn’t been addressed.
Let us know if you have a constructive idea for how to improve something.
Volunteer your time to help address known issues.

Formal complaints

The A11Y Project is hosted in the United States of America. You are entitled to escalate a complaint to the national authority, should you be dissatisfied with our response. We ask you notify us if doing so.

Last updated on July 15th, 2020.