WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: "read more" links

for

From: Ryan E. Benson
Date: Mar 29, 2012 7:00PM

> One option is to simply remove the link and have a preceding heading
> be a link to the expanded content. Most users understand this
> convention. Another option is to add off-screen, explanatory text to
> the "Read more" link for screen reader users.

I saw a post somewhere yesterday that does just that. They wrap the
post title or wording that provides more context in a span tag then
throw it offscreen. Since the span is still in the anchor, it should
still grab all of the words if you pull up a link list.

--
Ryan E. Benson



On Thu, Mar 29, 2012 at 7:04 PM, Jared Smith < <EMAIL REMOVED> > wrote:
> Ambiguous links are problematic for all users. Everyone must scan
> before or after the link to determine its function. This is typically
> more difficult for screen reader users.
>
> WCAG 2.0 allows ambiguous links as long as the purpose of the link can
> be found in the link's context. There is a Level AAA requirement that
> all links must make sense all by themselves.
>
> With all this said, if a "Read more" link is necessary and adding more
> descriptive text to that link would be clearly repetitive to nearby
> text, this could actually decrease it's accessibility for most users.
> One option is to simply remove the link and have a preceding heading
> be a link to the expanded content. Most users understand this
> convention. Another option is to add off-screen, explanatory text to
> the "Read more" link for screen reader users.
>
> Jared Smith
> WebAIM.org
> > >