Hi John,
Do you ever find that your solution causes you page layout problems
(that is, including the uri as the link text)?
When I first encountered “web standards” folk, it was suggested to me
that including uris as link text wasn’t ideal for accessibility reasons,
because of screen readers reading them out (tedious and often
meaningless for end user – Patrick Lauke summarises this in a post to
the list back on 31 October 2005, “Re: [WSG] {WSG] What's the best way
to display links?”.
Placing the tag around descriptive text can be more meaningful
(just as placing the around "Click Here" can be meaningless).
But in the largely academic world that I work in, scholarly citation is
the key to what we do, so we see including a url in its full glory on
the page as necessary, and at present we do make it the text that is
linked. This sometimes causes me problems in the design, breaking page
layout – possibly because I am not a brilliant exponent of css -
especially when you are citing urls created by government departments
which ridiculously long.
I am aware of several workarounds, but haven’t found them satisfactory.
Cheers,
Helen
John Foliot wrote:
James Leslie wrote:
On a related note, though not involving galleries, I find a lot of
our clients want to have linked text along the lines of "Click here
for more details on product x". I have managed to fairly much insist
that we always use the entire sentence as a link to show context,
rather than just the "click here" that they tend to want being the
only linked part. The main reason I have not been able to get rid of
the "click here" part altogether though is due to an absence of a
suitable alternative that incorporates other technologies... Does
anyone have any suggestions for these circumstances?
One thing I try to encourage is to rephrase the statement to actually
present the URL as part of the "on screen" text, for example:
"...More information regarding foobar can be found at: link_uri."
1) almost everyone recognizes a structured URI as being a link, there is no
ambiguity there
2) surprisingly, some people still print out web pages, and providing the
actual uri in print benefits these people
3) making the uri the actual link text ensures that the link text is unique
for the page
4) this is technology agnostic
JF
*blah blah in uri above = title, class or id declarations as
required/desired
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
