PixelPilot: Instructions file for GitHub Copilot

UI/UX Accessibility Statement Generator

Generate professional WCAG compliance statements. Includes all required sections per W3C template.

OVERVIEW

This skill generates accessibility statements that include:

1. Conformance status
2. Scope and limitations
3. Testing methodology
4. Known issues and remediation
5. Contact information
6. Formal compliance language

TEMPLATE

# Accessibility Statement for {{ config('app.name') }}

**Last Updated**: {{ date('F j, Y') }}

---

## Our Commitment

{{ config('app.name') }} is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

---

## Conformance Status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities.

**Current Status**: {{ CONFORMANCE_LEVEL }}

- **WCAG 2.1 Level AA**: {{ STATUS }}
- **Target Date**: {{ TARGET_DATE }}
- **Last Audit**: {{ AUDIT_DATE }}

### Conformance Levels Explained

| Level | Description |
|-------|-------------|
| **Level A** | Essential accessibility features |
| **Level AA** | Addresses major barriers (our target) |
| **Level AAA** | Highest level of accessibility |

---

## Scope

This accessibility statement applies to the following:

### Included
{{ SCOPE_INCLUDED }}

### Not Included
{{ SCOPE_EXCLUDED }}

---

## Technical Specifications

This website relies on the following technologies for conformance:

- HTML5
- CSS3
- JavaScript
- WAI-ARIA 1.2
- SVG

The website is designed to be compatible with the following assistive technologies:

- Screen readers (NVDA, JAWS, VoiceOver)
- Screen magnification software
- Speech recognition software
- Keyboard-only navigation

---

## Known Limitations

While we strive for WCAG 2.1 Level AA conformance, some content may have accessibility limitations:

{{ KNOWN_LIMITATIONS_TABLE }}

We are actively working to address these issues.

---

## Testing Methodology

Our accessibility testing includes:

### Automated Testing
- **axe-core** - Automated accessibility scanner
- **WAVE** - Web accessibility evaluation tool
- **Lighthouse** - Performance and accessibility audits
- **Pa11y** - Automated accessibility testing

### Manual Testing
- Keyboard navigation testing
- Screen reader testing (NVDA, VoiceOver)
- Color contrast verification
- Focus management review
- Form validation accessibility

### User Testing
- Usability testing with people with disabilities
- Feedback collection and analysis

---

## Feedback and Contact

We welcome your feedback on the accessibility of {{ config('app.name') }}. Please let us know if you encounter accessibility barriers:

**Accessibility Contact**:
- Email: {{ ACCESSIBILITY_EMAIL }}
- Phone: {{ ACCESSIBILITY_PHONE }}
- Address: {{ ACCESSIBILITY_ADDRESS }}

**Response Time**: We aim to respond within {{ RESPONSE_TIME }} business days.

---

## Formal Complaints

If you are not satisfied with our response, you may escalate your complaint to:

{{ COMPLAINT_AUTHORITY }}

---

## Assessment and Audit History

| Date | Auditor | Scope | Result |
|------|---------|-------|--------|
{{ AUDIT_HISTORY }}

---

## Remediation Plan

We have an ongoing accessibility improvement plan:

{{ REMEDIATION_PLAN }}

---

## Additional Resources

- [Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/)
- [How to Meet WCAG (Quick Reference)](https://www.w3.org/WAI/WCAG21/quickref/)
- [Understanding WCAG 2.1](https://www.w3.org/WAI/WCAG21/Understanding/)

---

*This statement was created on {{ CREATION_DATE }} and was last reviewed on {{ LAST_REVIEW_DATE }}.*