A scanner can tell you where smoke might be. It cannot tell you who owns the fire.

Tools like Siteimprove are useful. They can surface broken links, missing alt text, contrast issues, heading problems, duplicate titles, and other signals that something needs attention. But a scanner is not an accessibility program. It is not an ADA coordinator. It is not a manual tester. It is not a governance model.

Accessibility work becomes dangerous when organizations treat a dashboard as proof that users are protected.

What Scanners Do Well

Automated tools absolutely have value. They help teams:

  • Find recurring technical issues at scale
  • Identify templates causing repeated failures
  • Catch regressions after updates
  • Prioritize obvious fixes quickly
  • Measure trends over time

If you manage a large site, scanners can save enormous time. They are often the fastest way to move from chaos to a manageable backlog.

That matters.

What Scanners Cannot Do

A scanner cannot tell you:

  • Whether keyboard navigation is logical and usable
  • Whether a PDF form can be completed by a screen reader user
  • Whether captions are accurate and synchronized
  • Whether link text makes sense in context
  • Whether workflow is confusing, broken, or traps users
  • Whether staff know how to create accessible content tomorrow
  • Who is accountable when issues remain open for months

A scanner can report symptoms.

It cannot run the organization.

The Real Failure Mode

The most dangerous sentence in accessibility work is:

“We have Siteimprove.”

That often translates into:

  • No ADA coordinator
  • No ownership model
  • No manual testing plan
  • No content training
  • No document remediation process
  • No release standards
  • No one is empowered to make decisions

In other words:

The tool exists, so leadership assumes the program exists.

Those are not the same thing.

What I Learned in Practice

I recently worked through a large remediation effort under a hard deadline. The scanner was useful, it showed smoke. It helped identify patterns, track progress, and expose repeat issues.

But the actual work required people to make decisions:

  • Which issues were structural vs cosmetic
  • Which fixes had the highest user impact
  • Who owned public pages vs videos vs forms vs other systems
  • What could be remediated immediately
  • What required training or new process
  • What still needed human testing

The hardest problems were not technical.

They were ownership problems.

Accessibility Is Governance

Real accessibility programs need more than dashboards. They need:

1. Clear Ownership

Every platform should have an owner:

  • Website
  • SharePoint / intranet
  • Forms and documents
  • Video/media
  • Internal applications

If everyone owns it, no one owns it.

2. Manual Testing

Automated tools should be paired with:

  • Keyboard-only navigation checks
  • Screen reader spot testing
  • Form completion testing
  • Mobile responsiveness checks
  • Real user feedback when possible

3. Content Standards

Most accessibility debt is created one upload at a time.

Train staff on:

  • Accessible Word docs before PDF export
  • Meaningful link text
  • Heading structure
  • Alt text
  • Captions and transcripts
  • Color contrast basics

4. Cadence

Accessibility is not a one-time sprint. It needs:

  • Regular review cycles
  • New content checks
  • Issue triage
  • Ownership follow-up
  • Measured progress over time

Dashboards Can Mislead

A rising score can be good news.

But scores can also create false confidence.

A site may score well while still containing:

  • Unusable forms
  • Broken user flows
  • Inaccessible videos
  • Documents no one can complete
  • Ownership gaps that recreate problems next month

Numbers matter.

Users matter more.

Use the Tool Correctly

Use scanners as:

  • Early warning systems
  • Prioritization aids
  • Trend indicators
  • Technical debt detectors

Do not use them as:

  • Legal shields
  • Accessibility coordinators
  • Replacements for testing
  • Excuses to avoid staffing responsibility

Final Thought

A scanner can tell you where smoke might be.

It cannot tell you who owns the fire, who needs to evacuate, or whether the exits are usable.

That part still belongs to people.

Leave a Reply

Your email address will not be published. Required fields are marked *

Latest Posts