Barrierefreiheits-Konformitätsbericht
VPAT® 2.5 INT – WCAG 2.2, EN 301 549 und Revised Section 508, aus den Belegen des Repositorys
Dieser Bericht erscheint nur auf Englisch: Die Kriterien, ihre Namen und die vier Konformitätsbegriffe sind in der VPAT-Vorlage englisch definiert, und die Beschaffung vergleicht ihn in dieser Form mit den Berichten anderer Anbieter. Die Barrierefreiheitserklärung darum herum gibt es auf Englisch, Türkisch und Deutsch.
Als Markdown herunterladenZurück zur Barrierefreiheitserklärung
- Produkt
- InternshipCRM — the web application (public pages, sign-in, mentee, mentor, admin and company areas)
- Berichtsdatum
- 2026-10-07
- Version
- The deployed version and commit are printed on /release-notes and returned by GET /api/health; the automated evidence below names the commit the baseline was last changed at.
- Kontakt
- The feedback channel (operator e-mail, response target and escalation route) is published on /accessibility; the public issue tracker is the second channel.
- Hinweise
- Self-assessment by the maintainers; no third-party audit has been commissioned. Conformance is claimed only for the product's own user interface: files users upload, e-mail as rendered by a mail client and the two embedded third parties (the Jitsi meeting room, the marketing-cookie-gated live chat on the home page) are out of scope and listed as known limitations on /accessibility.
Verwendete Prüfmethoden
- Automated: an axe-core scan (`@axe-core/playwright`) with the WCAG 2.0, 2.1 and 2.2 A and AA rule sets over every page state in `e2e/a11y-baseline.json`, each in light and dark mode, in five role contexts (public, mentee, mentor, admin, company). Critical and serious findings fail every pull request (`.github/workflows/e2e.yml`); the per-page result is the appendix generated by `npm run vpat:evidence`.
- Targeted mechanical checks written against single criteria: contrast of specific components in both themes (`e2e/contrast-*.spec.ts`, `e2e/helpers/hoverContrast.ts`), keyboard operation of the pipeline board, the global search combobox and the calendar (`e2e/board-a11y.spec.ts`, `e2e/global-search-a11y.spec.ts`, `e2e/calendar-a11y-2153.spec.ts`), the skip link (`e2e/a11y.spec.ts`), text resize and 320 px / 400 % reflow (`e2e/font-size.spec.ts`, `e2e/mobile-layout-audit.spec.ts`), and the OS preferences reduced motion, more contrast and forced colours (`e2e/a11y-media-preferences.spec.ts`).
- Manual: no structured screen-reader or keyboard test programme has been run yet. Every row whose only basis would be the authors' own use is marked Partially Supports and names the tracking issue, so this report does not imply coverage it does not have.
- Scope of the evaluated URLs: exactly the page states listed in the appendix. The rest of the product follows the same components and conventions but is pending evaluation.
Was geprüft wurde – und was nicht
Genau diese 25 URLs, jede im hellen und im dunklen Modus (50 Seitenzustände), bei Commit f419bba (2026-10-07), mit 0 offenen kritischen oder schweren Befunden in der Baseline. Jede andere URL des Produkts steht noch aus; der Bericht leitet aus dieser Menge keine Abdeckung des ganzen Produkts ab.
- /
- /auth/signin
- /accessibility
- /apply/:mentorId
- /portal
- /portal/journey
- /portal/goals
- /portal/calendar
- /account
- /portal/requests
- /portal/profile
- /portal/projects
- /portal/interactions
- /portal/notes
- /mentor
- /mentor/mentees
- /admin
- /admin/candidates
- /messages
- /notifications
- /mentor/board
- /admin/board
- /admin/companies/:id
- /admin/settings
- /company
Regelsatz: wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa · Lässt den Build scheitern: critical, serious
Stufe A und AA auf einen Blick
- 18 · Supports
- 32 · Partially Supports
- 0 · Does Not Support
- 6 · Not Applicable
Zählung über die 56 WCAG-2.2-Kriterien der Stufen A und AA. „Partially Supports“ steht überall dort, wo die einzige Grundlage unsere eigene Nutzung wäre – diese Zeilen nennen das Issue, das ein manuelles Testprogramm oder eine Korrektur bewegen würde.
Begriffe
- Supports
- The functionality of the product has at least one method that meets the criterion without known defects or meets 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.
WCAG-2.2-Bericht
Tabelle 1: Erfolgskriterien, Stufe A
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | The axe rules for images, icons, buttons and links (image-alt, svg-img-alt, button-name, link-name) report no violation on any scanned page state. Decorative icons are aria-hidden through the shared UI components; message and announcement images carry the file name as their alternative, which is a label, not a description — and no page outside the scan has been reviewed. manual verification pending (#2864). | |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | The product publishes no audio. Its only prerecorded video is the silent screen clip a release note may carry, and the release text next to it is the text alternative (releases/README.md, "media"). |
|
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded synchronized media with audio: release clips are silent. | |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded synchronized media with audio. | |
| 1.3.1 Info and Relationships | Partially Supports | Form labels, list and table structure, heading levels and ARIA parent/child requirements are checked by the axe rule set on every scanned page state with no violation. Structure of the pages outside the scan and the correctness of what the automation cannot judge (whether a visual grouping is also a programmatic one) await a screen-reader pass. manual verification pending (#2864). | |
| 1.3.2 Meaningful Sequence | Partially Supports | Layout is CSS over a DOM that reads in visual order; the responsive shells render one DOM for every width (e2e/mobile-layout-audit.spec.ts) rather than reordering. Not verified with a screen reader. manual verification pending (#2864). | |
| 1.3.3 Sensory Characteristics | Partially Supports | Pipeline stages, offer states and notification kinds are named in text next to any colour or icon (the Badge component always carries a label). No instruction in the interface refers to a position or shape alone, to the authors' knowledge; manual verification pending (#2864). | |
| 1.4.1 Use of Color | Partially Supports | Links inside running text are underlined (the axe link-in-text-block rule reports no violation), and every status that has a colour also has text. Charts in the analytics screens use colour plus a legend and a value table where one exists; not every chart has been reviewed. manual verification pending (#2864). | |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically: the product plays no audio of its own, and its one autoplaying element, the release-note clip, is muted and silent. |
|
| 2.1.1 Keyboard | Partially Supports | The interactions most likely to be pointer-only are covered mechanically: the pipeline board's drag-and-drop has a keyboard stage select on every card, the global search is a keyboard-operable combobox, calendar cells and the view switcher are buttons with names, dialogs manage focus. A whole-product keyboard pass has not been run. manual verification pending (#2864). | |
| 2.1.2 No Keyboard Trap | Supports | Dialogs hold Tab inside only while open and release it on Escape or close, restoring focus to the opener; no other component captures focus. The embedded meeting room is a third-party iframe the person can leave by closing it. | |
| 2.1.4 Character Key Shortcuts | Partially Supports | One single-character shortcut exists: "?" opens the shortcut sheet, and it is ignored while focus is in a text field; the others are chords (Mod+K) or non-printing keys. There is no setting to turn the "?" binding off or remap it. Tracked in #2864. | |
| 2.2.1 Timing Adjustable | Partially Supports | A session is renewed silently while in use and expires 12 hours after the last activity without a warning or an in-page way to extend it; "keep me signed in" removes the limit for 30 days per device. Toasts auto-dismiss, but what they report stays visible on the page. Tracked in #2864. | |
| 2.2.2 Pause, Stop, Hide | Partially Supports | No carousel, auto-advancing content or blinking. Loading indicators (pulse, spin) stop when the content arrives, and under prefers-reduced-motion every CSS animation and transition is neutralised. Real-time updates (unread counters, a live thread) cannot be paused from the interface. Tracked in #2864. | |
| 2.3.1 Three Flashes or Below Threshold | Supports | Nothing flashes: the only animations are a skeleton pulse, a spinner, the one-per-second ping ring on the live meeting pill and slide transitions, none of which exceeds three changes per second or repeats a flash. |
|
| 2.4.1 Bypass Blocks | Supports | Every page — public and signed-in — begins with a skip link that targets the main landmark, and the shells expose header, navigation and main landmarks. | |
| 2.4.2 Page Titled | Supports | Public pages declare their own title and description per language through one helper; the root layout appends the product name. The axe document-title rule reports no violation on any scanned page state. | |
| 2.4.3 Focus Order | Partially Supports | Focus follows DOM order, which follows visual order; dialogs take initial focus and return it on close. Not verified with a keyboard pass across the product. manual verification pending (#2864). | |
| 2.4.4 Link Purpose (In Context) | Partially Supports | The axe link-name rule reports no violation on the scanned page states; "see all" style links are rendered inside the card they refer to. Not reviewed outside the scan. manual verification pending (#2864). | |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gesture is required: the board's drag-and-drop has a single-pointer and keyboard alternative (the stage select on each card) and nothing else uses a gesture. | |
| 2.5.2 Pointer Cancellation | Partially Supports | Actions fire on click (the up event) through the shared Button; the board's drag library completes a move only on drop. Not systematically verified. manual verification pending (#2864). | |
| 2.5.3 Label in Name | Partially Supports | Visible labels are the accessible names by construction in the shared components (the label element is the name); icon-only controls carry aria-label. The label-content-name-mismatch rule is not part of the gate's tag set. manual verification pending (#2864). | |
| 2.5.4 Motion Actuation | Supports | No function is operated by device motion or user motion. |
|
| 3.1.1 Language of Page | Supports | The document declares the interface language (en, tr or de) from the request; the axe html-has-lang and html-lang-valid rules report no violation. | |
| 3.2.1 On Focus | Partially Supports | Nothing changes context on focus to the authors' knowledge; manual verification pending (#2864). | |
| 3.2.2 On Input | Partially Supports | The language, theme and text-size controls apply on change, as settings controls do; they do not navigate. Filter selects on the admin indexes re-query the list in place. No form submits on input. manual verification pending (#2864). | |
| 3.2.6 Consistent Help | Partially Supports | On the public pages the feedback and issue-tracker links sit in the footer and on /accessibility in the same place on every page; inside the signed-in shells the support entry exists only in the admin navigation, not in a consistent place for every role. Tracked in #2864. | |
| 3.3.1 Error Identification | Partially Supports | Field errors are rendered as text under the field through the shared Input/Select error prop and form-level errors in an alert box; not every form has been checked for naming the field in error. manual verification pending (#2864). | |
| 3.3.2 Labels or Instructions | Partially Supports | Every input rendered through the shared components has a label (the axe label rules report no violation on the scanned page states); hints are a first-class prop. Instruction sufficiency outside the scan is not reviewed. manual verification pending (#2864). | |
| 3.3.7 Redundant Entry | Partially Supports | Autocomplete is declared on identity fields and the account form is pre-filled from the profile; multi-step forms (registration, applications, the offer wizard) have not been audited for asking the same thing twice. Tracked in #2864. | |
| 4.1.1 Parsing | Not Applicable | Removed from WCAG 2.2 (always satisfied for HTML processed by modern user agents). Reported as Not Applicable per the WCAG 2.2 note; the duplicate-id and aria rules that used to stand in for it are in the scan. | |
| 4.1.2 Name, Role, Value | Partially Supports | Native elements are used for native things; the custom widgets that exist (combobox search, calendar grid, board stage select, dialogs) carry roles, names and states and have targeted specs; the axe aria-* and *-name rules report no violation on the scanned page states (the unnamed account selects of #2041 were fixed). Custom components beyond the scanned pages await a screen-reader pass. manual verification pending (#2864). |
Tabelle 2: Erfolgskriterien, Stufe AA
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The product publishes no live synchronized media. Real-time meetings between people run in the embedded third-party Jitsi room, which is out of scope (see EN 301 549 chapter 6). | |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded synchronized media with audio. | |
| 1.3.4 Orientation | Supports | Nothing locks or assumes an orientation: the web manifest declares `orientation: any`, no code calls `screen.orientation.lock` and no stylesheet gates a layout on the orientation; layouts are fluid from 320 px up and are exercised at phone and tablet widths in both themes. |
|
| 1.3.5 Identify Input Purpose | Partially Supports | Sign-in, registration and the account form declare autocomplete purposes (email, current-password, one-time-code, name, tel …). The remaining forms that collect personal data have not been audited field by field. manual verification pending (#2864). |
|
| 1.4.3 Contrast (Minimum) | Supports | The axe color-contrast rule runs over every scanned page state in light AND dark mode with no violation; a hover-contrast check hovers every `hover:text-*` element on each scanned page in both themes and enforces 4.5:1 against the real background; dedicated specs pin the pairs axe cannot see (white text on accent surfaces, the journey tracker, calendar and onboarding targets, the RSVP buttons, the unread badge, the mode switcher). A reflow of the layout can place a text over a new background, which is why the hover check exists; pages outside the scan are covered by the same colour tokens but are not measured. | |
| 1.4.4 Resize Text | Supports | An in-app text-size stepper scales the interface and persists; on top of it, 400 % browser zoom is exercised on the board and the calendar without loss of content or function, and no page scrolls sideways at phone width. | |
| 1.4.5 Images of Text | Partially Supports | The interface renders text as text; the only image of text is the logo (exempt). User-uploaded images (CVs rendered as previews, message attachments) can contain text and are outside the authors' control. manual verification pending (#2864). | |
| 1.4.10 Reflow | Partially Supports | Verified at 320 CSS px and 400 % zoom for the pipeline board, the calendar and the role shells, with the page never scrolling sideways; the calendar's view switcher scrolls inside its own strip at 320 px in German, which is the permitted two-dimensional exception for a toolbar but is recorded in the spec rather than assumed. Data tables (admin lists) scroll horizontally inside their container by design. Other screens are not measured at 320 px. manual verification pending (#2864). | |
| 1.4.11 Non-text Contrast | Partially Supports | The focus indicator is a 2 px ring in the accent colour, thickened under prefers-contrast: more; input borders and secondary text are strengthened under the same preference (e2e/a11y-media-preferences.spec.ts). Control boundaries and icon-only controls have not been measured against 3:1 systematically. manual verification pending (#2864). | |
| 1.4.12 Text Spacing | Partially Supports | Text containers use flexible heights (Tailwind utilities, no fixed-height text boxes by convention) and the 400 % zoom check passes, but the specific text-spacing override of this criterion has not been applied and checked. manual verification pending (#2864). | |
| 1.4.13 Content on Hover or Focus | Partially Supports | Menus and dialogs opened by pointer or keyboard are dismissible with Escape and stay open while hovered (useModalFocus); past instants show their absolute reading as a native title tooltip, which the user agent controls. Custom tooltips have not been inventoried. manual verification pending (#2864). | |
| 2.4.5 Multiple Ways | Supports | Signed-in: the role navigation, a global search (Mod+K) and in-page links. Public: the navigation, the footer and a sitemap built from the single public-route registry. | |
| 2.4.6 Headings and Labels | Partially Supports | Every page has a top-level heading and form controls have labels (axe label rules clean on the scanned page states). Whether each heading and label is also descriptive is a judgement the automation does not make. manual verification pending (#2864). | |
| 2.4.7 Focus Visible | Supports | A global :focus-visible ring on links, buttons, role=button, inputs and selects in the accent colour, thickened under prefers-contrast: more and kept under forced colours. | |
| 2.4.11 Focus Not Obscured (Minimum) | Partially Supports | The sticky mobile top bar and the messages header can sit over a focused control after a programmatic scroll; whether a focused element is ever entirely hidden has not been checked. Tracked in #2864. | |
| 2.5.7 Dragging Movements | Supports | The one dragging interaction, moving a card between pipeline stages, is also achievable with the stage select on the card (single pointer, no drag). | |
| 2.5.8 Target Size (Minimum) | Supports | Buttons and inputs are at least 44 × 44 CSS px on touch viewports; the axe target-size rule (wcag22aa) runs on every scanned page state with no violation. | |
| 3.1.2 Language of Parts | Partially Supports | The whole interface switches language together. Content written by people in another language than the interface (a Turkish note in an English session) is not marked with its own lang. Tracked in #2864. | |
| 3.2.3 Consistent Navigation | Supports | Every role's navigation comes from one registry and is rendered by one shell per surface, so order and placement do not vary between pages. | |
| 3.2.4 Consistent Identification | Partially Supports | Icons and labels come from the shared UI components and one dictionary per language, so the same function carries the same label. Not audited as a whole. manual verification pending (#2864). | |
| 3.3.3 Error Suggestion | Partially Supports | Validation messages say what is expected (format, length, required currency and period for an amount, …) where the rule is known; coverage per form is not audited. manual verification pending (#2864). | |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Irreversible actions (withdrawing or sending an offer, removing a device, deleting) require an explicit confirmation dialog, and multi-step submissions show a preview before they are sent. | |
| 3.3.8 Accessible Authentication (Minimum) | Supports | No CAPTCHA and no puzzle. Password sign-in accepts paste and password managers (autocomplete current-password); the second factor is an authenticator code with autocomplete one-time-code, with printable recovery codes as the alternative; a remembered device needs no re-entry for 30 days; enterprise tenants can sign in through their identity provider. A passwordless e-mail link (#1959) is in review. | |
| 4.1.3 Status Messages | Partially Supports | One app-wide live region (mounted empty, announced on change), toasts with role=status and loading/error sections with role=status/alert cover saves, errors and loading. Result counts of searches and filtered lists and the character counters are not announced consistently. Tracked in #2864. |
Tabelle 3: Erfolgskriterien, Stufe AAA
Level AAA is not a conformance target of this product. Only the criteria above were evaluated; every other Level AAA criterion is Not Evaluated.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 2.3.3 Animation from Interactions | Supports | Under prefers-reduced-motion every CSS transition and animation is neutralised and programmatic smooth scrolling becomes instant; the drawer still opens and closes without its slide. | |
| 1.4.6 Contrast (Enhanced) | Partially Supports | Under prefers-contrast: more, borders and secondary text are strengthened; 7:1 is not claimed for the default palette. |
Bericht Revised Section 508
Chapter 3: Functional Performance Criteria (FPC)
Answered from the WCAG rows above; the EN 301 549 clause 4.2 rows give the same answers in more detail.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 302.1 Without Vision | Partially Supports | Machine-checked semantics; screen-reader programme pending. manual verification pending (#2864). | |
| 302.2 With Limited Vision | Supports | Text resize, 400 % zoom, AA contrast in both themes, more-contrast and forced colours honoured. | |
| 302.3 Without Perception of Color | Partially Supports | Text accompanies colour; charts not all reviewed. manual verification pending (#2864). | |
| 302.4 Without Hearing | Supports | No audio of its own; text channels alongside third-party meetings. |
|
| 302.5 With Limited Hearing | Supports | As 302.4. |
|
| 302.6 Without Speech | Supports | No function requires speech. |
|
| 302.7 With Limited Manipulation | Partially Supports | Keyboard alternatives and 44 px targets; whole-product keyboard pass pending. manual verification pending (#2864). | |
| 302.8 With Limited Reach and Strength | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | Consistent navigation and plain errors; readability not evaluated. manual verification pending (#2864). |
Chapter 4: Hardware
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 4 Hardware | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
Chapter 5: Software
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | Partially Supports | See the WCAG 2.2 section: every WCAG 2.0 Level A and AA criterion is reported there, with the conformance level of each row. | |
| 502.2.1 User Control of Accessibility Features | Not Applicable | The product is not platform software. | — |
| 502.2.2 No Disruption of Accessibility Features | Supports | Platform preferences are honoured and no assistive-technology input is intercepted (EN 11.6.2). | |
| 502.3 Accessibility Services (502.3.1–502.3.14) | Supports | A web application: object information, row/column, values, label relationships, hierarchy, text, actions, focus, event notification and modification of states are exposed to the platform accessibility API through standard HTML and WAI-ARIA, which the axe rule set checks for the scanned page states; no custom accessibility service exists. | |
| 502.4 Platform Accessibility Features | Not Applicable | The product is not platform software. | — |
| 503.2 User Preferences | Supports | Colour scheme, contrast, motion and forced colours follow the platform settings. | |
| 503.3 Alternative User Interfaces | Not Applicable | No alternative user interface functions as assistive technology. | — |
| 503.4 User Controls for Captions and Audio Description | Not Applicable | No media player (EN 7.x). | |
| 504.2 Content Creation or Editing | Partially Supports | Authored text is accessible by construction; attached images take no alternative text (EN 11.8.2). Tracked in #2864. | |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Partially Supports | The certificate PDF conversion has not been evaluated (EN 5.4). Tracked in #2864. | |
| 504.2.2 PDF Export | Partially Supports | As 504.2.1. | |
| 504.3 Prompts | Does Not Support | No prompt or check guides authors towards accessible content (EN 11.8.4). Tracked in #2864. | |
| 504.4 Templates | Partially Supports | Administrator-provided document templates are the authors' own (EN 11.8.5). Tracked in #2864. |
Chapter 6: Support Documentation and Services
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 602.2 Accessibility and Compatibility Features | Supports | Documented on the public accessibility statement and in the repository (EN 12.1.1). | |
| 602.3 Electronic Support Documentation | Supports | Web pages and Markdown — text with structure (EN 12.1.2). | |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | No non-electronic documentation exists. | — |
| 603.2 Information on Accessibility and Compatibility Features | Supports | The statement names the channel, the response target and the escalation route (EN 12.2.2). | |
| 603.3 Accommodation of Communication Needs | Partially Supports | Text channels only (EN 12.2.3). Tracked in #2864. |
Bericht EN 301 549
Chapter 4: Functional Performance
Clause 4.2 — the functional performance statements, answered from the WCAG rows above.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 4.2.1 Usage without vision | Partially Supports | Semantics, names and live regions are in place and machine-checked; a screen-reader test programme has not been run (see 1.3.1, 4.1.2, 4.1.3). manual verification pending (#2864). | |
| 4.2.2 Usage with limited vision | Supports | Text resize, 400 % zoom reflow, AA contrast in both themes, prefers-contrast: more and forced colours honoured (1.4.3, 1.4.4, 1.4.10, 1.4.11). | |
| 4.2.3 Usage without perception of colour | Partially Supports | Every coloured state carries text; charts are not all reviewed (1.4.1). manual verification pending (#2864). | |
| 4.2.4 Usage without hearing | Supports | The product itself has no audio; meetings run in a third-party room and messaging is the non-voice channel. |
|
| 4.2.5 Usage with limited hearing | Supports | As 4.2.4. |
|
| 4.2.6 Usage with no or limited vocal capability | Supports | No function requires speech. |
|
| 4.2.7 Usage with limited manipulation or strength | Partially Supports | Keyboard alternatives to dragging, 44 px targets, no gesture or motion input (2.1.1, 2.5.x); whole-product keyboard pass pending. manual verification pending (#2864). | |
| 4.2.8 Usage with limited reach | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | Nothing flashes (2.3.1). |
|
| 4.2.10 Usage with limited cognition, language or learning | Partially Supports | Consistent navigation, plain-language errors, no time pressure beyond the 12-hour session, no CAPTCHA (3.2.x, 3.3.x, 2.2.1). Readability has not been evaluated. manual verification pending (#2864). | |
| 4.2.11 Privacy | Supports | Accessibility features (text size, theme, OS preferences) are ordinary settings that disclose nothing about the person; the activity tracker is opt-in. |
Chapter 5: Generic Requirements
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 5.1 Closed functionality | Not Applicable | No closed functionality: the product runs in the user's own browser with their own assistive technology. | — |
| 5.2 Activation of accessibility features | Supports | The documented features (text size, theme) are ordinary visible controls; the OS preferences are honoured without any activation step. | |
| 5.3 Biometrics | Not Applicable | No biometric is used or required; passkeys are not offered. | — |
| 5.4 Preservation of accessibility information during conversion | Partially Supports | The only conversion the product performs is generating a certificate PDF from structured data; the PDF's tagging has not been evaluated. Tracked in #2864. | |
| 5.5 Operable parts | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
| 5.6 Locking or toggle controls | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
| 5.7 Key repeat | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
| 5.8 Double-strike key acceptance | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
| 5.9 Simultaneous user actions | Supports | No function requires two simultaneous actions; the one chord (Mod+K) has a menu equivalent. |
Chapter 6: ICT with Two-Way Voice Communication
Video meetings are provided by the embedded third-party Jitsi room, which is outside this evaluation and named as a known limitation on /accessibility. The product's own channels are text.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 6.1 Audio bandwidth for speech | Not Applicable | Voice is carried by the third-party room, not by the product. | |
| 6.2 Real-time text (RTT) functionality | Not Applicable | As 6.1. The product offers asynchronous messaging alongside every meeting. | |
| 6.3 Caller ID | Not Applicable | No telephony. | — |
| 6.4 Alternatives to voice-based services | Supports | Everything a meeting is used for (scheduling, notes, follow-ups) is also available through the product's text channels: messaging, meeting notes and to-dos. | |
| 6.5 Video communication | Not Applicable | As 6.1. | |
| 6.6 Alternatives to video-based services | Supports | As 6.4. |
Chapter 7: ICT with Video Capabilities
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 7.1 Caption processing technology | Not Applicable | The product has no video player; release-note clips are silent and play through the browser's own controls. | |
| 7.2 Audio description technology | Not Applicable | As 7.1. | |
| 7.3 User controls for captions and audio description | Not Applicable | As 7.1. |
Chapter 8: Hardware
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 8 Hardware | Not Applicable | Not applicable: the product is a web application with no hardware, closed functionality or physical controls. | — |
Chapter 9: Web
Clauses 9.1 to 9.4 are WCAG 2.1 Level A and AA by reference; each row below carries the conformance of the WCAG row with the same number (9.x.y.z ⇔ x.y.z) and is generated from it. The WCAG 2.2-only criteria (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8) are not part of clause 9 and are reported in the WCAG section only.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 9.1.1.1 Non-text Content | Partially Supports | See WCAG 1.1.1 Non-text Content. | |
| 9.1.2.1 Audio-only and Video-only (Prerecorded) | Supports | See WCAG 1.2.1 Audio-only and Video-only (Prerecorded). |
|
| 9.1.2.2 Captions (Prerecorded) | Not Applicable | See WCAG 1.2.2 Captions (Prerecorded). | |
| 9.1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | See WCAG 1.2.3 Audio Description or Media Alternative (Prerecorded). | |
| 9.1.2.4 Captions (Live) | Not Applicable | See WCAG 1.2.4 Captions (Live). | |
| 9.1.2.5 Audio Description (Prerecorded) | Not Applicable | See WCAG 1.2.5 Audio Description (Prerecorded). | |
| 9.1.3.1 Info and Relationships | Partially Supports | See WCAG 1.3.1 Info and Relationships. | |
| 9.1.3.2 Meaningful Sequence | Partially Supports | See WCAG 1.3.2 Meaningful Sequence. | |
| 9.1.3.3 Sensory Characteristics | Partially Supports | See WCAG 1.3.3 Sensory Characteristics. | |
| 9.1.3.4 Orientation | Supports | See WCAG 1.3.4 Orientation. |
|
| 9.1.3.5 Identify Input Purpose | Partially Supports | See WCAG 1.3.5 Identify Input Purpose. |
|
| 9.1.4.1 Use of Color | Partially Supports | See WCAG 1.4.1 Use of Color. | |
| 9.1.4.2 Audio Control | Not Applicable | See WCAG 1.4.2 Audio Control. |
|
| 9.1.4.3 Contrast (Minimum) | Supports | See WCAG 1.4.3 Contrast (Minimum). | |
| 9.1.4.4 Resize Text | Supports | See WCAG 1.4.4 Resize Text. | |
| 9.1.4.5 Images of Text | Partially Supports | See WCAG 1.4.5 Images of Text. | |
| 9.1.4.10 Reflow | Partially Supports | See WCAG 1.4.10 Reflow. | |
| 9.1.4.11 Non-text Contrast | Partially Supports | See WCAG 1.4.11 Non-text Contrast. | |
| 9.1.4.12 Text Spacing | Partially Supports | See WCAG 1.4.12 Text Spacing. | |
| 9.1.4.13 Content on Hover or Focus | Partially Supports | See WCAG 1.4.13 Content on Hover or Focus. | |
| 9.2.1.1 Keyboard | Partially Supports | See WCAG 2.1.1 Keyboard. | |
| 9.2.1.2 No Keyboard Trap | Supports | See WCAG 2.1.2 No Keyboard Trap. | |
| 9.2.1.4 Character Key Shortcuts | Partially Supports | See WCAG 2.1.4 Character Key Shortcuts. | |
| 9.2.2.1 Timing Adjustable | Partially Supports | See WCAG 2.2.1 Timing Adjustable. | |
| 9.2.2.2 Pause, Stop, Hide | Partially Supports | See WCAG 2.2.2 Pause, Stop, Hide. | |
| 9.2.3.1 Three Flashes or Below Threshold | Supports | See WCAG 2.3.1 Three Flashes or Below Threshold. |
|
| 9.2.4.1 Bypass Blocks | Supports | See WCAG 2.4.1 Bypass Blocks. | |
| 9.2.4.2 Page Titled | Supports | See WCAG 2.4.2 Page Titled. | |
| 9.2.4.3 Focus Order | Partially Supports | See WCAG 2.4.3 Focus Order. | |
| 9.2.4.4 Link Purpose (In Context) | Partially Supports | See WCAG 2.4.4 Link Purpose (In Context). | |
| 9.2.4.5 Multiple Ways | Supports | See WCAG 2.4.5 Multiple Ways. | |
| 9.2.4.6 Headings and Labels | Partially Supports | See WCAG 2.4.6 Headings and Labels. | |
| 9.2.4.7 Focus Visible | Supports | See WCAG 2.4.7 Focus Visible. | |
| 9.2.5.1 Pointer Gestures | Supports | See WCAG 2.5.1 Pointer Gestures. | |
| 9.2.5.2 Pointer Cancellation | Partially Supports | See WCAG 2.5.2 Pointer Cancellation. | |
| 9.2.5.3 Label in Name | Partially Supports | See WCAG 2.5.3 Label in Name. | |
| 9.2.5.4 Motion Actuation | Supports | See WCAG 2.5.4 Motion Actuation. |
|
| 9.3.1.1 Language of Page | Supports | See WCAG 3.1.1 Language of Page. | |
| 9.3.1.2 Language of Parts | Partially Supports | See WCAG 3.1.2 Language of Parts. | |
| 9.3.2.1 On Focus | Partially Supports | See WCAG 3.2.1 On Focus. | |
| 9.3.2.2 On Input | Partially Supports | See WCAG 3.2.2 On Input. | |
| 9.3.2.3 Consistent Navigation | Supports | See WCAG 3.2.3 Consistent Navigation. | |
| 9.3.2.4 Consistent Identification | Partially Supports | See WCAG 3.2.4 Consistent Identification. | |
| 9.3.3.1 Error Identification | Partially Supports | See WCAG 3.3.1 Error Identification. | |
| 9.3.3.2 Labels or Instructions | Partially Supports | See WCAG 3.3.2 Labels or Instructions. | |
| 9.3.3.3 Error Suggestion | Partially Supports | See WCAG 3.3.3 Error Suggestion. | |
| 9.3.3.4 Error Prevention (Legal, Financial, Data) | Supports | See WCAG 3.3.4 Error Prevention (Legal, Financial, Data). | |
| 9.4.1.1 Parsing | Not Applicable | See WCAG 4.1.1 Parsing. | |
| 9.4.1.2 Name, Role, Value | Partially Supports | See WCAG 4.1.2 Name, Role, Value. | |
| 9.4.1.3 Status Messages | Partially Supports | See WCAG 4.1.3 Status Messages. | |
| 9.5 WCAG conformance requirements | Partially Supports | Conformance level AA is targeted; full pages and complete processes are claimed only for the evaluated page states (appendix) — the remainder of the product is pending, so the conformance requirements are met partially. | |
| 9.6 WCAG conformance requirements (continued) | Partially Supports | As 9.5. |
Chapter 10: Non-web Documents
The product's interface is web content (chapter 9). The documents it produces itself are the certificate PDF and CSV/ICS exports; documents people upload (CVs, attachments) are their own.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 10 Non-web documents produced by the product | Partially Supports | CSV and ICS exports are plain structured text. The certificate PDF is generated from structured data but its tagging, reading order and language metadata have not been evaluated. Tracked in #2864. |
Chapter 11: Software
A web application: clauses 11.1 to 11.4 are covered by chapter 9 and are not repeated. The clauses that apply to the application as software are below.
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 11.5.2 Interoperability with assistive technology (accessibility services) | Supports | The product exposes semantics through HTML and WAI-ARIA to the browser's platform accessibility API; it ships no custom accessibility service and bypasses none. | |
| 11.6.1 User control of accessibility features | Supports | Text size and theme are ordinary settings; OS preferences are applied automatically (5.2). | |
| 11.6.2 No disruption of accessibility features | Supports | Reduced motion, more contrast and forced colours from the platform are honoured, not overridden; no key or gesture of the assistive technology is intercepted. | |
| 11.7 User preferences | Supports | Colour scheme, contrast, motion and forced colours follow the platform settings; the in-app text size adds to the browser's own zoom. | |
| 11.8.1 Authoring tool — content technology | Supports | What people author (messages, notes, announcements, goals) is stored as text and rendered as HTML; images are attached as files. | |
| 11.8.2 Authoring tool — accessible content creation | Partially Supports | Text content is accessible by construction; an attached image takes no alternative text and the composer gives no prompt for one. Tracked in #2864. | |
| 11.8.3 Authoring tool — preservation of accessibility information in transformations | Not Applicable | No transformation of authored content between formats, other than the PDF covered in 5.4. | — |
| 11.8.4 Authoring tool — repair assistance | Does Not Support | No accessibility checking or repair assistance is offered to authors. Tracked in #2864. | |
| 11.8.5 Authoring tool — templates | Partially Supports | Document templates an administrator provides are rendered through the same accessible interface; their own accessibility is the author's. Tracked in #2864. |
Chapter 12: Documentation and Support Services
| Kriterium | Konformitätsgrad | Anmerkungen und Erläuterungen | Beleg |
|---|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | The public accessibility statement documents the features, the standard, the scope, the known limitations and this report. | |
| 12.1.2 Accessible documentation | Supports | Product documentation is web pages in the product and Markdown in the public repository — text, with headings and alternatives, in EN/TR/DE where it is user-facing. | |
| 12.2.2 Information on accessibility and compatibility features | Supports | The statement names a feedback channel with a response target and an escalation route. | |
| 12.2.3 Effective communication | Partially Supports | Support is by e-mail and the public issue tracker (text); no alternative mode such as video relay is offered. Tracked in #2864. | |
| 12.2.4 Accessible documentation (support) | Supports | As 12.1.2. |
Anhang: automatisierte Belege
Was das Barrierefreiheits-Gate bei jeder Änderung prüft und was es fand – mit npm run vpat:evidence aus der Baseline-Datei erzeugt, nie von Hand geschrieben.
| Seite | Modus | Eingefrorene kritische/schwere Befunde |
|---|---|---|
| / | light | sauber |
| / | dark | sauber |
| /auth/signin | light | sauber |
| /auth/signin | dark | sauber |
| /accessibility | light | sauber |
| /accessibility | dark | sauber |
| /apply/:mentorId | light | sauber |
| /apply/:mentorId | dark | sauber |
| /portal | light | sauber |
| /portal | dark | sauber |
| /portal/journey | light | sauber |
| /portal/journey | dark | sauber |
| /portal/goals | light | sauber |
| /portal/goals | dark | sauber |
| /portal/calendar | light | sauber |
| /portal/calendar | dark | sauber |
| /account | light | sauber |
| /account | dark | sauber |
| /portal/requests | light | sauber |
| /portal/requests | dark | sauber |
| /portal/profile | light | sauber |
| /portal/profile | dark | sauber |
| /portal/projects | light | sauber |
| /portal/projects | dark | sauber |
| /portal/interactions | light | sauber |
| /portal/interactions | dark | sauber |
| /portal/notes | light | sauber |
| /portal/notes | dark | sauber |
| /mentor | light | sauber |
| /mentor | dark | sauber |
| /mentor/mentees | light | sauber |
| /mentor/mentees | dark | sauber |
| /admin | light | sauber |
| /admin | dark | sauber |
| /admin/candidates | light | sauber |
| /admin/candidates | dark | sauber |
| /messages | light | sauber |
| /messages | dark | sauber |
| /notifications | light | sauber |
| /notifications | dark | sauber |
| /mentor/board | light | sauber |
| /mentor/board | dark | sauber |
| /admin/board | light | sauber |
| /admin/board | dark | sauber |
| /admin/companies/:id | light | sauber |
| /admin/companies/:id | dark | sauber |
| /admin/settings | light | sauber |
| /admin/settings | dark | sauber |
| /company | light | sauber |
| /company | dark | sauber |
Baseline zuletzt geändert bei Commit: f419bba · 2026-10-07 · docs/legal/vpat-evidence.md
Selbstbewertung der Maintainer anhand der oben verlinkten Belege; zur Information, keine Zusicherung. Die Software erscheint unter AGPL-3.0-or-later und wird von unabhängigen Betreibern betrieben, die jeweils ihre eigene Erklärung und ihren Kontakt veröffentlichen.