4 ms·
There are techniques to solve that: https://www.w3.org/WAI/WCAG22/Techniques/html/H33 https://www.w3.org/WAI/WCAG22/Techniques/html/H33 https://www.w3.org/WAI
by layer8 1y ago
There are techniques to solve that:
https://www.w3.org/WAI/WCAG22/Techniques/html/H33 https://www.w3.org/WAI/WCAG22/Techniques/html/H33
https://www.w3.org/WAI/WCAG22/Techniques/css/C7 https://www.w3.org/WAI/WCAG22/Techniques/css/C7
However, I don’t know how well the first one is supported by screen readers.
(Edit: Updated the links from WCAG 2.0 to 2.2.)
- cluckindan 1y agoFor a more up-to-date version, see WCAG 2.2: https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-...
- layer8 1y agoThanks, I updated the links.
- amenghra 1y agoIn a similar vain to the second link, I previously wrote about using css to truncate git hashes so that search functionality continues to work: https://www.quaxio.com/truncating_hashes.html https://www.quaxio.com/truncating_hashes.html
- bevr1337 1y agoI'm particularly fond of the latter approach. There's some joy in applying hints that can be optionally read and only provide clarity. It's a great writing challenge. I did sweat localization with this approach. We use a workflow to ensure some peer review but it's an added challenge. Seemingly all good.
- joelanman 1y agoit's true, but these are more fragile than simply having clear link text, especially over time as a site is maintained