[wp-trac] [WordPress Trac] #58703: wp-list-table: <label> is preceding <input> in the checkbox column

[WordPress Trac]

#58703: wp-list-table: <label> is preceding <input> in the checkbox column
----------------------------+----------------------------
 Reporter:  dimitris.m      |       Owner:  joedolson
     Type:  defect (bug)    |      Status:  accepted
 Priority:  normal          |   Milestone:  6.3
Component:  Administration  |     Version:  trunk
 Severity:  minor           |  Resolution:
 Keywords:  needs-patch     |     Focuses:  accessibility
----------------------------+----------------------------
Changes (by joedolson):

 * keywords:   => needs-patch
 * owner:  (none) => joedolson
 * status:  new => accepted
 * severity:  normal => minor
 * milestone:  Awaiting Review => 6.3


Comment:

 It's not an accessibility defect, per se. The reason for placing a label
 after a checkbox is for visual clarity: it's the most predictable and
 usual location for a label to be associated with a checkbox. However,
 since these labels are not visible, this concern doesn't apply.

 See:
 https://www.w3.org/TR/WCAG20-TECHS/G162.html#:~:text=Labels%20for%20radio%20buttons%20and,fields%20sometimes%20vary%20in%20length.

 Techniques documents are non-conforming, so not following those
 instructions to the letter does not constitute a WCAG violation.

 That said, since the label is not visible, the placement is arbitrary - so
 there's no reason we couldn't move the label after the checkbox. It would
 have no visual consequences for design, and could resolve a small set of
 automated testing false positives.

 I do think there's a value in avoiding producing false positives, since
 those just add to the labor burden of managing accessibility, even if they
 have no real world consequences for the user.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58703#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform