This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9485 - Mandate all conformance checkers and validators must refer to WCAG
Summary: Mandate all conformance checkers and validators must refer to WCAG
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, a11ytf, a11y_text-alt
Depends on:
Reported: 2010-04-11 08:54 UTC by Laura Carlson
Modified: 2013-05-14 18:49 UTC (History)
8 users (show)

See Also:


Description Laura Carlson 2010-04-11 08:54:58 UTC
Mandate in HTML5 that all conformance checkers and validators must refer to the appropriate WCAG document and section that provides remedial guidance to authors whenever text alternatives are unknown or missing.
Comment 1 Henri Sivonen 2010-04-12 08:08:42 UTC
I think the spec shouldn't micromanage the user interface design of any class of products--including conformance checkers. Conformance checker vendors should be able to compete on the quality of the user experience of reporting conformance errors.

That is, I think this bug should be resolved as WONTFIX.
Comment 2 Ian 'Hixie' Hickson 2010-04-12 08:17:12 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: As Henri says, we try to avoid defining UI requirements. I would recommend putting such a requirement in a UAAG analogue for validators.
Comment 3 Martin Kliehm 2010-12-07 16:43:37 UTC
The bug-triage sub-team agrees with Henri's comment but is bringing it forward to the accessibility task force to achieve consensus.
Comment 5 Mark Sadecki 2013-05-14 18:49:47 UTC
The Task Force has decided that this bug is beyond the scope of the WG.