skills.rest
Luqman-Ud-Din
Luqman-Ud-DinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-form-a11y

Inspect web forms for accessibility defects in labels, aria attributes, and focus order.

Updated May 22, 2026
Search Tags:#accessibility#browser automation#wcag#forms#ui testing#aria
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-form-a11y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-form-a11y
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-form-a11y
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-form-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes accessibility checks for form controls so labels, required-state cues, error announcements, fieldset semantics, and password toggles are verified consistently instead of being missed across multiple detectors.

Core Features & Use Cases

  • Label coverage: Flags inputs, textareas, and selects that lack a real label or equivalent accessible name.
  • Error and required-state clarity: Detects errors that will not be announced by assistive tech and required fields that rely on color alone or omit visible indicators.
  • Form structure and interaction checks: Finds missing fieldset legends, password fields without show/hide controls, and focus order that does not match the visual layout.
  • Use case: Run it on a login, signup, checkout, or admin form to catch accessibility regressions before release.

Quick Start

Use the qa-form-a11y skill to inspect the current page for form accessibility issues and return a concise list of findings with selectors and explanations.

Frequently Asked Questions about qa-form-a11y

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

FAQPage Schema
How do I check web form accessibility for missing ARIA attributes and labels?▼

Form accessibility testing detects unannounced errors by validating ARIA attributes, required-state cues, and fieldset legends through browser-side DOM inspection, ensuring assistive technology receives proper error announcements.

How do I automate UI testing for WCAG compliance in multi-step form workflows?▼

Automating UI testing for WCAG compliance in multi-step workflows involves browser-side DOM inspection to verify focus order matches visual layout, password toggles exist, and interactive controls meet accessibility standards.

Does browser automation detect required fields that rely on color alone for form accessibility?▼

Browser automation detects required fields relying on color alone by inspecting the DOM for missing visible indicators and ensuring required-state cues are announced properly to assistive technology.

Can I test checkout and admin form accessibility with automated DOM inspection?▼

You can test checkout and admin form accessibility with automated DOM inspection that evaluates password show/hide controls, focus order, and label coverage across common UI component libraries.

Why are my form error states not announced by screen readers during accessibility testing?▼

Form error states go unannounced by screen readers when ARIA attributes are missing or misconfigured, which automated accessibility testing detects by validating error announcements against DOM structure.

Related Skills

Explore More Software Engineering Skills→
xg-gh-25xg-gh-25
36

browser-agent

Automate DOM-based browser interactions with Playwright via CDP.

Community
Advanced
MinhDuyDEVMinhDuyDEV

accessibility-audit

Audit web interfaces for WCAG compliance issues and remediation recommendations.

Community
Intermediate
yahav123147yahav123147

web-accessibility

Implement ARIA semantics, keyboard navigation, and accessible form patterns for React components.

Community
Intermediate
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced