Add accessibility regression tests - #400
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_67369248-541b-4118-9bc6-f0fe329ae1b9) |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ceiling | 2c837b5 | Commit Preview URL Branch Preview URL |
Aug 23 2026, 07:03 PM |
|
Warning Review limit reached
Next review available in: 5 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_60facbc2-c74d-49ae-bcbd-ab1f07a45193) |
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_477f1f48-b5fd-49b9-9069-34122642555a) |
# Conflicts: # CHANGELOG.md
# Conflicts: # CHANGELOG.md
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_40d484b6-7705-4406-8819-7fae606ff9e2) |
# Conflicts: # CHANGELOG.md
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_8176776d-60c7-4fe1-b68a-4e9eab53c5df) |
Fixes #222.
Adds vitest-axe, a shared assertion helper, and checks for quota cards, mini charts, and update banners in the existing Frontend test job. Color contrast is excluded because jsdom cannot measure rendered colors. Focused tests and the production frontend build pass.
Note
Low Risk
Test-only frontend change with a new devDependency; no production behavior or security-sensitive paths are modified.
Overview
Frontend CI now fails on axe accessibility regressions for quota cards, mini charts, and update banners.
Adds
vitest-axeplus a sharedexpectNoAccessibilityViolationshelper (color-contrast disabled because jsdom cannot measure it) and wires the matcher in the existing Vitest setup. Representative renders ofPlanStatusCard,SimpleBarChart, andUpdateBannercall that helper.Reviewed by Cursor Bugbot for commit 2c837b5. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Add axe-based accessibility regression tests for frontend components
expectNoAccessibilityViolationshelper in accessibility.ts that runs axe and disables the color-contrast rule due to jsdom limitationsMiniBarChart,PlanStatusCard, andUpdateBannertest suitesMiniBarChart,PlanStatusCard, andUpdateBannertest suites now fail when axe detects accessibility violations in their rendered outputMacroscope summarized 2c837b5.