Skip to main content
Glama
kinti

a11y-toolkit

by kinti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

a11y-toolkit: 320px reflow check

a11y_reflow
Read-onlyIdempotent

Check web pages at 320px viewport for horizontal scroll to confirm WCAG 1.4.10 reflow compliance, listing the overflowing elements.

Instructions

Reflow check at 320px — criterion 1.4.10 (AA), the check axe and Lighthouse do not automate. Loads the URL at 1280px, then at 320px, and reports real horizontal scroll + the overflowing elements. Method note: browser zoom RE-LAYS OUT at 320 CSS px (that is the standard's own equivalence: 1280 @ 400% zoom = 320px), so the correct measurement is a 320px viewport. Requires local Playwright. — Scope: 320px reflow only (1.4.10); for the full rendered pass use a11y_audit_dom.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPage URL to test at 320px (http/https or file://)
langNoOutput language (default en)
timeoutNoPage load timeout in seconds (default 45)
auth_stateNoPath to a Playwright storage_state JSON (exported session) to test behind login

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.0.0
    • addedInput schema / browser
      Added value: +{
+  "description": "Browser engine (auto = detect the first available)",
+  "enum": [
+    "auto",
+    "chromium",
+    "firefox",
+    "webkit",
+    "chrome",
+    "msedge"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / auth_state
      Added value: +{
+  "description": "Path to a Playwright storage_state JSON (exported session) to test behind login",
+  "type": "string"
+}
    • addedInput schema / properties / lang / description
      Added value: +"Output language (default en)"
    • addedInput schema / properties / timeout / description
      Added value: +"Page load timeout in seconds (default 45)"
    • addedInput schema / properties / url / description
      Added value: +"Page URL to test at 320px (http/https or file://)"
  2. Addedv3.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral context beyond that: it loads the URL at two viewports (1280px and 320px), reports horizontal scroll and overflowing elements, and states the local Playwright requirement. No contradiction exists.

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

Conciseness5/5

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

The description is front-loaded with the core purpose and scope, then adds the method note and prerequisite. Each sentence earns its place—there is no filler or repetition. The structure flows logically from what it does to how to do it correctly.

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?

For a read-only test tool with no output schema, the description is complete: it explains what is measured, what is reported (real horizontal scroll + overflowing elements), the scope (1.4.10 only), and the alternative tool for broader coverage. Nothing an agent needs to call it correctly is missing.

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 all four parameters (url, lang, timeout, auth_state) are documented in the schema. The description only implicitly references url ('Loads the URL') and does not add any param-specific guidance or format details, so it stays at the baseline for full schema coverage.

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 states a specific verb and resource: 'Reflow check at 320px' targeting criterion 1.4.10, and explicitly differentiates from siblings by noting it is the check axe and Lighthouse do not automate. It also names the sibling a11y_audit_dom as the alternative for a full rendered pass, making the tool's purpose unambiguous.

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?

It explicitly directs the agent to use a11y_audit_dom for the full rendered pass, and explains the correct measurement method (1280 @ 400% zoom = 320px) to avoid misinterpretation. The 'Requires local Playwright' prerequisite further clarifies when the tool is applicable.

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