Skip to main content Required by EU law for organizations with 50+ employees

EN 301 549 conformance report #

Last updated: 2026-05-24.

This report is a structured self-assessment of EthicsPortal against the accessibility requirements in EN 301 549 V3.2.3 (and, transitively, WCAG 2.2 Level AA). It is intended for procurement reviewers who need a clause-by-clause answer beyond the accessibility statement .

FieldValue
ProductEthicsPortal — EU whistleblower compliance platform
Product versionContinuously deployed; this report describes the state as of the preparation date
StandardEN 301 549 V3.2.3 (incorporating WCAG 2.2 Level AA)
Conformance approachSelf-assessment
Preparation date14 May 2026
Next reviewAugust 2026 (quarterly)
Contactaccessibility@ethicsportal.eu

A PDF copy of this report can be supplied for procurement on request.

Scope #

This report covers three deployment surfaces:

  1. Web applicationsecure.ethicsportal.eu, the authenticated case-handler interface
  2. Public reporting portals*.ethicsportal.eu, the whistleblower-facing report submission and case tracking
  3. Marketing websiteethicsportal.eu, the Hugo-rendered public site (this page included)

It also covers downloadable documents and support services delivered through these surfaces.

EthicsPortal is a web-based SaaS product. It does not provide native mobile apps, kiosk hardware, two-way voice ICT, video output for media, or real-time text. Clauses 6, 7, 8, and 13 of EN 301 549 are therefore largely not applicable.

Summary #

Clause areaStatus
§5 Generic requirementsConforms, with exceptions noted in §5.4
§6 ICT with two-way voice communicationNot applicable
§7 ICT with video capabilitiesNot applicable
§8 HardwareNot applicable
§9 WebPartially conforms (see §9 details)
§10 Non-web documentsDoes not conform — see §10.1
§11 SoftwarePartially conforms (see §11 details)
§12 Documentation and support servicesConforms
§13 ICT providing relay or emergency service accessNot applicable

Clause-by-clause assessment #

§5 Generic requirements #

ClauseRequirementStatusNotes
5.1.2.2 / 5.1.3Activation of accessibility featuresConformsThe platform exposes accessibility features through standard HTML and ARIA. No proprietary activation step is required
5.2Activation of accessibility featuresConformsBrowser- and OS-level accessibility settings (zoom, contrast, reduced motion, screen reader) are respected
5.3BiometricsNot applicableAuthentication is by magic link or one-time code with optional TOTP; no biometric input is required
5.4Preservation of accessibility information during conversionPartially conformsApplication content preserves accessibility information; PDF exports do not (see §10.1)
5.5Operable partsConformsAll interactive elements are operable by keyboard and pointer; target size meets §2.5.8
5.6Locking or toggle statusConformsToggle states are exposed via aria-pressed / aria-expanded
5.7Key repeatNot applicableSoftware does not configure system key-repeat
5.8Double-strike key acceptanceNot applicableSoftware does not configure system key-acceptance
5.9Simultaneous user actionsConformsNo interaction requires simultaneous user actions

§9 Web (incorporates WCAG 2.2 Level A and AA) #

EthicsPortal targets WCAG 2.2 Level AA. The new criteria added in WCAG 2.2 are reported individually so reviewers can confirm coverage beyond WCAG 2.1.

Principle 1 — Perceivable

SCTitleLevelStatusNotes
1.1.1Non-text ContentAConformsImages and SVG icons have alt text or are marked decorative. Icon-only buttons carry aria-label. Status indicated by icon alone has an sr-only text equivalent
1.2.xTime-based MediaA/AANot applicableNo audio or video content
1.3.1Info and RelationshipsAConformsSemantic HTML; tables use <th scope>; forms use <label>
1.3.2Meaningful SequenceAConformsDOM order matches visual order
1.3.3Sensory CharacteristicsAConformsInstructions do not rely on shape, size, or location alone
1.3.4OrientationAAConformsLayout works in portrait and landscape
1.3.5Identify Input PurposeAAConformsInputs that match WCAG input purposes use autocomplete
1.4.1Use of ColorAConformsColor is never the only signal — paired with text or icons
1.4.3Contrast (Minimum)AAConformsBody text ≥ 4.5:1, large text ≥ 3:1, audited internally
1.4.4Resize TextAAConformsLayout reflows at 200 % zoom without loss of content
1.4.5Images of TextAAConformsBrand logo is the only image of text; all UI labels are HTML
1.4.10ReflowAAConformsReflows at 320 CSS pixels wide (tables and code blocks excepted as permitted)
1.4.11Non-text ContrastAAConformsUI components and graphical objects meet 3:1
1.4.12Text SpacingAAConformsUser text-spacing overrides do not break layout
1.4.13Content on Hover or FocusAAConformsTooltips dismissible (Escape), hoverable, and persistent until trigger loses focus

Principle 2 — Operable

SCTitleLevelStatusNotes
2.1.1KeyboardAConformsAll functionality is keyboard-operable
2.1.2No Keyboard TrapAConformsModals trap focus only while open and restore it on close
2.1.4Character Key ShortcutsANot applicableNo single-character shortcuts implemented
2.2.1Timing AdjustableAConformsSession inactivity timeout is 30 days, satisfying the 20-hour exception
2.2.2Pause, Stop, HideAConformsNo auto-updating content moves, blinks, or scrolls for more than 5 seconds without a control to pause
2.3.1Three Flashes or BelowAConformsNo flashing content
2.4.1Bypass BlocksAConformsSkip-link to main content present on every layout
2.4.2Page TitledAConformsEvery page has a localised, descriptive <title>
2.4.3Focus OrderAConformsFocus follows DOM order
2.4.4Link Purpose (In Context)AConformsLink text describes the destination
2.4.5Multiple WaysAAConformsSite search, navigation, and breadcrumbs are available
2.4.6Headings and LabelsAAConformsOne <h1> per page; headings descend without skipping
2.4.7Focus VisibleAAConforms:focus-visible is enabled globally; focus rings are not disabled
2.4.11Focus Not Obscured (Minimum)AA (new in 2.2)ConformsFocused elements are not entirely covered by sticky headers or other author content
2.5.1Pointer GesturesAConformsNo multi-point or path-based gestures are required
2.5.2Pointer CancellationAConformsAll click actions complete on up-event
2.5.3Label in NameAConformsAccessible names contain the visible label
2.5.4Motion ActuationANot applicableNo device-motion inputs
2.5.7Dragging MovementsAA (new in 2.2)ConformsNo drag-only flows; uploads accept click and keyboard alternatives
2.5.8Target Size (Minimum)AA (new in 2.2)ConformsInteractive targets ≥ 24×24 CSS px

Principle 3 — Understandable

SCTitleLevelStatusNotes
3.1.1Language of PageAPartially conformsApplication and portal pages set <html lang> to the active locale. Static fallback error pages are English-only — see accessibility statement
3.1.2Language of PartsAAConformsInline foreign-language strings use lang attributes where required
3.2.1On FocusAConformsFocus does not trigger a context change
3.2.2On InputAConformsInput does not trigger a context change without warning
3.2.3Consistent NavigationAAConformsNavigation order is consistent across the application
3.2.4Consistent IdentificationAAConformsIcons and components are used consistently
3.2.6Consistent HelpA (new in 2.2)ConformsSupport contact and help links appear in the same location on every authenticated page (sidebar footer area) and in the portal footer
3.3.1Error IdentificationAConformsErrors are surfaced via role="alert" and described to the user
3.3.2Labels or InstructionsAConformsInputs are labelled; hints use aria-describedby
3.3.3Error SuggestionAAConformsErrors say what is wrong and how to fix it
3.3.4Error Prevention (Legal, Financial, Data)AAConformsReversible operations or explicit confirmation for destructive actions
3.3.7Redundant EntryA (new in 2.2)ConformsInformation previously entered (email, organization) is auto-filled where re-required in the same session
3.3.8Accessible Authentication (Minimum)AA (new in 2.2)ConformsAuthentication uses magic links and one-time codes that can be pasted; no cognitive function tests are required

Principle 4 — Robust

SCTitleLevelStatusNotes
4.1.2Name, Role, ValueAConformsControls expose name, role, and state
4.1.3Status MessagesAAConformsFlash messages, notifications, and async results use aria-live regions

§10 Non-web documents #

ClauseRequirementStatusNotes
10.1Non-web documents (PDFs)Does not conformCompliance reports, certificates, policy templates, posters, the case-handler manual, and case exports are produced as untagged PDFs. Accessible HTML alternatives are available on request via accessibility@ethicsportal.eu . A tagged-PDF pipeline is on the roadmap.
10.2DOCX policy templatesPartially conformsGenerated DOCX files (whistleblower policy, privacy notice) carry their structure but have not been audited against PDF/UA-equivalent expectations for editable documents. HTML alternatives are available on request.

§11 Software #

The web application qualifies as software under §11. §11 incorporates WCAG (assessed above under §9) plus software-specific clauses:

ClauseRequirementStatusNotes
11.5Interoperability with assistive technologyConformsBuilt on semantic HTML and ARIA; tested with VoiceOver, NVDA, and platform keyboard navigation
11.6Documented accessibility usageConformsThis page and the accessibility statement document accessibility features and known limitations
11.7User preferencesConformsOS-level preferences (reduced motion, color scheme, text scaling) are respected
11.8Authoring toolsPartially conformsCase-handler UI is an authoring tool under §11.8 because handlers create content consumed by whistleblowers. Attachment uploads accept descriptions; rich-text features (when introduced) will be assessed against ATAG 2.0

§12 Documentation and support services #

ClauseRequirementStatusNotes
12.1.1Accessibility and compatibility featuresConformsThis report and the accessibility statement describe the supported assistive technologies and platform combinations
12.1.2Accessible documentationConformsDocumentation is delivered as semantic HTML on the marketing site and through in-app help
12.2.2Information on accessibility featuresConformsSupport staff and the published statement can answer accessibility queries
12.2.3Effective communicationConformsAccessibility feedback channel is monitored each working day; acknowledgement within 2 working days
12.2.4Accessible documentation (support)Partially conformsDocuments delivered in response to support requests inherit the same status as the underlying artifacts — PDFs are flagged; HTML alternatives are available

Known limitations #

The items below are tracked, not hidden:

  1. Untagged PDFs. Largest gap. Mitigated today by accessible HTML alternatives on request; planned to be replaced by a tagged-PDF or HTML-canonical pipeline.
  2. Static error pages in English only. Encountered rarely; the same information is presented in the user’s language inside the application.
  3. Third-party embeds (Crisp, Stripe-hosted pages) sit outside our direct control; provider accessibility documentation is reviewed annually.

Test methodology #

The self-assessment combined:

Contact and feedback #

Accessibility concerns, requests for alternative formats, and procurement queries:

Standards and references #

Last updated: