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: WCAG 3.0 public comment (2 - Question on partial conformance #425

Closed
jspellman opened this issue Mar 10, 2021 · 5 comments
Closed
Assignees
Labels
only response needed issues that should be easy to close, acknowledgement only

Comments

@jspellman
Copy link
Contributor

jspellman commented Mar 10, 2021

Comment from Email:
from spreadsheet

Multiple means of measurement, in addition to pass/fail statements, allow inclusion of more accessibility guidance.

Will it still be possible to fully determine whether a website conforms to the guidelines or only partial?

@jspellman
Copy link
Contributor Author

Thank you for your comment. Project members are working on your comment. You may see discussion in the comment thread and we may ask for additional information as we work on it. We will mark the official response when we are finished and close the issue.

@jspellman jspellman added action: answer question when commenter has a question that we need to answer, not a critique of documents section: abstract & Intro status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default) section: Requirements Related to Silver Requirements document and removed section: abstract & Intro labels Mar 10, 2021
@JaninaSajka
Copy link

JaninaSajka commented Dec 10, 2021

DRAFT RESPONSE: We are indeed working out how to include web content that may not fully
conform to all WCAG 3 Guidelines and Outcomes. We are aware that persons with
disabilities can often use content that doesn't fully conform, so we are
working out what content and how much partially conforming content may be acceptable. Meanwhile, this
approach is balanced by our emerging concept described in
Sec. 5.1.2.1: Critical Errors in the WCAG3
Explainer
,
and exemplified in the current WCAG 3 Working Draft
Guidelines
where critical errors
are enumerated, when they're identified, for each Guideline. It is important
to understand that a critical error can cause
web content to completely fail WCAG 3 Conformance, even though the
remainder of the content might actually evaluate as very acceptable.

@jspellman jspellman added survey : ready for proposal or issue response is ready for group review and removed status: assigned to subgroup ask subgroup for proposal labels Dec 10, 2021
@rachaelbradley rachaelbradley removed section: Requirements Related to Silver Requirements document Subgroup: editors no specific subgroup (default) action: answer question when commenter has a question that we need to answer, not a critique of documents labels Jan 25, 2022
@rachaelbradley rachaelbradley removed the survey : ready for proposal or issue response is ready for group review label May 9, 2022
@rachaelbradley
Copy link
Contributor

@JaninaSajka This answer needs to be slightly revisited now that we are shifting approaches.

@jspellman
Copy link
Contributor Author

jspellman commented Feb 5, 2024

Approved Response


Thank you for your thoughtful response. This is one of the key areas of WCAG3 where it has been difficult to reach consensus because there is no clear good answer and we need more data and prototyping to determine the best path forward. Our intent has always been to have pass/fail conformance, but we have been exploring ideas that go beyond binary true/false success criteria.

We are aware of the importance of being able to determine that a website fully conforms for regulatory, legal, and testing reasons but there also are use cases for partial conformance. Some disability needs cannot be addressed within a binary measurement and therefore have been excluded from WCAG2. Some content that does not meet WCAG2 can still be used by people with disabilities. Content exists that cannot be made conformant for a variety of reasons that may not be under the control of the authoring organization. You can read some of our thinking about this complex topic in Use Cases for WCAG 3.0 Conformance draft that we have identified.

We are considering a variety of options to address this important issue, but do not have sufficient data yet to make an informed decision. We are first going to do a pass of the user needs that we wish to include in WCAG3 so we have good evidence to test which of our proposed solutions best addresses the user needs and the use cases we have identified. We will be sure to highlight these proposals in a future public draft where there will be sufficient examples to illustrate the problem and the solution(s) we are proposing.

@alastc alastc added the only response needed issues that should be easy to close, acknowledgement only label Feb 6, 2024
@alastc
Copy link
Contributor

alastc commented Mar 21, 2024

Response above approved.

@alastc alastc closed this as completed Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
only response needed issues that should be easy to close, acknowledgement only
Projects
None yet
Development

No branches or pull requests

4 participants