Re:Don't use "click here" as link text – W3C
by bevr1337 on Wednesday July 02, 2025 @11:44AM
(#44445139)
I'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.
Re:Don't use "click here" as link text – W3C
by joelanman on Wednesday July 02, 2025 @11:59AM
(#44445329)
it's true, but these are more fragile than simply having clear link text, especially over time as a site is maintained
Re:Don't use "click here" as link text – W3C
by cluckindan on Wednesday July 02, 2025 @09:30AM
(#44443503)
For a more up-to-date version, see WCAG 2.2:
https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-...
Re:Don't use "click here" as link text – W3C
by layer8 on Wednesday July 02, 2025 @09:40AM
(#44443623)
Thanks, I updated the links.
Re:Don't use "click here" as link text – W3C
by amenghra on Wednesday July 02, 2025 @09:52AM
(#44443741)
In 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.w3.org/WAI/WCAG22/Techniques/html/H33
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.)