Your accessibility score shows you at a glance how your website is doing. This guide explains how Marker.io scans your pages for accessibility, what moves your score, and what's specific to accessibility checks.

Marker.io runs its accessibility checks with axe-core, the open-source testing engine behind the accessibility audit in Google Lighthouse. It's an industry standard, so your results line up with what developers and accessibility testers already use.

On every scan, Marker.io loads each monitored page and runs every check against it.

Your accessibility score is a number from 0 to 100. It shows how your monitored pages perform against automated accessibility checks.

Marker.io tests your pages against the standard you choose in your monitor settings: WCAG 2.1 AA or WCAG 2.2 AA. If Best practices is turned on, extra checks that go beyond WCAG are included too. The standard you're scanning against is shown next to your score, for example WCAG 2.2 AA.

Your score falls into one of three levels:

The score is weighted by severity and by how often a problem repeats across your pages. For the full method, see [[How Marker.io calculates your accessibility score]].

ℹ The score is automated. It doesn't certify legal compliance or full WCAG conformance, and manual testing is still required for both.

Automated scanning finds many common accessibility issues, but not all of them. Some things need a person to judge, like whether alt text actually describes an image, or whether a page makes sense with a screen reader.

Monitoring catches common issues on every scan, so your manual testing can focus on what automation can't check.

Every check shows its Impact on score. This is the total number of points your score goes up once every issue in that check is fixed. You don't need to fix the whole check to see progress: each issue you fix raises your score a little.

Tip: the Top 10 failing checks list on your Overview is sorted by Impact on score. Start at the top to raise your score fastest.

Your score updates after every full website scan, and right away when you ignore an issue or mark a potential issue as resolved. To learn what happens after you rescan a single page, see [[How to manage checks and issues]].

Your website score covers every page you monitor. Each page score covers one page, and you'll find them on the Pages tab of the Accessibility page.

Your website score can be lower than all of your page scores. It isn't an average: a problem repeated across many pages counts more site-wide than on any single page. [[How Marker.io calculates your accessibility score]] explains why.

Marker.io runs 90 accessibility checks:

Accessibility checks have all the standard check fields, like Owner, Severity and Impact on score. See Understanding checks and issues. They also have two fields of their own:

For accessibility checks, Category is one of Images & Media, Interactive Elements, Page Structure or Code Quality. Responsibility shows the role usually best placed to fix it, like Content or Developer.

Accessibility severity levels are based on axe-core's. Here's what each one looks like in practice:

Medium and Low match axe-core's Moderate and Minor levels.

The Failing checks by severity card on the Accessibility page shows how many failing checks you have at each level. For how much each severity affects your score, see Accessibility checks and their weights

Each WCAG check also belongs to a conformance level. Level A covers the most basic requirements, and level AA builds on it. Best practice checks sit outside WCAG.

Start with your level A checks. Why? They're the foundation every other level builds on.

The Accessibility page shows your progress for A, AA, Best practices and in total. To see only one level in the checks table, use the All WCAG Levels filter.

Websites change all the time. New pages, new content and design updates can all introduce new accessibility issues, even after you've fixed everything.

Monitoring scans your pages on a schedule, so new issues show up quickly. The Scans page keeps a record of every full website scan, including new, recurring and resolved issues. Over time, this shows the work you've done to find and fix accessibility issues.

This record supports ongoing remediation. It isn't proof of legal compliance or WCAG conformance.

You can't export this history from Marker.io yet. In the meantime, all your current and historical monitoring data is available through the Marker.io MCP server, so you can build your own reports. See Create reports with the Marker.io MCP server.

Now check out how to manage your checks and issues: set owners, ignore what doesn't apply and rescan after a fix. See [[How to manage checks and issues]].

If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.