Build in simple page and site-wide accessibility reporting

Created on 28 May 2021, about 3 years ago
Updated 26 May 2023, about 1 year ago

Problem/Motivation

Drupal knows what URLs are available, butter than anything else. We can rely on a sitemap.xml file to crawl a Drupal site, or crawl a site, but ultimately there may be pages which are missing.

It would be nice if we build in axe testing for both individual pages and all pages using Deque's axe. This could be available to the author after a pages is published, but also aggregated so that an administrator could review pages for the number and complexity of errors that are on the site.

It could also be that tools like Editoria11y catch errors that happen in CKEditor, but miss errors that happen when the page components are stitched together into the final product. Upgrades of modules/themes can also affect accessibility. This Previous/Next post does a good job illustrating how axe can be built into NightwatchJS.

Proposed resolution

Proposed wireframes from Funka study:

Remaining tasks

User interface changes

  • Button for page level accessibility
  • Dialog for page accessibility errors
  • Page listing site-wide URLs & errors

Data model changes

This would need to be stored in the DB. We'd also ideally be able to see accessibility over time, so historical information should be captured.

Release notes snippet

✨ Feature request
Status

Active

Version

10.0 ✨

Component
BaseΒ  β†’

Last updated 36 minutes ago

Created by

πŸ‡¨πŸ‡¦Canada mgifford Ottawa, Ontario

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024