- Why Eleventy?
- Getting Started
- Working with Templates
- Using Data
- Template Languages
- API Services
- Release History
Accessibility Statement Jump to heading
The Eleventy project recognizes that Accessibility is an incredibly important baseline to developing inclusive and quality software. On Eleventy web properties specifically, we aim to meet WCAG 2.1 AA standards and to support our development community to do the same.
If you’ve encountered an issue with our web site—accessibility or otherwise—please let us know! The best way to do this is filing a new GitHub issue on the
We are also available on Mastodon at eleventy or feel free to contact zachleat directly.
Our Eleventy Leaderboards encourage best practices on sites that were Built with Eleventy through performance and accessibility auditing (via Lighthouse and axe) but automated auditing systems are only a starting point.
It’s very important that we take responsibility for the code we publish and deliver and strive to correct accessibility issues with the same veracity as a full service outage.
Accessibility Resources Jump to heading
- The A11Y Project (their website is Built with Eleventy!), including their incredible Accessibility Checklist
- GOV.UK Service Manual: Understanding WCAG 2.1
- WebAIM’s WCAG 2 Checklist
- W3C Web Accessibility Initiative: How to Meet WCAG (Quick Reference)
- Microsoft’s Inclusive Design Initiative
Tools Jump to heading
Automated Auditing Jump to heading
Compatibility Tests Jump to heading
- Accessibility Support, screen reader compatibility tables
- PowerMapper Assistive Technology Compatibility Tests
People to Follow Jump to heading
One of the best ways to immerse yourself in the accessibility development community is to follow the experts. Many of these folks are participants in the Eleventy community too!
- Marcy Sutton
- Scott O’Hara
- Adrian Roselli
- Sara Soueidan
- Eric Bailey
- Marco Zehe
- Dave Rupert
- Karl Groves
- Heydon Pickering
- and you? (Edit this page on GitHub)