Skip to main content
Glama
Sign In
a11y-toolkit

a11y-toolkit

by kinti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

a11y-toolkit: Hover dismissibility (1.4.13)

a11y_hover
Read-onlyIdempotent

Tests hover/focus tooltips and overlays to verify Escape dismisses them, flagging WCAG 1.4.13 failures. Requires local Playwright; returns candidates and findings.

Instructions

Content on Hover or Focus (1.4.13): finds tooltip/overlay candidates, hovers each, and tests whether Escape dismisses the result — tooltips that do not dismiss are flagged. Requires local Playwright. — Scope: tooltips only; full audit is a11y_audit_dom, keyboard traps are a11y_keyboard. Returns JSON: {candidates, dismissed_on_escape, findings}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "a11y_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to test
langNoOutput language (en default)
timeoutNoPage load timeout (45 default)
auth_stateNoPath to a Playwright storage_state JSON (exported session) to audit behind login — stays local

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.5.0
    • addedInput schema / properties / auth_state
      Added value: +{
+  "description": "Path to a Playwright storage_state JSON (exported session) to audit behind login — stays local",
+  "type": "string"
+}
  2. Addedv4.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so credit goes to added context: the description discloses the actual interaction performed (hovers elements, presses Escape), the local-Playwright dependency, and that non-dismissing tooltips are flagged. It doesn't discuss limits on candidate count or timing/pagination of the hover probing, but the operational disclosure is solid.

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?

Dense but front-loaded: purpose first, then the scope/alternative routing, then the return shape. Every clause carries information; the 'Returns JSON' sentence is justified because there is no output schema, though it is the least essential element.

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?

With no output schema, the description compensates by naming the return keys (candidates, dismissed_on_escape, findings), and it covers the environment requirement and the auth path via the schema. For a focused single-criterion checker with annotated safety, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (url, lang, timeout, auth_state) is already documented in the schema, including the enum and defaults. The description adds no parameter-level syntax or format detail beyond that, so the baseline 3 is appropriate.

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?

States a specific criterion (1.4.13 Content on Hover or Focus) and a concrete verb sequence: finds tooltip/overlay candidates, hovers each, tests whether Escape dismisses. It explicitly distinguishes itself from siblings by naming a11y_audit_dom and a11y_keyboard, so an agent can tell them apart without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit scope ('tooltips only'), names the alternative for full audits (a11y_audit_dom) and for keyboard traps (a11y_keyboard), and states the prerequisite (local Playwright). Nothing about when to pick this vs. a sibling is left to inference.

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

Deploy Server

Other Tools