[wp-trac] [WordPress Trac] #46899: Ensure that tables generated by the Settings API have no semantics

[WordPress Trac]

#46899: Ensure that tables generated by the Settings API have no semantics
------------------------------+--------------------------------------------
 Reporter:  greatislander     |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Plugins           |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  settings-api      |     Focuses:  accessibility, administration
  has-patch                   |
------------------------------+--------------------------------------------

Comment (by afercia):

 @greatislander thanks for the patch! Worth noting
 [attachment:"46899.diff"] will only have an effect on settings sections
 added by plugins. The core settings screens in WordPress don't use the
 Settings API, see #38734.

 For the core tables, `role="presentation"` needs to be added to all the
 settings pages `options-general.php`, `options-writing.php`, `options-
 reading.php`, etc. plus the settings pages in the multisite part.

 Note: There are other layout tables outside the settings pages (typically
 they have a `form-table` CSS class) but I'd say they're out of the scope
 of this ticket.

 For some background, there are various
 [https://core.trac.wordpress.org/query?keywords=~settings-api pending
 tickets related to the Settings API]. Some of them focus on the UI part,
 most notably #16413, #18801, and #39441. Also, a couple years ago
 @flixos90 and @afercia explored improvements to the Settings API in a
 plugin published on GitHub see https://github.com/wpaccessibility
 /settings-api-enhanced.

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