-
Notifications
You must be signed in to change notification settings - Fork 111
Complete the accessibility-ready review #408
Comments
There are 3 contrast errors in the Coming Soon pattern, they all related to the cover block not having a background image and being reliant on the right opacity to be set. This impacts the Coming Soon pattern as it uses yellow text by default. Using a dark image makes no difference as the contrast ratio is checked between the text and the background colour, the image has zero impact on this. I have created a ticket for this issue in the Gutenberg repo -- WordPress/gutenberg#65868 Pattern test with HTML_CodeSnifferPattern test with Wave ExtensionTest after adding inline background colour style |
The automated tools can't check the contrast when there is a background image used, and a human can't really check it either because there are many different colors in the photo. |
IMO an example like this has two-parts too it. Scanners will ignore the image and compare against the next available background colour, easily remedied in code with a bg colour on cover. The other goes beyond code and puts the responsibility in the hands of the content creator to consider the visuals impacts to some folks. |
Content links: I have a reservation about links in close proximity to the content, such as dates, author names, and categories not being underlined. |
ARIA landmark roles: In "Right-aligned single post" the comments area between the |
Heading error:
Fixed in PR - #510 |
I reviewed all patterns by inserted each of them one and a time and noted the following. @carolinan I am happy to fix anything here in a PR, just wanted to confirm that everything I've noted is a change that is needed. Should the following patterns have a heading?
Items that (maybe) should not display in patterns:
|
The headers with the site title should not use H1. The H1 should be the page title, describing the page content. I think hiding the query loop patterns, the list of posts and the photo blog posts, are handled in #411 But it has gone quiet. |
@beafialho @juanfra in the list in the comment above, there are some questions about some patterns that visually look like they should use headings, but don't use headings. Should they be updated? For example, the "Hey," in the CV pattern is very large, but is a paragraph. |
Sure, as long as the sizes look the same as they do now. |
I second Bea. If they should have headings let's make them use headings as long as the sizes look the same as they do now. |
Thanks @beafialho and @juanfra! I will create a PR for these later today @carolinan, skipping over the notes I made about site titles and level 0. Also noticed @juanfra PR'd in some changes relating to patterns |
Thank you, @troychaplin - Please keep us updated if you're blocked or need anything else. We're on our way to beta 3 coming Monday 🚀 |
Thanks, I'll be on this tonight, I cleared my evening to work on this. Shouldn't take long. |
@juanfra @carolinan I have a question, I just noticed as I was updating the heading the Assuming with translation, but wanna make sure before I get started |
The text strings should all be escaped and translatable, but Ideally, translators would use the same translation for this word, so maybe they need extra help. In Swedish for example there are several synonyms. |
@carolinan After a better review there was only 3 patterns to update and only one was missing translation Some other notes I made for clarification and I can make another PR if necessary:
|
I believe we have reviewed this to the best of our ability. |
Description
Default/bundled themes must pass the requirement for the accessibility-ready tag, which is a tag that is added to style.css and helps identify themes that have been tested for common accessibility problems.
More information and list of requirements.
The text was updated successfully, but these errors were encountered: