[Sakai Jira] Commented: (SAKIII-3837) Search result pager buttons [Prev] [1] [2] ... [Next] are not accessible

[Nicolaas Matthijs (JIRA)]

    [ https://jira.sakaiproject.org/browse/SAKIII-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136840#comment-136840 ] 

Nicolaas Matthijs commented on SAKIII-3837:
-------------------------------------------

We probably shouldn't be editing the source code of the pager widget. Instead, we should probably override the defaults somewhere inside of our API. I'll assign this JIRA to me as the i18n branch already has the perfect place to do this. I'll just pull your changes in there.

> Search result pager buttons [Prev] [1] [2] ... [Next] are not accessible
> ------------------------------------------------------------------------
>
>                 Key: SAKIII-3837
>                 URL: https://jira.sakaiproject.org/browse/SAKIII-3837
>             Project: Sakai 3 UI Dev
>          Issue Type: Bug
>          Components: Accessibility, Search
>    Affects Versions: Sprint 112, 1.1.0
>         Environment: Adaptive Technology Users
> DEBUG: Nakamura Version: 0.10-20110426-725-g35105af | UX Version: 0.6-1954-g53f4458
> DOC mod date: 08/10/2011 10:41:50 | PLACE: search#q=Parrish
>            Reporter: Brian Richwine
>            Assignee: James Sloane
>            Priority: Critical
>             Fix For: Sprint 112, 1.1.0
>
>
> The sakai_pager that appears on the bottom of a search results page which returns multiple pages of results is not keyboard accessible and does not show up to adaptive technology users as an actionable item (does not appear as a link or form control).
> Cause:
> The pgPrev, numbered, and pgNext buttons are not coded as buttons or links. Thus they don't receive keyboard focus or show up to adaptive technology users as buttons or links. They are coded only as list items. For example:
>   <li class="page-number"><span>2</span></li>
> Suggestion:
>  Code the sakai_pager's actionable elements as links (this is how Google does it) and screen-reader users will recognize the pattern since they encounter this pattern in other frequently visited places. Use CSS as necessary to maintain the desired appearance.
> For example:
>   <li class="page-number"><a href="#">2</a></li>
>  
> Converting them into links does several great things:
>   1. This is how Adaptive Technology users are used to finding similar features on major search engines (screen-reader users are sensitive to the underlying markup used -- they will know this is a list of links even though sighted users won't).
>   2. Web browsers automatically enter links into the tab index so they will become reachable by non-mouse users.
>   3. Web browsers convert keyboard activation of links and buttons into an onclick event to help make the onclick event hander on them device independent. Thus, you don't have to do it...
>   4. The links will show up in the screen-reader user's links list dialog, which they can then use first letter navigation on to easily find the "next" link allowing them quick and efficient navigation.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira