Skip to content
Feature

Accessibility

SiteScore runs automated accessibility checks that catch common, machine-detectable issues. Automated checks cannot confirm full accessibility compliance — they are a starting point for a broader manual and user-testing process.

What this feature checks

7 checks in this category. Every check links to the source markup it inspects.

Image alt text

Missing or empty alt attributes on content images.

Landmark regions

Presence of main, nav, header, and footer landmarks.

Form labels

Inputs without an associated <label>.

Heading order

Skipped heading levels that disrupt document outline.

Skip link

Presence of a "skip to content" link for keyboard users.

Button & link text

Empty or non-descriptive interactive element text.

Contrast (proxy)

Estimated contrast for text where colors can be computed.

How the analysis works

How SiteScore inspects accessibility

A straightforward look at what happens when you run this analysis.

  1. 1

    SiteScore walks the DOM checking for common, detectable accessibility issues.

  2. 2

    Each finding includes the offending element so you can locate it in your markup.

  3. 3

    Results clearly state that automated checks do not replace manual review or user testing.

SiteScore v3.0 Side Panel InspectionLive In-Browser Audit
SiteScore Side Panel: WCAG 2.1 AA automated heuristics for alt text, form labels, and landmarks.
SiteScore Side Panel: WCAG 2.1 AA automated heuristics for alt text, form labels, and landmarks.
Example findings

What a finding looks like

Each finding includes severity, observed evidence, and a suggested fix. The data below is labeled sample data.

Form input missing label

<input type="email"> has no associated <label>.

Critical
Suggested remediation

Associate a descriptive <label> with each form control.

Honest limits

Evidence and limitations

  • Automated checks detect roughly 30–40% of accessibility issues. Manual review and testing with assistive technology remain essential.
  • Passing automated checks does not equal WCAG conformance.
Practical guidance

How to act on findings

Treat each finding as a starting point. Use the evidence panel to locate the relevant markup, apply the suggested fix, then re-run the analysis to confirm the issue is resolved.

Severity is a guide, not a rule. A warning that affects your primary content may matter more than a critical issue on a low-traffic page.

Combine SiteScore with official tools — Search Console, the Rich Results Test, and PageSpeed Insights — for a complete picture.

FAQ

Accessibility questions

Run accessibility on your page

Install the SiteScore Chrome extension and analyze the page you have open right now.