WCAG 2.1 / BITV 2.0 Web Accessibility #638

Open
opened 2026-09-21 02:31:40 +00:00 by Cordy · 6 comments
Owner

research, check how others implement, pitfalls, challenges, post findings here first and approach, then decisions.

research, check how others implement, pitfalls, challenges, post findings here first and approach, then decisions.
Author
Owner

Research (2026-10-29)

Standards (VERIFIED): WCAG 2.2 adds 6 A/AA criteria to 2.1; EN 301 549 V4.1.1 (published 2 Sep 2026, WCAG 2.2 AA) expected in the OJ ~16 Dec 2026; EU WAD covers public bodies' intranets/extranets and requires an accessibility statement (model 2018/1523); Germany BGG §12a + BITV 2.0 explicitly cover electronic file management and procurement; Switzerland: eCH-0059 V3.0 = WCAG 2.1 AA, binding for the federal administration incl. intranets, statement + feedback required; BehiG revision planned for 2027. The EAA does not cover a self-hosted business file server (possibly the swisscairn.ch shop).
Market: Nextcloud "aims" for WCAG 2.1 AA (no ACR found); oCIS had axe tests but disabled in CI; OpenCloud has no product statement; Dropbox's 2025 ACR honestly lists "does not support" items; Microsoft publishes ACRs.

Audit of Cairn (axe-core over the static pages with everything visible, plus code reading; no real browser available):

  • Critical (Level A): Upload can't be reached by keyboard (label.btn around a hidden file input); the row ⋯ menu doesn't move focus, no aria-expanded, role=menu without menuitem, focus not returned.
  • High: file list has no table/list semantics; focus lost on folder navigation, no headings; ~21 unlabelled controls; contrast: --slate-400 text 3.12:1, input borders 1.2-1.5:1, dark danger text 3.88:1.
  • Medium: selected states only visual; untranslated English accessible names; tooltips not dismissible; crop only by dragging; sticky bars may hide focus; fixed 12 h session without warning (2.2.1).
  • Already good: page language incl. de-CH, login form, native modal dialogs, focus outlines, zoom allowed, targets ≥ 24 px.

Recommended approach: target WCAG 2.2 AA. Phase 0 tooling (jsdom + axe-core gating test with a shrinking baseline, plus webcheck pattern checks); phase 1 Level A blockers (upload, menus, list semantics, focus, labels, session warning); phase 2 AA (contrast tokens across themes, translated names, tooltips, crop alternative, scroll-padding, live regions); phase 3 manual AT pass (NVDA/JAWS/VoiceOver), ACR (VPAT 2.5 INT), statement template; phase 4 optional external audit. Roughly 15-25 days. Ship an operator-fillable accessibility statement (EN/DE/FR/IT, 2018/1523 + eCH-0059) and an operator setting for the statement URL/feedback contact.

Open questions (recommendations): target → WCAG 2.2 AA; file list → ARIA table roles on the existing grid (no display tricks), tiles as a list; menus → one shared APG menu-button helper; npm devDependencies (jsdom + axe-core, pinned) for the test → yes; external audit → after the self-assessed ACR, before the first public-sector tender; session timeout → warning dialog with "Stay signed in"; contrast → fix tokens so all themes pass; shop + EAA → short legal check.

## Research (2026-10-29) **Standards (VERIFIED):** WCAG 2.2 adds 6 A/AA criteria to 2.1; EN 301 549 V4.1.1 (published 2 Sep 2026, WCAG 2.2 AA) expected in the OJ ~16 Dec 2026; EU WAD covers public bodies' intranets/extranets and requires an accessibility statement (model 2018/1523); Germany BGG §12a + BITV 2.0 explicitly cover electronic file management and procurement; Switzerland: eCH-0059 V3.0 = WCAG 2.1 AA, binding for the federal administration incl. intranets, statement + feedback required; BehiG revision planned for 2027. The EAA does not cover a self-hosted business file server (possibly the swisscairn.ch shop). **Market:** Nextcloud "aims" for WCAG 2.1 AA (no ACR found); oCIS had axe tests but disabled in CI; OpenCloud has no product statement; Dropbox's 2025 ACR honestly lists "does not support" items; Microsoft publishes ACRs. **Audit of Cairn** (axe-core over the static pages with everything visible, plus code reading; no real browser available): - **Critical (Level A):** Upload can't be reached by keyboard (`label.btn` around a hidden file input); the row ⋯ menu doesn't move focus, no `aria-expanded`, `role=menu` without `menuitem`, focus not returned. - **High:** file list has no table/list semantics; focus lost on folder navigation, no headings; ~21 unlabelled controls; contrast: `--slate-400` text 3.12:1, input borders 1.2-1.5:1, dark danger text 3.88:1. - **Medium:** selected states only visual; untranslated English accessible names; tooltips not dismissible; crop only by dragging; sticky bars may hide focus; fixed 12 h session without warning (2.2.1). - Already good: page language incl. de-CH, login form, native modal dialogs, focus outlines, zoom allowed, targets ≥ 24 px. **Recommended approach:** target **WCAG 2.2 AA**. Phase 0 tooling (jsdom + axe-core gating test with a shrinking baseline, plus `webcheck` pattern checks); phase 1 Level A blockers (upload, menus, list semantics, focus, labels, session warning); phase 2 AA (contrast tokens across themes, translated names, tooltips, crop alternative, scroll-padding, live regions); phase 3 manual AT pass (NVDA/JAWS/VoiceOver), ACR (VPAT 2.5 INT), statement template; phase 4 optional external audit. Roughly 15-25 days. Ship an operator-fillable accessibility statement (EN/DE/FR/IT, 2018/1523 + eCH-0059) and an operator setting for the statement URL/feedback contact. **Open questions (recommendations):** target → WCAG 2.2 AA; file list → ARIA table roles on the existing grid (no `display` tricks), tiles as a list; menus → one shared APG menu-button helper; npm devDependencies (jsdom + axe-core, pinned) for the test → yes; external audit → after the self-assessed ACR, before the first public-sector tender; session timeout → warning dialog with "Stay signed in"; contrast → fix tokens so all themes pass; shop + EAA → short legal check.
Author
Owner

Decision (Nikola, 2026-10-29): target WCAG 2.2 AA; the phased approach above is approved, including pinned jsdom + axe-core as test-only dependencies. Next: phase 0 (gating test + baseline) and phase 1 (Level A blockers); a mockup only where the UI changes visibly (session warning dialog).

**Decision (Nikola, 2026-10-29):** target WCAG 2.2 AA; the phased approach above is approved, including pinned jsdom + axe-core as test-only dependencies. Next: phase 0 (gating test + baseline) and phase 1 (Level A blockers); a mockup only where the UI changes visibly (session warning dialog).
Author
Owner

Phases 0 and 1 shipped in v0.6.371 (PR #1047).

  • Phase 0: gating accessibility check in CI (web/test/a11y: jsdom 26.1.0 + axe-core 4.14.0 pinned with lockfile integrity; WCAG 2.0/2.1/2.2 A+AA rules over all four pages; baseline only shrinks, 59 → 27 entries, all script-filled labels); internal/webcheck checks for label-as-button, untranslated aria-labels, menus without menu items.
  • Phase 1: keyboard-reachable Upload (toolbar, empty state, profile picture); one APG menu-button helper for every menu (focus, arrows, Home/End, Escape/Tab, focus return, menu names); file list as ARIA table (tiles as list, sorted column, selected rows, lock text); folder navigation moves focus to a hidden heading when needed and announces the folder politely; unlabelled controls labelled; current/pressed/checked states exposed. No visual changes. app.test.js (38 tests) boots the app in jsdom.

Still to do: the session-timeout warning (mockup 638-session-warning-mockup.html waiting for review), phase 2 (contrast tokens across themes, ⋯ button names "Actions for {name}", tooltips, crop alternative, sticky bars, avatar button name, type-ahead, aria-rowcount), phase 3 (manual NVDA/JAWS/VoiceOver pass, ACR, operator statement template). Live check: try the app with keyboard only (#1005).

Phases 0 and 1 shipped in v0.6.371 (PR #1047). - **Phase 0:** gating accessibility check in CI (`web/test/a11y`: jsdom 26.1.0 + axe-core 4.14.0 pinned with lockfile integrity; WCAG 2.0/2.1/2.2 A+AA rules over all four pages; baseline only shrinks, 59 → 27 entries, all script-filled labels); `internal/webcheck` checks for label-as-button, untranslated aria-labels, menus without menu items. - **Phase 1:** keyboard-reachable Upload (toolbar, empty state, profile picture); one APG menu-button helper for every menu (focus, arrows, Home/End, Escape/Tab, focus return, menu names); file list as ARIA table (tiles as list, sorted column, selected rows, lock text); folder navigation moves focus to a hidden heading when needed and announces the folder politely; unlabelled controls labelled; current/pressed/checked states exposed. No visual changes. `app.test.js` (38 tests) boots the app in jsdom. Still to do: the session-timeout warning (mockup `638-session-warning-mockup.html` waiting for review), phase 2 (contrast tokens across themes, ⋯ button names "Actions for {name}", tooltips, crop alternative, sticky bars, avatar button name, type-ahead, aria-rowcount), phase 3 (manual NVDA/JAWS/VoiceOver pass, ACR, operator statement template). Live check: try the app with keyboard only (#1005).
Author
Owner

Session warning mockup approved (Nikola, 2026-10-29): design-direction-decision-needed/638-session-warning-mockup.html with its recommendations: warn 5 minutes before the end; local/LDAP: one extension to 24 h after sign-in, then sign in again in a dialog (password, no page change); OIDC: re-sign-in in a small window (/auth/done), callback ends the old session; Esc closes into a banner and never extends; any 401 keeps the page and offers sign-in; another person signing in reloads; no session-length setting; warning in every tab, closed everywhere via BroadcastChannel; uploads pause on 401 and resume after signing in. Next: build with the phase 2 items.

**Session warning mockup approved (Nikola, 2026-10-29):** `design-direction-decision-needed/638-session-warning-mockup.html` with its recommendations: warn 5 minutes before the end; local/LDAP: one extension to 24 h after sign-in, then sign in again in a dialog (password, no page change); OIDC: re-sign-in in a small window (`/auth/done`), callback ends the old session; Esc closes into a banner and never extends; any 401 keeps the page and offers sign-in; another person signing in reloads; no session-length setting; warning in every tab, closed everywhere via BroadcastChannel; uploads pause on 401 and resume after signing in. Next: build with the phase 2 items.
Author
Owner

Decision (2026-10-29): WCAG 2.2.1 Timing Adjustable is supported with a repeatable one-click extension.

Research, all read today:

  • W3C Understanding 2.2.1: a time limit passes if the user is warned and can extend it at least 10 times with a simple action, or if it is longer than 20 hours. Security time limits count as set by the content. Some security limits can be essential.
  • NIST SP 800-63B-4 §2.1.3, §2.2.3, §2.3.3 and §5.2:
    • AAL1: overall at most 30 days.
    • AAL2: overall should be at most 24 h, inactivity should be at most 1 h.
    • AAL3: overall shall be at most 12 h.
    • The RP may warn and let the user continue before the timeout.
  • OWASP ASVS 5.0 V7.1.1, V7.3.1, V7.3.2: the limits must be documented and justified against NIST.

Design:

  • A session lasts 12 h from sign-in, as before.
  • From 5 minutes before the end, the warning offers Stay signed in. Each press adds 1 hour.
  • Presses are allowed up to 24 h after sign-in, which gives 12 extensions. This meets the "Extend" option.
  • The 24 h hard cap falls under the 20-hour exception and stays within NIST AAL2's 24 h overall limit. Each press also shows that a person is still there.
  • At the cap, Cairn asks for a fresh sign-in in a dialog and keeps the page and held work (2.2.5).
  • This applies to OIDC sessions too. Cairn's own session is extended with one click, and disablement at the identity provider still ends it through the existing re-checks and back-channel logout.
  • Deployments that need AAL3's 12 h limit are a documented exception (essential security limit).

The conformance report row for 2.2.1 moves to "Supports". This is built into the #638 release before it ships.

**Decision (2026-10-29): WCAG 2.2.1 Timing Adjustable is supported with a repeatable one-click extension.** Research, all read today: - W3C Understanding 2.2.1: a time limit passes if the user is warned and can extend it at least 10 times with a simple action, or if it is longer than 20 hours. Security time limits count as set by the content. Some security limits can be essential. - NIST SP 800-63B-4 §2.1.3, §2.2.3, §2.3.3 and §5.2: - AAL1: overall at most 30 days. - AAL2: overall should be at most 24 h, inactivity should be at most 1 h. - AAL3: overall shall be at most 12 h. - The RP may warn and let the user continue before the timeout. - OWASP ASVS 5.0 V7.1.1, V7.3.1, V7.3.2: the limits must be documented and justified against NIST. Design: - A session lasts 12 h from sign-in, as before. - From 5 minutes before the end, the warning offers **Stay signed in**. Each press adds 1 hour. - Presses are allowed up to 24 h after sign-in, which gives 12 extensions. This meets the "Extend" option. - The 24 h hard cap falls under the 20-hour exception and stays within NIST AAL2's 24 h overall limit. Each press also shows that a person is still there. - At the cap, Cairn asks for a fresh sign-in in a dialog and keeps the page and held work (2.2.5). - This applies to OIDC sessions too. Cairn's own session is extended with one click, and disablement at the identity provider still ends it through the existing re-checks and back-channel logout. - Deployments that need AAL3's 12 h limit are a documented exception (essential security limit). The conformance report row for 2.2.1 moves to "Supports". This is built into the #638 release before it ships.
Author
Owner

Phase 2 and the session time limit warning shipped in v0.6.373 (PR #1049). Both dogfoods run v0.6.373; pods ready, only the known WARN lines at start.

Session time limit (frames A to E)

  • Warning: shown 5 minutes before the end. Stay signed in adds one hour from the current end and is accepted only within 10 minutes of it, so two tabs pressing at once still add one hour. It works up to 24 h after sign-in for every account source.
  • At the cap: local and LDAP accounts enter the password in a dialog; identity-provider accounts use the sign-in window, with /auth/done.
  • Signed out without losing the page:
    • A 401 without a code holds requests and sends them again after the same person signs in. A different person causes a reload.
    • Uploads pause and resume from the server offset.
    • Other tabs follow through BroadcastChannel.
    • When /me cannot be read, nothing is resumed.
  • Users & access: a Browser sessions row.
  • Audit: auth-session-extended with step=<n>.

WCAG 2.2.1: now "Supports". See the decision above: the Extend option allows 12 simple extensions, and the 24 h cap falls under the 20-hour exception.

Phase 2 (AA)

  • Contrast tokens pass for all 5 themes x 4 accents, with a contrast test. Visible changes: the light default accent is now #2b7483, and dark danger buttons and dark sign-in buttons now have dark text.
  • Names: "Actions for {name}" on row menus and "Account menu for {name}".
  • Tooltips can be hovered, dismissed with Esc and clicked through.
  • Crop and the details divider work without dragging.
  • Scroll padding keeps focused items clear of sticky bars, and reduced motion is respected.
  • Menu type-ahead, row count and index across pages, and focus moves to a sensible place after a delete.
  • One live-region helper: each message is spoken once, and errors are assertive.
  • The public share pages are in the axe check through golden pages. The axe baseline is empty, with 18 script-filled names, each tested in jsdom.

Docs: an accessibility statement template (EN and DE) and a WCAG 2.2 ACR skeleton under docs/accessibility/, plus the handbook and ARCHITECTURE.md.

Still open for phase 3:

  • An external audit or assistive-technology test.
  • Filling in the ACR rows.
  • FR and IT versions of the statement template.

The live checks are in #1005.

**Phase 2 and the session time limit warning shipped in v0.6.373** (PR #1049). Both dogfoods run v0.6.373; pods ready, only the known WARN lines at start. **Session time limit (frames A to E)** - **Warning:** shown 5 minutes before the end. **Stay signed in** adds one hour from the current end and is accepted only within 10 minutes of it, so two tabs pressing at once still add one hour. It works up to 24 h after sign-in for every account source. - **At the cap:** local and LDAP accounts enter the password in a dialog; identity-provider accounts use the sign-in window, with `/auth/done`. - **Signed out without losing the page:** - A 401 without a code holds requests and sends them again after the same person signs in. A different person causes a reload. - Uploads pause and resume from the server offset. - Other tabs follow through BroadcastChannel. - When `/me` cannot be read, nothing is resumed. - **Users & access:** a Browser sessions row. - **Audit:** `auth-session-extended` with `step=<n>`. **WCAG 2.2.1:** now "Supports". See the decision above: the Extend option allows 12 simple extensions, and the 24 h cap falls under the 20-hour exception. **Phase 2 (AA)** - Contrast tokens pass for all 5 themes x 4 accents, with a contrast test. Visible changes: the light default accent is now #2b7483, and dark danger buttons and dark sign-in buttons now have dark text. - Names: "Actions for {name}" on row menus and "Account menu for {name}". - Tooltips can be hovered, dismissed with Esc and clicked through. - Crop and the details divider work without dragging. - Scroll padding keeps focused items clear of sticky bars, and reduced motion is respected. - Menu type-ahead, row count and index across pages, and focus moves to a sensible place after a delete. - One live-region helper: each message is spoken once, and errors are assertive. - The public share pages are in the axe check through golden pages. The axe baseline is empty, with 18 script-filled names, each tested in jsdom. **Docs:** an accessibility statement template (EN and DE) and a WCAG 2.2 ACR skeleton under `docs/accessibility/`, plus the handbook and ARCHITECTURE.md. **Still open for phase 3:** - An external audit or assistive-technology test. - Filling in the ACR rows. - FR and IT versions of the statement template. The live checks are in #1005.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#638
No description provided.