What fresh hell is THIS now? - Patrick Lauke
[karlgroves] WCAG references links in context and links out of context.
Links in context is AA
Links out of context is AAA.
That being said, I think it is easy enough - and wise for SEO purposes - to have links make sense out of context. So, ideally, the link text (or, more accurately, the accessible name of the link) would be unique per destination.
However, if that’s not feasible, some good ways to add context is to provide wise groupings. Something like
```<h2>Foo header</h2>
<p>Foo Stuff and things <a href=”…”>Learn more</a></p>
<h2>Bar header</h2>
<p>Foo Stuff and things <a href=”…”>Learn more</a></p>
Other things provide context, too, depending on the nature of the content. Something else I’ve done is use aria-described by to add additional info ```<h2 id=”foo”>Foo heading</h2> <p>Foo Stuff and things <a href=”…” aria-describedby=”foo”>Learn More</a></p>
[stefanjudis] ```
<h2>Foo header</h2>
<p>Foo Stuff and things <a href="…">Learn more <span class="visuallyHidden">about Foo heading</span></a></p>
```
[karlgroves] @stefanjudis yeah, that visually hidden approach was the go-to before ARIA.
I agree with @jkva in that the full context being visible is the most universally usable part.
@melsumner that would only work on the link itself:
`\
<a href=”…” aria-label=”The actual stuff" >Read more</a>
The problem is, voice dictation users will expect that the link’s label is “Read More"
[karlgroves] Everyone:
https://www.access-board.gov/attachments/article/1877/ict-rule.pdf
That’s the text of the Final Rule of the Section 508 Refresh. If you do any work for the US Federal Government you should read it. There are very important and numerous changes in there from the old 508. Read the narrative stuff to read what’s been changed and why.