90 skills · sorted by relevance
Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.
Review rendered HTML and replace generic div elements with elements that describe their purpose, such as main, nav, and article. Clarify page structure to support screen-reader navigation, search-engine understanding, and code maintenance.
Review whether ARIA roles, which describe interface elements to assistive technology, have the required parent roles. Find misplaced menu items, tabs, or list items, suggest suitable containers, and explain how to verify the corrected structure.
Audit web or mobile pages and user journeys against an agreed WCAG accessibility standard. Combine automated scans with manual checks to document barriers, prioritize fixes, and record retest results alongside any remaining gaps.
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces. Use when the user says: accessibility-audit, accessibility audit, a11y audit, a11y architect, wcag audit, wcag 2.2, wcag 2.2 aa, accessibility pass.
The English summary is being prepared. Showing the original description.
One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.
The English summary is being prepared. Showing the original description.
Review website animations against users’ reduced motion preferences, a setting that requests less movement. Check flashing content, scrolling effects, alternative transitions, pause controls, and advance warnings, and identify changes needed in rendered pages and interactive states.
Review website text and interface instructions for jargon, complex sentences, and unclear actions. Simplify wording, explain technical terms, and adjust reading difficulty so the intended audience can understand content and follow instructions.
Review HTML object elements and add meaningful fallback content for people who cannot load or view embedded material. Identify missing alternatives, suggest text or appropriate HTML elements, and explain how to verify accessibility.
Review parallax effects, where backgrounds and foregrounds move at different speeds. Check reduced-motion support and access to essential content, then suggest static alternatives and an optional site-wide control for disabling motion.
Review form fields for code that blocks pasting, then remove those restrictions. The skill helps check password manager use, keyboard interactions, and accessibility so people can paste passwords and other long values into inputs.
Review page landmarks, the named regions screen reader users navigate between. The skill checks semantic HTML elements, a single main content region, and labels for repeated region types, then identifies markup changes and ways to verify them.
Review whether interactive web elements work with keyboard navigation. Check Tab order, hidden elements, and focus traps where users cannot move away, then identify specific fixes and ways to verify behavior with browser accessibility tools or assistive technology.
Review links so their destinations are clear even without surrounding text. Identify vague wording, improve names announced by screen readers, and check keyboard behavior and download details such as file type and size.
Review HTML lists for incorrect child elements and nesting, then identify fixes that help screen readers, tools that read page content aloud, announce item counts and positions accurately.
Review modal dialogs for keyboard and screen reader accessibility. The skill checks dialog roles, title labels, focus movement within the modal, Escape dismissal, and focus returning to the opening control, then identifies issues and ways to verify fixes.
Compare button and link text with accessible names, the names assistive technology uses for controls. Identify mismatches and suggest ARIA label changes so people using voice control can refer to the words they see.
Review a page to ensure it has exactly one main landmark, the region identifying its primary content. Find missing or duplicate main regions and get corrections that give assistive technology users a clear navigation target.
Check HTML for meta refresh redirects that can interrupt reading and confuse users. Suggest server-side redirects or clear links users choose themselves, with guidance for checking the resulting behavior using accessibility tools or assistive technology.
Check form fields for duplicate labels that may confuse screen readers or voice control. Identify affected inputs and suggest consolidating labels or using aria-labelledby, an attribute that connects a field to multiple pieces of naming text.
Review form fields to ensure each has a properly connected label. Identify placeholder-only names and missing group headings, then guide markup fixes that help screen readers identify inputs and make labels clickable.
Review interface copy for assumptions about disability, gender, or culture. Suggest neutral wording, clearer instructions, and constructive error messages that guide people through problems without blaming them or relying on culturally specific expressions.
Review web page headings for skipped levels, unclear labels, and incorrect structure. Organize HTML headings around the content so people using screen readers can understand page sections and navigate between them.
Review iframe and frame titles so screen reader users can identify embedded content before entering it. Find missing or empty title attributes, add meaningful descriptions, and verify the changes with browser accessibility tools or assistive technology.