| 1 | | Having a look at the code, yeah, they're not actually graphical links. That makes it a bit more tricky. I'll play with it a bit on this side and see if I can tweek things a bit. Screenreaders *should* be reading these links correctly by default, though--they're valid HTML, whether or not Aria is involved, so far as I'm aware. This has only been a problem since version 3.3, so it's definitely related to one of the changes implemented there. However, verifying on wordpress.com which still runs 3.2.1 still, yes the screenreader still reads those links as, for instance, wp-admin/index, but it *also* reads the Dashboard links etc. And, in that version, they behave more as expected--the menus are available as needed, without guess work/screen manipulation on an extensive scale. Not sure how much help that is, but you'll have that. I have another ticket open on this issue re: an accessibility option for the dashboard menus, similar to what we have for widgets etc (#14045). Is it possibly time to revisit that ticket as well? |
| | 1 | Having a look at the code, yeah, they're not actually graphical links. That makes it a bit more tricky. I'll play with it a bit on this side and see if I can tweek things a bit. Screenreaders *should* be reading these links correctly by default, though--they're valid HTML, whether or not Aria is involved, so far as I'm aware. This has only been a problem since version 3.3, so it's definitely related to one of the changes implemented there. However, verifying on wordpress.com which still runs 3.2.1 still, yes the screenreader still reads those links as, for instance, wp-admin/index, but it *also* reads the Dashboard links etc. And, in that version, they behave more as expected--the menus are available as needed, without guess work/screen manipulation on an extensive scale. Not sure how much help that is, but you'll have that. |
| | 2 | |
| | 3 | Scratch my ticket reference from earlier. That'll teach me to look before I type. That ticket actually isn't related. |