WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #47610, comment 54


Ignore:
Timestamp:
10/14/2019 04:22:35 PM (14 months ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #47610, comment 54

    v1 v2  
    2020This is (technically) incorrect. Strictly speaking it triggers a request to the server and loads the new content in the modal.
    2121
    22 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.
     22I 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) code, 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.
    2323
    2424In 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.