You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark Faine (JIRA)" <my...@incubator.apache.org> on 2005/06/07 20:06:45 UTC
[jira] Created: (MYFACES-274) Section 508 Requirement for link components that use javascript events.
Section 508 Requirement for link components that use javascript events.
-----------------------------------------------------------------------
Key: MYFACES-274
URL: http://issues.apache.org/jira/browse/MYFACES-274
Project: MyFaces
Type: Improvement
Versions: Nightly Build, 1.0.7 beta, 1.0.8 beta, 1.0.9 beta
Reporter: Mark Faine
Priority: Trivial
A corresponding redundant event handler should be added to all components that use javascript events. The event mappings are listed below.
OnClick -> OnKeyPress
OnMouseDown -> OnKeyDown
OnMouseUp -> OnKeyUp
OnMouseOver -> OnFocus
OnMouseOut -> OnBlur
OnDblClick -> OnKeyDown
OnMouseMove -> (no equivalent)
OnDragDrop -> (no equivalent)
This is a change that would help support Section 508 requirements when using Myfaces:
WCAG Priority 2 : Checkpoint 6.4/9.3 [priority 2]
Section 508 : Section 1194.22 - Paragraph L
This element uses a device-dependent event handler that does not have a redundant device-dependent event handler, as required by both the Section 508 and WCAG standards. This may be inaccessible to some users of assistive technologies who cannot trigger the event because, for example, they do not use a mouse. An event handler is a script that runs upon a specified event, such as when the mouse is clicked or is moved into a certain region of the page. Some event handlers produce purely cosmetic effects. But if an event handler results in some substantial information or function, such as displaying a pull-down menu, it is important that a redundant input mechanism be provided for this element. This is most commonly done by assigning a keyboard-based event handler for every mouse-based event handler. Further, event handlers should not rely on mouse coordinates, which prevents device-independent input. For scripts and applets, page authors should ensure that event handlers are input device-independent. For scripts, specify logical event handlers rather than device-dependent event handlers. Alternatively, page authors should remove the event handlers if they do not wish to add a redundant device-dependent one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-274) Section 508 Requirement for link components that use javascript events.
Posted by "Adam Winer (JIRA)" <my...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-274?page=comments#action_12317148 ]
Adam Winer commented on MYFACES-274:
------------------------------------
In practice, this isn't especially necessary: modern browsers fire onclick in response to an Enter onkeypress. As long as the built--in mouse-related Javascript in MyFaces sticks to onclick (and doesn't use more problematic event handlers like onmousedown), and the components in question allow tab navigation, there's no need to add an onkeypress (and doing so would introduce bugs if you just copied the onclick code).
For custom Javascript provided by the user, it's the users responsibility to ensure their Javascript matches 508 standards.
> Section 508 Requirement for link components that use javascript events.
> -----------------------------------------------------------------------
>
> Key: MYFACES-274
> URL: http://issues.apache.org/jira/browse/MYFACES-274
> Project: MyFaces
> Type: Improvement
> Versions: Nightly Build, 1.0.7 beta, 1.0.8 beta, 1.0.9 beta
> Reporter: Mark Faine
> Priority: Trivial
>
> A corresponding redundant event handler should be added to all components that use javascript events. The event mappings are listed below.
> OnClick -> OnKeyPress
> OnMouseDown -> OnKeyDown
> OnMouseUp -> OnKeyUp
> OnMouseOver -> OnFocus
> OnMouseOut -> OnBlur
> OnDblClick -> OnKeyDown
> OnMouseMove -> (no equivalent)
> OnDragDrop -> (no equivalent)
> This is a change that would help support Section 508 requirements when using Myfaces:
> WCAG Priority 2 : Checkpoint 6.4/9.3 [priority 2]
> Section 508 : Section 1194.22 - Paragraph L
> This element uses a device-dependent event handler that does not have a redundant device-dependent event handler, as required by both the Section 508 and WCAG standards. This may be inaccessible to some users of assistive technologies who cannot trigger the event because, for example, they do not use a mouse. An event handler is a script that runs upon a specified event, such as when the mouse is clicked or is moved into a certain region of the page. Some event handlers produce purely cosmetic effects. But if an event handler results in some substantial information or function, such as displaying a pull-down menu, it is important that a redundant input mechanism be provided for this element. This is most commonly done by assigning a keyboard-based event handler for every mouse-based event handler. Further, event handlers should not rely on mouse coordinates, which prevents device-independent input. For scripts and applets, page authors should ensure that event handlers are input device-independent. For scripts, specify logical event handlers rather than device-dependent event handlers. Alternatively, page authors should remove the event handlers if they do not wish to add a redundant device-dependent one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-274) Section 508 Requirement for link components that use javascript events.
Posted by "Martin Marinschek (JIRA)" <my...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-274?page=comments#action_12316903 ]
Martin Marinschek commented on MYFACES-274:
-------------------------------------------
But what if both of the event-handlers are present and they do different things?
regards,
Martin
> Section 508 Requirement for link components that use javascript events.
> -----------------------------------------------------------------------
>
> Key: MYFACES-274
> URL: http://issues.apache.org/jira/browse/MYFACES-274
> Project: MyFaces
> Type: Improvement
> Versions: Nightly Build, 1.0.7 beta, 1.0.8 beta, 1.0.9 beta
> Reporter: Mark Faine
> Priority: Trivial
>
> A corresponding redundant event handler should be added to all components that use javascript events. The event mappings are listed below.
> OnClick -> OnKeyPress
> OnMouseDown -> OnKeyDown
> OnMouseUp -> OnKeyUp
> OnMouseOver -> OnFocus
> OnMouseOut -> OnBlur
> OnDblClick -> OnKeyDown
> OnMouseMove -> (no equivalent)
> OnDragDrop -> (no equivalent)
> This is a change that would help support Section 508 requirements when using Myfaces:
> WCAG Priority 2 : Checkpoint 6.4/9.3 [priority 2]
> Section 508 : Section 1194.22 - Paragraph L
> This element uses a device-dependent event handler that does not have a redundant device-dependent event handler, as required by both the Section 508 and WCAG standards. This may be inaccessible to some users of assistive technologies who cannot trigger the event because, for example, they do not use a mouse. An event handler is a script that runs upon a specified event, such as when the mouse is clicked or is moved into a certain region of the page. Some event handlers produce purely cosmetic effects. But if an event handler results in some substantial information or function, such as displaying a pull-down menu, it is important that a redundant input mechanism be provided for this element. This is most commonly done by assigning a keyboard-based event handler for every mouse-based event handler. Further, event handlers should not rely on mouse coordinates, which prevents device-independent input. For scripts and applets, page authors should ensure that event handlers are input device-independent. For scripts, specify logical event handlers rather than device-dependent event handlers. Alternatively, page authors should remove the event handlers if they do not wish to add a redundant device-dependent one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (MYFACES-274) Section 508 Requirement for link components that use javascript events.
Posted by "sean schofield (JIRA)" <my...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-274?page=all ]
sean schofield closed MYFACES-274:
----------------------------------
Resolution: Won't Fix
Closing this based on Adam's suggestion.
> Section 508 Requirement for link components that use javascript events.
> -----------------------------------------------------------------------
>
> Key: MYFACES-274
> URL: http://issues.apache.org/jira/browse/MYFACES-274
> Project: MyFaces
> Type: Improvement
> Versions: 1.0.7 beta, 1.0.8 beta, Nightly Build, 1.0.9 beta
> Reporter: Mark Faine
> Priority: Trivial
>
> A corresponding redundant event handler should be added to all components that use javascript events. The event mappings are listed below.
> OnClick -> OnKeyPress
> OnMouseDown -> OnKeyDown
> OnMouseUp -> OnKeyUp
> OnMouseOver -> OnFocus
> OnMouseOut -> OnBlur
> OnDblClick -> OnKeyDown
> OnMouseMove -> (no equivalent)
> OnDragDrop -> (no equivalent)
> This is a change that would help support Section 508 requirements when using Myfaces:
> WCAG Priority 2 : Checkpoint 6.4/9.3 [priority 2]
> Section 508 : Section 1194.22 - Paragraph L
> This element uses a device-dependent event handler that does not have a redundant device-dependent event handler, as required by both the Section 508 and WCAG standards. This may be inaccessible to some users of assistive technologies who cannot trigger the event because, for example, they do not use a mouse. An event handler is a script that runs upon a specified event, such as when the mouse is clicked or is moved into a certain region of the page. Some event handlers produce purely cosmetic effects. But if an event handler results in some substantial information or function, such as displaying a pull-down menu, it is important that a redundant input mechanism be provided for this element. This is most commonly done by assigning a keyboard-based event handler for every mouse-based event handler. Further, event handlers should not rely on mouse coordinates, which prevents device-independent input. For scripts and applets, page authors should ensure that event handlers are input device-independent. For scripts, specify logical event handlers rather than device-dependent event handlers. Alternatively, page authors should remove the event handlers if they do not wish to add a redundant device-dependent one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira