Skip to content
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.

Complete the accessibility-ready review #408

Closed
10 of 13 tasks
carolinan opened this issue Sep 25, 2024 · 18 comments
Closed
10 of 13 tasks

Complete the accessibility-ready review #408

carolinan opened this issue Sep 25, 2024 · 18 comments
Labels
Accessibility (a11y) Needs accessibility testing or feedback [Priority] Highest Used to indicate widespread, critical issues that need immediate attention Task

Comments

@carolinan
Copy link
Contributor

carolinan commented Sep 25, 2024

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.

@carolinan carolinan added Task Accessibility (a11y) Needs accessibility testing or feedback [Priority] Highest Used to indicate widespread, critical issues that need immediate attention labels Sep 25, 2024
@troychaplin
Copy link
Contributor

troychaplin commented Oct 4, 2024

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_CodeSniffer

Image

Pattern test with Wave Extension

Image

Test after adding inline background colour style

Image

@carolinan
Copy link
Contributor Author

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.

@troychaplin
Copy link
Contributor

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.

@carolinan
Copy link
Contributor Author

Content links:
Links in the post, page and comment content are underlined.

I have a reservation about links in close proximity to the content, such as dates, author names, and categories not being underlined.
Without an underline, they can only be discovered by focusing on or hovering over the item.

@carolinan
Copy link
Contributor Author

carolinan commented Oct 7, 2024

ARIA landmark roles:
In "News blog with featured posts grid", there is a pattern between the <main> and the <footer> that is outside a landmark (I thought I fixed this once).

In "Right-aligned single post" the comments area between the <main> and the <footer> is outside a landmark. Lets use the aside for this template, to not make any changes to the existing design.

@troychaplin
Copy link
Contributor

Heading error:

  • Banner with book description uses h3 creating an incorrect heading order

Fixed in PR - #510

@troychaplin
Copy link
Contributor

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?

  • Cover with big heading
  • Centered link and social links: if adding a header should that be applied to the whole line (p current has a br) or should it be split into an h2 and a p?
  • Centered footer
  • Centered header (site title has heading level 0)
  • Header with columns (site title has heading level 0)
  • Header with large title (site title has heading level 0)
  • Header (site title has heading level 0)
  • CV/bio
  • Link in bio with tight margins
  • 2 columns with avatar (compared to “3 column layout with 6 testimonials“ which has a header)
  • Vertical header (site title has heading level 0)

Items that (maybe) should not display in patterns:

  • Right-aligned blog, 404 (template-404-vertical-header-blog.php)
  • Photo blog page (template-page-photo-blog.php)
  • Page template for the right-aligned blog (template-page-vertical-header-blog.php)
  • Photo blog posts (template-query-loop-photo-blog.php)
  • List of posts, 1 column (template-query-loop.php)

@carolinan
Copy link
Contributor Author

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.

@carolinan
Copy link
Contributor Author

carolinan commented Oct 9, 2024

@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.

@beafialho
Copy link
Contributor

@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?

Sure, as long as the sizes look the same as they do now.

@juanfra
Copy link
Member

juanfra commented Oct 9, 2024

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.

@troychaplin
Copy link
Contributor

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

@juanfra
Copy link
Member

juanfra commented Oct 9, 2024

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 🚀

@troychaplin
Copy link
Contributor

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.

@troychaplin
Copy link
Contributor

troychaplin commented Oct 9, 2024

@juanfra @carolinan I have a question, I just noticed as I was updating the heading the Cover with big heading pattern that the content in the file is not wrapped in esc_html_x like we have in the CV/bio. Which is the preferred method, I will review them all again and make them consistent.

Assuming with translation, but wanna make sure before I get started

@carolinan
Copy link
Contributor Author

The text strings should all be escaped and translatable, but _x is only needed if additional context needs to be provided.
If it is not clear that Stories is intended to be an example brand name, yes, please add the translators context.

Ideally, translators would use the same translation for this word, so maybe they need extra help. In Swedish for example there are several synonyms.

@troychaplin
Copy link
Contributor

troychaplin commented Oct 10, 2024

@carolinan After a better review there was only 3 patterns to update and only one was missing translation so I used _x and PR'd the changes. I can change that for _e if you'd like. I reviewed again and it should be _e based on other patterns, changes have been pushed.

Some other notes I made for clarification and I can make another PR if necessary:

  • Centered link and social links: do we want to split this into a header + para, or one header while maintaining the br?
  • 2 columns with avatar: sorry I wasn’t more clear, this pattern has no heading, compared to a similar 3 column 3 testimonial pattern. Just a note as I’m not sure if this was intentional or if it should have a heading.

@carolinan
Copy link
Contributor Author

I believe we have reviewed this to the best of our ability.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility (a11y) Needs accessibility testing or feedback [Priority] Highest Used to indicate widespread, critical issues that need immediate attention Task
Projects
None yet
Development

No branches or pull requests

4 participants