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 9871 - provide normative advice to conformance checkers about use of onevent handler attributes
Summary: provide normative advice to conformance checkers about use of onevent handler...
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, NE
Depends on:
Blocks:
 
Reported: 2010-06-07 08:50 UTC by steve faulkner
Modified: 2010-10-12 12:30 UTC (History)
8 users (show)

See Also:


Attachments

Description steve faulkner 2010-06-07 08:50:14 UTC
Use of event handler attributes (http://dev.w3.org/html5/spec/index.html#attributes-1) on html elements with strong native semantics should trigger an error as they can and often do overload the default behaviours and semantics of the element, this can cause problems for some users in understanding how to use and interpret the elements as their native sematics do not convey adequately how to interact with the added beahviours and semantics. This issue is partcilularly problematic for users of assitive technology and therefore leads to a reduction in the accessibility of HTML.
Comment 1 Michael[tm] Smith 2010-06-17 15:56:31 UTC
added a11ytf keyword; see http://www.w3.org/2010/06/17-html-a11y-minutes.html for some related discussion
Comment 2 Ian 'Hixie' Hickson 2010-08-16 21:34: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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: onclick attributes have valid use cases, e.g. analytics. While it is certainly true that they are sometimes misused, such misuse is already made non-conforming by the spec and it is impossible for a conformance checker to reliably distinguish such cases from conforming cases.