scan.now
Premium Scan a site

Scan a Web Page for Structural Accessibility Issues

Enter a public page. Scan.now checks its HTML language, image alternatives, form labels, button names and heading order and reports exact rule counts.

Enter the exact public page to inspect. No form is submitted and no data is modified.

A registered account is required to run this test. Finding status, evidence, affected locations and remediation are Premium-only. How active scanning works · Acceptable use

A fast structural accessibility review, not a conformance badge

Many high-impact accessibility problems are visible directly in HTML: a document with no language, informative images with no alternative, form controls with no accessible name, empty buttons and heading levels that skip unexpectedly. These are objective defects a webmaster can fix quickly.

Scan.now checks the server-rendered page for those structures and reports counts by rule. It does not run assistive technology, calculate every colour contrast, operate widgets with a keyboard or claim WCAG conformance. The purpose is to catch basic regressions and direct the next manual review.

Put this result in context

This scanner answers one part of the review. Continue with Performance Scanner for response time, html size and render-blocking scripts, then SEO Audit for crawl, titles, links, speed, structured data. These are separate checks because a strong result here does not prove that the adjacent surface is healthy.

For the background behind these signals, read Website Security: What a Vulnerability Scan Looks For and How to Fix It and What Is a Vulnerability Scan? Types, Limits and What the Results Mean. The Structural accessibility basics check reference explains the exact test, evidence and remediation used in the report. The Scan.now methodology explains request limits, scan boundaries and what the scanner deliberately does not attempt.

Language, alternatives, labels and heading order

The check is deliberately bounded to the signals below.

Coverage areaWhat the scanner examines
Document and headingsThe html language and heading-order transitions are inspected for a usable document structure.
Images and controlsMissing image alternatives, form-control names and empty button names are counted.
Server-rendered HTMLThe check evaluates the response as delivered, before client-side frameworks render later states.

Structural issues and clean HTML checks

A scan result is evidence with a boundary, not a guarantee about every route.

Structural issue found

Fix the named rule at the component level, then verify the changed experience with keyboard and screen-reader testing.

No basic issue found

The bounded rules passed on this response. Colour, focus, reading order, dynamic announcements and task completion still need review.

Count, not conformance

The score is a regression signal for these exact rules; it is not a WCAG audit, legal opinion or accessibility certification.

Clear names, text alternatives and semantic structure

Use the recommendations below to address confirmed findings and strengthen the surrounding control.

  1. Give controls durable names

    Associate visible labels with inputs and provide clear button text; use aria-label only when no visible label can exist.

  2. Write useful alternatives

    Describe the purpose of informative images and use empty alt text for images that are genuinely decorative.

  3. Preserve semantic structure

    Use one descriptive page heading followed by logical levels; do not choose heading levels for visual size.

  4. Test keyboard operation

    Every interactive control needs a visible focus state, logical order and complete operation without a pointer.

  5. Test real tasks with assistive technology

    Automated checks cannot judge language clarity, reading order or whether a workflow makes sense when announced.

How it works

  1. Enter a representative page

    Choose an important template such as the homepage, form, checkout or account screen.

  2. Structural rules are counted

    Language, alternatives, control names, button names and heading order are checked in the returned HTML.

  3. Fix components, then test people-facing tasks

    Use the result as a regression list and follow it with keyboard, screen-reader and usability review.

What this tool checks

1 checks across 1 areas. Each links to its reference page with the test, the risk and the fix.

Full reference

Page content and JavaScript

1 check

The ones that most often decide the grade:

Medium Structural accessibility basicsStructural HTML checks found missing accessible names, image alternatives, document language or skipped heading levels.

Related tools

Continue the review with four checks that cover adjacent parts of the same attack surface.

All tools
Active Security Website Performance Scanner

Response time, HTML size and render-blocking scripts
Websites SEO & Site Health Audit

Crawl, titles, links, speed, structured data
Websites Website Vulnerability Scanner

Headers, TLS, cookies, exposed files
Browsers Browser Security & Privacy Check

Fingerprint, leaks, version, policies

Guides for this tool

Background reading written to go with these results.

13 min read · Updated Sep 13, 2026 Website Security: What a Vulnerability Scan Looks For and How to Fix It

A website vulnerability scan checks the parts of a site an attacker can reach without logging in: Transport security, HTTP headers,...

Read the guide
8 min read · Updated Sep 12, 2026 What Is a Vulnerability Scan? Types, Limits and What the Results Mean

A vulnerability scan checks a system against a list of known weaknesses and reports what matches. The types of scan, the difference...

Read the guide
8 min read · Updated Sep 14, 2026 Passive vs Active Scanning: What Each Can Find and When Each Is Appropriate

Passive scanning observes normal responses; active scanning sends crafted requests to trigger flaws. The boundary, why it matters...

Read the guide
9 min read · Updated Sep 18, 2026 How to Read a Security Scan Report: Severity, False Positives and What to Fix First

A scan report is a list of findings with severities, and the hard part is deciding what matters. How severities are assigned, how to...

Read the guide

Frequently asked questions

Does a clean result mean the page is WCAG compliant?

No. It means only that this bounded set of structural rules found no issue in the returned HTML. WCAG includes many visual, behavioural and human-judgement requirements.

Can automated software judge good alt text?

It can reliably find a missing alt attribute, but deciding whether the text communicates the image's purpose requires context and human review.

Why test more than the homepage?

Templates differ. Navigation, checkout, account forms, search results and modals often use separate components and fail in different ways.

Should I use ARIA to fix everything?

Prefer native HTML semantics first. ARIA can expose names, states and relationships, but incorrect ARIA often makes an otherwise usable control worse.