[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:  afercia
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  5.3
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  needs-post-mortem has-   |     Focuses:  ui, accessibility,
  screenshots has-patch              |  javascript
-------------------------------------+-------------------------------------

Comment (by azaozz):

 Replying to [comment:74 afercia]:
 > Sure that is, though today it's preferable to say "regardless of the
 ability level".

 Heh, sorry, the wording came petty much straight out of Wikipedia:
 https://en.wikipedia.org/wiki/Accessibility.

 > Code needs to convey meaning and UI elements should adapt to represent
 that meaning at their best. Web standards and accessibility guidelines
 should be implemented from the very beginning of any design process and on
 top of that progressive enhancement can be used to build modern,
 beautiful, interfaces.

 Right, exactly. At this point this is mostly a "principle" question.

 - This used to be an "application menu".
 - It still fulfills the role of "application menu".
 - However the underlying code for it was changed to be "not-a-menu". The
 reason for the change was that "a menu must trigger navigation or it is
 not a menu".
 - There are several other "application menus" in WP that do not trigger
 navigation. In that terms this menu is now inconsistent.

 So, the code for this UI element was changed to convey different
 (incorrect?) meaning, and then the UI element had to also change because
 the code was changed. This was done regardless of the fact that this UI
 element is (still) being used as a menu.

 In coding terms this is not a "progressive enhancement", but a
 "regression".

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