tota11y for Chrome

Accessibility

Version: 1.0.0

Last Update: 2016-02-14

Overview

tota11y for Chrome is a Chrome extension developed by seriema. According to the data from Chrome web store, current version of tota11y for Chrome is 1.0.0, updated on 2016-02-14.
3,000+ users have installed this extension. 2 users have rated this extension with an average rating of .
developer website: johansson.jp

Just click the tota11y icon to run tota11y from Khan Academy and visualize how your site performs with assistive technologies.

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.

Rating

2 ratings

Total Installs

3,000+

Information

Last Update

2016-02-14

Current Version

1.0.0

Size

35.02KiB

Author

seriema

Website

johansson.jp

Category

Accessibility

tota11y for Chrome Alternatives

Name	Category	Rating Count	Installs
WAVE Evaluation Tool	Accessibility	(135)	400,000+
Colour Contrast Checker	Accessibility	(28)	20,000+
Web Disability Simulator	Accessibility	(13)	10,000+
VisBug	Developer Tools	(217)	100,000+
IBM Equal Access Accessibility Checker	Developer Tools	(11)	10,000+
Siteimprove Accessibility Checker	Accessibility	(16)	30,000+
OpenWAX	Developer Tools	(26)	20,000+
taba11y	Developer Tools	(11)	4,000+
Accessibility Insights for Web	Developer Tools	(30)	90,000+
WCAG Color contrast checker	Developer Tools	(15)	50,000+
Color Contrast Analyzer	Accessibility	(63)	70,000+
Funkify – Disability Simulator	Accessibility	(41)	20,000+
Screen Reader	Developer Tools	(1014)	200,000+
axe DevTools - Web Accessibility Testing	Accessibility	(101)	200,000+
HeadingsMap	Developer Tools	(54)	80,000+
ARC Toolkit	Accessibility	(21)	20,000+
Landmark Navigation via Keyboard or Pop-up	Accessibility	(7)	8,000+
Visual ARIA	Accessibility	(3)	2,000+
UX Check	Productivity	(78)	50,000+
A11Y HTML5 Validator	Developer Tools	(1)	437
EqualWeb Accessibility Checker	Accessibility	(16)	9,000+
Stark Accessibility Checker	Developer Tools	(24)	10,000+
Access Assistant	Accessibility	(55)	10,000+
Silktide - website accessibility simulator	Accessibility	(15)	10,000+

Latest Reviews


Eric Scoles 2021-08-30 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.
Eric Scoles 2021-08-30 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.
Eric Scoles 2021-08-30 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.
Eric Scoles 2021-08-30 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.