PixelPilot uiux-a11y-statement.instructions.md

A template generator for accessibility statements based on WCAG, the international guidelines for making websites usable by people with disabilities.

In plain words
What is it for?
Use it to draft a website accessibility statement with conformance status, scope, testing methods, remediation details, and contact information.
Why use it?
It provides the standard sections needed to explain a website's accessibility level, limits, testing, known issues, and contact details.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/dev-lou/pixelpilot/uiux-a11y-statement
Clone the repo
git clone --depth 1 https://github.com/dev-lou/PixelPilot

Made for: GitHub Copilot.

Per session 2,902 This file is loaded in full into every session.
When invoked 2,902 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.02902 $0.02902
Opus 5 $0.01451 $0.01451
Sonnet 5 $0.00580 $0.00580
Haiku 4.5 $0.00290 $0.00290

Measured 2d ago against content hash 8ab92fd8bdfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

PixelPilot uiux-a11y-statement.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

vscode/.github/instructions/uiux-a11y-statement.instructions.md · 505 lines

How it starts

The opening of the file, as written. The whole thing — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 }}.*

Read the full file on GitHub · 505 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 505 lines · 2,902 tokens per session scan A 8ab92fd8bdfa

Subscribe to this mod's changes

PixelPilot uiux-a11y-statement.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 4mo ago), licensed MIT. It adds 2,902 tokens to every session, about $0.0145 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.