Support Forums
ATutor Feature Requests
Access keys
You must be signed-in to post.
| Author | Subject | |
|---|---|---|
| Page: 1 | ||
| blackwidow | Subject: Access keys |  |
| The access key combination [ALT s] is currently being used, within A-Tutor as a shortcut for 'Submit' on form pages. I was under the impression that this particular key combination was already used by WindowEyes as a function that reads the status bar. Ref: www.wats.ca/articles/accesskeyconflicts/37. Consequently won't this shortcut either create a conflict for users of WindowEyes or will simply not work within the A-Tutor system for this particular sub-set of users? Posted: 2004-08-02 12:04:57 | ||
 | ||
greg | Subject: Accesskey contention | |
| Accesskeys are an unresoved area of contention among accessibility advocates. The problem is accesskeys were poorly defined in the specification to begin with and as a result have been poorly implemented in the technologies that support them. Whose to say that Windoweye gets to use the Alt-s combination, but ATutor can not. Removing the submit accesskey from ATutor would make ATutor less usable for many users because it would require AT users to navigate through entire forms inorder to get to the submit button. When making quick content edits within ATutor for instance, it's much less time consuming to author if the form submit buttons can be accessed directly rather than having to navigate to them. Used consistently throughout ATutor, the submit accesskeys can greatly improve usability.... Current talk around correcting this poor implementation problem is revolving around defining the environments in which accesskeys operate. Such as being able to switch into Web mode so accesskey function within a Web page, or browser mode so browser menu keys function, or switch to screen reading mode so the keys control screen reader functions. Posted: 2004-08-02 12:42:00 | ||
| ||
| Page: 1 | ||
You must be signed-in to post.