Do not hardcode TABINDEX into comment_form()
|Reported by:||demetris||Owned by:|
|Component:||Accessibility||Keywords:||2nd-opinion dev-feedback has-patch|
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: