Making WordPress.org

Opened 4 months ago

Last modified 4 months ago

#7715 new enhancement

Add accessibility information section on theme single in Theme Directory

Reported by: alh0319's profile alh0319 Owned by:
Milestone: Priority: normal
Component: Theme Directory Keywords: needs-patch needs-design-feedback
Cc:

Description

Background
Currently, themes can receive the accessibility ready tag after undergoing an initial accessibility review by the accessibility team. Once a theme is approved, the theme developer can add the tag to the theme and is allowed to use that tag for the life of the theme without any further review.

For users who are looking for an accessible theme, they have no context for if a theme received the accessibility ready tag 10 days ago or 10 years ago. They also do not have context as to which version of the theme was reviewed, or that it may no longer pass accessibility-ready requirements.

Additionally, there is no visibility about accessibility on most WordPress themes in the directory. Many laws around the world require all businesses to have accessible websites, and it would benefit users to understand the current accessibility status of available themes.

This proposal stems from conversations at WordCamp Canada Contributor Day with @heatherleagault, @slferguson, @kjethapl12, @jessicagoddard, and @miriamgoldman.

Proposed Changes

We propose that a new section should be added to the right sidebar on every theme single. This section would appear below the report section and above the Translations section.

The section would have the following information:

  • Heading: Accessibility information
  • Accessibility review information
    • If no accessibility review has been completed this will say "This theme has not yet been reviewed for accessibility."
    • If a review has been completed there will be the following meta:
      • Last reviewed date
      • Version number of theme reviewed
      • Status Passed or Failed depending upon if the theme passed the review
  • Link to view accessibility statement for theme
  • Link CTA to review this theme for accessibility

@slferguson will upload a design showing these proposed changes.

Prerequisites

In order to achieve this design, there needs to be a way to store meta on the theme that someone from the community can edit. This would be separate from meta that comes out of the theme readme editable by the developer.

We would need to establish a process or workflow that allows anyone in the community or perhaps just people on the themes or accessibility team to submit accessibility reviews on themes that would log the reviewed date, version tested, and status (possibly with additional details available to the theme developer such as what items failed and the username of the reviewer?).

The accessibility statement link is a new accessibility.txt file we're proposing theme developers should be able to add to their theme to document their approach to accessibility, how they've tested for it, etc. There will be a separate ticket for this, which I will link in a comment later.

Why this should be on every theme

We strongly believe that the accessibility information section should be included in every theme and should not be tied to requesting the accessibility-ready tag.

With the upcoming European Accessibility Act legislation, and other laws around the world requiring accessibility, WordPress users should be aware if a theme has not been reviewed for accessibility, if it has been reviewed and has failed, or if it has been reviewed a long time ago.

Putting a section that points out the accessibility status on every theme may encourage theme developers to take accessibility into account; especially once there is a mechanism for the community to submit feedback on accessibility status independent of accessibility-ready tag requested reviews.

Change History (8)

#1 @dufresnesteven
4 months ago

I like the idea of surfacing more information about the theme performance. I'm slightly concerned about our ability to keep this up over time.

I understand a review done 3 months ago, is better than a review done 3 years ago, but that doesn't ensure that the latest version is compliant which is mentioned here as a motivating factor.

With the upcoming European Accessibility Act legislation, and other laws around the world requiring accessibility, [...]

This ticket was mentioned in Slack in #meta by amberhinds. View the logs.


4 months ago

#3 @alh0319
4 months ago

but that doesn't ensure that the latest version is compliant which is mentioned here as a motivating factor.

Yes, that's why we would like to list the version of the theme that passed the accessibility review.

I don't think there would be any extra work related to keeping this up since the information would only change following a manual audit of a theme for accessibility which is already manual anyway. I think updating this would just be a final step on that audit. Or perhaps the information could be pulled from a Trac ticket requesting an accessibility review?

#4 @dufresnesteven
4 months ago

Fair. What I'm trying to point out is that using the latest version of everything (plugins/themes/core) is baked into WP and loosely enforced via auto-updates. This would suggest to users that Version X is accessible but it may be auto-updated to a version that isn't. I recognize that auto-updates for themes are opt-in and not adding this as a blocker but as a consideration.

So in terms of behavior, are we expecting users to download the latest even though it hasn't been tested or download the tested version (there doesn't appear to be a link for that)?

#5 @alh0319
4 months ago

This would suggest to users that Version X is accessible but it may be auto-updated to a version that isn't.

I think that's the point. Currently, we may be misleading users into thinking that the current version of a theme is accessible when, in fact, that may not be the case.

I'd still expect users to download the current version of a theme. Just provide them with information so they can be aware that the current version may not still be accessibility ready.

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


4 months ago

Note: See TracTickets for help on using tickets.