Skip to content
Selma

Monitoring

Your whole site, reviewed on an ongoing basis

Monitoring reviews your whole domain against WCAG 2.2 AA, every month and whenever you need it. You see how the site is doing in one view, which issues to fix first and exactly what developers need to do, with technical evidence and a commit-ready code fix for every issue.

Monitoring in brief

  • The whole domain

    Up to 1,000 pages are scanned every month, and after a release you can scan straight away.

  • WCAG 2.2 AA

    Every issue is linked to WCAG 2.2 and to the European standard EN 301 549.

  • Code fix

    Every issue comes with technical evidence and a commit-ready code fix to put into the source code.

  • Made in Europe

    Selma is a Swedish company. Monitoring is developed in Sweden, with support from our team there.

Three steps

How it works

  1. Review

    Every month Selma goes through your whole domain and groups the issues by component and template, so the same issue does not show up a hundred times.

  2. Fix

    Developers get technical evidence and a commit-ready code fix for every issue, in the tool, in a requirements package for your agency or straight in their AI editor.

  3. Maintain

    When an issue is fixed, Selma checks it with a new scan. The history, the reports and the accessibility statement show what has been done.

The tool

What the tool looks like

The pictures show the tool, in Swedish, with example data for a made-up domain, exempel.se.

Overview

See how the whole site is doing

The overview brings the whole domain together in one view: a score for the site, how it has developed, what to deal with first and how much of the month's credits is left.

  • The score is weighted by severity. As long as one critical issue is left, the site is never approved.
  • Recommended next steps show which fixes have the most effect.
  • The month-by-month curve shows that the work is paying off.
The overview in Monitoring for exempel.se: a site score of 71 out of 100, not approved with two critical issues left, 38 unique issues, 3,200 of 5,000 credits left in October, active connections for MCP, the API, the accessibility statement and the supervision mode, a curve of the score month by month and four recommended next steps.
The overview for one domain. Example data. View the picture at full size (opens in a new tab)

Issues

You can see which issues are verified

Issues that Selma's experts have reviewed are marked Verified by Selma, so developers know an issue is real before they spend time on it.

  • Ask Selma to review an issue you are unsure about. The Expert support add-on includes ten expert questions a month.
  • Issues are grouped by component and template, so the same issue does not show up a hundred times.
  • Filter by severity, section and WCAG rule.
The issue list with eight issues grouped by component and template. Each row shows the severity, the WCAG criterion, the number of pages, the confidence level and the status, for example with the agency.
The issue list, grouped by component and template. Example data. View the picture at full size (opens in a new tab)

False positives

A false positive is marked once

If an issue is not a real issue, you mark it with a reason. The assessment is saved, and the issue does not show up in later reviews as long as the code stays the same.

  • Choose a reason, and whether the assessment covers one element or every occurrence.
  • Ask a Selma expert to confirm the assessment.
  • Hidden issues stay in the remediation report, with the reason and the date.
The dialog for marking a false positive, with a reason, a scope, an explanation and the choice to hide the issue in later reviews.
The dialog for marking a false positive. Example data. View the picture at full size (opens in a new tab)

For developers

Evidence your developers can use straight away

Every issue comes with the technical evidence needed to understand and fix it, without the developer having to reproduce it first.

  • Selector, role and computed accessible name.
  • ARIA states, the DOM state during the test and what the screen reader reads out.
  • A commit-ready code fix to put into the source code.
A critical issue, carousel buttons with no accessible name, with technical evidence: selector, role, computed accessible name, name source, focus, ARIA states and what the screen reader says.
An issue with technical evidence. Example data. View the picture at full size (opens in a new tab)

Agency

Give your agency clear requirements

Put the issues in a requirements package with a deadline and send it to your web agency. The agency gets its own link with the evidence, the code fixes and what counts as done.

  • The agency only sees the requirements package, not the rest of the tool.
  • An issue only counts as done once Selma's new scan confirms it.
  • You follow the delivery issue by issue.
A form for a new requirements package for a web agency, with the recipient, a deadline, the chosen issues and what it takes for an issue to count as done.
A requirements package for a web agency. Example data. View the picture at full size (opens in a new tab)

Example

What an issue looks like for a developer

This is the issue from the picture under For developers, now as text. This is how much evidence the developer gets for every issue.

CriticalVerified by SelmaWCAG 4.1.2 Name, Role, Value

Carousel buttons have no accessible name

The Back and Next buttons in the carousel have no name a screen reader can read out.

Technical evidence

Selector
section.hero-carousel > button.carousel__prev
Role
button
Computed accessible name
Empty – the button has no name
The screen reader says
“button” (expected: “Back, button”)
Found on
86 pages, 172 elements

Commit-ready code fix

- <button class="carousel__prev" type="button">
+ <button class="carousel__prev" type="button"
+   aria-label="Back" aria-controls="hero-slides">
- <button class="carousel__next" type="button">
+ <button class="carousel__next" type="button"
+   aria-label="Next" aria-controls="hero-slides">

The buttons get the names “Back” and “Next”. Because the carousel is a shared component, the same change closes the issue on all 86 pages.

For developers

Connected to developers' tools

Issues and code fixes go where developers already work.

  • MCP for AI editors

    Connect Claude Code, Cursor or GitHub Copilot to Selma. The AI assistant fetches the issues and suggests the fix in the right file.

  • API

    Fetch issues, scores and reports into your own systems.

  • AI-suggested alt text

    AI suggests descriptions of the images right in the tool, so you can review them and add them to the site.

  • Recommended next steps

    After every scan, the tool suggests what to deal with first.

Package

One package for the whole site

Monitoring is one package, and everything in the three steps is included. If you need more domains, more users or help from experts, you add it.

Monitoring

1 domain · up to 1,000 pages · 3 users

For a website that should be reviewed and followed up on an ongoing basis, with a code fix for every issue and a record of what has been done.

The package includes 5,000 credits a month for scans on demand, more frequent scans and calls through the API and MCP.

Review

  • Scans on demand, for example after a release
  • Overview with score, trend and latest scan
  • Technical evidence for every issue
  • Score weighted by severity
  • Inventory of the site's PDFs
  • A kick-off meeting where we set up the domain, pages, schedule and users

Fix

  • Issues by component and template
  • A commit-ready code fix for every issue
  • AI-suggested alt text
  • Recommended next steps
  • Mark false positives
  • Requirements packages for your agency
  • MCP for AI editors
  • API

Maintain

  • A scheduled scan of the whole domain every month
  • History per page
  • Reports and export
  • AI summary of the reports in plain language
  • An accessibility statement that is updated after every scan
  • A supervision mode for the private or public sector

Add-ons

Extend the package as the site or the team grows, or when you want a person by your side.

Add-ons for usage

More websites, more users or more frequent scans.

More domains
One more domain with up to 1,000 pages. The agency view brings all domains together in one view.
More users
Three users are included. Add more when more people need to sign in, for example developers, editors or your agency.
More credits
For more frequent scans, more than 1,000 pages and more calls through the API and MCP.

Add-ons with experts

Experts who confirm issues, review, remediate documents and give advice.

Expert support
A named contact at Selma and ten expert questions a month, where an expert tests the issue and confirms whether it is real.
Manual expert review
Up to ten template pages are reviewed by hand against WCAG 2.2 AA, with a report for the developers.
PDF remediation
Experts make the PDFs that the inventory finds accessible.

Read about our services

The price depends on how many domains and pages you want to monitor and which add-ons you choose. Book a demo and we will go through what suits you.

Book a demo

Frequently asked questions

How is it different from Insight?
Insight scans up to 20 pages a month and shows where the site stands today. Monitoring reviews the whole domain on an ongoing basis, follows issues over time and gives developers evidence and a commit-ready code fix for every issue.
How are false positives handled?
You can mark an issue as a false positive yourselves, with a reason, and it will not show up in later reviews as long as the code is unchanged. With the Expert support add-on, a Selma expert can review the issue.
Can we fetch the issues into our own systems?
Yes. Through the API and MCP you fetch issues, scores and reports into your own systems and into AI editors such as Claude Code, Cursor and GitHub Copilot. The calls count against the package's credits.
Does the tool make the site meet the law?
No, no automated tool can show that on its own. The monitoring finds and follows up issues and documents the work for you. An answer about the legal requirements takes a manual review.
What does it cost?
The price depends on how many domains and pages you want to monitor and which add-ons you choose. Book a demo and we will go through what suits you.

Want to compare different ways of monitoring accessibility in an online shop? Read about accessibility monitoring for online shops (in Swedish)

Want to see the tool in practice?

Book a demo and we will go through the monitoring and how it fits the way you work.

Book a demo