Support of W3C's accessibility standards

[hokkanent]

To accomodate users that use assistive software such as screen readers –how does
Klaro consent banner supports W3C's accessibility standards WCAG 2.1 (level AA) and WAI-ARIA?

[jaller94]

Thanks for your interest in Klaro. I noticed you created a GitHub account to create the issue. Thanks!
Klaro has not been tested for accessibility.
We have some plans to make it more accessibly though and will support contributions to make Klaro more accessible.

Klaro has been forked by Empreinte Digitale. The fork Orejime 🍪 focuses on accessibility. It follows Web Content Accessibility Guidelines (WCAG) via the French RGAA. I would love to apply most of there changes to our codebase as well, but it's not trivial and will take some planning and development time.

In regards to screen readers, I'm only familiar with the usage of the ChromeVox screen reader and I know that their detection of semantic HTML and aria features vary, but not how. A list of found issues per screen reader would help to address these. When in doubt, I would use the semantic HTML, hoping for screen readers to improve over time.

[darylknight]

I'd love to see this too. I'm currently stuck between a rock and a hard place... between "complying with international cookie laws" and "complying with US accessibility laws".

[frommo-juliane]

@jaller94 I have a short list from a specialized agency. That's all the information I have. I hope it helps.

• The accordion element in the settings of the cookie overlay "↓ 1 service" is a show-hide element and should be a button with aria-label.

• The link "Let me choose", with which the overlay for the cookie settings can be opened, should be a button with aria-label that opens a dialog.

• The modal window itself is not implemented correctly - especially when it comes to focus management.

[mrleblanc101]

@jaller94 $ years later, any news to share ? There hasn't seem to be any progress.

[darylknight]

FWIW, I've moved elsewhere. The last commit to this repository was a year ago. The subscription side of things also hasn't worked for at least a year, and the support team stopped replying to our emails.