English
Accessibility Conformance Report for Impressum Plus
Name of Product/Version: Impressum Plus, version 3.0.5
Report Date: August 12, 2026
Product Description: Impressum Plus is a commercial extension of the free Impressum plugin for WordPress. In addition to generating a legally compliant imprint (Impressum), it generates a privacy policy and an accessibility statement, can synchronise imprint data between sites through an API, and adds blocks for the block editor. It provides admin settings screens under Settings → Impressum (imprint, privacy policy, accessibility statement, API, and license tabs) and outputs its content on the front end via blocks and shortcodes.
Contact Information: Matthias Kittsteiner, https://epiph.yt/en/contact/
Notes: This report covers the Impressum Plus plugin's own user interface only — its admin settings screens, its block-editor controls, and the HTML markup it emits on the front end. It does not cover the surrounding WordPress admin, the active theme, other plugins, or content authored by the site owner. Accessibility of the final page also depends on the theme and site configuration (see Dependencies). Requirements shared with the free plugin are documented in the Impressum Accessibility Conformance Report; this report focuses on the additional functionality of Impressum Plus.
Evaluation Methods Used: Manual keyboard-only testing; screen reader testing with VoiceOver + Safari on macOS 26. Manual color-contrast checks. Tested with WordPress 7.0.2 and the theme Twenty Twenty-Three 1.6. Ratings were additionally cross-checked against the plugin source code (version 3.0.5).
Applicable Standards / Guidelines
This report documents conformance with the following:
| Standard / Guideline | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
| EN 301 549 v3.2.1 (2021-03) | Yes |
Terms
The terms used in the Conformance Level column are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. (May only be used for WCAG 2.x Level AAA criteria.)
WCAG 2.2 Report
Tables 1 and 2 document conformance with WCAG 2.2. Note: WCAG 2.2 removed Success Criterion 4.1.1 Parsing; it is therefore not listed below.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | The plugin emits no informative images, icons, or other non-text content; all output is text. The decorative "remove recipient" icon in the API settings is a Dashicon marked aria-hidden="true" accompanied by the visible text "Remove". Block-editor icons are supplied by WordPress. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The plugin produces no audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The plugin produces no prerecorded media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The plugin produces no prerecorded media. |
| 1.3.1 Info and Relationships | Supports | Imprint output is a description list (<dl>/<dt>/<dd>). The privacy policy uses semantic headings (<h2> per numbered section, <h3> for sub-sections) and <ul>/<ol> lists. The accessibility statement uses <h2> sections. Settings use the WordPress form-table pattern with each label in <th scope="row"><label for="…">. Radio-button sets on the API tab are exposed as named groups (role="radiogroup" with aria-label). |
| 1.3.2 Meaningful Sequence | Supports | Content is emitted in a logical DOM order that reads correctly without CSS. |
| 1.3.3 Sensory Characteristics | Supports | No instructions rely on shape, size, visual location, or sound. |
| 1.4.1 Use of Color | Supports | Color is never the sole means of conveying information; status notices and pre-selected-field hints always include explanatory text alongside any color cue. |
| 1.4.2 Audio Control | Not Applicable | The plugin plays no audio. |
| 2.1.1 Keyboard | Supports | All settings use native form controls. The "add recipient" and "remove recipient" controls on the API tab are native <button> elements, operable with Enter/Space. The settings tabs implement a full keyboard model (Arrow Left/Right, Home, End with roving tabindex). Block-editor controls use standard @wordpress/components. |
| 2.1.2 No Keyboard Trap | Supports | Focus can move away from every control with standard keys; the custom "edit field name" widget manages focus without trapping it. |
| 2.1.4 Character Key Shortcuts | Not Applicable | The plugin implements no single-character key shortcuts. (The settings tabs use only Arrow/Home/End, which are outside the scope of this criterion.) |
| 2.2.1 Timing Adjustable | Not Applicable | The plugin imposes no time limits. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | The plugin produces no moving, blinking, scrolling, or auto-updating content. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | The plugin produces no flashing content. |
| 2.4.1 Bypass Blocks | Supports | The plugin introduces no repeated blocks of content that would require a bypass mechanism; page-level skip links and landmarks are provided by WordPress and the theme. |
| 2.4.2 Page Titled | Supports | The settings screens render the admin page title in an <h1>; front-end page titles are supplied by WordPress and the theme. |
| 2.4.3 Focus Order | Supports | Focus order follows the logical DOM order. The settings-tab script moves focus to the newly selected tab and keeps inactive tab panels out of the tab sequence; the "edit field name" widget returns focus to a sensible location on entering and canceling edit mode. |
| 2.4.4 Link Purpose (In Context) | Supports | Front-end links are self-describing: e-mail addresses render as mailto: links whose text is the address, social-media links carry the network name, and privacy-policy references identify their destination (external references use the destination URL as visible text). Admin links have descriptive text. |
| 2.5.1 Pointer Gestures | Not Applicable | No functionality relies on path-based or multipoint gestures. |
| 2.5.2 Pointer Cancellation | Supports | Controls act on the standard click/up event; no functionality is triggered on the down-event. |
| 2.5.3 Label in Name | Supports | Each control's accessible name contains its visible label or button text; icon-only controls carry matching visible or screen-reader text. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is operated by device or user motion. |
| 3.1.1 Language of Page | Supports | The plugin sets no page lang attribute and does not interfere with the language declared by WordPress/the theme; its own strings are localized to the site language. |
| 3.2.1 On Focus | Supports | No change of context occurs when any control receives focus. |
| 3.2.2 On Input | Supports | Changing a <select> or checkbox reveals or hides related fields on the same page but does not submit the form or change context. |
| 3.3.1 Error Identification | Supports | Client-side validation errors (e.g. VAT ID format, required fields) are described in text and are programmatically associated with their field: the input is marked aria-invalid and linked to the message via aria-describedby. |
| 3.3.2 Labels or Instructions | Supports | Every field has an associated <label for> (or a group label for radio sets) plus a visible description where relevant. |
| 3.3.7 Redundant Entry | Not Applicable | The plugin has no multi-step process that asks for the same information more than once. |
| 4.1.2 Name, Role, Value | Supports | The UI is built from native form controls plus the block editor's standard components. The settings tabs expose correct roles and states (role="tablist/tab/tabpanel", aria-selected, aria-labelledby, hidden), kept in sync by their script. Radio sets on the API tab are exposed as named role="radiogroup" groups. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The plugin produces no live media. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | The plugin produces no prerecorded video. |
| 1.3.4 Orientation | Supports | The plugin locks neither content nor UI to a single display orientation. |
| 1.3.5 Identify Input Purpose | Supports | Fields that collect information about the user carry the appropriate autocomplete token: the license account e-mail uses autocomplete="email", and the e-mail/phone fields use type="email"/type="tel". Remaining fields describe the organization or third parties (e.g. the legal entity, the data protection officer), for which the WCAG input-purpose tokens do not apply. |
| 1.4.3 Contrast (Minimum) | Supports | The plugin defines almost no colors of its own, inheriting the WordPress admin palette (front-end text inherits the theme). Its only custom text color is the WordPress admin link blue (#2271b1 on white, ≈ 5.2:1, and its darker hover/focus shades), which meets the 4.5:1 minimum. |
| 1.4.4 Resize Text | Supports | The plugin sets no fixed pixel font sizes and uses standard, text-based markup, so text scales with the browser/zoom. Confirmed at 200 % zoom. |
| 1.4.5 Images of Text | Supports | All text is real text; the plugin uses no images of text. |
| 1.4.10 Reflow | Supports | Output uses fluid, semantic markup with no fixed-width layout containers (injected notices use max-width, not a fixed width). Confirmed at 320 px / 400 % zoom. |
| 1.4.11 Non-text Contrast | Supports | The plugin does not override control borders or focus indicators, inheriting the WordPress admin styles; the one custom focus style provides a visible #2271b1 focus ring. |
| 1.4.12 Text Spacing | Supports | No inline styles constrain line-height, letter- or word-spacing in a way that would clip text. |
| 1.4.13 Content on Hover or Focus | Supports | On the imprint settings screen, the control for editing a field's display title is revealed when its field row is hovered or focused. The revealed control is persistent (it stays visible while the row keeps hover or focus, including :focus-within while the control itself is focused) and hoverable (the pointer can move onto it without it disappearing); it appears in its own space within the row header and does not obscure other content, so no separate dismiss mechanism is required. |
| 2.4.5 Multiple Ways | Not Applicable | This is a site-level requirement about locating pages within a set of web pages; it is outside the scope of a single plugin's output. |
| 2.4.6 Headings and Labels | Supports | Headings and field labels are descriptive, and heading levels are correctly nested throughout the imprint, privacy policy, and accessibility statement. |
| 2.4.7 Focus Visible | Supports | The plugin stylesheet contains no focus suppression that removes the indicator; the default WordPress/browser focus indicator remains visible, and the one custom control provides its own visible focus ring. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | The plugin adds no sticky headers, overlays, or floating elements that could hide a focused control. |
| 2.5.7 Dragging Movements | Not Applicable | The plugin has no drag-based interactions. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive elements are native controls and standard block-editor/WordPress components at their default sizing (≥ 24 × 24 px). |
| 3.1.2 Language of Parts | Supports | Where the accessibility statement cites a national accessibility law by its official foreign-language title, that title is wrapped in a <span lang="…"> with the correct BCP-47 language code, so assistive technology announces it in the right language. The plugin's own strings are otherwise localized to the site language. |
| 3.2.3 Consistent Navigation | Supports | The settings screens present their tabs in a consistent order on every load. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are labeled consistently throughout the settings UI. |
| 3.2.6 Consistent Help | Supports | Help is offered consistently: per-field descriptions on the settings screens and a "Documentation" link in the plugin's row on the Plugins screen. |
| 3.3.3 Error Suggestion | Supports | Where an error is detected, the message suggests a correction (e.g. required-field prompts and specific format guidance for the VAT ID), announced and associated with the field (see 3.3.1 / 4.1.3). |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | The plugin performs no legal, financial, or data-commitment transactions; settings are editable and can be re-saved at any time. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | The plugin provides no authentication of its own; its license activation requires only entering an e-mail address and a license key, both of which support paste and password managers (no cognitive function test). Sign-in to WordPress is handled by WordPress. |
| 4.1.3 Status Messages | Supports | The "Settings saved" confirmation uses the standard WordPress mechanism, and the plugin's client-side validation messages are injected as a live region (role="alert"), so they are announced by assistive technology when they appear. |
EN 301 549 Report
The following tables document conformance with EN 301 549 v3.2.1. Chapters are marked Not Applicable where the associated technology is not present in the product.
4.2 Functional Performance Statements (informative)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4.2.1 Usage without vision | Supports | Content is exposed through native semantics (description list, associated labels, ARIA tabs and radio groups), and dynamic validation messages are announced to screen readers (see 4.1.3). |
| 4.2.2 Usage with limited vision | Supports | Text-based, zoomable output with no fixed sizes; plugin-defined colors meet contrast (see 1.4.3). |
| 4.2.3 Usage without perception of color | Supports | Information is never conveyed by color alone (see 1.4.1). |
| 4.2.4 Usage without hearing | Not Applicable | The plugin conveys no information through sound. |
| 4.2.5 Usage with limited hearing | Not Applicable | The plugin conveys no information through sound. |
| 4.2.6 Usage without vocal capability | Not Applicable | No operation requires the user to produce speech. |
| 4.2.7 Usage with limited manipulation or strength | Supports | All functionality is keyboard-operable with native controls (see 2.1.1). |
| 4.2.8 Usage with limited reach | Not Applicable | Software only; no physical reach requirements. |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | The plugin produces no flashing content (see 2.3.1). |
| 4.2.10 Usage with limited cognition, language or learning | Supports | Consistent layout, descriptive labels, per-field help, and plain error suggestions. |
| 4.2.11 Privacy | Supports | The plugin adds no accessibility feature that would expose the user's data differently from the standard controls. |
Chapter 5: Generic Requirements
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 5.1 Closed functionality | Not Applicable | The plugin runs in a general-purpose web browser and provides no closed functionality. |
| 5.2 Activation of accessibility features | Not Applicable | No platform accessibility features to activate. |
| 5.3 Biometrics | Not Applicable | The plugin uses no biometrics. |
| 5.4 Preservation of accessibility information during conversion | Not Applicable | The plugin performs no format conversion of user content. |
| 5.5 Operable parts | Supports | Operable parts are native controls and standard components; see WCAG 2.1.1 and 2.5.x. |
| 5.6 Locking or toggle controls | Not Applicable | The plugin exposes no locking/toggle status keys to report. |
| 5.7 Key repeat | Not Applicable | Key-repeat behavior is a platform/hardware function. |
| 5.8 Double-strike key acceptance | Not Applicable | Platform/hardware function. |
| 5.9 Simultaneous user actions | Supports | No operation requires simultaneous user actions. |
Chapter 6: ICT with Two-Way Voice Communication
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 6 (all clauses) | Not Applicable | The plugin provides no two-way voice communication. |
Chapter 7: ICT with Video Capabilities
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 7 (all clauses) | Not Applicable | The plugin provides no video capabilities. |
Chapter 8: Hardware
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 8 (all clauses) | Not Applicable | The plugin is software only; it includes no hardware. |
Chapter 9: Web
The plugin's front-end output and its browser-based admin UI are web content. Conformance is documented in the WCAG 2.2 Report above; EN 301 549 clauses 9.1–9.4 map directly to the corresponding WCAG 2.2 Success Criteria.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 9.1 – 9.4 (WCAG 2.2 A & AA) | See WCAG 2.2 Report | Refer to Tables 1 and 2 above; all Level A and AA criteria are rated Supports or Not Applicable. |
| 9.5 Non-interference | Supports | The plugin uses no color-only cues, flashing, audio, or timing that would interfere across the page. |
| 9.6 WCAG conformance requirements | Supports | The output meets the WCAG 2.2 Level A and AA conformance requirements. |
Chapter 10: Non-web Documents
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 10 (all clauses) | Not Applicable | The plugin produces no non-web documents (e.g. PDF or Office files). |
Chapter 11: Software
The plugin's user interface (settings screens and block-editor controls) is web-based software rendered in the WordPress admin. Requirements that correspond to WCAG map to the WCAG 2.2 Report.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 11.1 – 11.4, 11.5.2, 11.6 (WCAG-based) | See WCAG 2.2 Report | The UI is web-based; refer to Tables 1 and 2 above. |
| 11.5.1 Closed functionality | Not Applicable | Not closed functionality. |
| 11.7 User preferences | Supports | The plugin sets no fixed fonts or colors that would override the user's platform/browser preferences; it inherits the WordPress admin environment. |
| 11.8 Authoring tools | Supports | The plugin's blocks run inside the WordPress block editor (an authoring tool). The Privacy and Accessibility Information blocks use ServerSideRender with supports.html = false, so authors cannot inject arbitrary markup, and the blocks always emit the plugin's semantic output — the authoring tool produces accessible content by default. |
Chapter 12: Documentation and Support Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | This documentation describes the plugin's features, including this Accessibility Conformance Report. |
| 12.1.2 Accessible documentation | Supports | Documentation is published as HTML at docs.epiph.yt. |
| 12.2.2 Information on accessibility and compatibility features | Supports | Accessibility-relevant behavior is documented here and in the plugin readme. |
| 12.2.3 Effective communication | Supports | Support is offered through the vendor's channels at epiph.yt. |
| 12.2.4 Accessible documentation (support) | Supports | Support documentation is provided in accessible HTML. |
Chapter 13: ICT Providing Relay or Emergency Service Access
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 13 (all clauses) | Not Applicable | The plugin provides no relay or emergency-service functionality. |
Dependencies
The accessibility of the imprint, privacy policy, and accessibility statement as they finally appear to a visitor depends on factors outside the plugin's control, including:
- the active WordPress theme (colors, contrast, focus styles, heading structure, responsive behavior of the page around the plugin's output);
- other plugins on the site;
- content entered by the site owner — in particular the free-text imprint field and the privacy "Replacements" feature, which let authors supply their own markup (including headings and inline styles). Site owners remain responsible for the accessibility of content they author.
This report describes the plugin's own markup and UI. Site owners remain responsible for the overall accessibility of their website.
Known Issues
No outstanding accessibility issues are known at the time of this report.
Legal Disclaimer
This Accessibility Conformance Report is a self-reported statement of the product's conformance with the standards listed above, as of the report date and for the version stated. It is not a warranty or a guarantee of legal compliance. Accessibility is assessed on a best-effort basis and may change between releases.