W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

RE: Recursive Links in menu bars [SEC=UNCLASSIFIED]

From: Arch, Andrew <Andrew.Arch@finance.gov.au>
Date: Mon, 17 Sep 2012 10:44:07 +1000
To: Jan Eric Hellbusch <hellbusch@2bweb.de>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <008FC8994AEE7F49BF9BA9F12852CFB568337F885B@PCW9FINMB03.mercury.network>
UNCLASSIFIED

Hi Jan,

I've always felt that this falls under Link Purpose (Success Criteria 2.4.4 & 2.4.9) in that links take you somewhere as described by the link (or it's context) and that a link that just reloads the current page fails the intent of these success criteria.

SC 2.4.4 and 2.4.9 on their Understanding pages say "The intent of this Success Criterion is to help users understand the purpose of each link so they can decide whether they want to follow the link." If you are already on a page, then why would you want to reload and start again from the top?

Cheers, Andrew
---
Andrew Arch
Australian Government Information Management Office Dept. Finance and Deregulation
p: 02 6215 1618 | w: www.finance.gov.au/agimo/

-----Original Message-----
From: Jan Eric Hellbusch [mailto:hellbusch@2bweb.de]
Sent: Monday, 17 September 2012 1:15 AM
To: w3c-wai-ig@w3.org
Subject: Recursive Links in menu bars

Hi all,

recently I had a discussion with somebody about recursive links in menu bars. We were talking about static pages and identifying the current item in the menu bar. At the simplest level we are talking about the following
alternatives: 

<ul id="nav">
<li><a href="#">page 1</a></li>
<li><a href="#"><span class="sr">Current page: </span>Page 2</a></li> ...
</ul>

Or

<ul id="nav">
<li><a href="#">Page 1</a></li>
<li><strong><span class="sr">Current page: </span>Page 2</strong></li> ...
</ul>

Considerations:

* Visual ques are expressed in CSS. The currently displayed item in the menu bar is visually highlighted with standard color settings and in contrast mode.
* It is unclear whether the current item should be a link or not.

There is now success criterion in WCAG 2.0 to clarify the question, but in the best practice technique http://www.w3.org/TR/WCAG20-TECHS/G128.html
the third example presents a possibility.

I would be interested to know how others go about the matter. Should menu items that refer to the current page be linked or not? Are there pros or cons with respect to accessibility or usability (in general), or are there other (e.g. technical) reasons?

Regards,
Jan

--
Jan Eric Hellbusch
Tel.: +49 (231) 86436760 oder +49 (163) 3369925
Web: http://2bweb.de     Twitter: www.twitter.com/2bweb
--
Das Buch über barrierefreies Webdesign:
"Barrierefreiheit verstehen und umsetzen - Webstandards für ein zugängliches und nutzbares Internet"
812 Seiten, Dpunkt Verlag (2011)
http://www.barrierefreies-webdesign.de/dpunkt/





UNCLASSIFIED
________________________________

Finance Australian Business Number (ABN):   61 970 632 495
Finance Web Site:   www.finance.gov.au

IMPORTANT:

This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. 
If you have received this transmission in error, please notify us immediately by telephone on 61-2-6215-2222 and delete all copies of this transmission together with any attachments. 
If responding to this email, please send to the appropriate person using the suffix .gov.au. 

________________________________
Received on Monday, 17 September 2012 00:44:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:30 UTC