[wp-trac] [WordPress Trac] #15080: Comment Form Should use HTML5 input types for better accessibility

[WordPress Trac]

#15080: Comment Form Should use HTML5 input types for better accessibility
---------------------------+------------------------------------------------
 Reporter:  jorbin         |       Owner:           
     Type:  enhancement    |      Status:  new      
 Priority:  normal         |   Milestone:  3.1      
Component:  Accessibility  |     Version:  3.0      
 Severity:  normal         |    Keywords:  has-patch
---------------------------+------------------------------------------------

Comment(by demetris):

 Replying to [comment:4 jorbin]:
 > I tested in opera 10.62 and both .in and .eu domains work fine. I think
 that was an old bug.
 >
 It is not that old (it was reported 3 months ago) and, in any case, I only
 mentioned it as an example.  There are more issues and strange bits of
 behaviour.  If you play a bit with desktop browsers that understand these
 types, you’ll see that current implementations are not such that you would
 want to trust them with your user’s experience.  This thing is new and we
 should expect issues to keep popping up while it is new.

 >  http://webaim.org/blog/future-web-accessibility-new-input-types-in-
 html5/ has some info on how these improve accessibility.
 >
 The WebAIM article does not discuss the accessibility of existing
 implementations.  It just talks about what user agents could or might do
 in the future with the new types.

 > Also, the iphone does some very cool things with the type that we would
 now be enabling:  http://diveintohtml5.org/forms.html
 >
 I know about the iPhone keyboard adjustment and I agree that it is a smart
 and useful thing, but mobile themes can, and do, take care of that.  Both
 WPtouch and WPtouch Pro, for example, use the new input types.  WPtouch
 since March 2010;  WPtouch Pro since its first release.

 > Sites that want to use xhtml or html4 should be required to filter the
 content.  Twenty Ten is html5.

 {{{comment_form}}} is not a Twenty Ten function.  It is a core function
 meant for all themes.

 Expecting themes to use filters so that they generate valid XHTML 1 or
 HTML 4 does not seem like a sound approach to me.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/15080#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software