Help:Keyboard shortcuts



The MediaWiki software contains many keyboard shortcuts. You can use them to access certain features of Wikipedia more quickly.

Using access keys
An access key allows a computer user to immediately jump to a specific part of a web page via the keyboard. On Wikipedia, access keys allow you to do a lot more—protect a page, show page history, publish your changes, show preview text, and so on. See the next section for the full list.

Most web browsers require holding down one or two modifier keys to use an access key. Different web browsers invoke access keys in different ways. Please use the list below to determine the appropriate key combination for your browser and system:

Sortable list
Currently, in the a–z range, only  and   remain unassigned. ,,   are assigned to multiple functions, depending on the context.

Display access keys
By modifying your user CSS file, access key shortcuts can be displayed before internal links on any Wikipedia page.

Accessibility of access keys
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.

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 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 (G90, F42, SCR35, F58, F61).

Known issues: Gadgets which block keyboard shortcuts

 * Gadget wikEd blocks keyboard shortcuts on Google Chrome and Firefox.

User scripts that modify keyboard shortcuts
Some user scripts allow you to add more keyboard shortcuts for various actions or customize existing ones:
 * – The "U" keyboard shortcut now navigates up one subpage level.
 * – The "D" keyboard shortcut now edits the section you're hovering over.
 * – The "I" keyboard shortcut now opens the "Page information" link in your sidebar.
 * – Custom keyboard shortcuts to go to any page.
 * - The "?" keyboard shortcut now overlays a list of all keyboard shortcuts available on the current page.

Disabling access keys
A gadget exists that may be enabled to remove access key functionality. This may be opted in to using Special:Preferences