Run any Skill in Manus with one click

a11y-auditor

Stars168

Forks52

UpdatedApril 14, 2026 at 14:51

Audit web pages for accessibility issues in a real browser. Checks contrast, font sizes, focus indicators, keyboard navigation, ARIA labels, and semantic HTML against WCAG 2.1 AA. Reports findings with screenshots and specific remediation steps. Requires the hanzi browser automation MCP server and Chrome extension.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hanzili

hanzili/hanzi-browse

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	a11y-auditor
description	Audit web pages for accessibility issues in a real browser. Checks contrast, font sizes, focus indicators, keyboard navigation, ARIA labels, and semantic HTML against WCAG 2.1 AA. Reports findings with screenshots and specific remediation steps. Requires the hanzi browser automation MCP server and Chrome extension.
category	productivity

Accessibility Auditor

You audit web pages for accessibility issues using a real browser — real contrast, real tab order, real focus indicators, real screen reader semantics. This skill is read-only: observe and report, don't modify.

Tool Selection Rule

Prefer existing tools first (code search, local files). Review ARIA usage and semantic HTML before opening the browser.
Use Hanzi only for browser-required steps: visual checks, keyboard navigation, focus behavior.

Before Starting

Call browser_status to verify the extension is reachable. If unavailable, tell the user to install from: https://chromewebstore.google.com/detail/hanzi-browse/iklpkemlmbhemkiojndpbhoakgikpmcd

What You Need

URL — page or site to audit 2. Scope — single page, flow, or full site 3. Standard — defaults to WCAG 2.1 AA

Audit Phases

Phase 1 — Codebase Review (before browser): Scan for ARIA usage, semantic HTML (<div> vs <button>/<nav>/<main>), image alt text, form labels, heading hierarchy. Summarize before opening browser.

Phase 2 — Visual (browser): Check color contrast (4.5:1 normal, 3:1 large text), font sizes (min 12px), focus indicators (tab through page), touch targets (24×24px min), motion/animation. Screenshot each area.

Phase 3 — Keyboard (browser): Test tab order, focus traps in modals/dropdowns, keyboard operability (Enter/Space), skip links. Screenshot problematic focus states.

Phase 4 — ARIA & Semantics (browser): Verify landmarks, form label associations, dynamic content announcements (aria-live), image/icon accessible names, table headers.

Report Format

Categorize issues as Critical / Serious / Moderate / Minor with: element/location, impact, WCAG criterion, specific fix, screenshot. List passing checks. For each issue with source access, include file, specific fix, and complexity estimate. End with severity totals and top 3 priorities.

Rules

One page/flow at a time — screenshot every issue found
Be specific ("the search button" not "a button") and cite WCAG criteria (e.g., 1.4.3)
Don't report unverified issues — if unsure, say so
If browser_start times out, call browser_screenshot to diagnose

More from this repository

same repository

apartment-finder

hanzili/hanzi-browse

Search for apartments across multiple real estate platforms, compare listings side by side, and help submit inquiries or applications. Use when the user wants to find a place to rent — searching Zillow, Apartments.com, Craigslist, and similar sites with their real signed-in browser. Examples: "find me a 1BR in Boston under $2000", "search apartments near downtown Seattle and compare options", "help me apply to these listings".

2026-04-25168

hanzi-browse

hanzili/hanzi-browse

Delegates a browsing task to a sub-agent running in the USER'S OWN Chrome — the browser they have open right now, already signed into everything. Give it a task in natural language ("check my LinkedIn DMs", "post this reply on X", "test signup on localhost:3000") and watch the sub-agent with browser_status, steer it with browser_message, stop it with browser_stop. This is the ONLY tool that can access the web AS THE USER themselves — with their logins, sessions, and state. Reach for it whenever the task needs the user's real identity on a site, or when WebFetch / Tavily / Exa returned empty or hit a login wall.

2026-04-14168

competitor-monitor

hanzili/hanzi-browse

Monitor competitor websites for changes. Visit a list of URLs, extract pricing, features, positioning, and key content, compare against previous snapshots stored locally, and generate a change report summarizing what's different. Use when the user says "check competitors", "what changed on their site", "monitor these URLs", or wants periodic competitive intelligence. Requires the hanzi browser automation MCP server and Chrome extension.

2026-04-14168

competitor-researcher

hanzili/hanzi-browse

Research SaaS and AI-tool competitors in a real browser. Visit competitor sites, pricing pages, feature pages, and review platforms to extract pricing, features, positioning, and customer sentiment, then return a structured comparison report. Use when the user wants competitor analysis, market landscape research, pricing comparisons, feature comparisons, or review synthesis.

2026-04-14168

data-extractor

hanzili/hanzi-browse

Extract structured data from websites into CSV or JSON. Use when the user wants to scrape a list, table, directory, or repeated elements from one or more pages — especially pages that require login, handle CAPTCHAs, or load content dynamically. Examples: "pull all company names and emails from this directory", "export this table to CSV", "collect job listings from my recruiter dashboard".

2026-04-14168

e2e-tester

hanzili/hanzi-browse

Test a web app like a QA person — open it in a real browser, click through flows, and report what's broken with screenshots and code references. Works on localhost. Use when the user wants to test their app, verify a flow works, check for visual bugs, or validate changes before pushing.

2026-04-14168

name	a11y-auditor
description	Audit web pages for accessibility issues in a real browser. Checks contrast, font sizes, focus indicators, keyboard navigation, ARIA labels, and semantic HTML against WCAG 2.1 AA. Reports findings with screenshots and specific remediation steps. Requires the hanzi browser automation MCP server and Chrome extension.
category	productivity

Accessibility Auditor

Tool Selection Rule

Prefer existing tools first (code search, local files). Review ARIA usage and semantic HTML before opening the browser.
Use Hanzi only for browser-required steps: visual checks, keyboard navigation, focus behavior.

Before Starting

Call browser_status to verify the extension is reachable. If unavailable, tell the user to install from: https://chromewebstore.google.com/detail/hanzi-browse/iklpkemlmbhemkiojndpbhoakgikpmcd

What You Need

URL — page or site to audit 2. Scope — single page, flow, or full site 3. Standard — defaults to WCAG 2.1 AA

Audit Phases

Phase 3 — Keyboard (browser): Test tab order, focus traps in modals/dropdowns, keyboard operability (Enter/Space), skip links. Screenshot problematic focus states.

Phase 4 — ARIA & Semantics (browser): Verify landmarks, form label associations, dynamic content announcements (aria-live), image/icon accessible names, table headers.

Report Format

Rules

One page/flow at a time — screenshot every issue found
Be specific ("the search button" not "a button") and cite WCAG criteria (e.g., 1.4.3)
Don't report unverified issues — if unsure, say so
If browser_start times out, call browser_screenshot to diagnose