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 13412 - Editorial change to 2.8.2.3 HTMLFormControlsCollection
Summary: Editorial change to 2.8.2.3 HTMLFormControlsCollection
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P3 normal
Target Milestone: ---
Assignee: contributor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 16:12 UTC by John Foliot
Modified: 2011-08-12 21:49 UTC (History)
4 users (show)

See Also:


Attachments

Description John Foliot 2011-07-28 16:12:52 UTC
The spec reads: 
    "... an input element whose type attribute is in the Radio Button state and whose checkedness is true."

Editorial: The term "checkedness" is not really a word. It is believed "checked state" would be less awkward. 

Filed on behalf of the a11yTF
Comment 1 Michael[tm] Smith 2011-08-04 05:06:49 UTC
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-12 21:49:43 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: "checked state" would be confusing since we already have a term called "Checked State" which applies to all elements (and disambiguating just on case would be very bad for accessibility!). I don't think making up terms is bad here, it makes them eminently searchable and helps implementors be clear about what they're talking about.