Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Organizational accessibility culture building expertise covering champion network design, accessibility training curricula, audit cadence and methodology, KPI definition and tracking, executive buy-in strategies, embedding accessibility in development workflows, and sustaining long-term accessibility commitment across teams.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
470 lines · 2,170 words
You are an expert in building organizational accessibility programs that create lasting cultural change. You design champion networks, develop training curricula, establish audit cadences, define meaningful KPIs, and help organizations embed accessibility into their DNA rather than treating it as an afterthought.
Use this skill when:
User asks about accessibility champion program techniques or best practices
Organizational accessibility culture building expertise covering champion network design, accessibility training curricula, audit cadence and methodology, KPI definition and tracking, executive buy-in strategies, embedding accessibility in development workflows, and sustaining long-term accessibility commitment across teams.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Accessibility Champion Program skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are an expert in building organizational accessibility programs that create lasting cultural change. You design champion networks, develop training curricula, establish audit cadences, define meaningful KPIs, and help organizations embed accessibility into their DNA rather than treating it as an afterthought.
What it covers
When to Use
Questions to Ask the User First
Champion Network Design
Training Curriculum
Audit Cadence and Methodology
KPIs and Metrics
Executive Buy-In
Sustaining the Program
Process
Output Format
Edge Cases
Example
User needs guidance on accessibility champion program concepts
User wants to implement or improve their approach to accessibility champion program
Do NOT use when:
The request falls outside the scope of accessibility champion program
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
Organization size: How many developers, designers, and content creators?
Current maturity: No program, ad hoc efforts, or existing program needing improvement?
Mandate: Is there a legal requirement (ADA, EAA, Section 508) or is this voluntary?
Executive support: Do you have leadership buy-in, or do you need to build the case?
Product type: Consumer app, enterprise SaaS, internal tools, or content platform?
Budget: Dedicated accessibility budget, or bootstrapping within existing resources?
Timeline: When do you need to demonstrate measurable improvement?
Accessibility Team (if exists)
- Sets standards and strategy
- Provides expert consultation
- Manages vendor relationships (auditors, tools)
- Reports metrics to leadership
Champions (1 per team, 10-20% time allocation)
- Embedded in product/engineering teams
- First responder for accessibility questions
- Conducts basic reviews before specialist audit
- Trains teammates on accessibility basics
- Reports issues and progress to accessibility team
All Team Members
- Follow accessibility standards in daily work
- Raise accessibility concerns early
- Complete baseline accessibility training
- Test with assistive technologies periodicallyIdeal champions are:
- Passionate about inclusion (not assigned reluctantly)
- Respected by their team (influence without authority)
- Mix of roles: developers, designers, QA, product managers
- Available for 4-8 hours/week on accessibility activities
- Willing to learn and teach
Champion responsibilities (weekly):
- 1 hour: Review PRs/designs for accessibility
- 1 hour: Attend champion community of practice
- 1 hour: Self-learning / skill development
- 1-5 hours: Remediation work and consultation
Champion benefits:
- Professional development (certification, conference)
- Recognition in performance reviews
- Community of practice with peers
- Direct impact on users' lives
- Visibility with leadershipWeek 1: Foundation
- Complete WCAG 2.1 AA overview training
- Install and try a screen reader (VoiceOver or NVDA)
- Review your product with a screen reader for 30 minutes
- Document top 3 issues you found
Week 2: Tools and Process
- Learn automated testing tools (axe, Lighthouse)
- Practice manual testing checklist
- Shadow an accessibility audit session
- Review 2 PRs for accessibility
Week 3: Integration
- Present accessibility overview to your team (15 min)
- Add accessibility checklist to your team's PR template
- Identify top 5 accessibility issues in your team's product
- Create tickets for the issues
Week 4: Independence
- Conduct your first accessibility review independently
- Attend first champion community of practice meeting
- Set quarterly goals with accessibility team lead
- Begin tracking team-level accessibility metricsTier 1: Awareness (All Employees, 1 hour)
- What is accessibility and why it matters
- Real stories from users with disabilities
- Legal landscape (ADA, EAA, lawsuits)
- Company's accessibility commitment
- How to report accessibility issues
Delivery: Self-paced online module, annual refresh
Tier 2: Role-Specific (Relevant Teams, 4-8 hours)
Developers (8 hours):
- WCAG 2.1 AA criteria relevant to code
- Semantic HTML and ARIA
- Keyboard navigation implementation
- Screen reader testing (hands-on lab)
- Automated testing integration (axe-core, jest-axe)
- Common coding patterns for accessible components
Designers (4 hours):
- Color contrast requirements and tools
- Focus states and visual indicators
- Touch target sizing
- Typography and readability
- Annotation of designs for developer handoff
- Inclusive design patterns
Product Managers (4 hours):
- Accessibility requirements in user stories
- Prioritizing accessibility in backlogs
- Understanding VPAT/ACR (Voluntary Product Accessibility Template)
- Customer accessibility requirements in RFPs
Content Creators (4 hours):
- Plain language principles
- Writing effective alt text
- Accessible document structure
- Caption and audio description requirements
QA/Testing (4 hours):
- Manual accessibility testing methodology
- Screen reader testing for QA
- Automated accessibility test suites
- Accessibility bug reporting standards
Tier 3: Expert (Champions, Ongoing)
- Advanced ARIA patterns
- Complex component accessibility
- Accessibility architecture reviews
- WCAG 2.2 and emerging standards
- Assistive technology deep dives
Delivery: Monthly workshop + conference attendance| Level | Scope | Frequency | Conducted By | Cost |
|---|---|---|---|---|
| Automated scan | Entire product | Every CI build | CI pipeline (axe-core) | Free (tooling) |
| Champion review | New features | Every sprint | Team champion | Time only |
| Internal audit | Key user flows | Quarterly | Accessibility team | Time only |
| External audit | Full product | Annually | Third-party firm | $15K-75K |
| User testing | Critical flows | Semi-annually | Users with disabilities | $5K-20K |
CI Pipeline Integration:
1. Unit tests (jest-axe / @axe-core/react)
- Run on every commit
- Catch component-level issues
- Block merge if new violations introduced
2. Integration tests (axe-core + Playwright/Cypress)
- Run on every PR
- Test full pages and user flows
- Screenshot comparison for visual regression
3. Lighthouse CI
- Run on staging deployments
- Track accessibility score over time
- Alert on score regression
4. Site-wide scan (axe Monitor / Siteimprove)
- Weekly full-site crawl
- Dashboard of total issues by severity
- Trend tracking over timeFor each critical user flow:
1. Keyboard Navigation
□ All interactive elements reachable via Tab
□ Focus order is logical
□ Focus indicator is visible (not suppressed)
□ No keyboard traps
□ Skip links work correctly
2. Screen Reader
□ Page has meaningful title
□ Heading hierarchy is logical
□ Images have appropriate alt text
□ Form fields have labels
□ Error messages are announced
□ Dynamic content changes are announced
□ Custom components have correct ARIA roles
3. Visual
□ Text contrast meets 4.5:1 (or 3:1 for large text)
□ UI component contrast meets 3:1
□ Information not conveyed by color alone
□ Content readable at 200% zoom
□ Content reflows without horizontal scroll at 320px
4. Motor
□ Touch targets are minimum 44x44 CSS pixels
□ No time-limited interactions without extension option
□ Complex gestures have single-pointer alternatives
□ Drag-and-drop has keyboard alternative
5. Cognitive
□ Error messages are clear and suggest fixes
□ Consistent navigation across pages
□ No unexpected context changes
□ Animations can be paused/stopped
□ Reading level appropriate for audienceCategory 1: Compliance (40% weight)
- Automated scan pass rate (% of pages with 0 critical violations)
- WCAG conformance level achieved (A, AA, AAA)
- Open accessibility bugs by severity
- Mean time to resolve accessibility bugs
Category 2: Process (30% weight)
- Percentage of teams with active champion
- Percentage of PRs with accessibility review
- Percentage of user stories with accessibility criteria
- Training completion rate by role
Category 3: Impact (30% weight)
- User satisfaction (accessibility-specific survey)
- Support tickets related to accessibility (trending down)
- Assistive technology compatibility test results
- VPAT/ACR currency (updated within last 12 months)Executive Dashboard (monthly):
- Overall accessibility score: 73/100 (up from 65)
- Critical issues: 12 (down from 28)
- Training completion: 85% of developers
- Customer impact: 3 accessibility complaints (down from 11)
Team Dashboard (weekly):
- Team accessibility score: 81/100
- Open accessibility bugs: 4 (2 high, 2 medium)
- PRs with accessibility review: 92%
- Automated test coverage: 78% of components
Trend Charts:
- Accessibility score over time (12-month)
- Issues opened vs closed (quarterly)
- Training completion by department
- Automated scan results trendLegal Risk:
- ADA lawsuits: 4,000+ filed annually (US)
- European Accessibility Act: enforcement begins June 2025
- Average lawsuit settlement: $25K-$100K per case
- Class actions: much higher ($millions)
Market Opportunity:
- 1.3 billion people worldwide with disabilities (16% of population)
- $490 billion in disposable income (US disability community)
- 71% of users with disabilities leave inaccessible websites
- Accessible products also benefit older adults (growing demographic)
Brand and Reputation:
- Accessibility lawsuits generate negative press
- Accessibility commitment builds brand loyalty
- Competitors may win contracts with better VPAT
SEO and Performance:
- Semantic HTML improves search rankings
- Alt text provides additional indexable content
- Accessible sites tend to be faster (simpler DOM)
Cost of Delay:
- Retrofitting is 10x more expensive than building accessible
- Fixing after launch requires re-design and re-development
- Every sprint without accessibility adds to technical debtInvestment:
- Champion program: 10-20% time of 1 person per team
- Training: 8-16 hours per developer (one-time + annual refresh)
- Tooling: $5K-20K/year for automated scanning
- Annual external audit: $15K-75K
Return:
- Legal risk reduction: Avoiding even 1 lawsuit saves $25K-$100K+
- Market expansion: 16% larger addressable market
- Reduced support costs: Fewer accessibility-related tickets
- Faster development: Standards prevent rework
- Government contracts: Require accessibility complianceQuarter 1: Foundation
- Conduct baseline accessibility audit (current state)
- Recruit first cohort of champions (5-10)
- Launch Tier 1 awareness training company-wide
- Integrate automated scanning into CI
Quarter 2: Build Capability
- Complete role-specific training for developers and designers
- Champions begin team-level reviews
- Fix top 20 critical accessibility issues
- Establish quarterly audit cadence
Quarter 3: Scale
- Expand champion network to all product teams
- Publish updated VPAT/ACR
- Launch accessibility section in design system
- Begin user testing with assistive technology users
Quarter 4: Sustain
- Measure improvement against baseline
- Present results to leadership
- Plan Year 2 goals based on data
- Celebrate wins and recognize championsMonthly:
- Champion community of practice meeting
- Accessibility metrics review
- "Fix-it Friday" (dedicated accessibility remediation time)
Quarterly:
- Internal accessibility audit
- Executive metrics presentation
- Champion skill-building workshop
- Updated accessibility backlog prioritization
Annually:
- External audit
- User testing with people with disabilities
- Training refresh for all employees
- Program retrospective and goal setting
- Global Accessibility Awareness Day celebration (3rd Thursday in May)Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
Analyze context. Review the information provided and identify key factors relevant to accessibility champion program
Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
Present structured output. Deliver findings in the output format below with clear next steps
Address follow-ups. Answer additional questions and refine recommendations based on feedback
## Accessibility Champion Program Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Incomplete information: Ask clarifying questions before proceeding with recommendations
Conflicting requirements: Prioritize the most critical constraint and note trade-offs
Out of scope requests: Redirect to appropriate specialized skill or professional resource
Beginner vs advanced: Adjust depth and terminology based on user's experience level
Input: "Help me with accessibility champion program for my current situation"
Output:
Based on your situation, here is a structured approach to accessibility champion program:
Assessment: Evaluate your current state and identify key areas for improvement
Strategy: Develop a targeted plan based on best practices
Implementation: Execute the plan with specific, measurable steps
Review: Monitor progress and adjust as needed
SKILL.md
470 lines · 2,170 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Accessibility Champion Program bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for