Skip to main content
Glama

browser_a11y_check

Run an axe-core accessibility check on the current page to identify WCAG violations, with options to restrict scan scope, exclude regions, and filter by rule tags.

Instructions

Run an axe-core accessibility check on the current page, supporting scan-scope restriction, exclude regions, and rule-tag filtering, returning a violations summary.

中文详情:

  • 用途:使用 axe-core 对当前页面执行可访问性检查,支持限定扫描范围、排除区域和规则标签过滤,返回 violations 摘要

  • 何时使用:上线前 WCAG 合规检查时;可访问性自动化回归时;排查元素缺少 aria-label/alt 时;针对特定组件做 a11y 局部扫描时

  • 输出:{ ok: boolean, url: string, total: number, violations: array, passes: number, incomplete: number, summary: string } — 每项含 { id, impact, tags, description, help, nodes: array }

  • 参数:

    • selector (string, 可选):CSS 选择器;指定后只扫描该区域

    • excludeSelectors (array, 可选):排除扫描的 CSS 选择器列表

    • tags (array, 可选):axe runOnly 标签,如 wcag2a/wcag2aa/best-practice

    • sessionName (string, 可选):浏览器会话名称,默认当前活跃会话

  • 错误:浏览器未启动抛出 'Browser not launched';selector 无匹配抛出 'element not found'

  • 示例:{"selector":"main","excludeSelectors":[".ad-banner"],"tags":["wcag2a","wcag2aa"]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoaxe runOnly 标签,如 wcag2a、wcag2aa、best-practice
selectorNo可选 CSS 选择器;指定后只扫描该区域
sessionNameNo浏览器会话名称,默认当前活跃会话
excludeSelectorsNo排除扫描的 CSS 选择器列表
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It describes the tool as running checks, returning a violations summary, and mentions errors (browser not launched, selector not found). It also gives output structure, which is helpful transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with English summary followed by Chinese details, front-loaded with key purpose. Though slightly long, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no output schema, and no annotations, the description is very complete: purpose, use cases, parameters, output format, errors, and example. No output schema is needed because return values are described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description restates each parameter (selector, excludeSelectors, tags, sessionName) with purpose and optionality. It also adds example usage and error handling, providing clear meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it runs an axe-core accessibility check on the current page, with scan-scope restriction, exclude regions, and rule-tag filtering. This distinguishes it from sibling tools like browser_visual_check (visual regression) and browser_lighthouse_audit (performance/SEO) by specifically focusing on a11y violations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Chinese section explicitly lists when to use: pre-release WCAG compliance, automated regression, debugging missing aria-labels, local component scanning. It does not explicitly mention when not to use, but the specific use cases provide clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server