[Sakai Jira] (SAKIII-3729) No reliable means of bypassing the navigation is provided

[Gonzalo Silverio (JIRA)]

     [ https://jira.sakaiproject.org/browse/SAKIII-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gonzalo Silverio updated SAKIII-3729:
-------------------------------------

    Status: Pending Merge  (was: Open)
    
> No reliable means of bypassing the navigation is provided
> ---------------------------------------------------------
>
>                 Key: SAKIII-3729
>                 URL: https://jira.sakaiproject.org/browse/SAKIII-3729
>             Project: Sakai OAE UI Dev
>          Issue Type: Bug
>          Components: Accessibility
>    Affects Versions: 1.0.0
>         Environment: DEBUG: Nakamura Version: 0.10-20110426-725-g35105af | UX Version: 0.6-1820-g8b2a875
> DOC mod date: 07/28/2011 07:45:34 | PLACE: me
>            Reporter: Brian Richwine
>            Assignee: Gonzalo Silverio
>             Fix For: 1.5.0
>
>         Attachments: skip-link.png, skip_nav.jpg
>
>
> Since no reliable means to bypass the top navigation and to jump right to the main content, it may be difficult for people with some disabilities to reach the main content of a given Sakai OAE page quickly and easily. Screen reader users want a mechanism to avoid having to hear all heading graphics and navigation links on every page before the main content is spoken.Users who can use only the keyboard or a keyboard interface will want to reach the main content with fewer keystrokes. Otherwise, they might have to make dozens of keystrokes before reaching a link in the main content area. This can take a long time and could cause physical pain (let alone frustration) for some users. 
> Relevant Accessibility Guideline:
> WCAG 2.0 SC 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) 
> http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html
> Note that while the WCAG 2.0 Guidelines list as suitable techniques the use of headings and ARIA landmarks, page navigation by headings and landmarks is well supported only in screen-reading software which leaves out all other classes of non-mouse users. The Accessibility WG recommends including a "Skip to Main Content" link as the very first content on the page so keyboard only users can easily navigate directly to the main page content if they desire to do so.
> Frequently sites will code their "Skip Nav" link something like the following:
>   <a href="#content" class="auraltext">Skip navigation and jump directly to page content</a>
> Unfortunately, CSS is often used to hide skip to content links from sighted users. When the skip to content links are hidden, they do not help sighted keyboard only users who are not using screen reading software or equivalent technology. As a compromise between keeping the visual design free of the skip navigation links, and making them accessible to keyboard only users, CSS can be configured to hide the skip navigation links until they receive focus. An example of this technique can be found on the ATAC's Web site: http://iuadapts.indiana.edu/ (visit the page and then press the tab key until the "Skip Main Navigation" link text appears). Once a keyboard only user starts tabbing through the page, the skip navigation link will receive focus and CSS can make it become visible. An example of how to code CSS to do this follows:
> /* Hide skip to content link */
> a.skipnav, a.skipnav:hover, a.skipnav:visited  {
>    position: absolute;
>    clip: rect(1px 1px 1px 1px); /* IE6, IE7 */
>    clip: rect(1px, 1px, 1px, 1px);
>      overflow:hidden;
>    width:1px;
>    height:1px;
> }
> /* Make skip to content link visible when focused */
> a.skipnav:active, a.skipnav:focus {
>    position:static !important;
>    width:auto;
>    height:auto;
>    outline: thin dotted black;
>    color: #FFF;
> }
> To read more than you ever wanted to know on skip navigation links, visit: http://webaim.org/techniques/skipnav/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.sakaiproject.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira