- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 14 Aug 2009 10:13:48 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv15513
Modified Files:
Overview.html
Log Message:
Mention that <nav> might be used by ATs. (whatwg r3620)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2809
retrieving revision 1.2810
diff -u -d -r1.2809 -r1.2810
--- Overview.html 14 Aug 2009 09:17:19 -0000 1.2809
+++ Overview.html 14 Aug 2009 10:13:44 -0000 1.2810
@@ -10884,7 +10884,12 @@
<code><a href="#the-nav-element">nav</a></code> element. In particular, it is common for footers to
have a list of links to various key parts of a site, but the
<code><a href="#the-footer-element">footer</a></code> element is more appropriate in such cases, and
- no <code><a href="#the-nav-element">nav</a></code> element is necessary for those links.<div class="example">
+ no <code><a href="#the-nav-element">nav</a></code> element is necessary for those links.<p class="note">User agents (such as screen readers) that are
+ targetted at users who can benefit from navigation information being
+ omitted in the initial rendering, or who can benefit from navigation
+ information being immediately available, can use this element as a
+ way to determine what content on the page to initially skip and/or
+ provide on request.<div class="example">
<p>In the following example, the page has several places where
links are present, but only one of those places is considered a
@@ -67410,6 +67415,7 @@
Adam Roben,
Addison Phillips,
Adele Peterson,
+ Adrian Bateman,
Adrian Sutton,
Agustín Fernández,
Ajai Tirumali,
Received on Friday, 14 August 2009 10:13:58 UTC