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

Email: ITI Comments on First Public Working Draft of W3C Accessibility Guidelines (WCAG) 3.0 (18 - Flexibility for Conformance) #460

Open
jspellman opened this issue Mar 12, 2021 · 1 comment
Assignees
Labels
migration: core Issues that raise core questions that are still open for discussion section: conformance Deals with conformance aspect of Silver status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default)

Comments

@jspellman
Copy link
Contributor

Comment from Email:
from PDF

FPWD: We seek feedback on whether the flexibility introduced will encourage content providers to meet conformance because it is more achievable vs. whether they are less likely to improve if they don’t have to.

Flexibility for conformance is desperately needed. Full conformance is very difficult for most sites and products. Full conformance is impossible to evaluate for large and highly dynamic websites, and complex software. Flexibility in the conformance model will provide a substantial incentive for adoption, although it is unlikely that sites will opt to ignore WCAG 2.x conformance efforts. A mapping between the WCAG 2.x and 3 standards would also encourage adoption with a clear path to move to the new standard.

@jspellman jspellman added section: conformance Deals with conformance aspect of Silver status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default) labels Mar 12, 2021
@jspellman jspellman changed the title Email: ITI Comments on First Public Working Draft of W3C Accessibility Guidelines (WCAG) 3.0 (18 - Email: ITI Comments on First Public Working Draft of W3C Accessibility Guidelines (WCAG) 3.0 (18 - Flexibility for Conformance) Mar 12, 2021
@MakotoUeki MakotoUeki self-assigned this Dec 17, 2021
@MakotoUeki
Copy link
Contributor

MakotoUeki commented Dec 17, 2021

Draft Response:

Thank you for your comment.

We agree with you that we have to consider the need for flexibility around large and highly dynamic websites and complex software. And we already got this concern in the #448. Please let us use it to address this issue.

We will use this issue (#460) to track your proposal to create a mapping between "WCAG 2.x" and "WCAG 3.0". We will definitely create it to encourage those already using WCAG 2.x to adopt WCAG 3.0.

@rachaelbradley rachaelbradley added migration: other Issues that do not fall into the other three categories migration: core Issues that raise core questions that are still open for discussion and removed migration: other Issues that do not fall into the other three categories labels Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration: core Issues that raise core questions that are still open for discussion section: conformance Deals with conformance aspect of Silver status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default)
Projects
None yet
Development

No branches or pull requests

3 participants