WebRules

Introduction to WebRules

WebRules is the body that sets compliance standards for websites. We check whether a website meets the Americans with Disabilities Act, the payment card security standard and the accessibility laws that sit alongside them, and we publish those requirements as a single standard.

Every public website is measured against that standard. A scan checks the site, the report lists every rule it fails, and each failure carries a fine from our penalty schedule. A site is compliant only when it passes every rule.

5
Rules every site must meet
4
Laws and standards covered
3
Severity levels
1
Standard for every website

One standard, applied the same way to every site.

We write the rules

Every check in the scan is a rule we set, based on the ADA, PCI DSS and the accessibility laws alongside them, in one standard that applies to every site.

Results stand until fixed

A failed check stays failed until the problem is fixed and the site is scanned again. Rescanning is the only way to change a result.

Comply or pay

Every failed check carries a fine, set in our penalty schedule. Sites that comply owe nothing.

Four standards, five rules.

Each rule is tied to the law it comes from, so every result shows exactly which requirement a site meets or breaks.

ADA Title III compliance

Critical

Websites open to the public must be accessible to people with disabilities under the Americans with Disabilities Act, and their compliance must be on record.

ADA Title III · 28 CFR Part 36

PCI DSS compliance

Critical

Sites that take card payments must meet the Payment Card Industry Data Security Standard, and their Attestation of Compliance must be on record.

PCI DSS v4.0 · Attestation of Compliance

Section 508

Critical

Sites used by or for US federal agencies must meet the Section 508 accessibility standards.

36 CFR Part 1194

European Accessibility Act

Serious

Sites selling products or services to customers in the EU must meet the European Accessibility Act.

Directive (EU) 2019/882 · EN 301 549

Accessibility statement

Moderate

Every site must publish an accessibility statement that explains its accessibility and how to report a problem.

EAA Annex V · ADA Title III guidance

From scan to compliant in four steps.

  1. 1

    Scan

    The site is loaded in a real browser on desktop and mobile, and every rule is checked.

  2. 2

    Report

    Every failed rule is listed with where the problem is, how serious it is and the reference it breaks.

  3. 3

    Fines

    Each failed rule carries a fine. The fine estimate adds them up, item by item.

  4. 4

    Fix and rescan

    Once problems are fixed, a new scan updates the result. Fixed rules no longer carry a fine.

Not every failure is equal.

Each rule has a severity, and the fine follows it. Amounts are in the penalty schedule.

Critical

Breaks a core legal requirement

The site does not meet a law that applies to it, such as ADA Title III.

Serious

Breaks a regional requirement

The site does not meet a law in some of the places it serves, such as the EU.

Moderate

Missing a required notice

The site meets the law but leaves out something it must publish, such as an accessibility statement.

Every public website.

If the public can visit a website, it is held to the standard. Size, country, platform and industry make no difference.

Businesses and online stores

From a single landing page to a full catalogue with checkout.

Public sector

Government, councils, agencies and public services.

Schools and nonprofits

Education, charities, clubs and community groups.

Personal sites

Portfolios, blogs and personal pages.

Frequently asked questions

What happens if my site fails?

The site is not compliant. The report lists every failed rule, and each one carries the fine set in the penalty schedule. The fine estimate shows the total for your site.

How are fines calculated?

One fine per failed rule. The amount depends on the rule and its severity. Passed rules cost nothing, so a site that passes every rule owes $0.

Can a result be challenged?

A result stands until the site changes. Fix the problems and scan again; the new scan replaces the old result.

How often should a site be scanned?

After every significant change to the site, and at least once a quarter.

Does a subdomain count as a separate site?

Subdomains are measured against the same rules as the main site.

What does a scan check?

ADA Title III compliance, PCI DSS compliance, Section 508, the European Accessibility Act and whether the site publishes an accessibility statement.

Find out where your site stands.

Scan it against every rule and get the full report.

Scan a website