fixing-accessibility workflow skill. Use this skill when the user needs Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
fixing-accessibility
description
fixing-accessibility workflow skill. Use this skill when the user needs Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/fixing-accessibility from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses metadata.json plus ORIGIN.md as the provenance anchor for review.
fixing-accessibility Fix accessibility issues.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: how to use, common fixes, review guidance, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns
building forms, validation, error states, helper text
implementing keyboard shortcuts or custom interactions
working on focus states, focus trapping, or modal behavior
rendering icon-only controls
adding hover-only interactions or hidden content
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: how to use
/fixing-accessibility
Apply these constraints to any UI work in this conversation.
/fixing-accessibility <file>
Review the file against all rules below and report:
violations (quote the exact line or snippet)
why it matters (one short sentence)
a concrete fix (code-level suggestion)
Do not rewrite large parts of the UI. Prefer minimal, targeted fixes.
Examples
Example 1: Ask for the upstream workflow directly
Use @fixing-accessibility to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @fixing-accessibility against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @fixing-accessibility for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @fixing-accessibility using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
priority - category - impact
1 - accessible names - critical
2 - keyboard access - critical
3 - focus and dialogs - critical
4 - semantics - high
5 - forms and errors - high
6 - announcements - medium-high
Imported Operating Notes
Imported: rule categories by priority
priority
category
impact
1
accessible names
critical
2
keyboard access
critical
3
focus and dialogs
critical
4
semantics
high
5
forms and errors
high
6
announcements
medium-high
7
contrast and states
medium
8
media and motion
low-medium
9
tool boundaries
critical
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/fixing-accessibility, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@20-andruia-niche-intelligence-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@2d-games - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: quick reference
1. accessible names (critical)
every interactive control must have an accessible name
icon-only buttons must have aria-label or aria-labelledby
every input, select, and textarea must be labeled
links must have meaningful text (no “click here”)
decorative icons must be aria-hidden
2. keyboard access (critical)
do not use div or span as buttons without full keyboard support
all interactive elements must be reachable by Tab
focus must be visible for keyboard users
do not use tabindex greater than 0
Escape must close dialogs or overlays when applicable
3. focus and dialogs (critical)
modals must trap focus while open
restore focus to the trigger on close
set initial focus inside dialogs
opening a dialog should not scroll the page unexpectedly
4. semantics (high)
prefer native elements (button, a, input) over role-based hacks
if a role is used, required aria attributes must be present
lists must use ul or ol with li
do not skip heading levels
tables must use th for headers when applicable
5. forms and errors (high)
errors must be linked to fields using aria-describedby
required fields must be announced
invalid fields must set aria-invalid
helper text must be associated with inputs
disabled submit actions must explain why
6. announcements (medium-high)
critical form errors should use aria-live
loading states should use aria-busy or status text
toasts must not be the only way to convey critical information
expandable controls must use aria-expanded and aria-controls
7. contrast and states (medium)
ensure sufficient contrast for text and icons
hover-only interactions must have keyboard equivalents
disabled states must not rely on color alone
do not remove focus outlines without a visible replacement
8. media and motion (low-medium)
images must have correct alt text (meaningful or empty)
videos with speech should provide captions when relevant
respect prefers-reduced-motion for non-essential motion
avoid autoplaying media with sound
9. tool boundaries (critical)
prefer minimal changes, do not refactor unrelated code
do not add aria when native semantics already solve the problem
do not migrate UI libraries unless requested
Imported: common fixes
<!-- icon-only button: add aria-label --><!-- before --><button><svg>...</svg></button><!-- after --><buttonaria-label="Close"><svgaria-hidden="true">...</svg></button><!-- div as button: use native element --><!-- before --><divonclick="save()">Save</div><!-- after --><buttononclick="save()">Save</button><!-- form error: link with aria-describedby --><!-- before --><inputid="email" /><span>Invalid email</span><!-- after --><inputid="email"aria-describedby="email-err"aria-invalid="true" /><spanid="email-err">Invalid email</span>
Imported: review guidance
fix critical issues first (names, keyboard, focus, tool boundaries)
prefer native HTML before adding aria
quote the exact snippet, state the failure, propose a small fix
for complex widgets (menu, dialog, combobox), prefer established accessible primitives over custom behavior
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
