tota11y for Chrome tota11y for Chrome

Accessibility
Version: 1.0.0
Last Update: 2016-02-14

User Reviews


avatar 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.

avatar 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.

avatar 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.

avatar 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.

Related Extensions