Most accessibility bugs are one line. A button with no name. An input with no label. A focus ring someone turned off. Rams finds them in the pull request and writes the fix.
Each finding says what a person runs into and which line causes it. The fix is one click on GitHub.
This button is only an icon. A screen reader says "button" and nothing else.
src/components/Toolbar.tsx:41
The placeholder is the only label. It’s gone as soon as someone types, and a screen reader never reads it as the field’s name.
src/app/signup/form.tsx:18
The focus ring is turned off and nothing replaces it. Anyone on a keyboard can’t see where they are.
src/components/ui/button.tsx:9
The code is an example. The rules are the real ones.
Built on WCAG 2.2 AA, plus the things keyboard and screen reader users hit every day. One critical finding caps the score at 59.
Someone can’t use it at all.
Someone can use it, but it’s hard.
Small things that keep screen readers predictable.
Accessibility is one of nine categories in a Rams review. All the rules
Install the GitHub App. Every pull request that touches UI gets a review, and the fixes post inline. No CI config.
The GitHub AppClaude Code, Cursor and Codex can call Rams after they edit a component. They fix what it finds before you see the code. A quick check takes about ten seconds.
Set up an agentThe Action scores each change. It writes the findings and patches to a folder your pipeline can read.
The ActionGive your agent a public URL. Rams opens it at desktop and phone width and returns the top issues.
The MCP toolsRams reviews source files. It can’t see contrast over a photo, focus order after a script runs, or what a screen reader actually says. Run axe or Lighthouse on the rendered page for those.
A clean review means Rams found none of the problems its rules cover. It is not a WCAG conformance report or an ADA compliance statement. No automated tool can give you one.
Rams catches the common failures early. Tab through the page yourself. Try it with VoiceOver or NVDA before you call it accessible.
Install the Rams GitHub App on the repo. Every pull request that changes a UI file gets a review in about a minute. Accessibility findings post inline with the file, the line and a one-click fix. There’s no CI to set up.
36 rules today, built on WCAG 2.2 AA. They cover missing alt text, buttons and links with no name, inputs with no label, click handlers a keyboard can’t reach, focus rings turned off, small touch targets, low contrast, focus that escapes a dialog, and errors that show up but never get announced. The full list is on this page.
No. They test the rendered page in a browser. Rams reviews the code in the pull request, before anything renders, and writes the fix. Use both.
No. No tool can. Rams finds common WCAG 2.2 failures in your code and helps you fix them early. It cannot make a conformance claim for you. That takes testing in a browser, and testing by people who use assistive technology.
Yes. Rams is an MCP server. Claude Code, Cursor, Codex and other agents can call quick_review after they edit UI code, then fix what it finds in the same session. Setup is at /setup.
React, Next.js, Vue, Svelte, SvelteKit, Angular, React Native, SwiftUI, and plain HTML and CSS. SwiftUI reviews also check VoiceOver against Apple’s Human Interface Guidelines.
No. Accessibility is one of nine categories. The same review covers color, typography, spacing, components, UX, motion, craft and native iOS. That’s 365 rules and one score from 0 to 100.
It’s free to start: 15 reviews, no card. Paid plans start at $39 a month.
Install Rams on a repo. The next pull request gets a review. 15 reviews free, no card.
Compare
Frameworks