#2381: [patch] Add accesskeys to admin-site forms
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Admin interface | Version:
Severity: minor | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by ubernostrum):
I'm not sure about this; accesskeys are a good idea in theory, but in
actual practice they leave a lot to be desired. The attached patch, for
example, includes an access key (the 'a' binding for 'save and add
another') which conflicts with keyboard shortcuts in one browser (IE) and
two screen readers (JAWS and IBM Home Page Reader).
A good chart of which keys are bound to built-in functions in which user
agents is here: http://www.wats.ca/show.php?contentid=43
WATS, which produced that chart and which is a good resource on
accessibility issues, also has an article which points out problems with
accesskeys: http://www.wats.ca/show.php?contentid=32
--
Ticket URL: <http://code.djangoproject.com/ticket/2381>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
