W3C home > Mailing lists > Public > public-html-a11y@w3.org > December 2010

[Bug 11540] The willful violation clause is most unwise. A standard should not violate another standard for any reason. This wouls lead to 2 things : 1) Content correctly encoded content would never be displayed correctly. 2) All future standards would need to includ

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Dec 2010 11:17:14 +0000
To: public-html-a11y@w3.org
Message-Id: <E1PS6P4-0003D6-Kv@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11540

Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bhawkeslewis@googlemail.com

--- Comment #4 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-12-13 11:17:13 UTC ---
(In reply to comment #3)
> Reopening. Would like to hear editor's rationale.

The spec gives the rationale, as it does for every designated willful
violation: "motivated by a desire for compatibility with legacy content". Are
you disputing that user agents need to follow this behavior in order to enable
people to access the current web corpus?

> Also applicable to "willful violations" of WCAG and other accessibility
> guidelines.

It's certainly not, since (a) there are no willful violations of conformance
criteria of accessibility-related standards designated in the spec and (b) if
they were, it would be off-topic for this bug, which is concerned with the
willful violations in:

http://www.whatwg.org/specs/web-apps/current-work/#table-encoding-overrides

(If you think that the spec should designate a willful violation of a
conformance criterion of an accessibility-related standard where it currently
does not, please file a bug to that effect. Note it's technically impossible
for HTML5 to establish conformance criteria that willfully violate WCAG2, since
(unlike WAI-ARIA) WCAG2 does not establish any conformance criteria for host
languages and (unlike UAAG) WCAG2 does not establish any conformance criteria
for user agents. At worst, HTML5 might introduce features that are impossible
for authors to use in conformance with WCAG, but I don't think that's been
demonstrated to be the case.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 13 December 2010 11:17:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:27 GMT