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

Where requirements go within the structure #155

Open
alastc opened this issue Dec 10, 2024 · 0 comments
Open

Where requirements go within the structure #155

alastc opened this issue Dec 10, 2024 · 0 comments

Comments

@alastc
Copy link
Contributor

alastc commented Dec 10, 2024

From an email to the list:

Keyboard Focus Appearance doesn’t specify target size or contrast requirements. That is the same problem WCAG 2.0 has, which AGWG tried and failed to address in 2.2. This draft shows no progress in filling that gap. If anything, the lack of progress shows the new structure of WCAG 3.0 isn’t helping to address WCAG 2’s gaps and equity challenges.

There are requirements for focus-appearance (which is further along in development), however, they are further down in the structure.

This is problematic because we need the or at least a level of testable requirements to be part of the normative spec. This is an issue to track progress on this topic.

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

No branches or pull requests

1 participant