Low Vision Tips

This page has guidance for using tools for W3C work. Please add your tips and questions.

GitHub

• dark mode — and other color schemes in the appearance tab it's "Night theme" -- for good contrast, "Dark high contrast"
• additional accessible settings in the accessibility tab including keyboard shortcuts, underlined links, motion, and more.
• At the moment using browser spell check in the repository editor may crash the browser causing a loss of all work since last commit. This is not a problem with the text editor in Issues or discussions.

• Question: In GitHub Projects, there was a way to hide the content at top, so you could see more of the project data at once. I think it was a toggle top right. But now I cannot find it. (~Shawn)

Try switching to classic projects mode. However, they redesigned the header, and did a poor job of it—it may need a support ticket. Andrew Somers (talk) 13:00, 5 November 2023 (UTC)

MacOS

In accessibility in system preferences, there are many useful tools. One is "Zoom", I set to "Use scroll gesture with modifier keys to zoom" and the mod key to OPTION, then to zoom without affecting the rpage or any contents, and zoom the screen as is, put the cursor to the center of where I want to zoom, hold option, and then drag to zoom. Ideal for doing a quick soom to see something, wihtout affecting the rest of your settings.

Google tools

Google Docs

• Pageless generally works better with zoom. To set it: File > Page setup. Pageless. optionally, Set as default. OK.

Browsers

• Vivaldi browser is easy to customize, for example, make scrollbars bigger and different color. (@@SLH to add hers)

• Stylus is a browser add-on for user style sheets. (Many users quit using Stylish because of tracking and privacy issues.)