-
Notifications
You must be signed in to change notification settings - Fork 266
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
Update from target size min #2858
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Discussed on TF call 11/22. Concurrence on edit, and already highlighted in email to AG. |
-1 from me. This is a backwards-incompatible normative change; this erratum would mean that some cases will pass in 2.2+errata which would have failed under 2.2 without errata (ie, in 2.2 as referenced in some legislation). I agree that it's frustrating that they're inconsistent, but I think backwards compatibility is more important than consistency. |
This may be a good example for allowing us to identify the scope of the TF's work. Retaining in Discussion until we confirm process with w3c. |
Hi @dbjorge, which legislation references the AAA guidelines? At AA I'd agree, but (as per the advice in conformance) I don't think anyone requires AAA criteria.
I'd argue this is a disambiguation, where the original text is more ambiguous than the update. I.e. people aren't arguing whether something is a sentence or not. Therefore cross-tester consistency is improved and some proportion of things people failed before, and others didn't, would be reduced. |
This PR aligns the older AAA target-size with the newer AA version, for the "inline exception".
The old definition is essentially: The target is in a sentence, or multiple sentences. (Because the definition of "block of text" is one or more sentences.)
The new one is better, but slightly different.
This would be a normative change. As things stand, IF this were approved, it would go into the errata page for WCAG 2.2 and 2.1, and the editors draft, but would not appear on the front of WCAG unless it was re-published.
Closes #2857
Preview | Diff