Built-in accessibility checker for Wagtail #9262
Replies: 8 comments
-
A few thoughts
|
Beta Was this translation helpful? Give feedback.
-
I think this a great idea. Sa11y is designed for content authors and focuses on content related issues and successes. Just make sense given the target audience. It will make it easier implementing this since no too much coding is required |
Beta Was this translation helpful? Give feedback.
-
We’re starting work on this today, as an Outreachy open source internship. @albinazs is our new contributor, supported by @jams2, @thibaudcolas, @laymonage. From now on we’ll be using this Discussions thread to share our notes and updates – starting today, for the next 13 weeks. |
Beta Was this translation helpful? Give feedback.
-
Week 1 sprint planning
|
Beta Was this translation helpful? Give feedback.
-
Quick mockup of our goal for the first integration approach – integrating Sa11y with the userbar: And when there are errors: |
Beta Was this translation helpful? Give feedback.
-
Week 2 update
Last but not least, @albinazs wrote about her experience so far! How I got my first internship as a junior front-end developer |
Beta Was this translation helpful? Give feedback.
-
Mid-internship updateAs Sa11y changed their license to GPL, we’ve decided it’s enough of a concern for us that we won’t integrate Sa11y directly in Wagtail. We created a custom accessibility checker based on the axe-core testing engine with UI designed for content authors to easily identify and fix accessibility issues. The first integration is within the userbar - the corresponding PRs were merged last week, meaning that the feature will be included in the Wagtail 4.2 release. The checker scans the loaded page for errors and displays the results in the GUI, with 3 initial rules ( We are planning to improve the checker and following a discussion with the accessibility team last week, our priorities include:
The full list of ideas can be checked in the meeting minutes here. We would love to hear any feedback and suggestions for further improvements. |
Beta Was this translation helpful? Give feedback.
-
Quick update based on recent work – and because we’re almost reaching the end of @albinazs’s internship 🥲. This happened:
Here are remaining improvements we intend to do during the internship or shortly after:
Things that are on our radar in the near future (hopefully in time for the next release):
Our full project backlog showcases other improvements which we’d like to do but we are unlikely to get to at this time. |
Beta Was this translation helpful? Give feedback.
-
Is your proposal related to a problem?
As part of our goal to conform with ATAG 2.0, we need a built-in accessibility checker for Wagtail. We’ve currently settled on Sa11y as a good candidate. It’s based on Tota11y, similarly to the popular wagtail-accessibility package, but is purpose-built for content management use cases.
Describe the solution you'd like
We should integrate Sa11y as part of Wagtail’s full page previews, and within the page editor, either in the live preview panel, or in a separate panel alongside it.
Describe alternatives you've considered
We’ve considered two kinds of alternatives:
Beta Was this translation helpful? Give feedback.
All reactions