# Plan an EU Accessibility Audit

Teams need to assess EU accessibility obligations and organize testing evidence. This guide frames scope assessment, WCAG review planning, remediation priorities, and draft accessibility statements.

## Install

```bash
npx skillstore add nexaiguy/nex-eu-accessibility-audit
```

## Metadata

- Status: approved
- Slug: nexaiguy-nex-eu-accessibility-audit
- Version: 1.0
- Author version: 1.0
- Skillstore revision: r1
- Version status: invalid
- Tree hash: b44f72532ad20692988250d280bc9f2aa1a38dff92ee41161593d6b50d2b92af
- Author: nexaiguy
- GitHub username: nexaiguy
- License: MIT
- Repository: https://github.com/nexaiguy/nex-ai-skills/tree/463aaff26593654193deb52f24d18e80ec21e323/skills/nex-eu-accessibility-audit
- Ref: 3ddfdca559084abffbfdd188f2ba14b597dcfd9c
- Supported tools: Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/nexaiguy-nex-eu-accessibility-audit
- Manifest: https://skillstore.pages.dev/api/skills/nexaiguy-nex-eu-accessibility-audit/manifest

## Capabilities

- Outlines EAA scope considerations, including service categories, product rules, micro-enterprise exemptions, and disproportionate burden.
- Defines WCAG 2.1 A and AA as the intended audit coverage.
- Identifies keyboard, screen reader, zoom, reflow, and automated scanning as testing areas.
- Describes prioritized remediation reports and illustrates a keyboard accessibility finding with a suggested fix.
- Frames draft accessibility statements with feedback mechanisms and enforcement contacts.

## Use Cases

- Assess an online shop: Organize business facts and unresolved questions for an EAA scope memo before commissioning a detailed audit.
- Plan checkout accessibility testing: Structure keyboard, screen reader, zoom, and reflow checks, then turn verified findings into remediation priorities.
- Prepare a draft accessibility statement: Summarize tested coverage, known barriers, feedback channels, and enforcement contacts for legal review.

## Prompt Templates

### Start a scope assessment

```
Help assess EAA scope for my business: [country, service, employee count, turnover]. Ask for missing facts and distinguish assumptions from conclusions.
```

### Plan a focused review

```
Plan a WCAG 2.1 AA review of [checkout flow]. Include keyboard, screen reader, zoom, and reflow checks. Mark all untested criteria explicitly.
```

### Prioritize verified barriers

```
Use these verified findings: [evidence]. Draft a remediation report with affected steps, relevant WCAG criteria, user impact, suggested fixes, and retest requirements.
```

### Prepare review documents

```
Using [business facts], [audit evidence], and [contact details], draft a scope memo and accessibility statement. Separate verified results, assumptions, exemptions, and legal questions.
```

## Limitations

- The supplied folder contains only a public guide, without the original scripts, extension source, or templates.
- The guide does not include detailed procedures for every WCAG success criterion or a complete reusable checklist.
- Actual findings require website access, suitable testing tools, and manual verification.
- Draft statements and scope assessments require legal review and do not certify compliance.

## Best Practices

- Record tested pages, user journeys, environments, and evidence before drafting findings.
- Combine automated checks with manual keyboard, screen reader, zoom, and reflow testing.
- Have qualified reviewers verify legal scope, exemption claims, and accessibility statements before publication.

## Anti Patterns

- Treating an AI-generated statement as proof of legal compliance.
- Claiming all WCAG criteria pass after automated scanning alone.
- Assuming the public guide includes executable audit tools or the original package templates.

## Security Audit

- Audited at: 2026-11-02T12:38:35.163\+00:00
- Summary: All four static findings are false positives: attribution links and accessibility audit descriptions do not constitute exfiltration or system reconnaissance. No evidence found of prompt injection, credential collection, executable payloads, or unauthorized data transfer in the supplied guide.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0