WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Links vs. static text URLs


From: whitneyq
Date: Jul 25, 2016 11:49AM

And I'd want to see the context. 
For example I've seen situations where the active link is on a more descriptive set of words, but the URL is provided for visibility if printed.

Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: "Patrick H. Lauke" < <EMAIL REMOVED> > Date: 7/25/16 11:02 AM (GMT-05:00) To: <EMAIL REMOVED> Subject: Re: [WebAIM] Links vs. static text URLs
On 25/07/2016 15:59, Wright, Eric [USA] wrote:
> It seems intuitive that when working with authoring tools that allow
> you to create hypertext, active links should be preferred to static
> text URLs. The text
> <p>https://www.example.com</p<https://www.example.com%3c/p>> is not
> focusable or actionable. It basically requires a user who wants to
> reference that URL to understand a string of text as a URL, and then
> copy and paste it into a browser's address bar. That said, would it
> be fair to fail such a construction under the WCAG 2.0 Parsing
> success criteria? Is there a better way to map this failure - or am I
> wrong to presume it a failure?

I'd say it's a problem that affects all users, not just those users with
potential disabilities, so not a specific WCAG failure, more of a
general usability issue.

Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke