Repository navigation
Conversation
accessibilityExpert is going away. Until it is removed it keeps answering from BrowserStack's accessibility knowledge base, so nothing that calls it breaks. Its description and title now say it is deprecated, each answer starts with a note that it will be removed and what to use instead (answer general WCAG questions directly; use startAccessibilityScan or fetchAccessibilityIssues for a page's or a report's issues), and docs/TOOLS.md marks it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
 |
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Title check |  |
This assessment has not completed. The check will be retried on the next pre-merge check run. |
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled.
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
…skBrowserStackAI for advice Listing or filtering a report's issues goes to fetchAccessibilityIssues; advice on a report, such as raising its score or what to fix first, goes to askBrowserStackAI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SavioBS629
previously approved these changes
Nov 11, 2026
Resolves the conflicts with #566 and #568: - accessibilityExpert answers start with the deprecation note, then main's "question was shortened" note when the question was cut, then the answer. - docs/TOOLS.md keeps main's re-run wording for startAccessibilityScan and marks accessibilityExpert deprecated. - accessibilityExpertQuery tests now expect the deprecation note first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
accessibilityExpertis going away, and product has been notified. #512 removed it outright, but that was reverted (f9ebfee) because the tool was still in use: about 700 calls from about 120 users in 30 days. The agreed path was a deprecation first, naming what to use instead, and the removal in a later release. This is the deprecation.What changed
fetchAccessibilityIssues;startAccessibilityScan;askBrowserStackAIwithproduct: a11y, giving the user its answer;askBrowserStackAIis not enabled for the account, answer from the report's issues.docs/TOOLS.mdmarks it deprecated.This is #512's first commit (0be9a14) on current
main, with the note now naming what to use instead.Verified
tscand vitest all pass (127 files, 1836 tests).claude -psession with a strict MCP config: asked "what contrast ratio does normal body text need under WCAG 2.2 AA?", the agent called the tool and got the note and the answer, and answered 4.5:1. That run used the earlier wording of the note.Next
Remove the tool in a later release, once telemetry shows calls have dropped off. The removal is #512's second commit (e8b8ac9).
🤖 Generated with Claude Code