qa-detect-a11y

Detect accessibility defects in web pages via DOM inspection.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-a11y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-detect-a11y
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-detect-a11y
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify common accessibility failures in web interfaces before they reach users, reducing friction for keyboard and screen-reader navigation and preventing mobile usability regressions.

Core Features & Use Cases

  • Accessible name detection: Finds unnamed buttons and icon-only controls that lack labels for assistive technologies.
  • Baseline page accessibility checks: Flags missing language attributes, missing skip-to-content links, and unsafe viewport meta settings that break zoom or mobile scaling.
  • Use case: Run it on a web app after a UI release to catch missing labels, weak navigation support, and mobile accessibility issues across pages and viewports.

Quick Start

Use the qa-detect-a11y skill to scan the current page for accessibility issues and report any missing labels, language attributes, skip links, or viewport problems.

Frequently Asked Questions about qa-detect-a11y

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect unnamed buttons and missing aria-labels in my web app?

Accessibility scanning finds unnamed buttons and icon-only controls lacking labels for assistive technologies. It inspects the page DOM to identify interactive elements missing accessible names.

What's the best way to check for missing skip links and language attributes on a web page?

Baseline page accessibility checks flag missing skip-to-content links and language attributes. The scan reviews the DOM to ensure keyboard navigation support and proper screen reader metadata are present.

How can I prevent unsafe viewport settings from breaking mobile zoom accessibility?

Viewport-aware checks detect unsafe viewport meta settings that break zoom or mobile scaling. The scan audits these settings to prevent mobile accessibility regressions across responsive layouts.

Does this accessibility check work across mobile, tablet, and desktop viewports?

Yes, browser-based UI audits apply across mobile, tablet, laptop, and desktop screens. The checks distinguish true violations from hidden and off-screen elements across responsive layouts.

How does the scan handle false positives from chart libraries and hidden DOM elements?

DOM inspection distinguishes true accessibility violations from hidden, off-screen, and chart-library false positives. This prevents inaccurate reporting on complex interactive web components.