Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#12963 closed enhancement (fixed)

Do not hardcode TABINDEX into comment_form()

Reported by: demetris Owned by:
Milestone: 3.0 Priority: normal
Severity: normal Version: 3.0
Component: Accessibility Keywords: 2nd-opinion dev-feedback has-patch
Focuses: Cc:


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.:


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().


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



Attachments (1)

remove_tabindex_comment_form.diff (3.6 KB) - added by ptahdunbar 5 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 @ptahdunbar5 years ago

  • Keywords has-patch added

comment:2 @nacin5 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [14114]) Remove tabindex from comment_form(). fixes #12963

Note: See TracTickets for help on using tickets.