skills.rest
denish12
denish12COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ui_a11y_smoke_review

Identify UI accessibility gaps in focus, ARIA labeling, and state coverage against the UX spec.

Updated Aug 23, 2026
Search Tags:#design#ui#accessibility#a11y#smoke-review#qa-hand-off
One-click install
npx skills add https://github.com/denish12/codex-ai-agent-and-skills --skill ui-a11y-smoke-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui_a11y_smoke_review
Source: https://github.com/denish12/codex-ai-agent-and-skills/tree/main/locales/en/.agents/skills/ui_a11y_smoke_review
Command: npx skills add https://github.com/denish12/codex-ai-agent-and-skills --skill ui-a11y-smoke-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick UI/a11y smoke review by a designer — loading/empty/error states, focus, keyboard, aria/labels, compliance with UX Spec. Executed BEFORE handoff to QA.

Core Features & Use Cases

  • Quick designer-level check of focus order, ARIA labeling, and state coverage against the UX spec.
  • Use during early handoff to QA to catch obvious accessibility issues before formal testing.
  • Example: review a prototype screen to confirm aria-labels and keyboard navigation.

Quick Start

Run a quick designer-level accessibility smoke review on the current UI prototype to verify focus, keyboard navigation, and aria attributes.

Frequently Asked Questions about ui_a11y_smoke_review

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

FAQPage Schema
How do I check UI accessibility before handing off to QA?▼

Run a fast UI accessibility smoke check before QA handoff to verify keyboard focus, ARIA labeling, and state coverage against the UX spec. It outputs a structured findings template for developers to resolve obvious issues early.

What is a UI a11y smoke review and when should I use it?▼

A UI a11y smoke review is a quick designer-level check of focus order, ARIA attributes, and state coverage against the UX spec. Use it during early handoff to QA to catch obvious accessibility issues before formal testing begins.

Can I verify loading, empty, error, and success states for accessibility compliance?▼

Yes, you can verify loading, empty, error, and success states for accessibility compliance. The review checks state coverage against the UX spec to ensure keyboard navigation and aria-labels meet the project's a11y baseline across multiple screens.

How do I review keyboard focus order and ARIA labeling in a UI prototype?▼

Review keyboard focus order and ARIA labeling in a UI prototype by running a designer-level accessibility check. It confirms focus navigation, validates aria attributes, and checks state coverage against the UX spec to meet baselines.

Does the accessibility smoke review require any specific testing dependencies?▼

No specific testing dependencies are required to run the accessibility smoke review. It operates as a standalone designer-level check to verify focus, keyboard navigation, and aria attributes before formal QA testing.

What is the best way to output accessibility findings for developers?▼

The best way to output accessibility findings for developers is using a structured findings template. The review generates this output after verifying keyboard focus, aria labeling, and state coverage to align with the project's a11y baseline.

Related Skills

Explore More Design & Creative Skills→
kay6198835kay6198835

ux-design

Create structured UX specifications for game screens, flows, and HUDs.

Community
Advanced
kiruna-labskiruna-labs
5

picky-tester

Simulate diverse user personas to generate structured friction logs with screenshots.

Official
Advanced
CaneproCanepro

design-system-maintenance

Align design tokens, primitives, and component APIs across products.

Community
Advanced
tom-xstom-xs

accessibility-selenium-testing

Automate WCAG 2.1/2.2 accessibility audits with Selenium WebDriver and axe-core.

Community
Advanced