Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility Vocabulary #18

Open
MRuecklCC opened this issue Jul 19, 2022 · 1 comment
Open

Accessibility Vocabulary #18

MRuecklCC opened this issue Jul 19, 2022 · 1 comment

Comments

@MRuecklCC
Copy link

MRuecklCC commented Jul 19, 2022

Currently, the accessibility vocabulary holds 5 different choices:

  • A
  • AA
  • AAA
  • WCAG
  • BITV

Unfortunately, I was not able to find any documentation about when exactly use which choice. Reading about BITV and WCAG, I found that BITV seems to be a superset of the WCAG AAA rating, i.e. if a site is BITV compliant it would also have a AAA WCAG rating. This makes the current definition of the value space slightly confusing:

  • Why is there a WCAG value?
  • There is no value for "not even A", i.e. a site that does not fulfill even the lowest standards,
  • We could change to (in ascending order):
    • B (or some other name, no compliance)
    • A (WCAG)
    • AA (WCAG)
    • AAA (WCAG)
    • BITV

IMHO, it is very important to distinguish the scenario, where a rating is not available (missing meta-datum) and where a site is not compliant with any rating (currently also a missing meta-datum), so we should definitively add a "B" rating value.

@lummerland
Copy link
Collaborator

I agree, the A-ratings belong to WCAG so there is no need for the extra value. BITV, for one, has 2 levels (Priorität 1 + 2) that maybe should be taken into account here as well? I find the distinction "no rating" and "low rating" very useful, actually there is only a "no rating" available.
Why not propose a change via pull request? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants