3 ms·
Sighted users normally have a whole bunch of CSS to convey the same information (as is recommended by most [all?] accessibility standards). Users of assistive t
by runarberg 4y ago
Sighted users normally have a whole bunch of CSS to convey the same information (as is recommended by most [all?] accessibility standards). Users of assistive technology have to rely on the semantics of the document.
Also sighted users get this information as well. If you hover over a link, it displays the target href in the lower corner or your window.
- jameshart 4y agoThe article does not mention changing what the control looks like, only how it is marked up. The design is shown as settled - a roller icon - and the only question to be decided is if that icon is implemented as a link or a button in the DOM. And there’s no hover-link-pop up on a mobile phone touchscreen.
- runarberg 4y agoWell actually the article is wrong on the markup, it should be neither a link nor a button, but a <details> <summary>
- darekkay 4y ago> Also sighted users get this information as well. If you hover over a link, it displays the target href in the lower corner or your window. You shouldn't rely on that: it won't work on mobile nor for users who don't want or can't use a mouse (e.g. people with a motoric disability).
- runarberg 4y agoThe target usually shows as well if you navigate using the keyboard. But you are right, I shouldn’t rely on that, and I don’t, I style my links with CSS so that sighted users can distinguish them by their styles. The location is a bonus. Also if sighted mobile users want to see the location, I think they can click and hold the link, and see it in the context menu.