Screenshot of axe Linter auto finding and suggesting accessibility fixes in GitHub

Deque Introduces Automated Source Code Accessibility Checker

Axe Linter Requires Minimal Effort to Detect and Suggest Accessibility Fixes;

New GitHub App is Free for Personal Repositories  

HERNDON, VA – May 5, 2020  – Deque Systems, a leading software company specializing in digital accessibility, today introduced axe Linter, an automated GitHub-based app which checks source code for common accessibility issues, automatically finding and suggesting fixes.

Developers can supplement existing accessibility testing efforts by using axe Linter to catch accessibility problems early in the development process, significantly reducing future testing and remediation efforts. Once axe Linter is enabled for a GitHub organization, it can be installed or enforced on every repository, running automatically on every change or pull request without further input or processes from the development team.

Axe Linter is available now on GitHub at or on the Deque website at, and is free for all personal repositories. Axe Linter currently supports the React (JSX / TSX), Vue, HTML and Markdown formats.

“Axe Linter saves time and money by shifting inspection to the earliest phase of development, so accessibility problems can be identified and repaired before code even gets merged,” says Dylan Barrell, Chief Technology Officer at Deque Systems. “Once installed in your GitHub repository, it requires no further developer effort to get feedback on code changes. Axe Linter only analyzes new or changed code and makes suggestions on how to resolve accessibility issues. We expect it will become a must-have element of our axe DevTools solutions.”

Axe Linter is built upon a growing list of rules based on WCAG 2.1 as well as a number of best practices. The application has been refined to return zero false positives.

Axe Linter can have an immediate impact on the accessibility of development efforts, helping to make websites and applications more accessible for all, including people with disabilities.

“Axe Linter offers easier-than-push-button accessibility checking for source code, ensuring accessibility checks are in place for every change or pull request. When combined with the popular free axe Browser Extension for testing within the browser, or any of Deque’s Enterprise offerings, development teams have everything they need to make a huge impact on making their apps more accessible to people with disabilities,” says Preety Kumar, CEO, Deque Systems.

About Deque Systems

Deque (pronounced dee-cue) is a web accessibility software and services company, and our mission is Digital Equality.  We believe everyone, regardless of their ability, should have equal access to the information, services, applications, and everything else on the web.

We work with enterprise-level businesses and organizations to ensure that their sites and mobile apps are accessible. Installed in over 250,000 browsers and with over 1,000 audit projects completed, Deque is the industry standard.

News Media Contacts

At Deque:
Ryan Bateman, 703-225-0380,
Kristina LeBlanc, 508-930-5636,
Frank Cioffi, 415-893-1570,

update selasa

Comments 8 responses

  1. Does AxeLinter work with Azure DevOps as a source control environment? I know the Borg have integrated Git into it since they bought GitHub, but I don’t know details on how that affects AxeLinter.

  2. This is a great tool. Kudos to you, Deque Systems.

    Will this be made available for GitHub organizations? If so, do you have an estimate of when?

    Thank you

  3. This looks like an amazing tool, does it work on markup styled using the styled-components or emotion libraries?

  4. Cara – Axe Linter doesn’t have specific rules for them, but components that use this can be tested with axe Linter for other types of issues.

  5. Can Axe Linter be configured to Jenkins CI/CD pipeline, if my source code is on GitHub repository?

  6. Jai – It is currently GitHub only, but we are looking at expanding (questions like these help us gauge interest).

Leave a Reply

Your email address will not be published. Required fields are marked *