-
Notifications
You must be signed in to change notification settings - Fork 92
Meet WCAG AA level accessibility requirements #82
Comments
Providing multiple ways to locate a page within a website. #83 |
Below is a list of criteria for meeting WCAG 2.1 AA. There isn't many! It is trimmed down to suit the FSE themes. I did not include most of the criteria because the majority of the criteria are handled by Gutenberg or consideration for content creators. Please note this checklist is based on WebAIM's WCAG Checklist. I’m still learning web accessibility and FSE so please feel free to add, remove or edit. Guideline 1.3
Guideline 1.4
Guideline 2.4 |
Will the theme also target meeting the existing guidelines for accessibility-ready themes? https://make.wordpress.org/themes/handbook/review/accessibility/required/ |
@joedolson Yes. Though at a glance, I think a major chunk of that those requirements will be Gutenberg's responsibility this time around. |
I checked briefly and everything looks great, except the focus hover styles on the buttons. The following theme requirements also look good on the default template and the block patterns. Headings:
ARIA Landmark Roles:
Content Links:
Repetitive Link Text:
Contrasts:
Media
This theme is so beautiful ✨ Great job!! |
I'm going to mark this one as complete for now — as far as we're aware the theme conforms at this point. If any further a11y issues arise, we can address them as individual issues. Thank you! |
Description
2022 should be WCAG AA level compliant. What is needed to achieve this? Let's use this issue to discuss and track.
The text was updated successfully, but these errors were encountered: