Skip to main content
Back to the directory
ibelick/ui-skillsSoftware EngineeringFrontend and Design

fixing-accessibility

Audit and fix HTML accessibility issues across ARIA labels, keyboard navigation, focus management, and WCAG compliance.

SkillJury keeps community verdicts, source metadata, and external repository signals in separate lanes so ranking data never pretends to be a review.

SkillJury verdict
Pending

No approved reviews yet

Would recommend
Pending

Waiting on enough review volume

Install signal
10

Weekly or total install activity from catalog data

Sign in to review
0 review requests
Install command
npx skills add https://github.com/ibelick/ui-skills --skill fixing-accessibility
SkillJury does not have enough approved reviews to publish a community verdict yet. Source metadata and repository proof are still available above.
SkillJury Signal Summary

As of Apr 30, 2026, fixing-accessibility has 10 weekly installs, 0 community reviews on SkillJury. Community votes currently stand at 0 upvotes and 0 downvotes. Source: ibelick/ui-skills. Canonical URL: https://skills.sh/ibelick/ui-skills/fixing-accessibility.

Security audits
Gen Agent Trust HubPASS
SocketPASS
SnykPASS
About this skill
Audit and fix HTML accessibility issues across ARIA labels, keyboard navigation, focus management, and WCAG compliance. Fix accessibility issues. /fixing-accessibility Apply these constraints to any UI work in this conversation. /fixing-accessibility Review the file against all rules below and report: Do not rewrite large parts of the UI. Prefer minimal, targeted fixes. Reference these guidelines when: - Covers nine rule categories prioritized by impact: accessible names, keyboard access, focus management, semantics, forms and errors, announcements, contrast, media, and tool boundaries - Provides targeted fixes for common patterns like icon-only buttons, form error linking, and focus trapping in modals - Includes quick reference for when to apply (interactive controls, forms, dialogs, custom interactions) and common code-level fixes with before/after examples - Emphasizes minimal, surgical changes over large UI rewrites and prefers native HTML elements over ARIA workarounds - /fixing-accessibility Apply these constraints to any UI work in this conversation. - /fixing-accessibility 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) - adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns - building forms, validation, error states,...

Source description provided by the upstream listing. Community review signal and install context stay separate from this narrative layer.

Community reviews

Latest reviews

No community reviews yet. Be the first to review.

Browse this skill in context
FAQ
What does fixing-accessibility do?

Audit and fix HTML accessibility issues across ARIA labels, keyboard navigation, focus management, and WCAG compliance.

Is fixing-accessibility good?

fixing-accessibility does not have approved reviews yet, so SkillJury cannot publish a community verdict.

Which AI agents support fixing-accessibility?

fixing-accessibility currently lists compatibility with Skills CLI.

Is fixing-accessibility safe to install?

fixing-accessibility has been scanned by security audit providers tracked on SkillJury. Check the security audits section on this page for detailed results from Socket.dev and Snyk.

What are alternatives to fixing-accessibility?

Skills in the same category include grimoire-morpho-blue, conversation-memory, second-brain-ingest, zai-tts.

How do I install fixing-accessibility?

Run the following command to install fixing-accessibility: npx skills add https://github.com/ibelick/ui-skills --skill fixing-accessibility

Related skills

More from ibelick/ui-skills

Related skills

Alternatives in Software Engineering