[META] Simplify / streamline codebase to allow accessibility tests to be extended for contrib themes

Created on 28 January 2017, over 7 years ago
Updated 30 May 2023, about 1 year ago

It would be really great if there was a simple process to extend core's tests for use in a contrib module to ensure that all of the accessibility improvements are not accidentally broken by the contrib module.

Initial idea:

  • Refactor / streamline / simplify the tests around accessibility so that they have a hierarchical structure:
    • Base tests for system output.
    • Each bundled theme would extend these to include any additional accessibility adjustments necessary for the theme, e.g. DOM-level adjustments where the output adds extra DIVs, etc.
  • Clearly document how a contrib theme would go about leveraging the core tests.
  • Later on.. create a generator in DrupalConsole to create the necessary test files for a given subtheme.
📌 Task
Status

Active

Version

11.0 🔥

Component
Theme  →

Last updated about 7 hours ago

Created by

🇺🇸United States DamienMcKenna NH, USA

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.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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