Cypress Can Now Show Accessibility Results in Your Terminal. Use It to Fix One Rule at a Time

Cypress Can Now Show Accessibility Results in Your Terminal. Use It to Fix One Rule at a Time

ยท 4 min readPublished inEngineering Quality
QAAssist graphic: Fix accessibility one rule at a time

Cypress Cloud CLI 0.6.0 adds accessibility commands. Here is what they do, how to use them to fix one rule at a time, and where a score can mislead you.

Quick answer

On November 3, 2026, Cypress added cy-cloud accessibility commands in @cypress/cloud 0.6.0. They show a run's accessibility score, failing rules and failing elements in the terminal as JSON. They need the Cypress Accessibility add-on or trial. Use them to rank rules by impact and count, then fix one rule per pull request. Do not treat the score as proof of access, and do not gate CI on it too early.

Key takeaways

  • Cypress Cloud CLI 0.6.0 (November 3, 2026) adds commands to read a run's accessibility report from the terminal.
  • The accessibility commands need the Cypress Accessibility add-on or a trial. The CLI itself is on every plan.
  • Rank failing rules by impact and count, then fix one rule across the app per pull request.
  • A score from 0 to 100 is a trend line, not proof that people can use your app.
  • Start by watching the number. Gate CI only on critical rules once the count is low.
  • Read every change an AI agent suggests. Some accessibility fixes only hide the problem.

Cypress now lets you read a run's accessibility report from the terminal. The new commands shipped on November 3, 2026, in @cypress/cloud 0.6.0. If your team already records runs in Cypress Cloud and has the Accessibility add-on, this is worth ten minutes. If not, there is nothing to switch on yet.

Here is what changed, what it is good for, and where I would be careful.

What Cypress added

According to Cypress's release note, the new cy-cloud accessibility commands bring a run's Accessibility report into your terminal. You can:

  • Read the score and the failing rules.
  • List failing elements by rule or by impact.
  • Check which App Quality configuration the run used.

That last point matters. It helps you tell whether a change in the report came from your app or from your config.

The Cloud CLI docs give the details:

  • cy-cloud accessibility report get returns the score (0 to 100), the report URL, element counts and each failing rule with its count.
  • cy-cloud accessibility element list returns the failing elements, worst impact first. You can filter with --ruleId or --impact critical,serious.
  • Every command returns JSON. Every command exits with a non-zero code on failure.
  • The commands only read data from runs Cypress Cloud has already processed.

The Cloud CLI itself is available on every Cypress Cloud plan, including the free one. The accessibility commands are different. They need an active Cypress Accessibility add-on or trial. Without one, the command fails with an error that says the feature is not enabled for the organization. The CLI also needs Node.js 22.21.0 or later.

Why this is useful

Most teams do not ignore accessibility on purpose. They ignore it because the report lives in a place nobody opens during a normal day.

A terminal command changes that. Your accessibility results can now sit next to the rest of your CI output. You can pipe the JSON into a script or hand it to an AI coding agent. Cypress's own docs describe both uses.

The biggest win is sorting. A report with dozens of failing elements is easy to put off. A short list of rules, ranked by how many elements fail each one, is easier to start. The docs suggest this approach: fix one rule across the whole app, starting with the rule that fails on the most elements.

A simple way to use it

Here is a plan I would try. It is a suggestion, not Cypress's official process.

  1. Run your suite with recording on, as you do today.
  2. Pull the report summary for the latest run.
  3. Look at the failing rules. Sort them by impact first, then by count.
  4. Pick one rule. Pull its failing elements.
  5. Fix that rule everywhere in one pull request.
  6. Run again and compare the score and the rule count.

Keep each pull request to one rule. Reviewers can then check it quickly. If a rule is fixed in one shared component, the count should drop in many places at once.

Where I would be careful

Do not treat the score as the goal. A score from 0 to 100 is a handy trend line. It is not proof that your app works for people who use screen readers or keyboards. Automated checks find only part of the problems. A person still has to try the main flows.

Do not fail the build on a score too early. The CLI makes it easy to gate CI on a number. If you start at a low score, a hard gate will block every release and people will learn to ignore it. Start by watching the number. Gate only on critical rules once the count is low.

Check the config before you blame the app. If the score jumps, look at the App Quality configuration first. The new config command exists for this reason.

Be careful with AI agents. The docs say the CLI is built for agents as well as people. An agent can list elements and suggest fixes. You still need to read each change. A fix that adds an aria-label to hide a missing visible label is not a real fix.

Know the cost. The CLI is free, but the accessibility commands need the add-on or a trial. Check the price and ask whether your team will use it every week before you commit.

What this says about test tooling

Other tools shipped small updates the same week. AT*SQA's tool news page, updated on November 9, lists a Playwright 1.65.0 release, a Katalon update and an Autify update alongside this one. The pattern is that vendors keep moving results out of dashboards and into places where scripts and agents can read them.

For a QA team, that is a good thing if you do one job first: decide who owns the result. A report that anyone can read but nobody owns will not get fixed, whether it sits in a dashboard or a terminal.

What to do next

If you use Cypress Cloud with the Accessibility add-on:

  • Update @cypress/cloud to 0.6.0 or later and run cy-cloud accessibility report get on your last run.
  • Write down the top three failing rules.
  • Fix one of them this sprint.

If you do not have the add-on, you can still copy the habit. Pick one accessibility check you already run, rank the failures by impact, and fix one rule at a time.

CypressAccessibility TestingCypress Cloud CLITest AutomationQA

Frequently asked questions

Cypress added cy-cloud accessibility commands in @cypress/cloud 0.6.0. They let you read a run's accessibility score and failing rules, list failing elements by rule or impact, and check the App Quality configuration the run used.

About this article

Gulshan KumarProduct & Engineering
Ship release-ready quality

Try QA Assist

Plans, runs, and defect handoff in one workspace.

Get it free