agentleFS
Sign inStart free
weselbenweselben/RooForge/skills/forge-eu-accessibility/SKILL.md

forge-eu-accessibility

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Load when building or auditing digital products for the EU market — accessibility work, WCAG compliance, accessibility statements — or when the user mentions BFSG, EAA, EN 301 549, or EU accessibility law.

The file

Create a free account to mount
Files
SKILL.md

EU Accessibility Compliance — BFSG / EAA / WCAG

Leading word: presumption of conformity. Compliance with EN 301 549 V3.2.1 (which includes WCAG 2.1 Level AA) creates a presumption of conformity with BFSG/BFSGV. That presumption is the target of every checklist item.

Framework-agnostic — no React, Vue, Angular, or Svelte-specific guidance. Apply the principles to any stack.

TL;DR

  1. Scope — Does the product/service fall under BFSG § 1 Abs. 2 (products) or § 1 Abs. 3 (services)?
  2. Baseline — WCAG 2.1 Level AA via EN 301 549 V3.2.1 is the binding technical standard.
  3. Documentation — Prepare an accessibility statement (BFSG Anlage 3) and keep assessments for 5 years.
  4. Penalties — Up to €100,000 for serious violations (§ 37 BFSG).
  5. Verification — Use the harness's WebSearch / FetchURL tools to check live legal sources before making compliance claims.

Applicability scope

BFSG § 1 Abs. 2 — Products (placed on market after 28 June 2025)

  1. Consumer general-purpose computer hardware systems and operating systems.
  2. Self-service terminals (payment, ATMs, ticketing, check-in, interactive info).
  3. Consumer terminal equipment for electronic communications services.
  4. Consumer terminal equipment for audiovisual media services.
  5. E-book readers.

BFSG § 1 Abs. 3 — Services (provided to consumers after 28 June 2025)

  1. Electronic communications services (excluding machine-to-machine).
  2. Passenger transport services (air, bus, rail, waterborne): websites, mobile apps, e-tickets, real-time travel info, interactive terminals.
  3. Consumer banking services.
  4. E-books and dedicated software.
  5. E-commerce services (websites and mobile apps for consumer contracts).

Exclusions

  • Pre-recorded time-based media and office file formats published before 28 June 2025.
  • Online maps (if essential navigational info is provided in an accessible digital manner).
  • Third-party content not funded, developed, or controlled by the economic operator.
  • Archive content (not updated or edited after 28 June 2025).
  • Microenterprises (fewer than 10 persons, annual turnover/balance sheet ≤ €2 million) providing services are exempt from service requirements. Product requirements still apply if they place products on the market.

Legal framework

LawRoleKey Reference
BFSGGerman national transposition of EAA; adds enforcement, penalties, market surveillance§ 1 (scope), § 3 (accessibility), § 37 (penalties), § 14 (service provider obligations)
EAA Directive 2019/882EU directive harmonizing accessibility requirements across the internal marketArticle 2 (scope), Article 4 (requirements), Article 13 (service obligations), Article 14 (disproportionate burden), Article 30 (penalties)
BFSGVGerman ordinance specifying concrete technical requirements implementing Annex I of Directive 2019/882§ 12 (general service requirements), § 4–6 (product requirements), § 20–21 (functional performance criteria)
EN 301 549 V3.2.1Harmonized European standard for ICT accessibility; incorporates WCAG 2.1 Level AAPresumption of conformity under § 4 BFSG / Article 15 EAA
BGBGeneral civil law underpinning contractual and tort liability for accessibility barriers§ 241 (duty of consideration), § 275 (disproportionate burden analog), § 307 (content control of T&Cs), § 823 (tort liability)

Penalties — § 37 BFSG

  • Up to €100,000 for serious violations: placing non-compliant products on the market, providing non-compliant services, missing or incorrect CE marking.
  • Up to €10,000 for other violations (missing/incorrect documentation, information, labeling).

Market surveillance authorities may check services without cause, order corrective measures, and prohibit service operation if non-compliance persists (§ 28–31 BFSG).

Technical baseline — WCAG 2.1 Level AA via EN 301 549 V3.2.1

BFSGV § 12 requires content to be Perceivable, Operable, Understandable, Robust (the four WCAG principles). The BFSGV functional performance criteria (§ 21) also require usage without vision, with limited vision, without color perception, without hearing, with limited hearing, without vocal capability, with limited manipulation/strength, with limited reach, minimizing photosensitive seizure risk, with limited cognition, and privacy protection.

Practical compliance checklist

The full framework-agnostic checklist — perceivable, operable, understandable, robust, documentation/transparency, testing — lives in references/compliance-checklist.md. Load it when auditing or building; every item maps to the WCAG 2.1 AA baseline.

Key non-obvious items:

  • No overlay plugins as sole solution — third-party accessibility overlay widgets are not sufficient to meet BFSG requirements. Native accessibility in design and code is required.
  • Accessibility statement — published in an accessible format, clearly noticeable (footer, alongside imprint and privacy policy), per BFSG Anlage 3.
  • Document accessibility — PDFs provided as part of the service must be accessible (PDF/UA, tagged PDFs, alt text).

Exceptions and exemptions

Fundamental alteration (BFSG § 16 / EAA Article 14)

Requirements apply only to the extent that compliance does not require a fundamental alteration of the product or service's basic nature. The economic operator must assess and document this, keeping the assessment for 5 years.

Disproportionate burden (BFSG § 17 / EAA Article 14)

Requirements apply only to the extent that compliance does not impose a disproportionate burden. Assessment criteria are in BFSG Anlage 4. Service providers must renew the assessment at least every 5 years, or when the service is altered or requested by authorities. Operators receiving public or private funding for accessibility improvements cannot rely on this exemption.

Live legal source verification

Always verify current legal texts before making compliance claims. Laws and ordinances may be amended. Use the harness's WebSearch tool for queries and FetchURL to read the official sources below.

Key official sources

Example verification queries

  • BFSG § 37 Barrierefreiheitsstärkungsgesetz Bußgeld 2025
  • EAA Directive 2019/882 Article 13 service provider obligations
  • EN 301 549 V3.2.1 WCAG 2.1 Level AA

Conventions

  • Framework-agnostic — no framework-specific implementation guidance.
  • No overlay plugins — never recommend accessibility overlay widgets as a compliance solution.
  • Document everything — accessibility statements, assessments, and conformity claims must be kept for the duration of the service plus 5 years for products.
  • Penalties are real — non-compliance can result in service prohibition orders and fines up to €100,000.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free