Accessibility
Accessibility settings are those that affect things like colors, zoom, screen reading software and keyboard navigation. Even if you do not require accessibility settings for a particular handicap, you may still find some of them useful. For this reason, I recommend going through the accessibility settings anyway.
Many of the accessibility settings are under
{
"accessibility.*": ...,
}
but not all of them. From this website you can use the Tags feature to find all settings that have the Accessibility Tag. From within VSCode, you can use the filters feature of the Settings UI to find all settings that VSCode tags as being related to Accessibility. i.e. @tag:accessibility
.
What is the “Accessible View”?
- opened with option + F2
- its primarily used to assist screen readers
- it opens up on things that have accessible views, and does nothing when triggered on things that do not have it
- it basically brings up the current context in a separate window that isolates information so that it is easier to direct accessibility tools like screen readers
- READ THIS. IT IS VERY HELPFUL!
What is the “Accessibility Help”?
- opened with option + F1
- afaik it brings up the same thing no matter the context
- it gives useful information in dealing with accessibility settings and gives tips n tricks
- i recommend bringing it up at least once and going through it to see if there is something that suits your needs
- READ THIS. IT IS VERY HELPFUL!
I am only using macOS with the default system screen reader (called “Voice Over”) to test these settings. As such, I will not go into specifics about how these settings affect screen reader behavior since you may be using a different operating system, a different screen reader, or the same operating system with the same screen reader but configured differently.