Over the past few years, the Wagtail CMS core team and accessibility subteam have made a [significant commitment to improving Wagtail's accessibility](https://wagtail.org/accessibility/) – of the CMS interface itself as well as the websites that it produces. This talk is focused on the latter, showing how you (a developer of a Wagtail-powered site) can set up your models, templates, and workflows in order to make it as easy as possible for your editors to create websites that are as accessible _as possible_. I say "as possible" because it's important to recognize that it's _not_ possible for a website to ever be considered 100% accessible, but by putting some care into what we do on the development side, we can prevent some of the most widespread accessibility issues that users may come across.
Topics that will be covered include:
- How to use Wagtail's [new built-in accessibility checker](https://wagtail.org/blog/introducing-wagtails-new-accessibility-checker/)
- Custom validation to ensure that a page has a logical heading order
- Ensuring alt text is used appropriately (Spoiler alert: every image doesn't need alt text!)
- Usage of `aria-label` attributes to provide essential context to screen readers
- Providing timely, contextual help to editors as they create their content
