[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]

#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 azaozz):

 Replying to [comment:53 afercia]:
 > I'm not fully sure I understand what "visual semantics" is.

 Yeah, sorry, that's probably not the right term. What I mean by "visual
 semantics" is what you understand what you see on the screen. Basically if
 you look at a picture of a house and a tree, you "know" it is a house and
 a tree, if you look at a picture of a flower, you know it is a flower :)

 > Of course I agree they both change depending on context. However, they
 do that in a very different way and the interaction is very different.
 > ...
 > These items in the left part of the media modal are not comparable to an
 operating system "context menu" in any way, at least to me :)

 Right, this is not "hidden" like right-click menus in applications and
 operating systems. However:
 1. This is a menu.
 2. The content of the menu changes depending on context.

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

 Regardless, I can't find any examples in other applications (or web pages)
 that have menus with headings. So unless there are some, and unless the
 plan is to add headings to the main WP menu and to the admin bar menu, I
 think this change is inappropriate.

 > ...Not a menu that triggers navigation to a different resource.

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

 I think I'm starting to understand what the problem is here. The problem
 is that "accessibility enhancements" are being applied by looking at the
 underlying (HTML) core, and not by looking at the elements on the screen.
 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.

 In any case, calling a menu "not a menu" and adding a heading to it
 doesn't make sense. It was designed to be a menu, looks like a menu, and
 works like a menu.

 That's also the reason there is no good title for it. Neither "Media
 Types" nor "Actions" describe what it is or what it does well. Even worse,
 perhaps in some cases that "title" can be confusing for some users.

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