AccessLint
accesslint.com
- Free plan
- macOS
- Web
- Browser extension
- API
What AccessLint is
AccessLint checks accessibility in development, on pull requests and on live sites. Its WCAG engine has 95 rules and a stated 53ms median audit across 5,000 real-world sites. Pull-request reviews examine changed files and post inline comments naming the rule and suggesting a correction, but they do not fail builds or block merges. Deploy-triggered scans require Starter or Pro, run asynchronously and do not synchronously fail builds when violations appear. Saved user journeys can run daily, with email alerts for new violations or changes against a baseline. The toolkit provides checks for Playwright, Vitest and Storybook, while pull-request reviews use a GitHub App. Starter and Pro include shareable, read-only evidence reports with before-and-after screenshots of affected elements. The Free plan includes public-repository pull-request reviews, one flow with daily runs and violation trends. Starter costs $19 a month, or $190 a year; Pro costs $349 a month, or $3,490 a year. AccessLint says automated checks alone cannot make a site compliant. Routine passing-flow screenshots are deleted after seven days; screenshots from runs needing attention remain until the customer deletes them.
Who it suits
AccessLint suits teams that want accessibility checks in development, pull requests and recurring live-site journeys. It can help demonstrate an accessibility process, but it does not make a site compliant.
Good to know, and what to watch
- Checks changed files in pull requests.
- Includes daily monitoring for one free flow.
- Supports Playwright, Vitest and Storybook.
- Starter and Pro provide evidence reports.
- Offers email alerts for baseline changes.
- Pull-request reviews do not block merges.
- Deploy-triggered scans require Starter or Pro.
- Alerts are sent by email only.
- Automated checks cannot make a site compliant.
Plans
Every plan and priceFree
Starter
Pro
Free plan · 14-day trial
Getting started
- Visit the AccessLint website.
- Choose the Free plan or a paid plan; a 14-day trial is available.
- Connect pull-request reviews through the GitHub App.
- Use the toolkit checks for Playwright, Vitest, or Storybook.
- Set up saved user journeys for daily monitoring.
Limits to check
The Free plan includes public-repository pull-request reviews and one flow with daily runs. Deploy-triggered scans require Starter or Pro; Starter includes one monitored flow, while Pro includes 20.
The Club's review
AccessLint is an accessibility checker for development workflows, pull requests and monitored live-site journeys. It is best suited to teams that want recurring checks and actionable findings near their code. Its main trade-off is that scans report issues but do not stop a build or block a merge.
Overview
AccessLint combines automated WCAG 2.2 checks with browser-extension scans, GitHub pull-request reviews and daily monitoring of saved user journeys. Its engine has 95 rules and a reported 53ms median audit across 5,000 real-world sites, making speed a clear strength for frequent checks. That breadth still has a boundary: AccessLint says automation cannot make a site compliant by itself, so teams need to treat results as one part of their accessibility work.
Key features
Pull-request reviews examine changed files and add inline comments with the relevant rule and a suggested fix. This puts guidance beside the code under review, which is useful for teams acting on accessibility findings during normal development. The limitation matters for release controls: reviews do not fail builds or block merges. Deploy-triggered scans on Starter and Pro also run asynchronously, so they do not hold a deployment until violations are resolved.
For production monitoring, AccessLint revisits saved user journeys daily and emails alerts about new violations or changes from the baseline. This keeps alerts focused on changes rather than repeatedly reporting unchanged issues. The toolkit supports Playwright, Vitest and Storybook, and pull-request reviews use a GitHub App. Findings include before-and-after screenshots of affected elements; shareable, read-only evidence reports are included on Starter and Pro.
A browser extension supports page checks outside the pull-request workflow. AccessLint also describes its core engine as having no dependencies, which suits teams looking to add checks to development tooling. Routine passing Flow screenshots are deleted after seven days; screenshots from runs needing attention remain until the customer deletes them.
Pricing
The Free plan costs nothing. It includes public-repository pull-request reviews, one flow with daily runs and violation trends. It is a practical starting point for open-source projects or teams evaluating the workflow, but private repositories, deploy-triggered scans and shareable evidence reports require a paid plan.
Starter costs $19 a month when billed monthly, or $190 a year with two months free. It adds private-repository reviews, deploy-triggered scans, a shareable evidence report and one monitored flow with daily runs. This is the natural choice for a small team monitoring a single important journey and wanting evidence to share. It still offers only one monitored flow.
Pro costs $349 a month when billed monthly, or $3,490 a year with two months free. It includes everything in Starter and raises the allowance to 20 monitored flows with daily runs. That makes it more appropriate for teams with many journeys to track; the steep step up from Starter is difficult to justify for a single-flow setup. AccessLint offers a 14-day trial. No seat limits are stated for these plans.
Platforms
AccessLint supports API, browser extension, macOS and web. The mix gives teams several ways to reach the checks, though platform support alone does not change the lack of build or merge enforcement.
Who it's for
AccessLint fits development teams that use GitHub pull requests, want suggested fixes close to changed code, and need daily monitoring for key live-site journeys. Starter suits a small private-code team tracking one flow; Pro is aimed at organizations monitoring a wider set of journeys. Teams that need accessibility findings to act as a release gate should choose a tool or process that can enforce one.
Pros and cons
- Pros: Inline comments pair rule references with suggested fixes, giving developers a concrete starting point for remediation.
- Pros: Daily journey monitoring and baseline-focused email alerts help teams keep watch on production without repeating unchanged findings.
- Pros: The free tier covers public-repository reviews and one daily monitored flow, so a team can begin without a paid subscription.
- Cons: Findings do not fail builds or block merges, limiting its use as an enforced quality gate.
- Cons: Free is restricted to public repositories, while Starter monitors just one flow; broader private-team coverage requires a paid plan.
- Cons: Pro's $349 monthly price is a substantial jump for teams that need more than one flow but do not need 20.
- Cons: Automated findings are not proof of compliance, so teams still need accessibility work beyond scanning.
Alternatives
Choose WAVE if you want a freemium option available across more operating systems, including Linux and Windows; its Subscription API plan starts at $10 a month with a 250-credit minimum purchase.
A11yInspect is a free-plan alternative for unlimited webpage testing, with no login or credit card required. Consider Assistiv Labs when you want to test with assistive technologies such as NVDA or Narrator; its Freelancer plan is $19 a month for 120 testing minutes, one user and one parallel test.
Octopus Scanner (formerly A11y Scanner) is a free download with optional developer contributions. Total Validator offers a free single-page summary and a $10 one-time Basic plan. Evinced is a paid option without a free plan, with a 14-day Site Scanner trial that covers up to 50,000 URLs crawled and 50,000 U.
Oobee is a free, open-source option powered by GovTech Singapore. Pa11y offers free, open-source accessibility tools.
For more options, browse Website Accessibility Tools or Accessibility Testing Software.
Verdict
AccessLint is a strong fit for teams that want accessibility checks woven into GitHub reviews and continued monitoring of important live-site journeys. Suggested fixes, daily runs and evidence reports give those teams useful ways to act on and track findings. Look elsewhere if merge-blocking enforcement is essential, or if your monitoring needs exceed Starter but do not warrant Pro's 20-flow plan and $349 monthly price.
The verdict
AccessLint can surface issues across development, pull requests and saved live-site journeys, with suggested fixes and evidence reports on paid plans. Treat its findings as part of an accessibility process rather than proof of compliance.
Questions people ask
Is there a free plan?
Yes. Free includes public-repository pull-request reviews, one flow with daily runs, and violation trends.
How much do the paid plans cost?
Starter is $19 a month or $190 a year. Pro is $349 a month or $3,490 a year.
Which platforms and tools does AccessLint support?
Its listed platforms are API, extension, macOS, and web. Its toolkit provides checks for Playwright, Vitest, and Storybook.
Does AccessLint block a pull request or fail a build?
No. Pull-request reviews post inline comments but do not fail builds or block merges. Deploy-triggered scans also run asynchronously and do not synchronously fail builds.
Does AccessLint make a site compliant?
No. AccessLint says it can help demonstrate an accessibility process, but automated tools cannot make a site compliant.
How does AccessLint handle security and privacy?
AccessLint says it does not sell personal information or share it for advertising, and does not ask for or store site passwords. Its policy states that traffic uses TLS and sensitive data is encrypted at rest.
What the maker publishes
- Automated scans
- Yes source
- Browser extension
- Yes source
- Browser extension
- The a11y agent is a Chrome extension that audits pages in real time and gives AI-generated remediation suggestions in Chrome’s side panel. source
- CI/CD integration
- Yes source
- Compliance limitation
- AccessLint says it can help demonstrate an accessibility process but does not make a site compliant, and no automated tool can do so. source
- Core engine
- The zero-dependency WCAG engine has 95 rules and a 53ms median audit across 5,000 real-world sites. source
- Data retention
- Screenshots from routine passing Flow runs are deleted after seven days, while screenshots from runs needing attention remain until the customer deletes them. source
- Deploy triggers
- Deploy-triggered scans require Starter or Pro, run asynchronously, and do not synchronously fail builds when violations are found. source
- Free plan
- Yes source
- Integrations
- The toolkit provides accessibility checks for Playwright, Vitest, and Storybook, while pull-request reviews use a GitHub App. source
- Maker
- The privacy policy identifies the maker as AccessLint, LLC and lists its address in Albany, New York, United States. source
- Privacy
- AccessLint says it does not sell personal information or share it for advertising, and says it never asks for or stores site passwords. source
- Product
- AccessLint checks apps during development, on pull requests, and on live sites to catch accessibility issues. source
- Production monitoring
- Flows revisit saved user journeys daily and alert by email only about new violations or changes from the baseline. source
- Pull request reviews
- AccessLint reviews changed files and posts inline comments identifying the rule and suggested fix; it does not fail builds or block merges. source
- Remediation guidance
- Yes source
- Reports and evidence
- Starter and higher plans provide shareable read-only evidence reports, and findings include before-and-after screenshots of the affected element. source
- Security
- The privacy policy states that site traffic uses TLS, sensitive data is encrypted at rest, and payment card numbers are handled by Stripe and never reach AccessLint servers. source
- Paid from
- 19 source
- Support
- AccessLint directs users who cannot find an answer in Help to email [email protected]. source
- WCAG coverage
- wcag 2.2 source
Checked against the maker's pages on 30 Sept 2026.