SCR35
SCR35: Making actions keyboard accessible by using the onclick event of anchors
Notes on the WCAG Technique Sections
- Applicability: PLACEHOLDER
- Description: PLACEHOLDER
"The default action occurs when the user clicks the element with a mouse, but it also occurs when the user focuses the element and hits enter or space, and when the element is triggered via the accessibility API."
Enter key doesn't invoke action with Bluetooth keyboard. Press up + down arrow keys, etc.
- Examples: PLACEHOLDER
- Related: PLACEHOLDER
- Tests: PLACEHOLDER
"Check that pressing ENTER invokes the scripting action."
"If the control is an anchor element, check that pressing ENTER invokes the URI of the anchor element's href attribute."
Enter key doesn't invoke action with Bluetooth keyboard. Press up + down arrow keys, etc.
- NAME and DATE
David Todd 2/27/2014.
Question about bluetooth keyboard behavior and change requirements
David: Is the observed behavior of bluetooth keyboards common or limited to particular mobile platforms (esp. iOS)? I'm asking because tabbing to links and form elements and activating with Enter seems to work fine on a Nexus 7 (running Android 4.4.3) and Chrome. It even partly works in other more fringe scenarios such as using bluetooth kb on a Nokia 808 / Opera mini or on a Blackberry Q10 / BB Browser.
One could argue that this problem needs to be adressed by the OSs and their APIs and does not invalidate the technique - in the same way that gaps in screen reader support do not invalidates a Technique if it otherwise follows standard recommendations.
- NAME and DATE
Detlev Fischer 20 Aug 2014.