Edit comment LC-467 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1257 Next: LC-1038

Comment LC-467: Comment Shortname:; Commenter: Csaba Gabor <csaba@alum.mit.edu>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Item Number: Make all functionality operable via a keyboard interface
Part of Item:
Comment Type: GE
Comment (Including rationale for any proposed change):
A few years back I tried to pay my Sprint account online and found that even though I could submit a payment form via an image, the payment was not accepted because the x and y coordinates which are automatically submitted with the image (and are 0 in the case of a keyboard click) were both 0. This was bad programming on their part, but the point is:

If an element has focus where a mouse click would take an action that takes the mouse location into account, then using the arrow keys at that point (or some other keyboard means) should allow the user to set the mouse position that will be used upon keyboard simulated clicking (such as using the spacebar) of the element.

This example may be too specific for this document, but I thought I'd mention it as a concrete case that really troubled me.

Csaba Gabor from Vienna

Proposed Change:; Related issues: (space separated ids); WG Notes: [TEAMA] Submitted from Team A 5/23/06 Resolved in WG telecon 5/25/06; Resolution: Thank you for your note. You will be happy to know that Guideline 2.1 and SC 2.1.1 of WCAG 2.0 require that all functionality of content be operable from the keyboard interface (unless the underlying function requires input that depends on the path of the user's movement and not just the endpoints - which yours doesn't). So the Web page you describe would not pass WCAG 2.0 even at the basic level of conformance.; (Please make sure the resolution is adapted for public consumption)