This page is deprecated. Redirecting to https://developer.android.com/studio/intro/accessibility.html This document contains information on how to use the accessibility features of Android Studio (version 2.2 and later), as well a provide recommendations to improve usability for accessibility users. Using the keyboardAndroid Studio has been optimized so that the keyboard can be used to navigate through all controls as well as for activating features. Android Studio shares many common keyboard shortcuts with IntelliJ -- a frequently used list of shortcuts can be found at https://www.jetbrains.com/idea/help/keyboard-shortcuts-you-cannot-miss.html. However, there are currently still many UI elements that can only be activated using the object navigation (or similar) feature of your screen reader. For help with object navigation or equivalent, consult your screen reader documentation, for example http://www.nvaccess.org/files/nvda/documentation/userGuide.html#toc33 for nvda. Activating the main (top-level) menu
Navigating between Files and Tool Windows
Navigation Bar
Another useful tool to navigate between files of the project is to use the Navigation Bar, which is activated with Alt-Home. Press left/right to switch between various item in the navigation hierarchy Press space to show a popup of the various entries of the current navigation hierarchy item Code foldingBy default, the Android Studio editor “folds” part of the text into expandable regions. For example, the list of “import” at the beginning of a Java source file is folded into a single line containing the text “import …”. This can make navigation confusing for accessibility users. To disable all code folding options, go to the “Editor > General > Code Folding” page of the "File | Settings" dialog. Auto insertion featuresBy default, Android Studio automatically insert closing curly braces, quotes, or parentheses, which can be confusing for accessibility users. You can disable this behavior (and others) in the “Editor > General > Code Completion” page of the "File | Settings" dialog. Similarly, you can disable the autopopup of “Code Completion” in the “Editor > General > Smart Keys” page of the "File | Settings" dialog. Accessing errors, warnings and code inspectionsReviewing all errors of all files in a projectAndroid Studio does not have a tool window dedicated to showing all errors & warnings of all files in the current project. However, when using the “Build | Make Project” action, all warning errors are written to the “Messages” tool window.
Note: The “Message” tool window is accessible as of Android Studio Preview 5 (see bug https://code.google.com/p/android/issues/detail?id=198013). Reviewing errors (and code inspections) in a single file opened in the editor
IndentationBy default, Android Studio uses the space character for indentation. This can be changed to the tab character in the “Editor > Code Style > Java” page of the "File | Settings" dialog. The “Tabs and Indents” tab page contains a “Use tab character” checkbox. Using the layout editorThe layout editor of Android Studio is currently not fully accessible (see bug https://code.google.com/p/android/issues/detail?id=199182). A temporary workaround would be to open layout files in text mode by default. See bug https://code.google.com/p/android/issues/detail?id=199181. As a workaround, change the Layout Editor options to check “Prefer XML Editor”. For example, this can be done using Object Navigation of NVDA:
|
Technical docs > Accessibility >