[wp-trac] [WordPress Trac] #12963: Do not hardcode TABINDEX into comment_form()

[WordPress Trac]

#12963: Do not hardcode TABINDEX into comment_form()
---------------------------+------------------------------------------------
 Reporter:  demetris       |       Owner:                          
     Type:  enhancement    |      Status:  new                     
 Priority:  normal         |   Milestone:  3.0                     
Component:  Accessibility  |     Version:  3.0                     
 Severity:  normal         |    Keywords:  2nd-opinion dev-feedback
---------------------------+------------------------------------------------
 Have we thought whether we have a good reason for adding {{{tabindex}}} to
 the elements of the new {{{comment_form()}}}?

 If we are doing it for accessibility, the accessibility folks seem to
 recommend against it.  E.g.:

 http://www.webaim.org/techniques/keyboard/tabindex.php

 Are there other considerations in addition to accessibility?

 We could take the safe road of making {{{tabindex}}} filterable.  However,
 since that would take work, if it was up to me I would be itching to
 remove {{{tabindex}}} completely from {{{comment_form()}}}.

 Thoughts?

 PS.  Two articles I came across while searching to see if the issue had
 been discussed before within WordPress:

 http://www.lukerodgers.ca/2009/03/wordpress-comment-form-tabindex-no-no/

 http://www.456bereastreet.com/archive/200712/overdoing_accessibility/

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12963>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software