oliver-accessibilityEnhances web accessibility by ensuring semantic HTML, ARIA roles, keyboard navigation, focus management, and screen reader support per WCAG guidelines.
Install via ClawdBot CLI:
clawdbot install wangzhiming1999/oliver-accessibilityGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/wangzhiming1999/oliver-skill/issuesAudited Apr 21, 2026 · audit v1.0
Generated May 3, 2026
Audit existing web pages or applications for WCAG 2.1 AA compliance, identify issues like missing ARIA labels, keyboard traps, or low contrast, and provide detailed remediation steps with code examples.
Generate or review code for custom UI components (modals, dropdowns, tabs) to ensure they follow a11y best practices: proper roles, keyboard navigation, focus management, and screen reader support.
Evaluate design mockups or prototypes for a11y issues such as color contrast, focus indicators, and semantic structure, providing actionable recommendations before development begins.
Test and improve how content is announced by screen readers (e.g., NVDA, VoiceOver) by adding aria-live regions, proper headings, and descriptive labels for dynamic updates.
Ensure all interactive elements are reachable and operable via keyboard only, fix focus order, implement focus trapping in modals, and add visual focus styles.
Provide accessibility audit services per project, charging a flat fee or hourly rate for reviewing code/designs and delivering remediation reports.
Offer workshops or online courses teaching developers and designers how to implement a11y best practices, with tiered pricing for individuals or teams.
Integrate as a premium service within development agencies or platforms, charging an extra 15-30% on projects to ensure WCAG compliance.
💬 Integration Tip
Use the skill to automatically generate a11y reports from code snippets or design specs, integrating with CI/CD pipelines via comment-friendly output.
Scored Apr 21, 2026
Frontend development with React, Next.js, Tailwind CSS. Build landing pages, dashboards, forms, components. Responsive, accessible, performant UI.
Create distinctive, production-grade static sites with React, Tailwind CSS, and shadcn/ui — no mockups needed. Generates bold, memorable designs from plain text requirements with anti-AI-slop aesthetics, mobile-first responsive patterns, and single-file bundling. Use when building landing pages, marketing sites, portfolios, dashboards, or any static web UI. Supports both Vite (pure static) and Next.js (Vercel deploy) workflows.
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Generate landing page content from PRD — hero section, features, A/B headline variants, CTA, and SEO meta tags. Use when user says "create landing page", "wr...
Scaffold a new presale service foundation (docs/config/plans/readiness) before coding. Use when starting a new presale automation service, rebuilding project...
Tailwind reference tool. Use when working with tailwind in frontend contexts.