Saved

Press the star next to a tool's name to save it.

All my tools

Accessibility

Last updated

We want everyone to be able to use ToolsRuby, including people who use a screen reader, a keyboard, voice control or zoom. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

What we do

  • Inputs have labels, and buttons and links can be reached and used with a keyboard, with a visible focus outline.
  • Each page starts with a “Skip to content” link, and uses headings in order, so you can move around with a screen reader.
  • Results are written out as text, not only shown in a chart or a picture.
  • Pages are designed for small screens first, text can be enlarged with your browser’s zoom, and buttons are sized to be easy to tap.
  • You can switch between a light and a dark theme with the button in the header.
  • We don’t use time limits, except in tools that measure speed on purpose, such as a typing or reaction-time test.

Known limits

  • Speed and reaction tests, and some games, depend on quick pointer or keyboard input, so they may be hard to use with some assistive technology.
  • Some image and PDF tools show a picture preview. The settings and results around the preview are text, but the preview itself can’t be read by a screen reader.
  • Files that some tools make, such as label sheets, flyers and image conversions, are pictures. A PDF made this way doesn’t contain text that a screen reader can read.
  • Ads are supplied by Google and its partners. We don’t control their content, and some may not meet these guidelines.

We keep working on these limits.

Report a barrier

If something on the site is hard or impossible for you to use, please tell us. Email service@toolsruby.com with “Accessibility” in the subject, the page’s address and what went wrong, or use our Report a problem page. If you can, tell us which browser and assistive technology you use.