Skiplink is in pre-release: the hosted API is still being deployed, so scanning and sign-up are not live yet. The docs and the reference are complete.

Skiplink

Roadmap

What works today, what is built and on its way, and what we are only thinking about. There are no dates on this page. A date on a roadmap is a promise, and the only promises here are the things that have already shipped.

Shipped

Everything in this section is in the first release. From here on, each change is recorded in the changelog, including the ones that can turn a build red.

Hosted scan API changelog
Send a URL, get WCAG violations back as JSON: rule, impact, success criteria, selector and the offending markup, plus the axe-core version that found them. One page or a batch. No browser fleet of your own to run. Docs.
Baselines changelog
Commit .skiplink/baseline.json and the gate fails only on violations that are not in it. An existing site can turn the check on today without fixing everything first. How baselines work.
CLI changelog
npx @skiplink/cli scan <url> in any CI system that has Node 20. Separate exit codes for "a new violation" and "could not find out", so a pipeline can block on one and retry the other. Docs.
GitHub Action changelog
One step in a workflow. Annotates the offending lines and keeps a single pull-request comment up to date instead of adding one per run. Setup.
Playwright adapter changelog
Checks pages a hosted scanner cannot reach — behind a login, on localhost, mid-checkout — from inside the tests you already have, against the same baseline file. Setup.
Free scanner changelog
One public URL, no sign-up. The quickest way to see what the API returns before wiring anything into CI. Scan a URL.
Monitors and alerts changelog
Re-scan a site hourly, daily or weekly and get a webhook or Slack message only when something new breaks. Catches regressions that arrive outside a pull request, such as a CMS edit. Growth and Agency plans. Docs.
Client workspaces and white-label reports changelog
One workspace per client, each with its own branding, and a PDF report with the agency's logo and colours. The note on what automated testing cannot cover is on every report. Agency plan. For agencies.
WCAG coverage reference changelog
All 55 WCAG 2.2 A and AA success criteria, and which of them a scanner can detect a failure of — generated from axe-core's rule metadata rather than written by hand. The reference.

Next

Being built, or built and waiting for its release. The first two are finished and documented already; they ship separately so each gets a proper release of its own.

Cypress adapter
cy.checkA11y() anywhere in a spec, failing only on violations that are not in the baseline. Teams on Cypress get the same gate Playwright users have, with the same baseline file. Documentation, ready for release.
Editor integration
Works with your editor: explain any axe-core rule, see what a project's baseline already accepts, and scan a URL without leaving it. Most of it needs no account and no API key. Documentation is ready for release.
Self-serve paid plans
Upgrade, change plan and manage billing from the dashboard. Today the free tier is self-serve and paid plans are set up by email, so upgrading means waiting for a reply.
Before-and-after reports
One report comparing two rounds of scans of the same site: what was fixed, what is new, what remains, matched by violation fingerprint rather than by count. The document an agency hands a client at the end of remediation work.
Guides for more CI providers
Step-by-step setup for GitLab CI, Vercel and Netlify. The CLI already runs on all of them; the guides cover each one's preview URLs, secrets and exit-code handling so nobody has to work that out alone.

Later, or exploring

Not promised. These are ideas we are weighing, not commitments. Some will happen, some will change shape and some will be dropped. Do not choose Skiplink because of anything in this section.

Reports on your own domain
Share a report as a link on the agency's own domain rather than sending a PDF, so the client never sees our name unless the agency wants them to.
A Shopify app
Accessibility checks for Shopify stores without touching CI. Very few stores run any accessibility check at all, which is the reason to look at it.
An open accessibility study
A large scan of real sites — the home pages of a thousand popular open-source projects, for example — published with the full dataset, so anyone can check the method and the numbers.
Guides beyond English
European Accessibility Act guidance in German, French, Spanish and Italian. The law applies across the EU, and nearly everything written about it for developers is in English.

Tell us what is missing

If something you need is not on this page, or something here matters more to you than its position suggests, email hello@skiplink.dev. Say what you are trying to do rather than which feature you want; it is the more useful half of the request.