MCP Accessibility Bridge

Connect to a running Chrome browser via the Chrome DevTools Protocol (CDP). Chrome must be started with --remote-debugging-port=9222. Command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug-profile

Navigate the connected browser to a URL. Returns the page title and HTTP status code when complete.

Close the CDP connection to Chrome. Does NOT kill the Chrome process. Call this when you are done to release the connection.

Capture a snapshot of the current page's accessibility tree. Returns a hierarchical tree of ARIA roles, names, and properties. Use interestingOnly=false for the complete raw tree. Use useFullTree=true for the CDP-level complete tree (slower but more accurate). Use maxDepth to control how deep the tree goes.

Search the accessibility tree by ARIA role and/or accessible name. Returns matching nodes with their properties. Example: role="button", accessibleName="Submit" finds all Submit buttons.

Given a CSS selector, returns the element's full accessibility properties and multi-framework test selectors (Playwright, Selenium, Cypress, WebdriverIO). Selectors are prioritized: data-testid > stable id > ARIA role > semantic CSS.

Find all interactive elements on the page (buttons, inputs, links, etc.) and return their accessibility info plus multi-framework test selectors. Covers 20 interactive ARIA roles. Use roles[] to filter to specific roles.

Returns the currently keyboard-focused element's accessibility info and suggested selectors. Useful for checking focus management in accessible UIs.