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: David Poehlman
Date: Mon, Jun 18 2007 1:48 PM

I wonder how they'd write it now a year later. I see this as relivant today
and have two requests. we need to emphasize that we are moving to something
not skipping something or bypassing something and we need to make it
visible. i ask this. when you don't use a screen reader and you tab to and
press enter on a target point that is intenal, does the user agent actually
scroll to that point?

----- Original Message -----
From: "Mike Paciello" < = EMAIL ADDRESS REMOVED = >
To: "'TEITAC Web/Software Subcommittee'"
< = EMAIL ADDRESS REMOVED = >
Sent: Wednesday, June 13, 2007 8:55 AM
Subject: Re: [teitac-websoftware] Bypassing content.



Gez Lemon co-authored an article on the topic of skip navigation that may be
helpful to the subcommittee. The article is located at the following URL:

http://accessites.org/site/2006/05/skip-link-pros-and-cons/

Regards,

Mike

Mike Paciello
Cell: +1.603.566.7713

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Katie
Haritos-Shea
Sent: Wednesday, June 13, 2007 9:33 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Bypassing content.

As far as the visual appearance of 'skip to main content' links affecting
the page real estate........

I think we all understand the hard-sell issues, but that shouldn't keep us
from requiring and defining the functionality we know is useful and
important for *all* persons with disabilities, to cover as many needs as
possible.

One could argue that sitemaps, redundant links (ie for image maps), table
captions, white space/spacing requirements, even the semantic structure
(h#), affect visual page real estate and possibly some cognitive
understanding.

Have these not been useful tools towards our goal of providing accessibility
standards? Has this not steered AT and IT development in the right
direction?

My point is that....though visual 'skip to main content' links (as one
method of meeting this requirement) can indeed be a hard sell, it should not
stop us from requiring what we know will assist users in acheiving
comparable access.

Katie Haritos-Shea


-----Original Message-----
>From: Sailesh Panchang < = EMAIL ADDRESS REMOVED = >
>Sent: Jun 12, 2007 4:54 PM
>To: 'TEITAC Web/Software Subcommittee' < = EMAIL ADDRESS REMOVED = >
>Subject: Re: [teitac-websoftware] Bypassing content.
>
>>It is also one of the very few things that directly impact visual design
>>and that is a *VERY* big barrier for implementation in many areas. I thus
>>advocate a broader definition of "mechanisms" to allow flexibility and
>>future-proofing.
>I second this without hesitation. Indeed even private sector organizations
>not covered by S508 implement invisible skip nav because it does not come
in
>the way of visual design and yet helps a section of their visitors. I agree
>that a visible link helps some users. But a visible skip nav link like a
>visible D-link has the ability to confuse many users who have no use for
>them. It is also a hard-sell to powers that be who are responsible for site
>design and need accessibility-education.
>Sailesh Panchang
>Senior Accessibility Engineer
>Deque Systems Inc. (www.deque.com)
>11130 Sunrise Valley Drive, Suite #140,
>Reston VA 20191
>Phone: 703-225-0380 (ext 105)
>E-mail: = EMAIL ADDRESS REMOVED =
>
>

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University