Audit digital content against WCAG 2.2 and implement accessibility fixes.
npx skills add https://github.com/webjetcms/basecms --skill wj-accessibility
Please help me install this Agent Skill. Skill: wj-accessibility Source: https://github.com/webjetcms/basecms/tree/main/.agents/skills/wj-accessibility Command: npx skills add https://github.com/webjetcms/basecms --skill wj-accessibility
Digital content often lacks sufficient accessibility, excluding people with disabilities. This skill provides WCAG 2.2-aligned guidance and practical patterns to audit and fix issues.
Audit a page for WCAG 2.2 compliance and apply the recommended pattern changes to improve accessibility.
High-intent search queries and answers about installing and using this skill.
To audit WCAG 2.2 compliance, evaluate digital content against POUR principles and success criteria. This process identifies accessibility issues and provides actionable steps using semantic HTML, ARIA patterns, and keyboard navigation fixes.
Implement accessible keyboard navigation by applying semantic HTML, correct ARIA usage, and focus management patterns. This ensures users can navigate digital content efficiently without a mouse, meeting WCAG 2.2 accessibility standards.
Yes, you can fix missing alt text and poor color contrast by applying the implementation patterns provided. The skill audits these specific issues and recommends concrete pattern changes to improve overall content accessibility.
Screen readers interact with ARIA live regions and semantic HTML by interpreting dynamic content updates and document structure. Correct ARIA usage and semantic markup ensure these updates are announced properly to users relying on assistive technologies.
WCAG 2.2 requires accessible authentication patterns that do not rely solely on cognitive function tests. This skill provides reference patterns to ensure authentication mechanisms meet current accessibility guidelines and supply actionable implementation steps.
Digital content fails accessibility checks for non-semantic markup because it lacks proper HTML structure and ARIA roles, preventing screen readers from interpreting elements correctly. Applying semantic HTML patterns resolves these compliance violations.
89jobrienAudit web content for WCAG 2.1/2.2 conformance and accessibility issues.
zero-rehqAudit frontend UI against 100+ Web Interface Guidelines rules for accessibility, UX, and performance gaps.
calcosmicEnforce semantic HTML, ARIA, color contrast, and flat CSS architecture.
zeronx798Navigate web pages and interact with DOM elements to detect functional, visual, accessibility issues via browser snapshots and console error monitoring, producing structured bug reports.
