|
|-
! scope="row" style="width: 2em;" | e
| Edit this page / view source (if you are [[WP:BLOCK|blocked]] or the page is protected from editing)
| Current page tools
|-
! scope="row" | v
| Edit with [[w:VisualEditor|VisualEditor]] (if available, namespace must be: [[WP:Article|(Main)]], [[WP:File|File]], [[WP:User|User]], [[WP:Category|Category]] or [[WP:Help|Help]])
| Current page tools
|-
! scope="row" | g
| Open associated [[wikidata:|Wikidata]] item
| Current page tools
|-
! scope="row" | h
| [[Help:View history|View history]]
| Current page tools
|-
! scope="row" | j
| [[Special:Whatlinkshere|What links here]]
| Current page tools
|-
| Admin only
|}
== Accessibility of access keys ==
{{update section}}<!--see https://www.mediawiki.org/w/index.php?title=Topic:Uuzp0ij8mnzoq1t2&topic_showPostId=x475fxqhgee13yqa&fromnotif=1#flow-post-x475fxqhgee13yqa-->
{{Wikipedia:WikiProject Accessibility/Navigation menu|impaired}}
Keyboard shortcuts, in the way they are implemented on Wikipedia, are useful for some users with disabilities and do not require JavaScript to work. At the same time, they are bothersome for some screen reader users because it interferes with the shortcuts of their screen reader. The best solution would be to have customizable keyboard shortcuts.
The accessibility of keyboard shortcuts (access keys) is a complicated matter. This feature, in its current implementation, was temporarily abandoned in [[WCAG]] 2.0, notably because it conflicts with the shortcuts of assistive technologies. Usage of access keys is currently discouraged in the online contents and applications.{{update-inline}}
But presence of access keys is also an [[Authoring Tool Accessibility Guidelines]] (ATAG) requirement—the ATAG approach is particularly relevant in Wikipedia's case—where this matter is looked into thoroughly. In particular, ATAG requires the possibility to customize shortcuts. This should be requested in [[phab:T2477]].
Currently, their presence in Wikipedia's interface can be problematic for some users and can be useful for others. But more importantly, it misleads developers into thinking that the interface is keyboard accessible. Requirements that need to be fulfilled for a website to be keyboard accessible are not related to keyboard shortcuts ([http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G90 G90], [http://www.w3.org/TR/WCAG-TECHS/F42.html F42], [http://www.w3.org/TR/WCAG-TECHS/SCR35.html SCR35], [http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/F58 F58], [http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/F61 F61]).
==Known issues: Gadgets which block keyboard shortcuts==
* Gadget [[User:Cacycle/wikEd|wikEd]] blocks keyboard shortcuts on Google Chrome and Firefox.
== Disabling access keys ==
A [[MediaWiki:Gadget-removeAccessKeys.js|gadget]] exists that may be enabled to remove access key functionality. This may be opted in to using [[Special:Preferences#mw-prefsection-gadgets|Special:Preferences]]
|