You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AccessLint brings automated web accessibility testing into your development workflow. When a pull request is opened, AccessLint reviews the changes and comments with any new accessibility issues, giving you quick, timely, and targeted feedback, before code goes live.
AccessLint helps you keep on target with digital accessibility by giving specific, ongoing accessibility feedback to your team. It can catch simple errors that might break your website for your customers with disabilities.
Accessibility guidelines defined in WCAG 2.0 help us build applications that work better for more people. They also give us a rough measure of compliance with legal requirements outlined in the ADA and Section 508. AccessLint runs a growing list of WCAG 2.0 tests, e.g. missing alt attributes that make pages more opaque for screenreader users, positive tabindex values that can create confusion for keyboard users, invalid ARIA, and unlabelled fields.
Use AccessLint to hold on to the hard-earned progress you've made with accessibility, or to inspire your team to start chipping away at issues. That frees you from costly bug-fixes and remediation, and socializes accessibility to your team. That way you'll have fewer bugs and can focus on delivering features.
When you open a Pull Request, AccessLint works quickly to find accessibility issues in your code, and comments with specific, line-by-line feedback.
When subsequent commits are add to the Pull Request, AccessLint reviews your code again and approves any fixes.