[wp-trac] [WordPress Trac] #63482: wp:list does not like additional attributes on ul

WordPress Trac noreply at wordpress.org
Tue Jul 15 15:41:58 UTC 2025


#63482: wp:list does not like additional attributes on ul
-------------------------+----------------------------
 Reporter:  jasonmader   |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Editor       |     Version:
 Severity:  minor        |  Resolution:  wontfix
 Keywords:  close        |     Focuses:  accessibility
-------------------------+----------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


Comment:

 In my opinion, `aria-orientation` is very much a special case - it should
 probably only be inserted in scripting, since it's only application is to
 communicate how a user should navigate a component. That navigation will
 need to be controlled in external scripts, so the orientation
 characteristic should also be defined there.

 If it's in the HTML directly, then if the scripting fails, the user will
 be informed that they are in a horizontal orientation context, then
 attempt to navigate using left/right arrow keys, but they will not work.

 I would also avoid supporting `role="menu"` for the list block; it's also
 a special case, and in my opinion should only be added via scripting. Like
 orientation, `role="menu"` informs a user how they should interact with
 the element, and if you have the role without associated scripting to
 provide the needed interactions, then you're giving the user
 misinformation.

 I agree with closing this issue. In both cases, these attributes should
 not be supported in the source HTML; they should only be added in script.

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


More information about the wp-trac mailing list