Skip to content
This repository was archived by the owner on Oct 15, 2025. It is now read-only.

Conversation

rickschmoo
Copy link

Typo in first sentence - scope of WCAG 3 is incorrectly "web A11y". Changed to "digital A11y".

Typo in first sentence - scope of WCAG 3 is incorrectly "web A11y". Changed to "digital A11y".
@rickschmoo
Copy link
Author

See issue #242 (I don't have write access so can't link)

@rickschmoo rickschmoo closed this Jan 24, 2021
@rickschmoo rickschmoo reopened this Jan 24, 2021
Base automatically changed from master to main February 16, 2021 13:32
@Myndex
Copy link
Member

Myndex commented Nov 17, 2021

OBJECTION

As I stated in survey, there are legal ramifications for the organization and for those developing guidelines or technology for guidelines. This is not a trivial matter.

"Digital" is exceedingly broad. It is important to point out that attempting to be that broad also means a potential increase legal liabilities. This adds a trickle down concern for those of us that are donating certain technologies, originally intended for web served content only.

As such I have to object — while WCAG is used for non-web development of apps anyway (because WCAG is a freely available standard) that's different than claiming in a statement that it's good for all things digital.

Do you want to create an implied liability for "digital" systems for clinical or medical use? Aerospace? Human safety?

Rethink this please. I am NOT saying it has to be limited to web, but that if you are going to extend, it also can not be at the wave of a hand, and the extensions need to be well defined.

Other standards agencies are very granular in the approach to what a given standard document covers.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants