Jeikin Accessibility installs statistics

Jeikin doesn't just find accessibility issues — it enforces compliance, tracks evidence, and proves your team ships accessible code.

How it works

• Open a pull request — Jeikin automatically reviews changed UI files. • See issues on the exact line — Inline comments with WCAG criteria, severity badges, and plain-language explanations. • Fix in one click — Deep links open the file in Cursor or VS Code with the issue context pre-loaded. • Merge is blocked until it's right — Critical WCAG violations prevent merging. Non-critical issues are flagged but won't slow you down. • Compliance is tracked — Every review is logged. Connect the Jeikin dashboard to see your team's accessibility posture over time.

Not just another linter

Most accessibility tools stop at flagging issues. Jeikin is different:

• Enforcement, not suggestions — Critical issues block the merge. Your team can't ship inaccessible code by accident. • WCAG-mapped findings — Every issue is traced to a specific WCAG 2.2 success criterion, not a generic rule name. You always know which standard is at risk. • Evidence you can share — Every review is tracked. Connect to the Jeikin dashboard to see compliance trends across your team, project, and time. • One-click fixes — Deep links open the exact file and line in Cursor or VS Code with the issue context pre-loaded. From finding to fixing in one click. • Privacy first — Your code never leaves GitHub. Jeikin reads changed files via the GitHub API but never stores source code. Only analysis results are kept.

The bot currently checks for missing image descriptions, keyboard accessibility gaps, heading structure violations, focus management issues, tab order problems, and invalid navigation elements — with more rules added regularly. But the real value is the workflow: catch → explain → fix → verify → track.

Description from the GitHub Marketplace listing.