tota11y for Chrome

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

What is tota11y for Chrome?

tota11y for Chrome is a chrome extension that aims to help assess and visualize how a website performs with assistive technologies. Originally released as a bookmarklet by Khan Academy, this extension allows you to run tota11y directly from your browser. All it does is inject the tota11y script onto the page. Developed by John-Philip Johansson and Michael Strömberg Razmgah, the project code can be accessed at GitHub.

Download

Extension stats

By: https://johansson.jp

View on Chrome Web Store

Users: 3,000+

Rating: 2.25 (4)

Version: 1.0.0 (Last updated: 2016-02-14)

Creation date: 2016-02-14

Risk impact: Very low risk impact

Risk likelihood: Low risk likelihood

Manifest version: 2

Permissions:

activeTab

Size: 35.86K

URLs: Website

Ranking

# 18266 ▲ 607

Other rankings

#4309 in Accessibility ▼ 9

Other platforms

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

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.

User reviews

Me pasa lo mismo que el comentario anterior. No funciona al pulsar el icono

Diana Saimovici, 2024-05-02

Pulso el icono de la extensión en la barra de herramientas pero no pasa nada.

Olga Carreras Montoto, 2024-03-07

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.