[WG: Accessibility] [Sakai Jira] Commented: (SAM-1228) Accessibility: Remove onkeypress handlers from links and form controls

Richwine, Brian L brichwin at indiana.edu
Sat Jul 30 12:52:33 PDT 2011


We’ve submitted patches for the following SAMigo accessibility JIRAs. Mary Stores, in the Accessibility Working Group has tested the patches with the JAWS screen-reader using our local development server. We believe fixes to these issues would greatly improve the accessibility of Test and Quizzes. Please let us know if there is anything we can do to help get these resolved.

SAM-1295<https://jira.sakaiproject.org/browse/SAM-1295> - Multiple Choice Questions in Samigo Are Not Very Accessible

SAM-1228<https://jira.sakaiproject.org/browse/SAM-1228> (w/subtasks) - Remove onkeypress handlers from links and form controls

SAM-1279<https://jira.sakaiproject.org/browse/SAM-1279> - Hide Division Feature Is Not Accessible

SAM-1232<https://jira.sakaiproject.org/browse/SAM-1232> - Many Question Types Marked-Up Entirely As a Level 5 Heading

SAM-1231<https://jira.sakaiproject.org/browse/SAM-1231> - Tabbing off of the "What's This?" link generates a HTTP Status 404 Error Message to appear (would be resolved by applying patches in SAM-1228)

SAM-1229<https://jira.sakaiproject.org/browse/SAM-1229> - Username and Password Input fields not labeled on Begin Assessment Page


  Brian Richwine

  Sakai Accessibility Working Group

-----Original Message-----
From: Karen Tsao (JIRA) [mailto:bugs-admin at sakaiproject.org]
Sent: Wednesday, July 06, 2011 7:37 PM
To: Richwine, Brian L
Subject: [Sakai Jira] Commented: (SAM-1228) Accessibility: Remove onkeypress handlers from links and form controls

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

Karen Tsao commented on SAM-1228:


Hi Sam,

Thanks a lot for offering helps. This is actually is on my work list. I will start to work on all the accessibility issues after I am done with my current local tasks. However, it will be great if you can help me to test it once I am done.


> Accessibility: Remove onkeypress handlers from links and form controls

> ----------------------------------------------------------------------


>                 Key: SAM-1228

>                 URL: https://jira.sakaiproject.org/browse/SAM-1228

>             Project: Samigo

>          Issue Type: Bug

>          Components: Tests & Quizzes (Samigo)

>    Affects Versions: 2.7.2, 2.8.0

>         Environment: Non-mouse users (keyboard only and other adaptive technology users), screen-reader users

>            Reporter: Brian Richwine

>            Assignee: SAMIGO TEAM

>            Priority: Critical


> The onclick event handler is triggered when the mouse is pressed when over an HTML element. At first glance, it appears that onclick is a device dependent event handler and that its use alone would be an accessibility problem. However, that is not always the case and here lies the problem.

> onclick is intended to be a mouse dependent event handler. However, if the onclick event handler is used with hypertext links or form controls, then most major browsers and assistive technologies trigger onclick if the Enter key or Space bar are pressed when the link or control has focus. In these cases, onclick is a device independent event handler. If an onkeypress hander is also used on these controls, then a problem occurs due to the redundancy created by both event handlers firing when the Enter key or Space bar are pressed.

> (Note/FYI: the Enter key will not trigger the onClick event if it is

> used with non-link and non-control elements, such as div, span, table cells, etc.) In the Samigo tool, there are many links and form controls that have both an onclick event handler and an onkeypress event handler. This cause many problems for non-mouse users attempting to use the tool. Please watch the following videos for a demo of just a couple of the problems it causes in Tests and Quizzes:

> Demonstration of effect on buttons: http://screencast.com/t/KwnYrVCK

> Demonstration of effect on links: http://screencast.com/t/QRPKJI1v4

> How you reproduce this:

>  Disconnect the mouse and try to navigate with the keyboard. Assuming that you know how interact with a website using keyboard only navigation, this simple test will very quickly show if it is possible to navigate or interact a feature using an input device other than the mouse. Be especially sure to test interactive features like forms, drop-down menus, expand/contract menus, etc.

> Suggestions:

>   1) Simply remove the redundant onkeypress handler from links and form controls.

>   2) Where onkeypress handlers are required, do not use onkeypress handlers that carry out actions without first testing which key was actually pressed. For instance, make sure only the appropriate keys activate an action (typically the enter and/or space keys). Typically it is inappropriate to let standard navigation keys (like tab, shift+tab, F6, shift+F6, any of the arrow keys (or their modified forms), the escape key, etc.) activate a "control".



This message is automatically generated by JIRA.


For more information on JIRA, see: http://www.atlassian.com/software/jira

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20110730/ffb9e0da/attachment.html 

More information about the accessibility mailing list