Audit web pages and UI components against WCAG 2.2 accessibility criteria.
npx skills add https://github.com/jtgiron/portfolio --skill accessibility-jtgiron
Please help me install this Agent Skill. Skill: accessibility Source: https://github.com/jtgiron/portfolio/tree/main/.agents/skills/accessibility Command: npx skills add https://github.com/jtgiron/portfolio --skill accessibility-jtgiron
This Skill helps teams find and fix accessibility barriers so websites and interfaces work for people using keyboards, screen readers, low-vision settings, and other assistive technologies.
Ask the accessibility skill to audit the attached page or component and return WCAG 2.2 issues with specific fixes.
High-intent search queries and answers about installing and using this skill.
You audit pages and components against WCAG 2.2 criteria including contrast, labels, focus order, media alternatives, and keyboard support. This process identifies barriers and provides specific HTML, ARIA, and CSS fixes to resolve them.
Fixing keyboard navigation and screen reader support requires semantic HTML, correct ARIA usage, and visible focus states. You implement skip links, manage live regions, and ensure logical focus order to eliminate keyboard traps and improve assistive technology interaction.
Checking color contrast and form labels involves validating UI elements against WCAG 2.2 standards. This ensures text meets minimum contrast ratios and all form inputs have properly associated labels for users relying on screen readers and low-vision settings.
Yes, this accessibility review covers dynamic interface patterns and reduced-motion support. It evaluates dialogs, live updates, and motion handling to ensure interfaces work for users with vestibular disorders and those navigating via assistive technologies.
ARIA live regions fail to announce updates when implemented with incorrect ARIA roles or non-semantic HTML. Auditing dynamic interface patterns ensures correct ARIA usage so screen readers properly detect and vocalize live content changes.
Yes, you can get step-by-step HTML and ARIA fixes for an inaccessible checkout flow. The review identifies missing labels, poor focus states, and keyboard traps, then returns targeted implementation guidance to resolve issues before release.
ehmoEnforce WCAG 2.2, ARIA, and responsive design guidelines in web UI reviews.
thec3ukGuide frontend code to meet accessibility standards like ARIA and keyboard navigation.
MAX5271Audit CometChat UI Kit integrations for WCAG 2.1 AA accessibility compliance.
leboncoinAutomate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.
