Skip to content
Selma

Selma Developer Tools

Accessibility built into your development workflow

Selma Developer Tools scans your domains against WCAG 2.1 AA, prioritizes the issues and gives you ready-made code suggestions – right in your editor, your tests and your pipeline.

Book a demoSee the packages
Illustration of two code windows, gears and an API box on a pink platform.

Where developers already work

The tool connects to your editor, your tests and your CI/CD through MCP and an SDK, and creates tickets in your issue tracker. You do not need to change how you work to start building accessibly.

Three steps

How it works

  1. 1

    Review

    The platform scans your pages and user flows automatically and finds accessibility issues against WCAG 2.1 AA.

  2. 2

    Fix

    The issues are prioritized and come with guidance and ready-made code suggestions, in the tool, in your editor or as tickets.

  3. 3

    Follow up

    Ongoing scans and alerts by email and in the tool tell you when new issues appear, so they are caught in time.

What is included

Tools for the whole development workflow

  • In your editor with MCP

    Connect the tool to the AI assistant in your editor, such as GitHub Copilot or Cursor. You see the issues and get code suggestions while you write.

  • In your tests with the SDK

    Build accessibility checks into your tests with Cypress, Playwright or Selenium, and catch issues locally and in staging before they reach production.

  • In your CI/CD

    Run the checks in your pipeline, for example in Jenkins, CircleCI or GitLab, so new issues are found before release.

  • Ready-made code suggestions

    Every issue comes with a code suggestion and guidance based on WCAG. You can check a fix straight away, without waiting for the next scan.

  • User flows

    Record important flows such as purchases, logins and forms, and test them step by step.

  • One overview

    Follow the status across several domains and projects, share out the work and spot issues that keep coming back.

  • Issue tracking

    Create tickets in Jira, Asana or ClickUp straight from an issue.

  • Suggested alt text

    Let AI suggest image descriptions in seconds, and review them before they are published.

  • Auto-resolve

    Temporary fixes for some common issues are applied when the page loads, while you fix the code for real. Every change is logged and can be undone.

Packages

Three packages by size

The packages differ in how many pages, domains and users they cover and how often the pages are scanned. Book a demo and we will go through which one suits you.

  • Essential

    • Up to 1,000 pages and 2 domains
    • Up to 2 users
    • Automatic scan every month
    • 20 on-demand scans per day
    • Connection to issue tracking
    • Guidance and code suggestions in the tool
    • Accessibility statement that updates itself
    • Personal onboarding

  • Professional

    • Everything in Essential
    • Up to 10,000 pages and 10 domains
    • Up to 10 users
    • Automatic scan every other week
    • 50 on-demand scans per day
    • Connection to CI/CD
    • SDK and MCP for your editor
    • Auto-resolve
    • Sign-in with Google

  • Enterprise

    • Everything in Professional
    • More than 10,000 pages and up to 100 domains
    • Unlimited users
    • Automatic scan every week
    • 150 on-demand scans per day
    • Custom agreements and SLA
    • Single sign-on (SSO)
Book a demo

Good to know

What the tool does not do for you

Automated tests and AI find and suggest a lot, but not everything. You review the code suggestions yourselves before they go into the code.

What a person needs to check

  • How a flow works for someone who uses a screen reader or a keyboard every day
  • Whether texts and instructions are easy to understand
  • Whether an alternative text describes the image correctly in its context
  • Whether a code suggestion fits your code and your design

For the full picture, Selma Services carries out manual expert reviews and user tests with people who use screen readers every day.

Book an appointment

Common questions about Selma Developer Tools

What is Selma Developer Tools built on?
On automated checks in the development work. Selma connects the tool and is your contact for the demo, setup and follow-up.
Which standard does the tool test against?
WCAG 2.1 at level AA. WCAG is the international standard for web accessibility.
Do we need to change how we work?
No. The tool connects to your editor through MCP, to your tests and your CI/CD through the SDK, and to your issue tracker.
How is it different from Selma Scanning?
Selma Scanning tests one page at a time and gives you a report. Selma Developer Tools scans your domains continuously, gives code suggestions and becomes part of the development work.
Does auto-resolve change our source code?
No. Auto-resolve applies temporary fixes for some common issues when the page loads. Every change is logged and can be undone, and you make the permanent fix in the code.
Is the tool enough to meet the legal requirements?
No, no tool is enough on its own. Automated tests find many common issues, but not all of them. To know whether your service meets the Swedish act on the accessibility of certain products and services (LPTT) or the Swedish act on accessibility to digital public services (DOS-lagen), a manual review is also needed.
What does Selma Developer Tools cost?
It depends on how many pages, domains and users you need. Book a demo and we will go through which package suits you.

See the tool with your own code

Book a demo and we will show you how the tool works with your pages, your flows and the way you work.

Book a demo