Thread Subject: Re: Bypassing content.
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Peter Wallack
Date: Mon, Jun 18 2007 1:47 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Tom Brett: "Re: Bypassing content."
- Previous message in thread: David Poehlman: "Re: Bypassing content."
- Messages sorted by: Author | Thread | Date
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I'd buy that! <br>
<pre class="moz-signature" cols="72">Peter Wallack
Accessibility Program Director
Oracle Corporation</pre>
<br>
<br>
David Poehlman wrote:
<blockquote cite="mid:003801c7ad47$c5b97f20$0901a8c0@HANDS" type="cite">
<pre wrap="">I almost like this but would change it slightly thus:
Web pages shall provide a visible method that is programmatically
determinable to provide a means for navigation among blocks of content.
----- Original Message -----
From: "Hoffman, Allen" <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">< = EMAIL ADDRESS REMOVED = ></a>
To: "TEITAC Web/Software Subcommittee" <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">< = EMAIL ADDRESS REMOVED = ></a>
Sent: Tuesday, June 12, 2007 4:34 PM
Subject: Re: [teitac-websoftware] Bypassing content.
The problem with skip-nav as is is that it is difficult to test in an
automated fashion as unless a consistent text is used, automated tools
have a hard time evaluating the tab order and functionality of the page
to shorten it effectively.
So:
how about:
Web pages shall provide a visible method that is programmatically
determinable to skip repetitive navigation and blocks of content.
Sufficient techniques may include:
use of anchor tags in HTML.
example should be inserted.
Use of scripting to make links visible when tabbed to.
example...
Use of tables of contents in non-HTML formats.
example...
use of scripting to appropriate direct focus dependent upon inputs.
example... yeah right.
use of consistent content block mark up such has headers.
example...
Allen Hoffman -- <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>; v: 202-447-0303
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
[<a class="moz-txt-link-freetext" href="mailto: = EMAIL ADDRESS REMOVED = ">mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of
Barrett, Don
Sent: Tuesday, June 12, 2007 4:17 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Bypassing content.
We have accepted frames, headings, and skip nav links as methods of
meeting the standard. All the standard has required is a method to skip
repetitive nav links; it's been very generic and very helpful.
Don Barrett
Section 508 Coordinator
U.S. Department of Education
(202)-205-8245
<a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
[<a class="moz-txt-link-freetext" href="mailto: = EMAIL ADDRESS REMOVED = ">mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of Andrew
Kirkpatrick
Sent: Tuesday, June 12, 2007 4:12 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Bypassing content.
The skip nav link offers very poor control - you get one option and that
is to move focus to where the link is and nowhere else.
AWK
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
[<a class="moz-txt-link-freetext" href="mailto: = EMAIL ADDRESS REMOVED = ">mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of
Hoffman, Allen
Sent: Tuesday, June 12, 2007 4:08 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Bypassing content.
I concur with Andrew, but.
The skip-nav requirement is intended to allow the end-user more
control of directing the focus. if an application allows focus to be
moved without inefficient keyboard or other driving, then it meets the
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">standard already.
Allen Hoffman -- <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>; v: 202-447-0303
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
[<a class="moz-txt-link-freetext" href="mailto: = EMAIL ADDRESS REMOVED = ">mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of
Andrew Kirkpatrick
Sent: Tuesday, June 12, 2007 3:48 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Bypassing content.
Exactly. The concept of the skip link is a possible success
technique, but we should not skew the requirement to eliminate other
success techniques that people are able to use presently.
AWK
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
[<a class="moz-txt-link-freetext" href="mailto: = EMAIL ADDRESS REMOVED = ">mailto: = EMAIL ADDRESS REMOVED = </a>] On
</pre>
</blockquote>
<pre wrap="">Behalf Of David
</pre>
<blockquote type="cite">
<pre wrap="">Poehlman
Sent: Tuesday, June 12, 2007 3:45 PM
To: TEITAC Web/Software Subcommittee; Katie Haritos-Shea
Subject: Re: [teitac-websoftware] Bypassing content.
I just know there is already methodology for dealing with
</pre>
</blockquote>
<pre wrap="">this without
</pre>
<blockquote type="cite">
<pre wrap="">using a special link though.
----- Original Message -----
From: "Peter Wallack" <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">< = EMAIL ADDRESS REMOVED = ></a>
To: "Katie Haritos-Shea" <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">< = EMAIL ADDRESS REMOVED = ></a>; "TEITAC
</pre>
</blockquote>
<pre wrap="">Web/Software
</pre>
<blockquote type="cite">
<pre wrap="">Subcommittee" <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">< = EMAIL ADDRESS REMOVED = ></a>
Sent: Tuesday, June 12, 2007 11:52 AM
Subject: Re: [teitac-websoftware] Bypassing content.
I'd argue that it's useful far beyond that. Any keyboard-only user,
such as a 'power user', would appreciate the feature. I believe it
needs to be visible until User Agents provide a standard
</pre>
</blockquote>
<pre wrap="">mechanism to
</pre>
<blockquote type="cite">
<pre wrap="">invoke it.
Peter Wallack
Accessibility Program Director
Oracle Corporation
Katie Haritos-Shea wrote:
Mike,
The visible skip nav is also useful for persons with
</pre>
</blockquote>
<pre wrap="">limited mobility,
</pre>
<blockquote type="cite">
<pre wrap="">and the AT that they use. In that case the skip nav link must be
visible.
Katie
-----Original Message-----
From: "Langum, Michael J" <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">< = EMAIL ADDRESS REMOVED = ></a>
Sent: Jun 12, 2007 8:21 AM
To: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
Subject: Re: [teitac-websoftware] Bypassing content.
AWK wrote:
"An invisible skip link wouldn't satisfy the Functional
</pre>
</blockquote>
<pre wrap="">perfomance
</pre>
<blockquote type="cite">
<pre wrap=""> criteria,. . ."
Have I missed something?
I thought the "function" of the "skip link" was to allow
</pre>
</blockquote>
<pre wrap="">users of AT
</pre>
<blockquote type="cite">
<pre wrap="">to skip past banners, and standard navigation elements so that they
could quickly and easily get to the main content of a page. Since
sighted users can achieve the same "function" by simply
</pre>
</blockquote>
<pre wrap="">examining the
</pre>
<blockquote type="cite">
<pre wrap="">page and choosing to begin reading at whatever point they wish (and
hence don't rely on the "skip link"), I don't see how an "invisible
skip link wouldn't satisfy the Functional performance criteria."
-- Mike Langum
Asst. Webmaster, <a class="moz-txt-link-abbreviated" href="http://WWW.OPM.GOV">WWW.OPM.GOV</a>
U.S. Office of Personnel Management
- Next message in Thread: Tom Brett: "Re: Bypassing content."
- Previous message in Thread: David Poehlman: "Re: Bypassing content."
WebAIM is an initiative of:
