Accessibility statement

Last updated: 20 August 2026 · Applies to the Red Team Analyzer web interface.

ndaal Gesellschaft für Sicherheit in der Informationstechnik mbH & Co KG is committed to making the Red Team Analyzer accessible. This statement describes the current level of accessibility, the limitations we know about, and how we intend to remove them.

1. Scope

This statement applies to the Red Team Analyzer web interface: the analysis, reports, dashboard, API report, chat, account and authentication pages, together with this statement and the help page.

Not covered: report content supplied by third-party scanning engines, which is reproduced unaltered. The structure, markup, contrast and operability of the presentation of that content are in scope and are implemented accessibly.

2. Conformance status

The Red Team Analyzer web interface is partially conformant with:

  • WCAG 2.2, Level AA — partially conformant; see section 3.
  • EN 301 549 V3.2.1, in particular clauses 9 (web) and 12 (documentation and support) — partially conformant.

The version currently in force is EN 301 549 V3.2.1, which incorporates WCAG 2.1 Level AA. A revision incorporating WCAG 2.2 Level AA is in the final stage of standardisation. This product is developed against WCAG 2.2 Level AA and therefore exceeds the version currently in force.

Beyond Level AA, the following Level AAA criteria are implemented:

  • 2.5.5 Target Size (Enhanced) — 44 × 44 px for standalone controls.
  • 1.4.6 Contrast (Enhanced) — 7:1 for body text where the palette allows.
  • 2.4.13 Focus Appearance — a dual focus ring, at least 2 px thick, contrast-safe on any surface.
  • 2.3.3 Animation from Interactions — prefers-reduced-motion honoured globally.
  • 3.3.5 Help — help reachable from the same position on every page.

The interface is published in five languages — English, German, French, Spanish and Italian. Each page is delivered with a matching lang attribute, and the language switcher offers every language written in that language itself.

"Partially conformant" means some requirements are not yet fully met. Each one is listed individually below.

3. Non-accessible content

3.1 Non-conformance with the requirements

Known limitations, the criterion affected, and when each is due to be fixed
Area Limitation Criterion Alternative Due
Assistive technology testing Conformance has been verified by automated testing and by keyboard, zoom, reflow, text-spacing and forced-colours testing. Testing with NVDA, JAWS, VoiceOver and TalkBack has not yet been carried out, so criteria that depend on how a screen reader announces content are asserted from the markup rather than observed. 4.1.2, 1.3.1 Report barriers using the contact details below. Q4 2026
Session handling No warning is shown before a session expires, and unsaved input is not preserved across re-authentication. WCAG 2.2.1 None Q1 2027
Notification email The scan-notification email template has not been reviewed and still references external font and icon services. EN 301 549 clause 12 The same information is available in the web report. Q4 2026

3.2 Disproportionate burden

No disproportionate burden is currently claimed.

3.3 Content outside the scope of the requirements

Threat descriptions, YARA rule names and engine output reproduced in reports come from external scanning engines and are reproduced unaltered. Their linguistic clarity is outside our control.

WCAG 2.2 SC 3.1.5 Reading Level (AAA) is not claimed: the subject matter is malware analysis output, and an honest exclusion is more useful than an unsupported claim.

4. Preparation of this statement

This statement was prepared on 6 August 2026 and last reviewed on 20 August 2026.

  • Method: self-assessment.
  • Scope tested: 13 page states covering every route that renders a template, in English.
  • Automated testing: axe-core 4.x via Playwright, run against every page at desktop and 320 px widths, in light and dark themes.
  • Contrast: every declared colour pair measured with the WCAG relative-luminance formula and verified in the build.
  • Manual testing: keyboard operation, 200 % text zoom, reflow at 320 CSS pixels, text spacing per SC 1.4.12, forced colours, and reduced motion.
  • Assistive technologies tested: none yet — see section 3.1.

Full evaluation reports are available on request.

5. Feedback and contact

If you encounter a barrier, or need content in an accessible format, we would like to hear from you.

  • Email: support@ndaal.eu
  • Response time: we acknowledge receipt within 5 working days and respond substantively within 20 working days.

Where possible, please tell us the page concerned, the assistive technology you were using, and the nature of the barrier. It makes reproduction considerably easier.

6. Enforcement procedure

No statutory enforcement procedure applies to this service. If you are not satisfied with our response to your feedback, please write to support@ndaal.eu marking your message for the attention of the accessibility officer. We handle every report under the procedure described above.

7. Planned improvements

Improvements planned, with the criterion each one addresses
Action Criterion Target
Screen reader test pass (NVDA, JAWS, VoiceOver) 4.1.2, 1.3.1 Q4 2026
Session expiry warning with extension 2.2.1 Q1 2027
Accessible, self-hosted notification email template EN 301 549 clause 12 Q4 2026

This statement is reviewed at least annually and after every significant product change.