Accessibility Statement

I want my own pages to hold up to what I sell to my clients. This statement explains how accessible the pages on einfach-gute-webseiten.de are, how I tested them, and what is still open.

Scope of this statement

This statement covers all twelve pages of the site, the German ones as well as the English ones under /en/

  • Home page
  • Moving from RapidWeaver Classic to Elements
  • Web accessibility services
  • Site notice
  • Privacy policy
  • Accessibility
  • Startseite (German)
  • Umstieg von RapidWeaver Classic (German)
  • Webseite barrierefrei machen (German)
  • Impressum (German) 
  • Datenschutzerklärung (German)
  • Barrierefreiheit (German)

Conformance status

Based on my own review of 18 August 2026, these pages are conformant with the Web Content Accessibility Guidelines 2.2 at Level AA. No violation was found on any of the twelve pages.

I also reviewed the pages against the European standard EN 301 549, using version V3.2.1, which is the version currently referenced in law. For a website, clauses 9 and 12 apply, and both are met. The remaining clauses address
hardware, telephony, software and non-web documents, none of which apply here.

Why this is voluntary

I am a sole trader and therefore a microenterprise under the German Accessibility Strengthening Act. Under section 3(3) of that act, its requirements do not apply to microenterprises providing services. I am not obliged to make these pages accessible, and I am not obliged to publish this statement.

I do it anyway. Anyone selling accessibility should demonstrate it on their own pages and make it verifiable.

What is in place

  • Skip to content. On every page the first reachable control skips thenavigation. On every page the first reachable control skips the navigation.
  • Full keyboard operation. 196 reachable elements were stepped through individually on the main pages. Focus is always visible and is never obscured by the fixed button at the bottom edge.
  • Labelled form fields. Every field of the contact form has a real, visible label tied to the field, not just placeholder text. Name and email address are additionally marked so that browsers and assistive technology can fill them in.
  • Large enough targets. Every button and checkbox measures at least 24 by 24 pixels.
  • Clear structure. Each page has exactly one main heading, and subheadings follow without skipped levels.
  • Declared language. Each page declares its language so that screen readers choose the right pronunciation.
  • Silent video with a text description. The video about moving from RapidWeaver Classic to Elements has no audio track, plays muted, runs under five seconds and does not loop. A written description of what it shows sits directly below it. Captions are therefore not required.
  • Announced messages. Feedback from the contact form is marked up so screen readers announce it without moving focus.

Known limitations

Empty identifiers in the source code. The content management system I use, RapidWeaver Elements, writes an empty identifier (id="") onto many elements. The W3C validator reports this as an error. It has no effect on operability: I
verified that not a single association between a label and its field points nowhere. The cause and the fix rest with the vendor of the content management system, to whom I have reported this class of defect.

Self-assessment. This statement is based on my own review. There is no evaluation by an independent body, and no testing with users of screen readers has taken place. Automated tools are known to detect only a portion of possible
barriers.

How I tested

  • Date of review: 18 August 2026
  • Method: self-assessment
  • Basis: WCAG 2.2 Level AA and EN 301 549 V3.2.1, clauses 9 and 12
  • Tools: automated testing with axe-core version 4, manual keyboard testing, markup validation with the W3C validator
  • Environment: Safari and Chromium on macOS, viewport width 1400 pixels

This statement was created on 18 August 2026.

Report a barrier

If something on these pages gets in your way, write to me. Please tell me which page it was and what you are using. I aim to reply within five working days.

Email: ocEmail1
Phone: ocPhone1
or use the contact form on the home page

Jan Füllemann, Ellmerweg 13, 31224 Peine, Germany