Making WordPress.org

Opened 11 months ago

Last modified 5 months ago

#7165 assigned defect (bug)

Overview: Current state of accessibility-ready Themes

Reported by: travel_girl's profile Travel_girl Owned by: travel_girl's profile Travel_girl
Milestone: Priority: normal
Component: Theme Review Keywords:
Cc:

Description

I have noticed, that some Themes have the accessibility-ready tag, without beeing meeting the required criterias for the accessibility-ready-tag.

Does has different reasons:

  • it did not get checked at all for a11y
  • it did not get checked in a proper way
  • it got an update and is not accessible anymore
  • the Theme added the a11y-tag after the release in the repro

We should make sure, that themes with the a11y-ready-tag are actually accessible, as people rely on this. Otherwise this tag would not make any sense.

So I go through the a11y themes and do a quick check, if they are accessible. I made a google sheet, to keep track of it. Currently it lists all the themes who got into the repro with the a11y-tag between 1.1.2021 and 28. July 2023.

https://docs.google.com/spreadsheets/d/1auQFrOqEs_59ltqy2GydRCPwaNatwQWJF81EjoQsj0M/edit?usp=sharing

The workflow for this check is currently:

  • See if Theme got an A11y Audit
  • if not: quick check of 15 min
  • if bugs are found: report it to the theme developer and ask, if they would be willing to fix a11y issues, or if they would prefer to remove the accessibility-ready-tag

-- a11y tag is removed from developer
-- Theme Developer is not reacting back. My suggestion: Deadline of certain time, if no respond remove the theme from the repository?
-- Theme Developer fixes the first issues -> complete Accessibilit Audit + second round of fixing issues

I'm not a big Fan of removing a Theme in case developers are not removing the a11y-tag. But as far as I know, we don't have the posibility to remove the a11y-tag by ourself?

Further I think it would be a good idea to optimize the workflow for the a11y-ready-tag, but that is a topic for a different ticket.

Change History (2)

This ticket was mentioned in Slack in #accessibility by travelgirl. View the logs.


11 months ago

This ticket was mentioned in Slack in #themereview by kafleg. View the logs.


5 months ago

Note: See TracTickets for help on using tickets.