Skip to main content

How Accessibility Scoring Works

Understand how ObservePoint calculates and interprets accessibility scores to measure your website's compliance with WCAG standards.

Written by Luiza Gircoveanu

Overview

ObservePoint's Accessibility Scoring system provides a quantitative measure of your website's accessibility health. The Accessibility Score is calculated as a percentage from 0 to 100, reflecting the proportion of potential accessibility issues actually found on your pages. This metric helps you understand at a glance how well your site meets Web Content Accessibility Guidelines (WCAG) standards.

The score uses a weighted formula that accounts for both the severity and frequency of rule violations, giving you meaningful insights into where to prioritize remediation efforts.

The Scoring Formula

The Accessibility Score is calculated using the following formula:

Accessibility Score = 100 × (1 - actual penalties / maximum possible penalties)

This approach ensures that the score reflects:

  • Severity of issues - Critical issues have greater impact than minor ones

  • Frequency of issues - Issues that appear on multiple elements are weighted more heavily

  • Scope of testing - The score is normalized by the total number of elements checked

A higher score indicates fewer or less severe accessibility issues were found relative to what was tested.

Severity Levels and Penalty Weighting

Each rule violation contributes a penalty based on its severity level. ObservePoint uses a weighted penalty system to reflect the impact on users:

Severity Level

Penalty Weight

Definition

Minor

1

Small impact on usability; minor inconveniences or deviations from best practices without significantly hindering access.

Moderate

3

Noticeable challenges that can be overcome with some effort; impacts usability but doesn't completely block access.

Serious

5

Significantly impacts usability, causing considerable inconvenience or difficulty without completely blocking access.

Critical

8

Significantly hinders or completely blocks the ability of people with disabilities to access and use web content.

How Penalties Are Calculated:

For each rule violation:

  1. Identify the severity of the rule (1, 3, 5, or 8)

  2. Count the frequency of failures across all elements checked

  3. Calculate the penalty = severity weight × frequency

  4. Sum all penalties to get the total actual penalties

  5. Compare to maximum possible penalties if all checks had failed

Example: If a page checks 100 form fields and 20 are missing labels (critical issue, weight = 8):

  • Actual penalty = 8 × 20 = 160

  • Maximum possible penalty = 8 × 100 = 800

  • Score contribution = 160 / 800 = 20% penalty

  • Accessibility Score = 100 × (1 - 0.20) = 80

WCAG Versions and Conformance Levels

ObservePoint provides pre-calculated scores for multiple WCAG standards, allowing you to assess your accessibility across different regulatory and organizational requirements.

Supported WCAG Standards

ObservePoint supports all levels of conformance with the following WCAG versions:

  • WCAG 2.0 (Level A, AA, AAA)

  • WCAG 2.1 (Level A, AA, AAA)

  • WCAG 2.2 (Level A, AA, AAA)

Conformance Levels Explained

  • Level A — Basic accessibility support; foundational requirements

  • Level AA — Enhanced accessibility; the standard most organizations adopt for legal compliance

  • Level AAA — Advanced accessibility; the highest level of accessibility support

Note: Conformance at higher levels indicates conformance at lower levels. For example, a page that conforms to WCAG 2.1 AA meets both the A and AA requirements.

Interpreting Your Score

Your Accessibility Score serves as a high-level indicator of accessibility health, but interpretation should be context-dependent:

Score Range

Assessment

Recommendation

90–100

Excellent

Few or minor accessibility issues; maintain current practices.

75–89

Good

Some issues exist; prioritize critical and serious items.

50–74

Fair

Significant work needed; create a remediation roadmap.

Below 50

Poor

Urgent attention required; address critical issues first.

Using Scores in Account-Wide Reports

ObservePoint pre-calculates Accessibility Scores for your entire account across all supported WCAG versions and conformance levels. This allows you to:

  • Choose your standard — Select the WCAG version (2.0, 2.1, or 2.2) that aligns with your legal or organizational requirements

  • Choose your conformance level — Opt for Level A, AA, or AAA based on your accessibility goals

  • View multiple perspectives — Compare your site's performance under different standards to understand where additional work is needed

  • Customize your focus — Create filtered reports showing scores by domain, page type, or location

For example, your site might score 85 for WCAG 2.1 AA but 65 for WCAG 2.1 AAA. This tells you that you've addressed most AA-level requirements but would need additional remediation for advanced AAA standards.

The results can be found in the Page Details Report, in the Accessibility Tab. Also, in the Reports Gallery, there are several templates dedicated to Accessibility Issues; use the templates on your Audits to validate and understand results.

Key Takeways

  • Accessibility Score combines severity and frequency of issues into a single percentage (0–100)

  • Severity weighting ensures critical issues have proportionally greater impact

  • Scores are pre-calculated across multiple WCAG versions and conformance levels

  • Use your score to track progress over time and prioritize remediation efforts

  • Higher scores reflect fewer or less severe accessibility barriers for users with disabilities

Conclusion

ObservePoint's Accessibility Score distills complex compliance data into a clear metric for tracking progress and prioritizing fixes. By weighting violations by severity and frequency, the score helps you focus remediation efforts where they matter most, which is on issues that genuinely impact users with disabilities.

Use your score as a baseline, monitor it over time, and complement automated testing with manual and usability testing to build a truly accessible experience.

Did this answer your question?