Overview

Title

Implement Access Key For Actions

Duration

0 [time to delivery, in hours] (ttd = workhours * 12)

Difficulty

Unknown, Hard, Medium, Easy

Types

Documentation, Testing, Code, Translation, Training, Research, Outreach, User Interface

Tags

python,javascript,html,css,mercurial,sphinx,rst,py.test,babel,jinja2,jquery,english,artistic

Mentors

thomaswaldmann,rb_proj,waldi,esyr,pkumar_7

Count

-100 # see discussion

Description

Curently to execute wiki action on the page user have to pick it from menu. Goal would be to implement support for Access Key (keyboeard shortcuts) for all standard actions and the way to get them easy in for custom actions

Abstract

Details

Benefits

I see following benefits:

• This will speed up a lot wiki maitenance for advenced users of the wiki
• this will make wiki more accessible for blind users

Skill Requirements

Extra (optional)

Links

http://en.wikipedia.org/wiki/Access_key

Discussion

I object doing this as easy task.

If one reads that WP page linked from above, the only conclusion one can get is that it is not easy:

• there is no real standard about what hotkeys to use (except that UK gov standard that isn't that useful nor sufficient for wikis)
• there are lots of conflicts access keys vs. browser/OS/application used keys (read "is it worth it?" article linked from WP)
• there are potential i18n issues (like using "S" for save is fine for english speakers, but not for most others). but if one translates access keys, that might make things even worse (see also conflicts, plus inconsistency).

So, if we would want to do this, I need a suggestion for the mapping accesskey -> functionality first that we all can agree on and that works for most people / browsers / screen readers / platforms.