May also be worth considering the use of an alias URL that redirects the
user to the desired location on the page. They're good for referencing
URLs in non-electronic media as they're more descriptive, easier to
remember, and easier for the user to correctly type into their browser's
address bar.

For example, http://ato.gov.au/ActivityStatements as opposed to
http://ato.gov.au/businesses/pathway.asp?pc=001/003/001.

Both URLs take you to the same location.


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Chris Vickery
Sent: Wednesday, 5 November 2008 12:41
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] URL length best practices [SEC=UNCLASSIFIED]

More reasons to keep 'em short:
1. Makes it easy to quote URL (maybe over the phone) 2. I've seen a few
email or publication programs break URLs where there's a line return, so
breaks the hyperlink 3. Makes layout difficult for desktop publishers
and marketing ie.
www.chrisandhispetstore.com/what_i_keep_in_stock/supplies_for_birds/cage
s_and_ornaments/full_product_list.htm
4. If it's longer than the width of the address bar then the whole URL
is not visible.

Accessibility isn't just about clean code and text to speech readers.
It's about good IA and making everything generally better to get at.


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of silky
Sent: Wednesday, 5 November 2008 11:28 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] URL length best practices

On Wed, Nov 5, 2008 at 11:21 AM, Joe Ortenzi <[EMAIL PROTECTED]> wrote:
> other than making sense and having a strong  connection with the page 
> the content is on, there is no direct reason, other than being a bit 
> sensible about it, I wouldn't advise testing out the 2048 characters.

of course there is a good reason: so it's typable. not every url should
required to be clicked to be gotten to.

--
noon silky
http://skillsforvilla.tumblr.com/
http://www.themonkeynet.com/armada/


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************



***********************************************************************
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email in
error, we apologise for any inconvenience and request that you notify
the sender immediately and delete all copies of this email, together
with any attachments.
***********************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************


****************************************************************
                            IMPORTANT

 The information transmitted is for the use of the intended recipient only and 
may contain confidential and/or legally privileged material. Any review, 
re-transmission, disclosure dissemination or other use of, or taking of any 
action in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited and may result in severe penalties.  If you 
have received this e-mail in error please notify the Privacy Hotline of the 
Australian Taxation Office, telephone 13 28 69 and delete all copies of this 
transmission together with any attachments. 
****************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to