What is tota11y for Chrome?
tota11y for Chrome is a accessibility chrome extension. it's a free extension , it has 3,000+ active users since released its first version, it earns an average rating of 3.50 from 2 rated user, last update is 3012 days ago.
What’s new in version 1.0.0?
tota11y was just released by Khan Academy and was available as a bookmarklet. It seemed natural to create a Chrome extension. So here it is. All this does is inject the tota11y script onto the page.
See tota11y's website for information how to use it: http://khan.github.io/tota11y/
Notes:
The source code is available on https://github.com/kvasir/tota11y-chrome and was made with love by John-Philip Johansson and Michael Strömberg Razmgah.
How to install tota11y for Chrome?
You could download the latest version crx file or older version files and install it.
Preview of tota11y for Chrome
Technical Features:
- Latest Version: 1.0.0
- Requirements: Windows Chrome, Mac Chrome
- License: Free
- Latest update: Sunday, February 14th, 2016
- Author: seriema
tota11y for Chrome Available languages:
English.
FAQ
-
What about others talk about tota11y for chrome chrome extension?
100% user give 3-star rating. Read reviews of tota11y for chrome
-
How could i get help if there is something wrong with tota11y for chrome chrome extension?
You could find more help information from tota11y for chrome support page.
-
How could i contact the developer of tota11y for chrome chrome extension?
You could send emails to publisher, or check publisher's website.
-
What are the required permissions for extensions?
- activeTab
More about manifest_file of tota11y for chrome.
-
How could i report abuse of tota11y for chrome chrome extension?
You could click to report abuse of tota11y for chrome.
Reviews of tota11y for chrome:
No added value if if you're already using WAVE, AInspector, or SiteImprove Accessibility Checker. Might have value for content-creators if they're coached on which false errors to ignore & where. That said, WAVE is better for showing document structure & a bit more robust on contrast. False errors include showing error common & standard HTML such as anchor tags & misidentifying the relevant background color, which causes it to see insufficient contrast. Bottom line: Use something more current. This was a great effort in 2016 but there are better, very reputable checkers available now.