2.1.1. trying to cover two separate issues in one go?

Name: Patrick H. Lauke
Email: redux@splintered.co.uk
Affiliation: 
Document: W2
Item Number: Success Criterion 2.1.1
Part of Item: 
Comment Type: technical
Summary of Issue: 2.1.1. trying to cover two separate issues in one go?
Comment (Including rationale for any proposed change):
\"All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user\'s movement and not just the endpoints.\"



To me, these feel like two separate issues (operability and timing) mashed into one. Would it be useful to split these (which admittedly would need renumbering of the remaining 2.1 SCs)?

Proposed Change:
\"2.1.1 All functionality of the content is operable through a keyboard interface, except where the underlying function requires input that depends on the path of the user\'s movement and not just the endpoints.



2.1.2 Keyboard operation does not require specific timings for individual keystrokes



2.1.3 ...\"

Received on Friday, 29 June 2007 18:09:31 UTC