13635 2011-08-03 20:25:04 +0000 Feedback on Various Input Types and Attributes 2014-02-13 14:53:26 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows NT CLOSED WORKSFORME a11y, a11ytf, a11y_semantics, needsinfo P2 normal --- 1 kelly.ford cyns chaals cooper ian joshue.oconnor laura.lee.carlson mark.sadecki+w3c mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52234 0 kelly.ford 2011-08-03 20:25:04 +0000 HTML5 includes new input types and attributes, such as type="tel", pattern, and placeholder. These new types and attribute have usability and accessibility implications, and guidance within the HTML5 specification is at times contradictory. The pattern attribute From the spec The pattern attribute specifies a regular expression against which the control's value, or, when the multiple attribute applies and is set, the control's values, are to be checked. http://dev.w3.org/html5/spec/Overview.html#the-pattern-attribute Comment: The pattern attribute value, in regular expression notation, is not suitable as a hint or description for end-users. The HTML specification describes methods for presenting the pattern to end-users: From the spec: When an input element has a pattern attribute specified, authors should include a title attribute to give a description of the pattern. User agents may use the contents of this attribute, if it is present, when informing the user that the pattern is not matched, or at any other suitable time, such as in a tooltip or read out by assistive technology when the control gains focus. The specification goes on to state: When a control has a pattern attribute, the title attribute, if used, must describe the pattern. Additional information could also be included, so long as it assists the user in filling in the control. Otherwise, assistive technology would be impaired. For instance, if the title attribute contained the caption of the control, assistive technology could end up saying something like The text you have entered does not match the required pattern. Birthday, which is not useful. UAs may still show the title in non-error situations (for example, as a tooltip when hovering over the control), so authors should be careful not to word titles as if an error has necessarily occurred. Comment: The lack of a keyboard accessible mechanism for displaying title content within all major UAs prevents keyboard users from accessing the pattern description. The statement "Otherwise, assistive technology would be impaired" fails to address the actual accessibility implications. The use of the title, implied in the second paragraph above, as text for an error message, implies processing by the UA or assistive technology, and is in effect a special casing of the title attribute. The definition of the placeholder attribute also contradicts the recommendation of using title. 53363 1 mike 2011-08-04 05:13:09 +0000 mass-move component to LC1 54311 2 ian 2011-08-06 07:27:42 +0000 Please file only one specific actionable issue per bug. 60230 3 mike 2011-11-20 18:06:56 +0000 Kelly, this bug is waiting on your response to comment #2: > Please file only one specific actionable issue per bug. 60852 4 ian 2011-12-02 21:01:08 +0000 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: Did Not Understand Request Change Description: no spec change Rationale: I don't understand what problem this bug is about. 100540 5 mark.sadecki+w3c 2014-02-13 14:53:26 +0000 The HTML Accessibility Task Force concluded that this issue has been overcome by changes to the HTML5.1 spec. There is sufficient warning that "title" attribute should not be used alone to convey any input requirements of the element. http://www.w3.org/2014/02/12-a11y-bugs-minutes.html#item03