[wp-trac] [WordPress Trac] #47610: Media modal: add more headings to better identify the main sections and improve content navigation for assistive technology users

WordPress Trac noreply at wordpress.org
Mon Oct 14 16:49:59 UTC 2019


#47610: Media modal: add more headings to better identify the main sections and
improve content navigation for assistive technology users
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  karmatosed
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  5.3
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-post-mortem has-   |     Focuses:  ui, accessibility,
  screenshots has-patch i18n-change  |  javascript
-------------------------------------+-------------------------------------

Comment (by afercia):

 > I'm not sure what else to call it except a "contextual menu" :)

 "Dynamic menu" :)

 > Regardless, I can't find any examples in other applications (or web
 pages) that have menus with headings.

 In the previous comment I mentioned the macOS finder, the Gnome file
 manager, and even the Google Chrome settings page as quick examples.

 > This is (technically) incorrect. Strictly speaking it triggers a request
 to the server and loads the new content in the modal.

 Yep, okay but not traditional navigation anyways. Not the same interaction
 and not the same feedback. The browser doesn't navigate to a new resource
 nor the media modal implements a routing system to emulate navigation.
 Technically, these are buttons that trigger an AJAX request to fetch data
 and inject them dynamically within the current page together with a mix of
 JS and HTML. To me, that's not navigation so this is not a navigation
 menu. I could agree it's an "actions menu".

 > Then the accessibility recommendations are being applied to the code
 regardless of the UI elements that code represents. This seems like "the
 wrong way to do things" and often leads to inconsistencies in user
 experience for users of assistive technology.

 I'm sorry but this sounds very arguable to me :) And sounds like a lack of
 a full understanding of what accessibility is.

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


More information about the wp-trac mailing list