Accessibility issues hide in component logic, not just markup. VibeRails scans your entire codebase to find missing ARIA attributes, keyboard navigation gaps, focus management problems, and WCAG violations that automated scanners miss.
Most teams approach web accessibility by running an automated scanner – Lighthouse, axe, or WAVE – against their rendered pages. These tools are valuable, but they have a fundamental limitation: they analyse the DOM at a single point in time. They see the HTML that was rendered, not the code that produced it. This means they catch approximately 30 to 40 percent of accessibility issues. The rest require understanding application logic, user interaction flows, and dynamic state changes.
Consider a modal dialogue component. An automated scanner can verify that the modal has
role="dialog" and an aria-label when it is open. But it cannot verify that
focus is correctly trapped inside the modal while it is open, that pressing Escape closes it, that
focus returns to the triggering element when it closes, or that screen readers are properly notified
when the modal appears. These behaviours are defined in JavaScript, not in HTML attributes, and they
require reading the component logic to assess.
The gap widens further in modern single-page applications. Route changes that do not announce the new
page to screen readers, form validation messages that appear visually but are not connected to their
inputs via aria-describedby, loading states that provide no feedback to assistive technology
users, and interactive components built with div and span elements instead of
semantic HTML – all of these are invisible to DOM-level scanners but visible in the source code.
VibeRails analyses your source code, not your rendered DOM. It reads every component, every event handler, every state transition, and identifies accessibility patterns that require code-level reasoning to detect.
VibeRails scans every component, template, and interaction handler in your codebase and surfaces accessibility issues across the full WCAG spectrum:
aria-label or aria-labelledby, custom components that lack role attributes, dynamic content regions without aria-live announcements, and toggle buttons without aria-pressed or aria-expanded stateh2 to h5), components that hardcode heading levels regardless of their position in the page, and dynamically rendered content that breaks the document outlinealt attributes, decorative images that should have empty alt="" but have descriptive text instead, icon buttons that rely solely on visual recognition, and background images that convey information without text alternativeslabel elements or aria-label, error messages not connected to their fields via aria-describedby, required field indicators that are visual-only, and fieldsets without legends for grouped controlsaria-live regions or other programmatic meansEach finding includes the component file path, the specific WCAG success criterion violated, the severity level, and a clear explanation of the impact on users who rely on assistive technology.
Accessibility debt accumulates from the first line of code. There are specific moments when addressing it becomes urgent:
Before a public launch or major release. Launching with accessibility barriers excludes users from day one and creates legal exposure. A VibeRails scan before launch identifies the most impactful issues so the team can address them before real users encounter barriers.
After receiving a legal demand or complaint. Accessibility lawsuits and demand letters have increased significantly in recent years. When a complaint arrives, the team needs a comprehensive inventory of issues immediately – not a months-long manual audit. A VibeRails scan produces a structured remediation plan within minutes.
When building a component library or design system. Accessibility issues in shared components propagate to every application that uses them. Reviewing the component library is the highest-leverage accessibility investment because fixing one component fixes every instance of it across the organisation.
During WCAG compliance efforts. Teams working towards WCAG 2.1 AA or 2.2 AA compliance need to identify every violation across the entire codebase. Running automated scanners page by page is slow and misses code-level issues. A VibeRails scan covers the entire codebase in a single pass and maps findings to specific WCAG success criteria.
After adopting a new framework or component library. Switching from one UI library to another often introduces accessibility regressions. The new library may handle focus differently, use different ARIA patterns, or lack accessibility features that the previous library provided. A scan after the switch identifies what was lost in the transition.
Professional accessibility audits typically cost thousands of pounds and produce a report that is outdated by the next sprint. VibeRails makes ongoing accessibility review practical:
VibeRails runs as a desktop app with a BYOK model. It orchestrates Claude Code or Codex CLI installations you already have. Your source code is read from disk locally and sent directly to the AI provider you configured – never to VibeRails servers. For organisations handling sensitive user data or operating in regulated industries, this means your codebase is not uploaded to a VibeRails cloud service.
Export findings as HTML for compliance documentation and stakeholder presentations, or CSV for import into Linear, Jira, or whatever project management tool your team uses. The structured format – with WCAG success criteria mapped to each finding – integrates directly into accessibility remediation workflows and compliance reporting.
Start with the free tier today. Run a scan on your codebase and see what VibeRails finds. If the findings are valuable, upgrade to the lifetime licence for $299 – less than a single day of contractor time.
Vertel over je team en doelen. We reageren met een concreet uitrolplan.