An accessibility review on every pull request.

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.

Review a repo for freeSee the 36 rules

What it catches.

Each finding says what a person runs into and which line causes it. The fix is one click on GitHub.

Critical · A11Y-002

This button is only an icon. A screen reader says "button" and nothing else.

src/components/Toolbar.tsx:41

Before: <button onClick={openSearch}><SearchIcon /></button>
After: <button aria-label="Search" onClick={openSearch}><SearchIcon /></button>
Critical · A11Y-003

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

Before: <input type="email" placeholder="Email" />
After: <label htmlFor="email">Email</label>
<input id="email" type="email" autoComplete="email" />
Serious · A11Y-005

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

Before: const base = 'px-4 outline-none'
After: const base = 'px-4 outline-none focus-visible:ring-2'

The code is an example. The rules are the real ones.

36 accessibility rules

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.

Critical 5

Someone can’t use it at all.

  • A11Y-001Images have descriptive alt textWCAG 1.1.1
  • A11Y-002Buttons and links have accessible namesWCAG 4.1.2
  • A11Y-003Form inputs have associated labelsWCAG 1.3.1
  • A11Y-004Interactive divs have role, tabIndex, keyboard handlersWCAG 2.1.1
  • A11Y-039Nothing flashes more than three times a secondWCAG 2.3.1

Serious 20

Someone can use it, but it’s hard.

  • A11Y-005Focus indicators are visibleWCAG 2.4.7
  • A11Y-007Touch targets are at least 44x44pxWCAG 2.5.5
  • A11Y-008Color is not the only indicatorWCAG 1.4.1
  • A11Y-009Text contrast meets WCAG AA 4.5:1WCAG 1.4.3
  • A11Y-012Never cap viewport zoom to dodge the iOS input zoom
  • A11Y-013Keep text at 12px or above
  • A11Y-015Every dialog has a title and a visible way out
  • A11Y-017Glass surfaces need transparency and contrast fallbacks
  • A11Y-019Expanded hit areas never overlap
  • A11Y-021Hidden UI leaves the tab order
  • A11Y-022Errors are wired, not just shown
  • A11Y-023Suggestion lists are comboboxes, not div stacks
  • A11Y-024A card is not one giant link
  • A11Y-025Navigation is a link, not a click handler
  • A11Y-027Tab order is DOM order, and a composite widget is one stop
  • A11Y-028Single-key shortcuts need a modifier, a sequence, or a guard
  • A11Y-030aria-hidden never covers a focusable element
  • A11Y-032Tooltips hold no controls
  • A11Y-040Hover-opened content survives the trip to itWCAG 1.4.13
  • A11Y-041A timer that acts for the user can be stopped or extendedWCAG 2.2.1

Moderate 11

Small things that keep screen readers predictable.

  • A11Y-006Heading levels are sequentialWCAG 1.3.1
  • A11Y-010Modals trap focus and return it on close
  • A11Y-011Mark decorative icons aria-hidden
  • A11Y-014Set lang on the document root
  • A11Y-016Announce async feedback with a live region
  • A11Y-018Duplicated DOM is hidden from assistive tech
  • A11Y-020Controls opt out of double-tap zoom
  • A11Y-026After the DOM changes, focus goes somewhere on purpose
  • A11Y-029The accessible name says what happens and matches what is visible
  • A11Y-031Link text says where it goes
  • A11Y-033Moving media can be paused

Accessibility is one of nine categories in a Rams review. All the rules

Four places to run it.

On the pull request

Install the GitHub App. Every pull request that touches UI gets a review, and the fixes post inline. No CI config.

The GitHub App

In your agent

Claude 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 agent

In CI

The Action scores each change. It writes the findings and patches to a folder your pipeline can read.

The Action

On a live page

Give your agent a public URL. Rams opens it at desktop and phone width and returns the top issues.

The MCP tools

What Rams doesn’t do.

It reads code, not the browser

Rams 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.

It doesn’t certify anything

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.

You still have to test

Rams catches the common failures early. Tab through the page yourself. Try it with VoiceOver or NVDA before you call it accessible.

How Rams and axe fit together

Questions

How do I check accessibility in a pull request?

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.

What accessibility issues does Rams catch?

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.

Does Rams replace axe or Lighthouse?

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.

Will Rams make my site WCAG or ADA compliant?

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.

Can my coding agent run the accessibility check itself?

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.

Which frameworks does it review?

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.

Does Rams only check accessibility?

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.

What does it cost?

It’s free to start: 15 reviews, no card. Paid plans start at $39 a month.

Fix it before it merges.

Install Rams on a repo. The next pull request gets a review. 15 reviews free, no card.

Review a repo for freeSet up an agent