Skip to content

[WCAG/WAI-ARIA] Accessibility audit for core components, making them meet the full criteria for current standards #2917

Open
@Uriziel01

Description

Feature Request

Is your feature request related to a problem? Please describe.
Some current accessibility audit reports have shown that multiple components lack proper ARIA/WCAG compatibility according to the last published web standards, WCAG and WAI-ARIA scanners show that although most of the tags are there, some are still missing or are not used correctly.

Describe the solution you'd like
There are already partial measures in most core components to support accessibility web standards so it's a matter of supporting more feature complete and/or latest versions of the mentioned standards. Probably it was implemented before current versions of the standards where ratified.
So ARIA 1.2 from 06 June 2023 (ARIA 1.3 is W3C First Public Working Draft as of 23 January 2024) and WCAG 2.2 from 5 October 2023

Are there alternatives?
---

Documentation
Examples are carousel elements missing proper structure when it comes to parent->child structure required by ARIA and/or tab elements without aria-controls tags, there is way more.

It could be fixed by overloading the core components template files in our AEM Project but that is not advisable as this would make future migration more complicated and unreliable.

Not sure in what details you would like this feature request report to describe them?

https://www.w3.org/TR/wai-aria-1.2/

https://www.w3.org/TR/WCAG22/

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions