RFC 89 - ATAG 2.0 audit #89
Conversation
| - Fail: Image upload fields in the image edit/create form. The image’s title displays as a field next to the visuals. The title acts as alt text by default in Wagtail. This is missing a programmatic association between the title text and image. | ||
| - Example: [Wagtail 5.1 - Editing image Boston Cream Pie](https://static-wagtail-v5-1.netlify.app/admin/images/43/) | ||
| - Current: The alt text is permanently set to the contents of the Title field on page load. | ||
| - Proposed actions: |
There was a problem hiding this comment.
Feedback from @streats:
Might it be worth adding reference to Chiemezuo’s proposal for improving alt text capabilities?
|
|
||
| Proposed actions: | ||
|
|
||
| - Document all keyboard commands (SC _A.3.1.6 Present Keyboard Commands_) |
There was a problem hiding this comment.
Feedback from @streats:
Document all keyboard commands - is this related to 445 Implement Keyboard shortcut documentation for editor in the Wagtail UI #3949? I see that issue moved to a discussion but I’m not clear if the documentation part has been done or not. If they are the same thing, it might be worth linking to it in 427 for context
|
|
||
| Proposed actions: | ||
|
|
||
| - [Accessibility features documentation #69](https://github.com/wagtail/roadmap/issues/69) |
There was a problem hiding this comment.
Feedback from @streats:
Accessibility features documentation - the linked issue is closed, so if it’s been completed we could omit this (and if not, maybe re-open that issue?)
View the audit in HTML. View the audit in standardised ATAG reporting formats on GitHub Gists.
Cite this audit report with a permanent link: wagtail.org/accessibility/atag-audit/
Thank you to the Wagtail accessibility team @wagtail/accessibility for the foundational work that made this audit and report possible. It’s a big deal for us that we finally have this first audit, so THANK YOU @Scotchester @thibaudcolas @jessemenn @kbayliss @Stormheg @SaptakS @anujaraj @janehughes @albinazs @laymonage @jams2. Also thank you to my employer Torchbox for sponsoring this audit and associated reporting.
Additional thanks to @albinazs, @jams2, @laymonage, @thibaudcolas, and @nicklee for their work on Wagtail’s first ever accessibility checker (https://wagtail.org/blog/introducing-wagtails-new-accessibility-checker/), which was essential for us to (partly) meet B.3. and B.4. guidelines.
And finally thanks to people who provided early guidance on conducting ATAG audits in the web-a11y Slack in the #atag channel! This has been an invaluable source of information for us to figure out how to go about this.