Changes between Initial Version and Version 3 of Ticket #62548

Timestamp:

11/25/2024 07:16:50 PM (21 months ago)

Author:

sabernhardt

Comment:

As @afercia noted in ticket:47141#comment:1, the ​accessibility coding standards in 2018 said that the labels should not combine both methods.

Existing code uses a mixture of explicitly and implicitly labeled fields, but all new code must use an explicitly associated <label> element (using for/id attributes and not wrapping the form control).

[34991] removed the for attribute in the implicitly associated hide-column-tog checkbox labels with list tables, but other screen options still have the for attribute:

• the hide-postbox-tog checkboxes on the Dashboard
• wp_welcome_panel-hide on the Dashboard
• editor-expand-toggle in the Classic Editor

Removing the for attributes from these implicitly labeled checkboxes would be simple. If switching to explicit association, the input/label pairs should still have a wrapper span to make sure they stay together when they appear on multiple lines.