AccessPoint Accessibility Conformance Report
WCAG 2.2 Level A / AA and WCAG 2.1 Level A / AA — self-assessment. This report covers the AccessPoint application in both editions — Microsoft 365 and hosted. The accessibility statement for this website is at realizer.io/accessibility.
| Product | AccessPoint — the platform for public-sector access, privacy, and responsible AI, in two editions: Hosted AccessPoint and AccessPoint for Microsoft 365 |
|---|---|
| Version evaluated | 2.6.0 — the application, the public portal, the generated outputs and, new in 2.6.0, the hosted edition (AccessPoint on Realizer's own service). The sections on the surfaces built for 2.6.0 still say built for 2.6.0, not part of 2.5.0: they were written before this edition. 2.5.0, the release before, was the first published since 2.1.0 and carried the code built during September 2026 as the "2.2.1 pre-release" and then numbered 2.4.0, so the dated notes below that name 2.2.1 or 2.4.0 refer to code shipped in 2.5.0. Rows first assessed on an earlier version were carried forward and re-checked where they say so |
| Report date | 2026-11-12 — for 2.6.0: the owner's NVDA pass over the 2.6.0 surfaces and the hosted edition on hosted stage (method 26), the in-page checks and the 320 CSS px reflow pass on stage (method 25: three defects, fixed) and the 2.6.0 core functional run on the dev tenant (method 27), after the code reviews and audits of 2026-11-01 – 10 (methods 17 – 24). Earlier editions: 2026-09-03 (2.1.0); revised 2026-09-25 for the 2.4.0 code, 2026-10-05 for 2.5.0, 2026-10-07 for its release candidate, 2026-10-13 for its runtime pass and 2026-10-14 for its core functional run (method 16) |
| Vendor | Realizer Services Inc. |
| Contact | realizer.io/support/contact |
| Standards applied | Web Content Accessibility Guidelines (WCAG) 2.2, Levels A and AA (w3.org/TR/WCAG22), and WCAG 2.1, Levels A and AA (w3.org/TR/WCAG21). WCAG 2.2 contains every WCAG 2.1 success criterion except 4.1.1 Parsing (obsolete, removed in 2.2) and adds six at Level A / AA (Table 2b), so one set of findings answers both: Tables 1 and 2 hold the criteria the two versions share (and 4.1.1 for 2.1), Table 2b the six 2.2 adds. See Conformance at a glance |
| WCAG 2.2 additions — whole application | Assessed 2026-09-25 on 2.4.0 (method 8): every drag, sticky or floating element, small target, help placement, repeated entry and sign-in across the application, the PDF viewer and the portal; the media viewer was first assessed against them on 2026-09-23. The defects found were fixed the same day — Table 2b. The PDF viewer assessed then was the third-party viewer used before 2.5.0; the native viewer that replaced it was measured against the same criteria on 2026-09-30 (method 13) |
| Report format | Modelled on the ITI VPAT® 2.5 WCAG edition (self-assessed; not an ITI-certified VPAT) |
| Evaluation type | Vendor self-assessment. No third-party audit has been performed. |
| Media records section | Re-assessed 2026-09-23 on the 2.2.1 pre-release against WCAG 2.2 Level A / AA and EN 301 549 V3.2.1 clause 7 (video and audio) — a line-by-line code audit (34 findings: 3 High, 15 Medium, 16 Low); every High and Medium finding and most Low ones were fixed the same day in code. Re-checked later the same day for the marking UI that replaced the mark editor (the mark bar and the marks area), audio description (an imported description track, played and released), secondary audio tracks in releases, Windows forced colours, and Escape on the hover preview. Code-reviewed 2026-09-23; live screen-reader pass pending — see Accessibility features and known limitations — media records |
| Media marks in the panel card (2.6.0) | 2026-11-04, code-reviewed against WCAG 2.2 A / AA and tested on the build branch: a video or audio mark's effect, exemption and alternate exemptions moved from the mark bar into the redaction card (the same card as a document mark), and a new mark gets a New mark card. The effect is a radiogroup named by its visible label (1.3.1, 4.1.2), each option's accessible name is its visible name (2.5.3) and its one-line explanation its description; a change commits once the arrow keys stop or focus leaves the group, so arrowing never writes three edits; the mark bar's summary button's name begins with its visible text and moves focus to the card's checked radio (2.4.3), showing the panel first when it was hidden (1.4.10 — the rail starts collapsed at narrow widths); targets are 24 × 24 CSS px or more (2.5.8); theme tokens only (1.4.3, 1.4.11). Evidence: Jest (RedactionCardMediaSection, MediaDraftCard, MediaViewerModal.card) and axe-core in the demo's Playwright run (videoCard.spec.ts, English and French: the New mark card and a saved mark's card). On 2026-11-10 (method 21) the viewer was measured at 320 CSS px in the demo: player, timeline, marks area and panel stack, nothing scrolls sideways, axe finds nothing. On 2026-11-12 the owner's NVDA pass on hosted stage heard the card's effect radio group and its options as this row describes (method 26, SR-27) |
| Redaction discussion in the document preview (2.6.0) | 2026-11-04, code-reviewed against WCAG 2.2 A / AA and tested on the build branch: the read-only document preview offers advisors and reviewers Discuss redactions, a panel beside the record (RF-2). The header button is a disclosure with aria-expanded and aria-controls (4.1.2), keeps its accessible name when its label collapses to an icon below 900 px (2.5.3, 1.1.1), and the panel is a complementary landmark named by its heading (1.3.1). Each redaction is a native button disclosing its thread (2.1.1); a flag is shown by an icon AND said in the button's name (… Flagged for discussion, 1.4.1, 1.3.1). Flag and Resolve open Fluent dialogs named by their titles, which trap and return focus (2.1.2, 2.4.3); the flag's reason is a labelled, required field and Flag stays off until it is filled (3.3.2); after an action focus goes back to the redaction and the outcome is announced through a status message (4.1.3). At 640 px the panel stacks under the record (1.4.10); targets are 24 × 24 CSS px or more (2.5.8); theme tokens only (1.4.3, 1.4.11). Evidence: Jest (PreviewRedactionDiscussion.test.tsx: the disclosure states, the accessible names, the required reason, focus return and the status messages). axe-core in jsdom over every test of the panel found nothing on 2026-11-10 (method 21). Not yet scanned with axe-core in a browser — not on the dev tenant, and the demo has no advisor persona. The owner's NVDA pass on hosted stage heard the panel, a redaction's thread, a flag and its outcome as described here on 2026-11-12 (method 26, SR-22) |
| Status colours and Label in Name (2.6.0, UI-1 / UI-2) | 2026-11-04, on the build branch. One status palette (UI-1): every status chip, summary card, row accent and settings preview takes its colour from one palette with light, dark and high-contrast values; the message tints of notices, banners, check results and report KPI accents are hues of the same palette since UI-2, gaining a high-contrast set (they used the dark values there). Every text pair is computed from the tokens in all three themes — chip and tint text ≥ 4.5:1 on its fill AND on every page surface (1.4.3), every accent, dot, bar and hairline ≥ 3:1 (1.4.11) — and colour is never the only signal (1.4.1): chips keep their words and icons. Label in Name (2.5.3): axe-core 4.14 (label-content-name-mismatch) found four patterns whose accessible name did not contain the words shown — the summary cards (their count and title ran together in the DOM: 6Active requests), the preview's file name button (named only Show document details), and the redaction list and media mark rows (their badges ran together, and the status, origin, author and comment count were missing from the name). Each name now starts with the visible words; the rows end with what only a screen reader needs (Locked, Flagged for discussion, the alternate exemptions), and a card's tooltip is its explanation, never a second reading of its name. The Settings colour swatches are named by the palette's colours in the user's language (they read the raw token, in English). Evidence: Jest (statusPalette.contrast.test.ts, labelInName.test.tsx — the four patterns in all 11 languages, checked as axe checks them — StatusSwatchPicker.test.tsx) and axe-core 4.14.0 on every screen of the demo's Playwright run in a real browser, 11 languages. No screen-reader pass of the new names yet |
| Generated outputs section | Re-assessed 2026-09-25 on the 2.2.1 pre-release after the accessible-releases program (phases 1–5, 2026-09-23 – 25): tagged conversions with described links, tagged package pages and the all-or-nothing merge, the accessibility check, the accessible edition for redacted, scanned and untagged records, and release captions that say what withheld a passage. Evidence: code review, unit tests and local runs of the PDF/UA checker (PDF/UA-1); no generated PDF or edition has been read with a screen reader yet |
| Application runtime pass | 2026-09-25 on the 2.2.1 pre-release (dev tenant, SharePoint, Chrome): axe-core 4.10.2 scans, a 320 CSS px reflow pass and keyboard checks over the dashboards, case panels, document workspace, media viewer, PDF-viewer shell, release variants and Settings. Eight kinds of defect were fixed and re-scanned the same day; one Fluent UI pattern is recorded, not changed — see method 6 under Evaluation methods. Repeated for the 2.5.0 release candidate on 2026-10-13 (method 15) |
| DPIA validation section | 2.5.0: the Validation tab, section evaluation, the regulator consultation card, the risk map and overview, the screening-list question and Settings → Screening lists, code-reviewed against WCAG 2.2 A / AA on 2026-10-05 (contract obligations and their Jest suites); no runtime or screen-reader pass yet. The CNIL PIA report layout and the risk maps printed in the assessment PDFs are built too; no generated report has yet been checked with the PDF/UA checker or read with NVDA — see the section |
| Native viewer and editors section | 2.5.0: AccessPoint's own PDF viewer and its own Working Files Word and spreadsheet editors, which replaced the third-party viewer and editors. Scanned with axe-core in real-browser tests on every build, and measured on the dev tenant with an NVDA pass at 200 % zoom on 2026-09-30 (four defects found and fixed the same day) — methods 12 and 13 and Native document viewer and Working Files editors |
| 2.5.0 release candidate | Method 15: a static review on 2026-10-07 of everything changed after the 2026-10-05 edition — the diagram editor's fourth and fifth versions, the privacy subject's Diagrams tab, the Training hub, Guide me and Get started by topic, request pattern review, identity verification on the Requestor tab, Open contact / Open institution, Require attestation, English spelling, review templates in every language, the statistical template form, the host abstraction — and of the 2.5.0 surfaces this report had not yet described (audits, follow-up rules and reminders, computed due dates and the received-date correction, the register filter bar, column menus and bulk reassign, the Risks tab and its heat map, the administrator banners and the SharePoint package update). The runtime pass on the dev tenant followed on 2026-10-13: axe-core over My Day and every dashboard, every tab of a request, assessment, incident, complaint and audit panel, the Training hub and its destinations, the privacy program and the diagram editor, all 80 Settings panels and all 42 report sections; a 320 CSS px and a 640 CSS px (200 %) reflow pass; and the keyboard paths of the new surfaces. Every item the static review left open and every defect the runtime pass found is fixed, and the fixes were re-checked on dev (a few by unit test) — see 2.5.0 release-candidate changes |
| Training section | 2.5.0: Lab mode, Guide me tours, first-time tips, Get started, the training case guide, the progress table and the exercise console, code-reviewed and unit-tested on 2026-10-05 and re-reviewed on 2026-10-07 for the Training hub, Get started by topic and Guide me following the person into a panel (Table 4 corrected); the surfaces were scanned with axe, measured at 320 and 640 CSS px and walked from the keyboard on 2026-10-13 (method 15); the live screen-reader pass has not been run — Table 4 |
| Other 2.5.0 surfaces | Spreadsheet layout and hidden content (axe scans on dev, 2026-10-01), case archiving and the discovery survey (code-reviewed 2026-10-05), Report Builder's register scoping and per-currency totals, the activity tray, System health, the privacy program hub and the Storage report. The privacy program hub (its Discovery tab included), System health on My Day, the Storage report and Settings → Storage and archiving were scanned with axe on 2026-10-13 (method 15). None has had a screen-reader pass — see Spreadsheet layout and hidden content, Case archiving and storage and Discovery survey, Report Builder and the other 2.5.0 additions |
| AccessPoint Learning coach section | Built for 2.6.0, not part of 2.5.0: the How we decide disclosure at the twelve coach points and the coach notes editor (its block editor included), code-reviewed against WCAG 2.2 A / AA on 2026-11-01 with their unit tests (method 17), and axe-core in jsdom over every test of these surfaces on 2026-11-10 (method 21, which also fixed focus after a linked module's Remove); no runtime axe scan in a browser yet. The owner's NVDA pass on hosted stage heard How we decide at a decision point on 2026-11-12 (method 26, SR-15); the coach notes editor was not part of it — AccessPoint Learning coach — How we decide and coach notes |
| AccessPoint Learning Studio, page editor and player section | Built for 2.6.0, not part of 2.5.0: the module player, My learning (with the mentor's Waiting for you and the learner landing), the Studio (module editor, step outline, findings, Learning paths and audience rules, Assets, Translations, the overlay editor) and the page editor host, code-reviewed against WCAG 2.2 A / AA on 2026-11-01 with their unit tests; the page editor itself also passes an automated axe WCAG 2.2 AA scan in a headless browser (method 18); the UX and accessibility audit of 2026-11-10 (method 21) ran axe-core in jsdom over every test of these surfaces and fixed the focus, language-of-parts, label-in-name and findings gaps method 18 recorded, except those its rows still name; no runtime axe scan over the Studio or the player in a browser yet. The owner's NVDA pass on hosted stage (method 26, 2026-11-12) covered My learning, the player and Mark done (SR-16), the Studio's findings on their fields (SR-24) and a module written in French (SR-32) — not the page editor, Assets, the overlay editor or the Translations tab — AccessPoint Learning — the Studio, the page editor and the module player |
| AccessPoint Learning L3 section | Built for 2.6.0, not part of 2.5.0: the Check, Decide and Exercise steps in the player and their Studio editors, certificates (Your certificates, Verify a certificate, revoking and More attempts), recertification and the new Team progress columns, the Training coverage report, the Studio's Quality, Glossary and Obligations tabs with the term picker and the glossary term in pages, training done elsewhere, suggested audiences and the coach's Learn more, code-reviewed against WCAG 2.2 A / AA on 2026-11-03 with their unit tests (method 19); the 2026-11-10 audit (method 21) ran axe-core in jsdom over their tests and fixed the focus, 3.3.4 and naming gaps method 19 recorded, except those its rows still name; no runtime axe scan in a browser yet. The owner's NVDA pass on hosted stage (method 26, 2026-11-12) covered a Check with Try again and the last attempt (SR-17), a Decide step and its confirmation (SR-18), the certificate and Verify a certificate (SR-19) and a Glossary refusal on its field (SR-25) — not Team progress, the Training coverage report, the Quality and Obligations tabs or Training done elsewhere — AccessPoint Learning — checks, certificates, reports and the L3 screens |
| Lab scenarios and the script editor (TM-3B) | Built for 2.6.0, not part of 2.5.0 (design §10.3, static review 2026-11-05): the Studio's Lab scenarios table has a caption and column headers; every action names its person (Write our script for Jamie Okonkwo); the script editor is a labelled panel whose every field has a visible label, whose rounds and different answers are fieldsets with legends (Reply 1, Different answer 1), whose order is set with numbered selects (never dragging, 2.5.7), and whose save errors sit in an error summary with role="alert" that takes focus (3.3.1, 3.3.3) and again on the round they concern (aria-describedby); focus returns to the button that opened it; status messages are polite (4.1.3); nothing times out. Planning's Write {name}'s script for this simulation opens the same editor. Supports (static review; the runtime pass is TM-Z's). |
| Onboarding, read-only states, the demo and the Training Lab (2.6.0) | Built for 2.6.0, not part of 2.5.0, code-reviewed against WCAG 2.2 A / AA on 2026-11-07 with their unit tests (method 20): the guided welcome dialog and the occasional user's Here's your task card; the hosted session warning and the signed-out notice (2.2.1 in Table 1 re-checked against the code); the licence read-only banner, the Free plan's register banner, case line and recorded-request line, the disabled New with its visible reason, and the Reader view; the privacy program hub on the Free plan; the marketing demo's welcome card, its Next steps pill, the Tours & pricing panel and the bar collapsed to Menu; and the Training Lab's one-box join (Is that you?, the e-mail code) and the instructor console's Show to the class, New resume code, Live grid chips, Results summary and New class wizard. The demo surfaces are also scanned with axe-core (WCAG 2.2 AA tags) in the demo's Playwright run; nothing else here had a runtime scan. The owner's NVDA pass on hosted stage (method 26, 2026-11-12) heard the welcome dialog (SR-05), the session warning (SR-13), Here's your task (SR-21) and the Free plan's unavailable New with its reason (SR-23); the marketing demo and the Training Lab's own site had no screen-reader pass. On 2026-11-10 (method 21) Here's your task got its unit test, with axe-core, and focus after Got it; the licence read-only banner's test runs axe-core too — Onboarding, read-only states, the marketing demo and the Training Lab |
| Rolling releases, dated settings, the Reports menu and AI deployments (2.6.0) | Built for 2.6.0, not part of 2.5.0, assessed on 2026-11-10 (method 21): the releases of a request, a release's index and schedule, Build the next release and its picker, Send release…, and the Reports menu in a real browser through the marketing demo — axe-core 4.14 at 1440 × 900 (English and French along the flows, the Releases sub-tab in all eleven languages), 1366 × 768 and 320 CSS px, target size, the keyboard; and dated settings (Available from / Available until, Fee change on a date, Mandatory from) and Settings → Features & AI → Your own AI deployments in jsdom with axe-core and by code review (they are not in the demo). One defect the keyboard could not get round (a release's index at 320 CSS px) and seven smaller ones were fixed the same day. The owner's NVDA pass on hosted stage (method 26, 2026-11-12) covered the Releases tab, a release's index, the picker and Send release… (SR-20), the Reports menu (SR-28) and dated settings (SR-29); Your own AI deployments had none — Rolling releases, dated settings, the Reports menu and AI deployments |
| Hosted edition (2.6.0) | Built for 2.6.0, not part of 2.5.0, assessed on 2026-11-10 (method 22): the hosted person's journey — the global entry (app.realizer.io: the region page, the chooser after the sign-in, Regions unavailable), the web host's signed-out, sign-in-failed and not-found pages, the live client's own screens (the sign-in and sign-up landings, Create organization with the data region, the Terms line and Ask to join, Create another organization and its two kinds, the organization picker, the header's switcher and account menu, the invitation, the session and organization dialogs) — in a real browser with axe-core 4.14 at 1366 × 768 and 320 CSS px in all eleven languages (the server pages in the light and dark schemes too); and, in jsdom with axe and by code review, the hosted parts of the app: the welcome's trial and Free lines, the trial and Free banners, Extend 30 days, the allowance banners and usage meters, the session warning, AI processing outside {geography}, Colleagues, Who can join, Signing out, the organization's e-mail and Reply-To code, the public portal's plan line and address, and — once hosted pricing P3 merged the same night — Settings → Subscription with Bundles and storage, the buy dialog and its one-click entry points. 43 findings, all fixed the same day. Then on hosted stage itself: in-page checks of contrast, target size and names with the keyboard (2026-11-10) and a 320 CSS px reflow pass (2026-11-12: three defects, fixed — method 25), and the owner's NVDA pass over the journey from the region page to signing out, Subscription and the buy dialog, AI processing outside Canada, the session warning and invitations (method 26, SR-01 – SR-14 and SR-30) — Hosted edition |
| Public portal section | AccessPoint.Portal, first shipped in 2.5.0. Self-assessed on its pre-release code on 2026-09-15 and re-checked 2026-09-22 for the phase 1–3 additions (steps, history, My requests, clarity panel, withdraw and fee answer, reading room) and 2026-09-23 for the second audit, against WCAG 2.1 Level A / AA and the six Level A / AA success criteria added in WCAG 2.2 (w3.org/TR/WCAG22) — Table 3. The changes made before release are listed under Changes before release (2.5.0) |
Product description and scope
AccessPoint is an enterprise access-to-information / privacy case-management application. The user interface is a React 18 + Fluent UI 8 application (≈670 components) in a shared UI package, rendered by a SharePoint Framework (SPFx) web part hosted inside SharePoint pages and as a Microsoft Teams personal tab, backed by an ASP.NET Core API in the customer's Azure tenant. (Since 2.5.0 the interface no longer depends on SharePoint code: the web part supplies sign-in, the page's theme and culture, navigation and storage through a host interface. The move adds nothing a user meets; what it touches for assistive technology — the app's language and its theme colours — is assessed under 3.1.2 and 1.4.3.) This report covers:
- The application UI — dashboards and data grids for five case registers (requests, assessments, incidents, complaints, risks), case detail panels, work-item panels, forms, the document workspace, settings, and reports.
- The document viewer — an API-served page in an iframe: AccessPoint's own PDF viewer, served from the API itself, with its toolbar, find bar, thumbnails and outline panes, the text layer, and the redaction-overlay layer (client-composed: one base PDF, redaction marks painted as focusable overlays, Original / Redline / Redacted preview as overlay styles). Since 2.5.0 it replaces the third-party viewer earlier editions of this report described.
- The media viewer — video and audio records are first-class documents in every document workspace (request, assessment, incident, complaint). The viewer is AccessPoint's own: a custom player control bar with a scrub lane, a canvas overlay that paints region marks over the frame with an 8-grip edit chrome for the selected region, a non-modal mark bar that creates and edits marks (it replaced the mark editor dialog on 2026-09-23), a marks area under the player (zoom, lanes, filters and a focus row with keyboard grips), a description lane for an imported audio-description track, a transcript drawer with find-in-transcript and closed captions, and the shared redaction side panel. Large-file uploads run through a chunked upload queue.
- Structured editors — the assessment diagram editor (canvas and List view), the repeating-row table editor, the working-document editor that hosts both for diagram / list working files, and (since 2.5.0) the Working Files Word editor and spreadsheet grid, AccessPoint's own, served by the API in an iframe for DOCX and XLSX working files.
- Generated outputs — PDFs (correspondence letters, certificates, response and evidence packages, converted uploads, accessible editions), released media files (burned MP4 / MP3) with their caption, transcript and description files, Excel and CSV exports, reported in their own section because they are consumed outside the application.
- The public intake portal — the separate internet-facing web app members of the public use to submit, track, collect and pay, standalone or embedded in the customer's site. It is assessed in its own section against WCAG 2.2 as well (Table 3), because it is the one surface the public uses.
- The hosted edition (2.6.0) — AccessPoint served by Realizer at
app.realizer.ioin the browser, with no SharePoint: the global entry's region page and chooser, the regional web host's own pages and the live client's screens around the same application UI (sign-up, organizations, invitations, the session), assessed in their own section because a hosted person meets them before and beside the application.
Host and third-party reliance. The SharePoint page / Teams client owns the page <title>, <html lang>, and page-level skip navigation; conformance for that chrome is Microsoft's (see Microsoft's published ACRs for SharePoint Online and Teams). UI primitives (buttons, panels, dialogs, grids, tooltips, sliders) are Fluent UI 8; PDF pages are drawn inside AccessPoint's own PDF viewer; Office, HTML and e-mail files are converted to PDF in the deployment's own document worker. Since 2.5.0 no third-party commercial viewer, editor or conversion component remains. Where a behaviour is entirely internal to a component AccessPoint did not write the remarks say so — refer to that component's accessibility documentation for those internals. This report covers how AccessPoint uses those components and everything AccessPoint builds itself.
Authored content caveat. Tenants configure their own tag and exemption colours, choice labels, and correspondence templates, and users upload arbitrary documents and recordings. Conformance of tenant-authored or uploaded content (a low-contrast custom exemption colour, an inaccessible uploaded PDF, a recording without intelligible speech) is outside the product's control; the product's own defaults and mechanisms are what is assessed here.
Exclusions. The viewer's page-rendering internals (the canvas page rendering and the text-layer spans it generates — the viewer's toolbar, panes, find bar and marks are AccessPoint's own markup and are in scope), Fluent UI internals, the SharePoint / Teams host chrome, the Realizer-hosted setup, install and launch pages of the Microsoft 365 edition (the hosted edition's own pages are in scope — item 7), and Microsoft Graph pickers surfaced through the host are out of scope.
Evaluation methods
This is a self-assessment of version 2.6.0 against WCAG 2.2 and WCAG 2.1: methods 1 – 16 were run on 2.5.0 and the code before it, methods 17 – 27 on the code built for 2.6.0. The first edition (2026-09-03) assessed 2.1.0 against WCAG 2.1; the media records, public portal and generated-output sections were re-assessed on the code then numbered 2.2.1 / 2.4.0 between 2026-09-15 and 2026-09-25, and the whole application against the WCAG 2.2 additions on 2026-09-25 (method 8). The native viewer and editors that replace the third-party ones were measured on 2026-09-30 (methods 12 and 13), and the other surfaces new in 2.5.0 were scanned or code-reviewed between 2026-10-01 and 2026-10-05 (method 14). The release candidate of 2026-10-07 had a static review the same day and a runtime pass on the dev tenant on 2026-10-13 (method 15). Evidence sources:
- Static code review of the full frontend source (per-element JSX analysis of every component; label and ARIA coverage counted per control type rather than sampled — 482 loading spinners, 330 icon buttons, 176 live regions), the server-generated viewer page (HTML / JS), and every document- and media-generation path. Contrast ratios were computed from source values with the WCAG relative-luminance formula for both the light theme and the product's dark-theme token set. Fluent UI behaviour (focus traps, focus restoration, live regions, spinner announcement conditions, slider and focus-zone key handling) was verified against the shipped library source rather than assumed. The media viewer, timeline, marks overlay, transcript drawer, mark editor, upload queue, diagram / table / working-document editors, release-variants panel, and the client-composed PDF viewer were each reviewed line by line for keyboard operability, focus management, ARIA names / roles / states, colour and contrast, reflow, timing, and status messaging.
- Runtime browser verification of the shell surfaces on a live SharePoint deployment: keyboard walkthroughs (grid row-open via Enter, Escape dismissal, focus restoration after panel close), live ARIA-state inspection (combobox
aria-expanded/aria-activedescendant/aria-selectedtracking arrow keys;langattributes; heading levels; reorder hints), tooltip Escape dismissal, the report-workspace viewport clamp, and a walk of the Chrome accessibility tree — the tree NVDA / JAWS consume on Chrome — across the dashboard, data grid, search, pickers, and pinned-tile surfaces (role, name, state, reading order at every node; page-wide sweep of focusables for missing accessible names). This pass was executed on the 2.0.7x line of the same shell (2026-08-20). At that time no runtime pass had been executed on the surfaces added or rebuilt for 2.1.0 — the media viewer, the client-composed PDF viewer, the diagram / table / working-document editors, the upload queue, and release variants; methods 6, 7 and 9 to 13 have since covered most of them, and what is still not scanned is listed under Known limitations of this assessment. - Ongoing enforcement: the SPFx lint gate runs a curated
eslint-plugin-jsx-a11yrule set (valid ARIA props / roles, alt text, required role attributes, no positive tabindex,aria-activedescendantfocusability, validlang) plus an in-house rule requiringariaLabelon every Spinner — all at error severity, so violations fail the build in CI. - Media records re-audit (2026-09-23). The media viewer and everything it hosts (player controls, timeline, marks overlay, mark editor, transcript drawer, the media paths of the redaction side panel, row chips, release variants, upload queue, Teams recordings picker) and the released-media path (release burn, export assembly, portal delivery) were re-reviewed line by line against WCAG 2.2 A / AA and EN 301 549 clause 7, with Fluent UI 8.125.7 behaviour checked in the shipped library source and contrast computed from source values. The findings and their fixes are recorded in the media section below; the rows of Tables 1 and 2 that the audit corrected say so.
- Generated outputs (2026-09-23 – 2026-09-25). The accessible-releases program was checked with the PDF/UA checker (command-line, PDF/UA-1 profile) run locally: the spike samples (S-2, the accessible edition's shape: 106 of 106 rules; S-3, the tag-preserving merge), the tagged package pages, a rebuilt redacted record and a merged accessible edition (
AccessibleEditionBuilderTests), and a four-record Word / Excel / PowerPoint corpus converted with tagging on (results indocs/test-runs/benchmarks/2026-09-25-d8-tagged-conversion-corpus.md; that corpus test was retired with the converter it measured in 2.5.0). In 2.5.0 the native engine's own PDF/UA checker tests cover a tagged HTML render with its footer, the table header-row correction, the tagged writer, the tag-preserving merge, the rebuilt redacted record and the accessible edition. These tests run from the suite wherever the PDF/UA checker is installed. The release-caption rules (what a muted passage says, which cues name no speaker) are unit-tested.
Automated screen-reader pass (2026-09-25): NVDA 2026.2 with a silent voice and its speech logged read five generated PDFs in Microsoft Edge's PDF viewer — tagged Word, Excel and PowerPoint conversions and an accessible edition of a scanned record — end to end (say all). Headings with their levels, tables, picture descriptions, links, reading order and the in-place redaction announcement ("[Withheld — s.1-210(b)(2)]") came through; Word's title style read as plain text and some links were read without "link"; Word lists read as plain text too. Fixed the same day: Word lists are tagged as lists, Word's Title as the top heading, a header cell in a table's body row as a row header, an Excel sheet's bold header row as column headers, and a one-cell table as a paragraph (the corpus still meets PDF/UA-1 under the PDF/UA checker). Details: docs/test-runs/benchmarks/2026-09-25-d8-tagged-conversion-corpus.md.
- Runtime pass (2026-09-25). On the dev tenant (SharePoint Online, Chrome), with the 2.2.1 pre-release:
- axe-core 4.10.2, WCAG 2.0 / 2.1 / 2.2 A and AA rules, scoped to AccessPoint's own DOM (the SharePoint chrome's findings are Microsoft's and are not counted): all seven dashboards (My Day, Requests, Assessments, Incidents, Complaints, Audits, Risks); a request panel on each of its nine tabs and the Documents sub-tabs (All documents with the filter sidebar, Response package, Redactions, Working files); an assessment panel on each of its seven tabs, including a section with a table answer; the media viewer on a recording being scanned; the PDF redaction viewer's shell and redaction side panel (32 proposals); the release-variants panel and its new-variant form; the Create or upload menu; Settings.
- Reflow at 320 CSS px (the width a 1280 px screen gives at 400 %), measured in a 320 px frame of the same page: every dashboard, every request-panel tab and the media viewer. No page-level horizontal scrolling anywhere; data grids scroll inside their own containers (permitted for data tables), panel tab bars fold into a More tabs menu, and the media viewer stacks player, timeline and marks.
- Keyboard: the media viewer's tab order (header, view tabs, speed, download, panel, close, then the player, timeline, marks area and side panel, in reading order) and focus returning to the document name when the viewer closes.
- Defects found and fixed the same day. Every surface above was re-scanned after the fix reached dev and now reports no violations, except the split buttons below:
- 4.1.2, about 360 notices: a dismissible notice's close button had no name (Fluent names it only when the caller passes a label). All of them now read "Close" in the user's language, and so does a panel's own close button.
- 4.1.2, 42 side panels and 5 dialogs: a panel with a custom header, and five dialogs (the screener, a comment's history, the two working-document editors, a document template's preview), had no accessible name. Each is now named by its visible title. This closes the working-document editor gap the 2.1.0 report recorded.
- 4.1.2, 10 progress bars: the progress columns of the request and assessment grids, the assignment and task cards, the hours estimate, repository progress, a recording being prepared and an export being generated. Each now has a name.
- 1.3.1 / 4.1.2, Response package: each reorderable row was wrapped in a focusable button, which took the row out of its grid and put the row's controls inside a button. The row itself now takes focus and carries the Alt+Arrow to reorder hint as its description.
- 1.3.1, Redactions sub-tab: its rows and column headers sat outside any table. It is now a table, with a row group per document headed by the document's row.
- 4.1.2, nested controls: a My Day row with Complete, Delete or Dismiss buttons, a risk card with its "…" menu, and a treatment-action card with its Cancel button were each a button containing buttons. The title is now the button; a mouse click anywhere on the row or card still opens it.
- 1.4.3, lifecycle rail: the names of stages not yet reached measured 2.63:1 (
neutralTertiary) on every case panel and closure tab. They are now 6.1:1. - 2.5.8 (WCAG 2.2), document filters: the date-uploaded radios sat in 22 px rows. Filter rows are now at least 24 px.
- Found, and fixed later the same day (method 8): the five Fluent UI split buttons (New access request, Register complaint, Export response package, Add from…, and Report Studio's Save) were one element with the button role wrapping the primary and menu halves, so axe reported nested interactive content. Each is now two buttons side by side in a group named by the action — the action, and a More options menu button of its own — so each half is reached and announced on its own.
- Not scanned at runtime: the PDF page frame itself (the third-party viewer used before 2.5.0, and AccessPoint's overlay marks). It is served from the API's domain, where the test browser had no permission to run scripts, so it kept the static review of method 1 until method 11; the native viewer that replaced it is scanned in real-browser tests (method 12). The upload queue during a real upload was not scanned either (a test upload would have added a document to a live test case); its names, progress announcements and buttons are covered by the static review.
- Automated NVDA pass on the media viewer (2026-09-25). NVDA 2026.2, with a silent voice and its speech logged, in Chrome on the dev tenant. Windows-level keystrokes played the part of a keyboard user: a Tab walk through the whole viewer (header, view tabs, player, marks area, Redactions panel), the timeline slider operated with the arrow keys, End and Home, a filter chip toggled with Space, and Escape.
- What was heard:
- every control announces a name and role in reading order;
- the timeline slider reads "Timeline, slider, 0:00 of 0:16" and each Right arrow "0:05 of 0:16";
- the marks area and the Redactions panel are announced as a region and a complementary landmark;
- each mark's checkbox is named by span, effect and exemption;
- "Loading recording…" is announced while the viewer loads.
- Found and fixed the same day (fixes checked in the live DOM):
- The five toggle buttons announced no state: the marks area's filter chips, Snap to edges, the mark bar's Show the effect, and the player's Captions and Descriptions. Fluent writes
aria-pressedonly on a button marked as a toggle and drops a caller's own, so the attribute this report claimed never reached the browser. They are now toggles, and the state is announced. - Three accessible names ran words together: "AI summaryGenerate on demand", a mark row's "00:00:05Box (solid)s.1-210(b)(5)", and the case header in browse mode ("REQUEST #FOIA-2026-00006STATUS Active TYPEFOIA records request"). They now read "AI summary, Generate on demand, button, collapsed", "00:00:07–00:00:16, Blur, No label" and "REQUEST #", "FOIA-2026-00006", "STATUS", "Active" as separate items. The header's separators are real text hidden visually: CSS alternative text reached Chrome's accessibility tree but not NVDA's browse mode.
- The five toggle buttons announced no state: the marks area's filter chips, Snap to edges, the mark bar's Show the effect, and the player's Captions and Descriptions. Fluent writes
- Recorded, not changed:
- Tab enters a Fluent tab list on its first tab rather than the selected one; the arrow keys reach the others, and the selected tab is announced as selected. This is the Fluent Pivot's behaviour.
- The first Escape with the pointer over the timeline dismisses its hover preview before a second closes the viewer, as designed (M-24).
- Re-checked by ear the same day: a second NVDA run heard each fix. The chip announced "Picture, toggle button, not pressed", then "pressed" and "not pressed" as Space toggled it. The three names read as separated words and items, as quoted above.
- What was heard:
- WCAG 2.2 audit of the whole application (2026-09-25). A read-only sweep of the application source, the PDF viewer page and the portal for the six criteria WCAG 2.2 adds at Level A / AA: every drag interaction (HTML5
draggable, pointer-move handlers, resize edges, grips), every sticky or fixed element that could cover focus, every target under 24 px, where help sits on each surface, where a process asks for something twice, and every sign-in step. What it found, all fixed the same day on 2.4.0 and covered by the lint gate and unit tests (SPFx 1,102 tests; the API suite):- 2.5.7: twenty-one lists reordered by dragging offered Alt+Arrow only, which is keyboard, not the single-pointer alternative 2.5.7 asks for (and HTML5 drag does not work on a touch screen). Every one now has Move up / Move down buttons on each row that call the same reorder. The request grid's column headers were dragged to reorder and their edges to resize: the header's grip is now a button with Move left, Move right, Wider and Narrower. The diagram editor's shapes were moved and resized by dragging: the Details pane now has X, Y, Width and Height fields for a shape and X / Y for each bend of a connector. A redaction box in the PDF viewer was moved and resized by dragging its grips: a grip clicked without moving is now armed, and the next click on the page puts that corner or side there (two opposite corners move the whole box); Escape cancels.
- 2.5.8: the PDF viewer's grips were 9 px; they now have 24 px hit areas around the drawn square. Move buttons in Manage shared views (24 × 18, stacked), five 22 px and one 18 px icon buttons, the relevance column's header buttons (22 px) and a tag chip's remove × (about 11 × 13) are now at least 24 × 24; the media timeline's group toggles, 16 px tall, are now at least 32 px apart. The request grid's 6 px column edge keeps its size, under the equivalent exception: Wider / Narrower on the column's grip button.
- 2.4.11: the floating upload tray could cover the control with focus; it now moves to the other bottom corner when the focused control is under it, and folds to one line when it would cover it in either corner. The requestor contact form's sticky Save / Cancel bar covered each field Tab scrolled to the foot of the panel; the panel now keeps a 72 px scroll padding under it. An embedded portal form scrolled to the top of the viewport, under a host page's sticky header: the embed script takes
data-ap-scroll-offset, the header's height. - Found alongside: the five split buttons (method 6; 4.1.2); the diagram editor's shapes and swimlane headers had no focus indicator (2.4.7) and now draw a dashed ring on keyboard focus; the small dashboard chart tiles told series apart by hue alone (1.4.1) and now draw each line in its own dash with a key of line samples, and keep their legends for multi-series bars and donuts (the compact trend tile also drew only its first series — Fluent's Sparkline ignores the rest); fields with a placeholder for their only visible label got visible labels, and search boxes keep their magnifier while focused (3.3.2);
[and]in the media viewer now move focus to the mark they select (2.4.3); lists reordered by dragging no longer wrap each grid row in a focusable button that contains the row's own buttons (1.3.1, 4.1.2); and the response package's reorder, which counted positions across recordings and native files it does not show, moved the wrong document when one sat between two PDFs. - Runtime re-scan (the same evening, dev tenant, the 2.4.0 package): axe-core 4.10.2 over the Requests dashboard,
Settings → Request types and a request's Response package tab. The split buttons are two buttons in a named group,
the reorderable rows carry Move up / Move down, and no row sits inside a button. Two further defects were found and
fixed the same evening: 40 panels with a custom header — most Settings sub-panels, and the create-request, contact,
delegation and view-builder panels — were dialogs with no accessible name, because Fluent points
aria-labelledbyat a header text the custom header never renders (4.1.2); each is now named by its header text. And the reorder hint that method 6 put on the Response package's rows never reached them, because Fluent's row setsaria-describedbyitself after the props it is given (it now goes through the row's own description hook, on all twelve reorderable lists). After the fixes the three surfaces report no WCAG violations; axe's best-practice check still noted the icon-only header cells of the drag-handle, actions and remove columns (named since method 9). - Supports as found: 3.2.6 — Help is the same top-right button, just before Close, on every panel, dialog and dashboard, and in the same footer position on every portal page; 3.3.7 — a request created from a portal submission or an e-mail is pre-filled, an existing contact can be picked, and a payment or refund defaults to the balance; 3.3.8 — the application signs in through Entra ID (the host's), and the portal's one-time code can be pasted, is marked
one-time-code, and there is no puzzle or CAPTCHA.
- Full runtime re-run after the silent-failure fixes (2026-09-25, late evening, dev tenant, the 2.4.0 package). axe-core 4.10.2 (WCAG 2.0 / 2.1 / 2.2 A and AA plus best practice) over the application and its open dialogs: the My Day and Requests dashboards; every one of the 69 Settings panels; the Assessments, Incidents, Complaints, Audits and Risks dashboards; a request, an assessment, an incident, a complaint and a risk with every tab of each panel, and every section of a PIA's questionnaire; the media viewer in its three views with the transcript drawer, the filters and the Redact menu; and the request grid's column menu. It found, and the same evening fixed and re-scanned clean on dev:
- 4.1.2: the jurisdiction pack cards (144) and the calendar cards were
role="button"around their own buttons (the name is now the button; the card keeps the mouse click); the Document tags rows and category headings were buttons around their Move / Edit / Delete buttons (a heading may not be a button either); the Dashboard views panel was an unnamed dialog; the up / down arrows of every number field were unnamed buttons (named app-wide, in the active language). - 1.3.1 / 4.1.2: a questionnaire answer box in a multi-language tenant had no accessible name (it is now named by its question, like the single-language box); the same for the request title, description and scope, an assignment's name and instructions, and a portal answer.
- 1.4.3: text drawn in the theme's two lightest greys (1.7:1 and 2.6:1) — "None", "—" placeholders, file sizes, repository types, separators — now uses the secondary text colour (6.3:1); document tag chips drew a dark tag's text white on its light tint (1.25:1) or a light tag's text in its own colour (2.67:1) and now use the body text colour on every chip.
- 2.5.8: the My Day catch-up links were 17 px tall and stacked, and a pack card's Show details 18 px; both are 24 px.
- Best practice: the Public portal settings skipped a heading level; the 45 icon-only columns (drag handles, actions, remove) now carry visually hidden header text; a Move button that a move disables keeps keyboard focus (
aria-disabled) instead of dropping it to the page. After the fixes every surface listed reports no violations. Not reachable by the scan: the PDF page frame (cross-origin), the floating upload tray (it exists only while an upload runs) and the diagram editor's shape fields (the only diagram on dev is empty, and adding a shape would change a live assessment).
- 4.1.2: the jurisdiction pack cards (144) and the calendar cards were
- Live NVDA session over the application (2026-09-26, dev tenant, the 2.4.0 package). NVDA 2026.2, driven by real Windows keystrokes (Tab, arrows, Space, Enter, Escape and NVDA's own commands) in Chrome, with its speech logged and read back by ear (255 announcements): the Requests dashboard (tabs, summary cards, the split New button, the grid's headers and its column menu), Settings → Jurisdiction packs, Document tags and Features, a PIA questionnaire, and the requestor combobox in New access request. Confirmed: the split button reads as a named group of a button and a menu button; a pack card's name is its button and Show details announces collapsed / expanded; the column menu reads Move left, 1 of 4 … Narrower, 4 of 4 and Escape returns to its button; a questionnaire answer box reads its question; the combobox announces expanded, then each suggestion with its position (… 1 of 2, Create new requestor “qa”, 2 of 2); a Move button a move disabled stays focused and reads unavailable. Found and fixed the same night: the summary cards on five dashboards were named without their count (Active requests, not 47 Active requests) and two read their explanation twice; after Move down a list reloaded behind a spinner and focus fell to the page (the Move buttons now return focus to the moved row, on all eighteen reorderable lists); Escape in the requestor picker and the global search cleared the typed text as well as closing the suggestions. Found as SharePoint's, and worked around the same day: SharePoint Online's own page script cancelled Tab on a grid column header and jumped to the next header, so Tab never reached the Column options button inside it (2.1.1), and its Enter handling on a grid row moved focus to the row's actions button while the record opened, so closing the record left focus at the top of the page (2.4.3). The web part now keeps Enter and Tab from reaching the page's handler (
keyboardBoundary.tsin the SharePoint host, unit-tested), so Tab stops on Column options and closing a record returns focus to its row. The functional run of the same day also found 59 Edit / Delete buttons that said only "Edit" or "Delete" — each now names what it acts on (Edit: Responsive) — and six more kinds of row that were buttons holding buttons (notices, key risk indicators, consultation cards and consultation contacts, complaint allegations, working-file folders), now restructured like those of method 6; the Reports cards' Pin to My Day is its own named control (Pin Volume & sources to My Day). - The PDF viewer frame (2026-09-26, dev tenant — the viewer used before 2.5.0). Opened on its own origin with the browser extension's permission; its content security policy blocks loading axe, so the same rules were checked in the page — accessible names, roles, focus order, target sizes, contrast,
langand title — and sample marks were pushed to it the way the host pushes them (nothing was saved). The vendor's toolbar (pages, zoom, pan, search, thumbnails) was named throughout (its of N page count took a tab stop, a vendor quirk that the native viewer does not have — its page count is plain text). What follows was AccessPoint's own code and was carried into the native viewer, where method 13 measured it again. The marks are named buttons (Redaction — s.19(1) Personal information, Suggested redaction — …), focusable in order, with a 3 px focus ring, Enter / Space to select, Alt+Arrow to move and Alt+Shift+Arrow to resize; the applied border is 5.89:1 and the proposed amber 4.55:1 against the page. Found and fixed: on a mark under 48 px the eight 24 px grips overlapped (a 26 px line had grip centres 12 px apart), so a grip's usable area fell under 24 px (2.5.8); overlapping grips are now hidden by size, and no two overlap from 18 × 15 px to 100 × 129 px. - Automated scans of the native viewer and editors in a real browser (2.5.0, every build). axe-core 4.14.0 (4.13.0 until 2.6.0), WCAG 2.0 / 2.1 / 2.2 A and AA rules, injected over the browser's DevTools protocol so each page keeps its production content security policy (the obstacle that kept axe out of the frame in method 11). Pages and states: the redaction viewer framed cross-origin by a host page; the plain viewer on load, with thumbnails open, and with the outline and a find run; the Word editor on a letter with a letterhead and with its insert-table dialog open; the spreadsheet on a workbook and with its column-width dialog open. Each scan is checked against a page with a planted missing
altand an unnamed button, so an empty result means nothing was found, not that nothing ran. The scans are part of the API's test suite (NativeViewerBrowserTests,NativeEditorBrowserTests) and run wherever a Chrome-family browser is installed, as on the build agents. Found and fixed: hidden-text passages in the Word editor were drawn at 55 % opacity (3.08:1, 1.4.3); they are now#605e5cwith Word's dotted underline (5.9:1). - Runtime pass, NVDA and 200 % zoom on the native viewer and editors (2026-09-30, dev tenant, SharePoint, Chrome). The viewer and editor frames loaded from the dev API, marks pushed the way the host pushes them, and the host's behaviour in SharePoint: text contrast (every enabled control at least 4.5:1), non-text contrast (applied mark border 4.93:1, proposed 4.55:1, focus ring 4.53:1 against the page), target sizes (no control under 24 × 24 px in the viewer, the Word editor or the spreadsheet; on a short mark the side grips hide so the six shown never overlap), names and roles, title and language, keyboard paths and no keyboard trap in the SharePoint host. Then NVDA 2026.2, with a silent voice and its speech logged, driven by real keystrokes with the browser at 200 % zoom, walked the Word editor, the spreadsheet and the redaction viewer: every control, cell, mark and thumbnail is announced with its name and role, the find result is spoken as a status, and at 200 % the toolbars reflow and no focused item is hidden. Four defects were found, fixed, deployed to dev and heard again the same day:
- 2.1.1 / 4.1.2: Left or Right on a toolbar dropdown changed its value (the paragraph became Heading 1, and the selected cells' font or format changed) instead of moving along the toolbar. Left, Right, Home and End now move focus; Up, Down, Alt+Down and typing change the value.
- 1.3.1: the spreadsheet's rows were read one too high (B12, row 13), because the column-letter header row was the grid's first row. The letter and number headers are hidden from assistive technology — every cell's name already carries its address — and rows are numbered from 1.
- 2.5.3: a mark's spoken name did not contain the caption painted on it (Redaction — CT-FOIA-B2 on a box showing s.1-210(b)(2)). The name now starts with the caption.
- 2.4.3 / 2.4.7: each page's text layer was an invisible Tab stop read as the whole page (the viewer's page-rendering internals make it focusable). The viewer takes it out of the Tab order; the document region stays the one stop that scrolls, and Tab goes from it to the marks. Not exercised: the spreadsheet's announcements after an edit and its sheet tabs.
- The other 2.5.0 surfaces (2026-10-01 – 2026-10-05). axe-core 4.10 scans on the dev tenant of the spreadsheet-layout surfaces (2026-10-01): Settings → Document conversion, the hidden-content review dialog, and the viewer's Parts section with its withhold form — one defect found and fixed (
heading-orderin the review dialog). Code reviews against WCAG 2.2 A and AA of the DPIA validation surfaces, the training surfaces, the case-archiving surfaces and the discovery survey (2026-10-05), with the web part's unit tests. None of these surfaces has had a 320 px reflow pass or a screen-reader pass; each section says what it still needs. - The 2.5.0 release candidate — static review (2026-10-07) and runtime pass (2026-10-13). The release candidate added and changed surfaces after method 14, and some 2.5.0 surfaces built before it were never described in this report; the inventory is under 2.5.0 release-candidate changes.
- Static review (2026-10-07, done): a code review against WCAG 2.2 A and AA of every surface changed after 2026-10-05 — the diagram editor's fourth and fifth versions, the privacy subject's Diagrams tab and the diagram question note, the Training hub, Guide me and Get started by topic, the Lab library, Lab mode uploads and the training reports, request pattern review, identity verification on the Requestor tab and its reuse, Open contact / Open institution, Require attestation, English spelling, review templates in every language, the statistical template form, the screener's checkboxes, the Teams header and the dark-theme colours — and of the 2.5.0 surfaces built before 2026-10-05 that this report did not yet describe: audits (engagement, evidence requests, findings, control tests, the five audit reports, Settings → Audits), follow-up rules, reminders and the waiting-period confirmation, computed due dates and the received-date correction, the register filter bar, column menus, multi-select and bulk reassign, the Risks tab with its heat map, the administrator banners and the SharePoint package update. It also re-ran the full
eslint-plugin-jsx-a11yrecommended rule set (the build carries a curated subset) over every changed component, checked how the shared UI package (host abstraction, below) sets the app's language, theme variables and keyboard boundary, and re-counted the spinners and live regions. The defects it found and fixed the same day (with the web part's unit tests; the shared UI's suite green, 2,958 tests) and the ones it left open — fixed on 2026-10-13, with the shared UI's suite green at 3,345 tests — are listed under 2.5.0 release-candidate changes. - Runtime pass (2026-10-13 — the dev tenant, SharePoint, Chrome; the release candidate as merged, web part bundle
a3b46f26, then with the fixes below, bundlesb8bc65f1and93ebccfe):- axe-core 4.10.2, WCAG 2.0 / 2.1 / 2.2 A and AA rules plus best practice, scoped to AccessPoint's root and its layers (panels, dialogs, menus, callouts), the scan checked first against a planted unnamed button so that an empty result means nothing was found: My Day and the six register dashboards; the register filter bar, a column menu, View options, multi-select with the bulk bar and the Reassign requests dialog; every tab of a request, an assessment, an incident, a complaint and an audit panel (the audit's Controls tab and its New finding and Add request dialogs included); the Requestor tab's Open contact profile and its four tabs, with the Conduct signals card and Log review outcome; How this date was calculated; the Training hub and every destination (training cases, My training, team exercises, paths and progress, readiness, exercise activity, training settings); Get started by topic and a Guide me tour; the privacy program (six tabs), a privacy subject (six tabs) and the diagram editor (empty, with shapes, with Details); all 80 Settings panels; and all 42 report sections. The real-browser scans of the native viewer and editors (method 12) passed the same day (30 of 30).
- Reflow at 320 CSS px, measured in a 320 px frame of the same page with animations off: My Day and the six dashboards, the filter bar and the bulk bar, every tab of the five case panels above, the Training hub, My training, team exercises, paths and progress and readiness, the privacy program's six tabs, a subject's six tabs and the diagram editor with its Details pane, eleven Settings panels (request pattern review, training, follow-up rules, localization, request types, audit types, statistical report templates, setup, review workflows, manage users, public portal) and the Reports page with five sections (received-date corrections, statistical reports, audit findings, complaints, training readiness). At 640 CSS px — what a 1280 px screen gives at 200 % — My Day, the Requests, Audits and Risks dashboards, every tab of a request and an audit panel, the Training hub, My training and paths and progress. No page scrolled sideways, and nothing reached past the viewport outside a container that scrolls on its own (data grids).
- Keyboard and focus: Escape from Reassign requests returns focus to the row; Escape from a Guide me tour to Guide me; Cancel in New finding and Add request to the button that opened them; Escape from the contact profile to Open contact; Clear selection keeps focus; closing any Training hub destination, or the hub reopened with a panel's Back, returns focus to the Training button; Log review outcome's Cancel returns to that button; in the diagram editor, Escape in a new shape's label editor returns focus to the shape, a second Escape stays on the canvas with the subject panel open, and Cancel returns to Draw diagram.
- How it was run: the browser window was in the background for most of the pass, where Chrome runs no animation frames and slows short timers to about once a minute. They were stood in for in the page by message-channel equivalents, so that focus moves that wait for a frame could be observed; an overflow of 40 px first seen at 320 px was a panel's slide-in animation that never played, not a defect (with animations off it was gone). No screen reader was used, and the dark theme was not measured.
- Found and fixed — under 2.5.0 release-candidate changes → Runtime checks (2026-10-13); each fix was re-scanned or re-checked on dev except where it says unit-tested.
- Static review (2026-10-07, done): a code review against WCAG 2.2 A and AA of every surface changed after 2026-10-05 — the diagram editor's fourth and fifth versions, the privacy subject's Diagrams tab and the diagram question note, the Training hub, Guide me and Get started by topic, the Lab library, Lab mode uploads and the training reports, request pattern review, identity verification on the Requestor tab and its reuse, Open contact / Open institution, Require attestation, English spelling, review templates in every language, the statistical template form, the screener's checkboxes, the Teams header and the dark-theme colours — and of the 2.5.0 surfaces built before 2026-10-05 that this report did not yet describe: audits (engagement, evidence requests, findings, control tests, the five audit reports, Settings → Audits), follow-up rules, reminders and the waiting-period confirmation, computed due dates and the received-date correction, the register filter bar, column menus, multi-select and bulk reassign, the Risks tab with its heat map, the administrator banners and the SharePoint package update. It also re-ran the full
- The core functional run (2026-10-14, dev tenant, SharePoint, Chrome; the same release candidate, web part bundle
93ebccfe). The functional test suite (docs/test-runs/2026-10-14-core.md) exercised the application with the keyboard as well as the mouse, and found five more places where focus was lost and one state that was not exposed. Each was fixed the same day in code with a unit test; the fixes were not yet deployed to dev at this report's date, so they are not runtime-verified:- 2.4.3: in the redaction side panel, every edit of a mark (leaving the custom label, Enter in the exemption picker) swapped the list for a spinner while it reloaded, so focus fell to the page and the list scrolled to the top. The list now stays mounted and is marked busy while it refreshes.
- 2.4.3: in the Settings catalogue lists (communication methods and the other choice lists), Alt+Arrow moved the row but the reload after the save replaced the list with a spinner, so focus fell to the page and a second Alt+Arrow did nothing. These lists now reload without the spinner after a reorder, so the moved row keeps focus — the behaviour method 10 established for the Move buttons.
- 2.4.3: removing a row from an assessment's table answer sent focus to the page; it now goes to the row that took its place, or to Add row. In a risk identification table, Table details → Save and Remove from this table also lost focus (the row's buttons are disabled while saving, so the dialog could not return it); focus now returns to the row's Edit table details button, or to the table.
- 2.4.3: saving or discarding any section card (Edit this section on incident, complaint, assessment, subject, vendor and audit panels, and a request's Details tab) left focus on the page, because Save and Discard unmount with the form and the pencil returns as a new button. Focus now returns to the pencil, and each pencil — four on an incident share the name Edit this section — is described by its card's title. Found in the second-account part of the run, the same afternoon.
- 4.1.2: the document tag callout showed which tags were applied only by a drawn check mark; each option now exposes it with
aria-pressed. - Still open (2.4.3, minor): after a repository is removed from an assignment, focus lands on the dialog's Help button rather than the list. Focus stays in the dialog and in a logical place, so 2.4.3 stays Supports.
- AccessPoint Learning coach (2026-11-01; built for 2.6.0, not in 2.5.0). A static code review against WCAG 2.2 A and AA of the How we decide disclosure and the coach notes editor (section AccessPoint Learning coach — How we decide and coach notes), with their unit tests, which find the controls by role and accessible name (
CoachDisclosure.test.tsx,CoachNotesSection.test.tsx,BlockEditor.test.tsx,blockModel.test.ts,StructuredContent.test.tsx). No runtime axe scan, reflow measurement or screen-reader pass yet. - AccessPoint Learning Studio, page editor and module player (2026-11-01; built for 2.6.0, not in 2.5.0). A static code review against WCAG 2.2 A and AA of the module player, My learning, the mentor's list and the learner landing, the Studio and the page editor host (section AccessPoint Learning — the Studio, the page editor and the module player), with their unit tests, which find the controls by role and accessible name (
ModulePlayer.test.tsx,MyLearning.test.tsx,LearnerLanding.test.tsx,Studio.test.tsx,CurriculumEditor.test.tsx,TranslationsTab.test.tsx,OverlayEditor.test.tsx,ModuleEditorHost.test.tsx). The page editor inside its frame (served by the API) is also covered byPageEditorBrowserTests: an axe scan with the WCAG 2.0 / 2.1 / 2.2 A and AA tags finds no violation (with and without the image dialog open), and every node and mark of AccessPoint Learning profile is made from the keyboard alone in a headless browser, behind a stand-in host page on another origin. No Jest test of these surfaces runs axe; no runtime scan of the Studio or the player, no reflow measurement and no screen-reader pass yet — the NVDA pass is owner-run (the player from a learner's seat, the Studio's outline and findings, the page editor in the Studio, the Translations tab). - AccessPoint Learning L3 — checks, certificates, reports and the other L3 screens (2026-11-03; built for 2.6.0, not in 2.5.0). A static code review against WCAG 2.2 A and AA of the player's Check, Decide and Exercise steps and their Studio editors, Your certificates, Verify a certificate, the Revoke and More attempts dialogs, recertification and the new Team progress columns, the Training coverage report, the Studio's Quality, Glossary and Obligations tabs, the term picker and the glossary term in a page, the Training done elsewhere dialog, the suggested audiences, How we decide's Learn more with the coach note's Linked modules, and the model answer under a training case's guide (section AccessPoint Learning — checks, certificates, reports and the L3 screens), with their unit tests, which find the controls by role and accessible name (
CheckDecideSteps.test.tsx,PractiseStep.test.tsx,CheckDecideEditors.test.tsx,PractiseEditor.test.tsx,CertificatesList.test.tsx,CertificateVerify.test.tsx,TrainingProgressSection.academy.test.tsx,TrainingProgressSection.certificates.test.tsx,TrainingProgressSection.d7.test.tsx,TrainingProgressSection.external.test.tsx,TrainingProgressSection.results.test.tsx,MyLearning.recertify.test.tsx,ReportTrainingCoverageSection.test.tsx,QualityTab.test.tsx,GlossaryTab.test.tsx,GlossaryTab.d7.test.tsx,GlossaryTermMark.test.tsx,ExternalCompletionDialog.test.tsx,CurriculumEditor.test.tsx,CoachLearnMore.test.tsx,TrainingCaseBanner.modelAnswers.test.tsx). The term picker has no unit test, and the Revoke and More attempts dialogs are exercised only through Team progress's tests; no Jest test of these surfaces runs axe. No runtime axe scan, reflow measurement or screen-reader pass yet — the NVDA pass is owner-run. - Onboarding, read-only states, the marketing demo and the Training Lab (2026-11-07; built for 2.6.0, not in 2.5.0). A static code review against WCAG 2.2 A and AA of the surfaces in the section Onboarding, read-only states, the marketing demo and the Training Lab, with their unit tests, which find the controls by role and accessible name: the welcome (
WelcomeDialog.test.tsx, whose last case runs axe-core over the dialog with the WCAG 2.1 / 2.2 A and AA rules that need no layout), the session warning and notice (SessionTimeoutWarning.test.tsx,SessionSignedOutNotice.test.tsx), the read-only seam (LicenseReadOnlyBanner.test.tsx,ReadOnlyRegisterBanner.test.tsx,readerView.test.tsx,ProgramHub.readOnly.test.tsx), the demo (DemoCtaPill.test.tsx,noWelcome.test.tsx,funnel.test.ts) and the Training Lab (join.test.tsx,courseHome.test.tsx,classCode.test.tsx,secondPass.test.tsx). The demo's welcome card, the pill over a request, the bar's Menu and Tours & pricing at 390 px are also scanned with axe-core (@axe-core/playwright, WCAG 2.2 AA tags) ine2e/funnel.spec.ts, which fails on any violation. The occasional user's card has no unit test; no Lab screen runs axe. No reflow measurement on the dev tenant and no screen-reader pass of any of these surfaces. - UX and accessibility audit of the 2.6.0 surfaces (2026-11-10; built for 2.6.0, not in 2.5.0). A pass over every stable surface new in 2.6.0 (
docs/test-runs/2026-11-10-ux-a11y-audit-2.6.0-surfaces.md), on the branch, nothing deployed, no screen reader:- In a real browser, through the marketing demo (Playwright 1.64.1,
@axe-core/playwright4.14.0, WCAG 2.0 / 2.1 / 2.2 A and AA tags) — the surfaces the demo reaches: rolling releases (the Releases sub-tab, a release's index, Send release, the release picker, building and sending a release), the Reports menu and media marks in the panel card. axe at 1440 × 900 in English and French (the existing flows) and over the Releases sub-tab in the other nine languages; reflow at 320 CSS px (no page-level sideways scrolling, and an exploratory listing of everything past the viewport's edge with the ancestor that scrolled or clipped it) and at 1366 × 768; target size computed in the page with 2.5.8's spacing and inline exceptions; and the keyboard (Send release and the release picker open with Enter and give focus back on Escape). Kept ase2e/uxAudit.spec.ts, which fails on any violation. - In jsdom, for what the demo does not reach (AccessPoint Learning, Lab mode's scripted people, the read-only states, the welcome card, redaction discussion, dated settings and AI deployments): axe-core 4.13.0 run after every test of the 74 Jest suites that render those surfaces (681 tests, 520 with something rendered). Its only findings were buttons left unnamed by the tests' empty string mocks (a header's Help or Close, Fluent's own labels that the app sets at start-up) — no product defect. axe assertions were then added to the unit tests of the Check and Decide steps, Verify a certificate, Your certificates, My learning, Here's your task, the licence read-only banner and the dated-settings forms. jsdom lays nothing out, so contrast, reflow and target size there rest on the theme's tokens and code review.
- A WCAG 2.2 A / AA code review of each new component, aimed at the gaps methods 17 – 20 recorded: focus after every action that removes or disables the control pressed, errors tied to their fields, language of parts, colour-only signals, names that repeat, and headings.
- Found and fixed the same day, each with a unit test or the browser spec except the headings and the chip's colour of the last item (code review), and the runtime ones re-run in the browser:
- 2.1.1 / 1.4.10: at 320 CSS px a release's index scrolled sideways in an area no keyboard could reach (axe
scrollable-region-focusable), and the release schedule pushed the whole Releases tab sideways. Each table now scrolls in a named, focusable area of its own. The Documents toolbar's Create or upload ran past the panel's edge; its two buttons now wrap. The schedule's Told to the requestor, a tick or an empty cell, says Yes or No (1.3.1). - 2.4.3: focus fell to the page after Mark done, I confirm and Save my note in the module player; a mentor's Confirm; Show the coaching I hid again; Try again on a check; Confirm and get the certificate and a certificate download; Team progress after a revocation, more attempts, a withdrawal or This completion stands (the table was read again behind a spinner — it now stays on show, marked busy); the view changes inside Training done elsewhere; the Studio's question and option Move up / Move down (and a move button that turned unavailable at the top or bottom); the overlay editor's Save and Cancel; a suggested audience's Switch on; a linked module's Remove; the glossary's and obligations' Shown / Counted switches; and Here's your task's Got it. Each now gives focus back to the control when it is still there, or moves it to the next sensible one.
- 3.3.4: a Decide commitment and the last attempt of a limited check — submissions that cannot be repeated — are now confirmed first (Submit your decision?, Use your last attempt?, with Review my answers).
- 3.1.2: in a module shown in a fallback language the player's own words were marked with the module's language; and text written in another language in the Studio — the module's title, summary and objectives, every step field, the block editor and the Translations tab's source and fields — carried no
lang(the Does not support row of method 18). Both now mark only what is written in that language. - 3.3.1 / 1.3.1: This number is used twice. now describes its select; a Studio text field's findings are its description, read with it (Fluent dropped a second description); an empty verification code is the field's error, on the field; a refusal of Revoke certificate or More attempts that is not about the reason no longer marks Reason invalid; Training done elsewhere moves focus to the first required field left empty; a Waiting for you list that could not be read and a failed Show the coaching I hid again now say so.
- 2.5.3 / 1.4.1 / 2.4.6: the step outline's move buttons are named with the step's visible label (not its internal key); its badge says to fix / to consider in words; each option's The right answer, Feedback on option n and The model answer's choice carries its number; a check question written as a formatted document describes its group with its words; the term picker's search has a visible label and announces how many terms match; the refused-acknowledgement message is announced once, not twice.
- 1.3.1 / 3.3.2 (dated settings, AI Assist): an exemption's or extension reason's Available from / Available until are one group whose explanation describes both dates, and a last day before the first is said on its field (Save waits); a fee schedule's earlier amounts are a group named by their heading; the Features & AI groups' titles and Your own AI deployments are headings; the Deployed chip's colour comes from the theme (it was a fixed hex in dark mode).
- 2.1.1 / 1.4.10: at 320 CSS px a release's index scrolled sideways in an area no keyboard could reach (axe
- Left open — Recommendations in the report and roadmap item 24: findings on a Studio document field (the block editor) are only repeated in words under it, and no Studio field is marked
aria-invalidfor a finding; the Glossary and Obligations editors' refusals stay a message at the top of the dialog; interface words inside a step's content (I confirm, Your answer) still carry the module's language in a fallback; the file preview from a File step is titled Open the file. All four were fixed by the polish pass later the same night (work/polish-260; the report's Recommendations, R-1 – R-5), with the narrow-screen items R-6, R-7 and R-9, and R-8's plural forms for the notices toast and the release schedule (a mechanism and a shrink-only ratchet for the 251 other (s) strings). R-10 (the dev tenant and NVDA) and R-11 stay open.
- In a real browser, through the marketing demo (Playwright 1.64.1,
- UX and accessibility audit of the hosted edition (2026-11-10; built for 2.6.0, not in 2.5.0). A pass over the hosted person's journey (
docs/test-runs/2026-11-10-ux-a11y-audit-hosted.md), on the branch, nothing deployed, no screen reader:- In a real browser (
playwright-core1.64.1,@axe-core/playwright4.14.0, WCAG 2.0 / 2.1 / 2.2 A and AA tags, contrast included): the built live client served with the web host's answers mocked (page.route) — the sign-in and sign-up landings, Create organization (colleague offers, the data region, a chosen pack and its notice; on the Free plan after an empty submit), the picker, the two kinds and an invitation (and one that needs a work account) — at 1366 × 768 and 320 CSS px in all eleven languages, with page-level sideways scrolling, everything past the viewport's edge and targets under 24 × 24 CSS px measured; and the server-rendered pages (the region page with one region and with two, the chooser, Regions unavailable, the signed-out, sign-in-failed and not-found pages) written out byHostedPagesAccessibilityTests, 7 pages × 11 languages at both sizes, in the light and dark schemes, with the focus ring's computed colour. - In jsdom, for what needs the API (the app over the live client): axe-core assertions added to the unit tests of Colleagues, AI processing outside {geography}, the organization's e-mail, Signing out, Who can join, the usage meters and Settings → Subscription (the trial, a paid plan with Bundles and storage, Change plan — the buy dialog already had its own), and of every live screen (
uxAudit.test.tsx); jsdom lays nothing out, so contrast, reflow and target size there rest on the theme's tokens. - A WCAG 2.2 A / AA code review of every component in scope — names, roles and states, focus after each action that removes or disables the control pressed, errors on their fields and when they are announced, language of parts, status messages, timing (2.2.1), redundant entry (3.3.7), accessible authentication (3.3.8) — and a localization check: the shared UI's 343 hosted strings — 773 with Subscription and the bundles — against English in the ten other languages (missing, empty, untranslated, placeholders), the live client's and the entry's through their own tests; and the terms of the 2.6.0 localization sweep applied to the hosted keys it had left for this pass.
- Found and fixed the same day (43; each with a unit test,
HostedPagesAccessibilityTestsor the browser pass):- 1.3.1: the jurisdiction list's country groups and the two kinds of Create another organization put a group role between a list and its items (axe
listitem); AI processing outside …'s title was styled text (now a heading); the e-mail notices switch's explanation and the storage meter's figures were not tied to their controls. - 2.5.3: the account button's visible initials were not in its accessible name (axe
label-content-name-mismatch, every signed-in screen); the initials are now drawn by the style sheet. - 2.4.3: focus fell to the page after Ask to join, a refused create, Continue in Create another organization's panel, an organization that could not be opened, an invitation's refusal and Try again, Continue in the session dialog, Stay signed in, Colleagues' Approve / Decline and switch, AI processing's Allow / Withdraw consent, the e-mail's Save, Confirm and Resend, Signing out's and the portal address's Save, Who can join's Save, Discard and a tenant's remove, Extend 30 days, the buy dialog's answers (to Close, or to Stripe's invoice page when the bank asks to confirm or the card is declined) and a buy button whose line the purchase resolved. Each now gives focus back to the control when it is still there, or moves it to the next sensible one.
- 3.3.1: the Reply-To's Enter one e-mail address. was announced from the first keystroke (it now waits until the field is left or saved), and a wrong, expired or locked code was said under the section rather than on the code field; the portal address refused an address still being typed (too short, a trailing hyphen) — it now says so once the field is left.
- 1.4.11: the server pages' focus ring kept #006CBE in the dark scheme, 2.9:1 on a dark card (now #7CC0F5, 8:1).
- 1.4.10: at 320 CSS px the picker's Work account needed badge ran past the edge in Spanish and Portuguese (it now goes under the name).
- 4.1.3, 3.1.2, 2.4.6, 2.5.8: the jurisdiction search says how many match; the Default language names carry their own language; two Ask to join buttons, and each join request's buttons, are told apart; the landing's footer links are 25 px tall.
- Words: four sentences told a person something untrue about the trial or the Free plan (Signing in starts your 30-day free trial, the trial includes everything, Choose a plan … to work in it on Free, and a member's portal line asking for the wrong thing) — corrected in all eleven languages; a member's used-up line said ask an administrator twice; Portuguese called the trial an avaliação (this product's word for an assessment), German said Anfrage for an access request, Finnish addressed the reader in the plural and Spanish used tú on the hosted billing lines.
- 1.3.1: the jurisdiction list's country groups and the two kinds of Create another organization put a group role between a list and its items (axe
- Left open — the report's recommendations and roadmap item 28: the invitation surfaces' focus after Revoke and while they work; links that open a new tab do not say so; a heading for the colleague offers; the extended trial's last week; a landing at
app.realizer.io/before Microsoft's sign-in; the disabled shared workspace kind kept focusable; the allowance banner's running low wording; focus after Subscription's Add a module; one pattern for a message bar inside a live region. All but the landing were fixed by the polish pass later the same night (work/polish-260; the report's Recommendations): the landing atapp.realizer.io/stays a product decision, and the stage pass and the owner's NVDA pass remain.
- In a real browser (
- The polish pass (2026-11-10; built for 2.6.0, not in 2.5.0). The recommendations of methods 21 and 22 taken up the same night (
work/polish-260, merged into the batch; each report's Recommendations table says what became of each), nothing deployed, no screen reader: unit tests with the fixes (jsdom, axe where the surface had it), the server pages' tests, and the marketing demo in a real browser at 320 CSS px for what it shows (uxAudit.spec.ts: every Bates number on one line; the media viewer's recording name ending inside its header). The full suites of the shared UI, the client and the web host, and the API's template tests, ran green on the merged branch (the reports' Tests). - Code reading for the owner's NVDA script (2026-11-10; built for 2.6.0, not in 2.5.0). Writing the screen-reader script (
docs/test-runs/2026-11-nvda-script-2.6.0.md) meant reading in the code what each check should hear, and six suspected defects turned up. Five were real and were fixed the same day onwork/pre-nvda-fixesfor the 2.6.0 batch, each with a unit test (jsdom; axe where the surface had it), nothing deployed, no screen reader: 3.1.2 — the module player's title (its heading and the trail's last crumb) did not carry the module's language; 4.1.3 / 2.4.3 — the Studio's check summary was mounted together with its words, so the first Check could be silent, and Check dropped focus to the page while it ran; 1.3.1 — the release picker's Already in Release {n} note was not tied to its combo box; 2.4.3 / 3.3.1 — a refused name to print left focus on the button, or on the page; and the words You may try 1 times. (now each language's plural forms). The sixth was not a defect: the language button's EN (2.5.3) is never drawn — Fluent's icon button draws no text — so the button is icon-only and its name has nothing visible to contain; the dead text was removed and a test pins the button as it is. The rows they touch say method 24; the script's expected lines for those checks (SR-17, SR-19, SR-20, SR-24, SR-31, SR-32) now say what the fixed code should be heard to say. The shared UI's full suite ran green on the branch. - The hosted edition on stage — the keyboard, in-page checks and a 320 CSS px reflow pass (2026-11-10 and 2026-11-12; built for 2.6.0, hosted stage, Chrome). On 2026-11-10, signed in to a trial organization on the Canada stamp: the stage app's content security policy keeps axe-core out (
connect-src) and the app refuses to be framed, so contrast, target size and accessible names were checked by a script in the page, with the keyboard, over My Day, Create another organization (Data region: Canada; focus back on the switcher), Settings → Subscription, Features & AI with the AI consent card, Members with Colleagues from your Microsoft organization, the Requests and Incidents registers and an incident's panel. Nothing failed; advisories only: the switches (40 × 20 CSS px) and the breadcrumb (56 × 16) meet 2.5.8 through its spacing exception, and the grey text measured is on disabled controls (exempt). On 2026-11-12, the reflow pass, in a browser window 320 CSS px wide opened from the app itself (same origin, since it cannot be framed): My Day; the Requests and Incidents registers; an incident's panel with its Risks of harm, Notifications, Documents, Closure and Activity tabs; the Settings list, Subscription, Features & AI, Members and Organization; the organization switcher's menu, Create another organization and the account menu. Three defects — content cut off or scrolled sideways (1.4.10) — were fixed the same day (cf2f3fd44) and checked by applying the same styles to stage at 320 CSS px: the header's organization switcher ran past the page's edge and lost its chevron (a long name would have lost its end) — it now wraps under the wordmark; on an incident's Notifications tab an obligation's Generate letter, Mark sent and Dismiss did not wrap, so Dismiss sat past the edge and the tab scrolled sideways — a panel's row of action buttons now wraps; in Features & AI the AI usage this month meter kept its label on one line and pushed Change monthly budget and Per-feature breakdown 100 px off the panel — the meter now shrinks and its words wrap (shrinking alone cut them off with an ellipsis;AiUsageMeter.reflow.test.tsxpins both). Advisories: Fluent's menus are placed against the window's width, so at 320 CSS px with a page scroll bar their last 7 px sit under it (nothing in them is cut); an incident's Documents tab keeps its sub-tabs in a strip that scrolls on its own, where the panel's own tabs fold into a More menu. The fixes reach stage with the next hosted release, where this pass is to be repeated (roadmap item 29). - The owner's NVDA pass over the 2.6.0 surfaces and the hosted edition (2026-11-12; owner-run, hosted stage, Chrome). The owner — a sighted person who is not an everyday screen-reader user — ran the script
docs/test-runs/2026-11-nvda-script-2.6.0.mdwith NVDA and its Speech Viewer on hosted stage (the Canada stamp, which ran buildd5ded2354of 2026-11-11: main with the 2.6.0 batch), in one organization with the add-ons, which covers the screens both editions share. All three blocks ran. P1 (SR-01 – SR-14): the region page on the global entry, the hand-off and the sign-up landing, Create another organization and its form (data region, errors, language, jurisdictions, Terms), the guided welcome, the trial banner, the organization switcher and the account menu, Settings → Subscription, Add a module, Bundles and storage and the buy dialog, Manage users and Signing out, AI processing outside Canada, the session warning (2.2.1) and signing out. P2 (SR-15 – SR-23): How we decide, My learning and the module player, a Check, a Decide step, the certificate, rolling releases, Here's your task, redaction discussion and the Free plan's unavailable New. P3 (SR-24 – SR-32): the Studio's findings on their fields, a Glossary refusal, Lab mode, a media mark's card, the Reports menu, dated settings, invitations and a French pass — the interface, and a module written in French for language of parts (3.1.2). The owner reported that all three blocks worked as the script expects: no check failed. The per-check results table and the NVDA and Chrome versions were not sent back, so this report records the pass by block; the three optional checks (SR-33 Ask to join, SR-34 the allowance banners, SR-35 the buy dialog's 3-D Secure path) were not reported and are not claimed. - The 2.6.0 core functional run (2026-11-11 – 12; dev tenant, SharePoint, Chrome; the 2.6.0 batch, API
81aa3a026). The promote-gate functional run (docs/test-runs/2026-11-11-core.md: 392 checks, 390 passed, none failed) exercised the application with the keyboard as well as the mouse and found one accessibility defect, DEF-21 (2.1.1, 2.4.3): on the Requests grid Down and Up did not move between rows, as they do on the other registers' grids, and opening a Draft request left focus on the grid row behind its modal panel. Fixed in code and verified on dev the same night: Down, Up, Home and End move the focused row, and Enter on the Draft request opens its panel with focus inside it.
Not performed: JAWS and VoiceOver sessions, and a session by a person who uses a screen reader daily — including table navigation with column headers, Acrobat Reader and caption files; and any screen-reader pass over the DPIA validation, training, case-archiving, discovery-survey and spreadsheet-layout surfaces new in 2.5.0. The automated axe scans and the 320 px pass were performed on 2026-09-25 (method 6), an automated NVDA pass over the media viewer the same day (method 7), a live NVDA session over the application on 2026-09-26 (method 10), and an NVDA pass at 200 % over the native viewer and editors on 2026-09-30 (method 13). The owner's NVDA pass over the 2.6.0 surfaces and the hosted edition (method 26, 2026-11-12) covered the 32 checks of the script's three blocks; among the surfaces built for 2.6.0 it left out the coach notes editor, the page editor, the Studio's Assets, overlay and Translations tabs, Team progress, the Training coverage report, the Quality and Obligations tabs, Training done elsewhere, Your own AI deployments, the script's three optional checks (Ask to join, the allowance banners, the buy dialog's 3-D Secure path), the marketing demo and the Training Lab's own site. The release candidate's runtime pass (method 15, 2026-10-13) used axe, reflow measurements and the keyboard, not a screen reader.
Applicable standards
| Standard / guideline | Included in report |
|---|---|
| WCAG 2.2 Level A | Yes (Table 1 and the Level A rows of Table 2b; 4.1.1 does not apply to 2.2) |
| WCAG 2.2 Level AA | Yes (Table 2 and the Level AA rows of Table 2b) |
| WCAG 2.1 Level A | Yes (Table 1) |
| WCAG 2.1 Level AA | Yes (Table 2) |
| WCAG 2.2 / 2.1 Level AAA | No |
| WCAG 2.2 and 2.1 Level A / AA — public intake portal | Yes (Table 3) |
| EN 301 549 clause 7 (video and audio) — media records | Yes (media section, 2026-09-23) |
| ISO 14289-1 (PDF/UA-1) — generated PDFs | Measured with the PDF/UA checker, not claimed (generated outputs section, 2026-09-25): a package or edition is described as meeting PDF/UA-1 only when its own check passed |
| Revised Section 508 / the rest of EN 301 549 | Not covered by this WCAG-edition report |
Terms
| Term | Definition |
|---|---|
| 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. |
| Not Evaluated | The product has not been evaluated against the criterion. (Not used in this report — every criterion was evaluated.) |
Conformance at a glance
The application (the SharePoint / Teams web part, the document and media viewers, the editors) on 2.5.0. The public portal has its own summary with Table 3, and generated outputs their own section. The surfaces new in 2.5.0 are assessed in their own sections (DPIA validation, the native viewer and editors, training, spreadsheet layout, case archiving, the discovery survey and the rest), which carry their own levels and are not counted below. The one gap found there on 2026-10-05 — five answer types of a translated survey question shown in its original wording kept the translated name (2.5.3) — was fixed the same evening. Most of those sections rest on code review and unit tests rather than a runtime pass; the release candidate's static review and runtime pass (method 15) are recorded under 2.5.0 release-candidate changes.
| Standard | Level | Criteria | Supports | Partially Supports | Does Not Support | Not Applicable |
|---|---|---|---|---|---|---|
| WCAG 2.2 | A | 31 | 28 | 2 | 0 | 1 |
| WCAG 2.2 | AA | 24 | 20 | 2 | 0 | 2 |
| WCAG 2.1 | A | 30 | 27 | 2 | 0 | 1 |
| WCAG 2.1 | AA | 20 | 17 | 2 | 0 | 1 |
The release candidate's static review (method 15, 2026-10-07) had moved 2.4.3, 3.3.1 and 4.1.3 to Partially Supports for the items it left open. All of them were fixed on 2026-10-13 — in code with unit tests, and re-checked on dev where the runtime pass of that day reached them — so the three are Supports again, as they were in the 2026-10-05 edition.
WCAG 2.2 Level A is WCAG 2.1's thirty criteria less 4.1.1 Parsing, plus 3.2.6 and 3.3.7; Level AA is WCAG 2.1's twenty plus 2.4.11, 2.5.7, 2.5.8 and 3.3.8. The four Partially Supports are the same in both versions: 1.2.1 and 1.2.2 (caption accuracy is speech recognition's, unverified), 1.2.5 (a described audio track cannot be chosen in the viewer) and 3.1.2 (letters held for sign-off by versions before the merge language was stored take the tenant's default language). 3.3.1 moved to Supports on 2026-09-25, when background loads and saves that used to fail silently were made to say so (method 8). Not Applicable: 2.5.4 (nothing responds to motion), 1.2.4 (no live media) and, for 2.2, 3.3.8 (sign-in is Entra ID's, through SharePoint or Teams). No criterion is Does Not Support.
How the product meets the guidelines. Every form control carries a programmatic name sourced from the same localized strings as its visible label; every icon-only button and per-row switch carries an explicit label; every loading spinner announces via role="status" (lint-enforced); save / validation outcomes announce through deliberate live regions plus Fluent MessageBar semantics. Keyboard operation is systematic: clickable cards and rows implement the role / tabIndex / Enter-Space pattern, grids open rows on Enter, every reorder surface has a keyboard alternative (Alt+Arrow with focus restoration, or menu items), document-viewer redaction marks are focusable, labelled, activatable, and geometry-adjustable by keyboard (Alt+Arrow move, Alt+Shift+Arrow resize, a "Place redaction box" command for free-form marks), and single-character shortcuts are active only while their surface holds focus. The media viewer is keyboard-operable for playback (Space, arrows, , . frame step, J / K / L, Home / End, F), view switching (1 / 2 / 3), mark navigation ([ ]), captions (C), descriptions (D), transcript find (/), marks (I / O in-out points; M or B starts a mark in the non-modal mark bar, whose In / Out, region, effect and exemption are typed or chosen; Enter saves, Esc discards; Alt+Arrow nudges and Alt+Shift+Arrow trims a focused timeline bar; the marks area's focus row has start / end grips that are slider thumbs; Ctrl+Z / Ctrl+Shift+Z undo and redo) and video regions (typed left / top / width / height, or R and the arrow keys); its shortcuts are scoped to the player and can be switched off; the timeline's scrub lane is an ARIA slider with whole-second value text; every processing, transcription, upload, and scan state is a status chip or live region; captions ride a native <track> so browser / OS caption preferences apply, and reach everyone who may play the recording; an imported description track is read through a polite live region behind a Descriptions switch; the transcript drawer is the text alternative for spoken content (and lists on-screen text), with click / Enter-to-seek segments, aria-current on the segment under the playhead, the recording's lang, and a polite match counter; released recordings carry redacted captions, a transcript and the description track; under Windows forced colours the viewer draws in system colours. Mixed-language content carries lang markup on the app root, translated fields, and correspondence rendered in the requestor's language. The status / state colour system is ONE map and palette (UI-1, 2026-11-04) with AA ratios computed from its tokens in light, dark and high contrast, and both type-ahead search controls implement the ARIA 1.1 combobox pattern (runtime-verified).
Known remaining gaps (each detailed in its criterion row): the viewer cannot play an original's described audio TRACK (the browser offers no track selector — a text description track is played, and released copies carry every audio track redacted) and the product writes no descriptions itself (1.2.5, EN 7.2); captions are speech-recognition output whose accuracy the product does not verify; and letters held for sign-off by versions before the merge language was stored are marked with the tenant's default language, which is wrong when such a letter was written in another (3.1.2). The silent background failures carried as 3.3.1 were fixed on 2026-09-25. The diagram focus indicator, the small-tile charts, the placeholder-only labels and the split buttons carried by the 2.1.0 report were fixed on 2026-09-25 (method 8). The media gaps the 2.1.0 report recorded — pointer-only region geometry, Space intercepted on focused buttons, captions and transcript withheld from users without the requestor-PII permission, the 2.05:1 Proposed amber, the suppressed focus on the selected timeline bar and the workspace body, the untagged transcript, and the non-reflowing viewer — were fixed on 2026-09-23 (see the media section). The most significant open assessment tasks are a person's screen-reader session on the media viewer — an automated NVDA pass (method 7) and a 320 px pass (method 6) ran on 2026-09-25 — and the screen-reader passes over the surfaces new in 2.5.0 (DPIA validation, training, case archiving, the discovery survey, the spreadsheet-layout dialogs and the grid review), none of which has been run. Smaller items left by the 2026-10-13 runtime pass — about seventeen people pickers that still say No results when the search itself failed, and the dark-theme colours of 2026-10-07 not yet measured at runtime — are under 2.5.0 release-candidate changes → Still open.
Table 1: Level A — the criteria WCAG 2.2 and WCAG 2.1 share (and 4.1.1, WCAG 2.1 only)
| Criterion | Conformance | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Images carry alt text and decorative icons are hidden from AT (Fluent Icon defaults to aria-hidden). Meaningful indicators carry text / ARIA equivalents: the document unread dot is role="img" with a localized label; media row chips (Preparing preview, Transcribing, Transcript, Scanning for faces & text, malware / content-type hygiene) are text pills with role="status" (MediaRowChips); every spinner (677 in the 2.5.0 release candidate) announces via ariaLabel (lint-enforced); the media poster is alt="", sprite hover thumbnails are aria-hidden, the audio waveform canvas is role="img" named with the file, its duration and the number of silenced spans, and the marks overlay canvas is aria-hidden because every mark it paints is also a named row in the redaction side panel (span, effect, exemption, status). In-viewer redaction overlays are labelled focusable controls; charts expose data-bearing accessible names (chart type + measure + total + top values, locale-formatted). 2.5.0 RC (2026-10-07): a read-only diagram (an approved or frozen answer, a custom field, the risk overview, an AI draft before it is used) now has a Text version under the drawing — the swimlanes, shapes and connectors as lists in the UI language; until then it was one image named by its question. |
| 1.2.1 Audio-only / Video-only (Prerecorded) | Partially Supports | The product authors no time-based media; the media it plays is user-uploaded evidence. For audio-only records the transcript drawer (MediaTranscriptDrawer) is the text alternative — time-coded, speaker-labelled segments that seek the player — produced by Azure AI Speech, imported from Teams, or imported as WebVTT. Since 2026-09-23 it reaches everyone who may play the recording (the audio's own gate); a user without the requestor-PII permission reads the same words with speaker names (a Teams or imported label) replaced by "Speaker n", the one thing a transcript adds to the audio. For video-only content the drawer lists the text the frame scan read on screen, time-coded and seekable. Gaps: the alternative exists only when transcription (or a frame scan) has run, and nothing describes visual content other than on-screen text. Captured records (chats, mail, OneNote, calendar) replace embedded media with text placeholders. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | Uploaded video plays with closed captions: a native <track kind="captions" default> with srclang set from the transcript language (MediaViewerModal), rendered by the browser so OS / browser caption preferences (size, colour, background) apply, toggled with a labelled Captions button (aria-pressed) or the C key, and retained in full screen. Since 2026-09-23 the captions URL is issued to everyone who may play the recording (with speaker names replaced for a user without the requestor-PII permission, through a separate token scope the address cannot upgrade) — and a defect that made the captions track fail to load for every user (its token was written with the wrong scope) is fixed. Teams meeting recordings import their Teams transcript directly; the transcript-import endpoint accepts a corrected WebVTT (there is no in-app control for a manual import). Remaining gaps: (1) captions are speech-recognition output unless a Teams or imported transcript exists, and their accuracy is not verified by the product; (2) audio-only records have no caption rendering (the <audio> element carries no track, so the Captions button is no longer offered there) — the transcript drawer is the alternative; (3) in Redacted preview a region mark that covers the lower part of the frame is painted over the native caption area. Released recordings carry captions too (see Generated outputs). |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Supports | Both mechanisms the criterion allows are provided; the recordings themselves are uploaded evidence (authored content). Audio description (since 2026-09-23): a recording's uploader or a document manager imports a text description track (WebVTT kind="descriptions", from the recording's details); anyone who may play the recording turns on Descriptions (a toggle button with aria-pressed beside Captions, or D) and each description is shown in a lane under the picture and read through a polite live region tagged with the track's language — a screen reader speaks it without interrupting itself, a sighted user reads it. Media alternative: the transcript drawer for the spoken content (find-in-transcript with previous / next seeks the player; segments read as a document; the playhead-following segment is aria-current) and the on-screen text the frame scan read, as time-coded entries. The product writes no descriptions itself. Code-reviewed 2026-09-23; live screen-reader pass pending. See 1.2.5 (AA). |
| 1.3.1 Info and Relationships | Supports | Every form control carries a programmatic label (custom-field editors expose required state). Panels and dialogs expose programmatic titles; detail and settings surfaces use real headings, semantic lists and tables, and labelled nav / region landmarks; data grids ride Fluent DetailsList semantics; the risk heat map is a semantically correct table. Media viewer: the redaction side panel is a labelled <aside>, the table editor renders a real <table> with header cells and required markers, the diagram List view exposes swimlanes / nodes / connectors as three labelled tables, and the required-row hint is role="alert". Media (2026-09-23): the keyboard-shortcuts list is a table; the timeline's scrub lane is the slider and the marks live in their own labelled section under the player (the marks area: a labelled group of bars, filter chips in a labelled group, a focus row that is a group named by the selected mark); the mark bar is a group named by its mark ("New mark" for a draft), its region fields a labelled group; the description lane's text carries the track's language; each recording's marks in the release-variants panel are a group named by the recording, under headings. Advisory, not a failure: the app relies on the SharePoint / Teams host for page-level landmarks; the transcript list is div-based rather than list markup. 2.5.0 RC (2026-10-07): every row of a question's choice options is named (only the first row's fields had names) inside a group named by the list; a translatable field's language boxes are named by the field and the language. Since 2026-10-13 the case panels' card titles — about seventy, in the sidebars and the card groups — are real headings (level 3 beside a tab's section headings, level 4 inside a card group), every grid in the report sections is named by the heading above it, a statistical template's section errors say which line or band they are about, and Threshold reached on the Conduct signals card is said in words as well as by its flag. The runtime pass (2026-10-13) found four dashboards' actions columns, the Documents tab's selection column and the statistical reports' row-label column with no header text; each has header text now, hidden visually. |
| 1.3.2 Meaningful Sequence | Supports | Content order in the DOM matches the visual reading order, with one CSS reordering: below 480 px the media control bar shows the scrub lane on its own row above the buttons (order), while in the DOM and the focus order it stays after Play and the readout — the controls' meaning does not depend on their sequence (corrected 2026-09-23: this row said no CSS reordering was used). In the media viewer the DOM order is header actions → player stage (with the placing bar and the selected region's edit chrome) → description lane → mark bar → control bar (play, readout, scrub lane, captions, descriptions, mute, volume, full screen) → in / out strip → marks area → shortcuts link → side panel (Redact menu, marks list, transcript). |
| 1.3.3 Sensory Characteristics | Supports | Instructions reference controls by their visible labels and key names (the shortcuts callout lists key → action pairs; the in / out strip names the M key and the Mark… button; the placing bar says "drag a box over it, or click one corner and then the opposite corner"). The one colour-worded instruction ("Amber / Red thresholds") names on-screen field labels. |
| 1.4.1 Use of Color | Supports | The dominant pattern is colour + icon + text: status chips carry glyph and text, overdue / due-soon dates pair an icon with the tinted pill and the date, tag chips always carry label text. Media viewer: timeline bars carry the exemption label and span as accessible name and tooltip; Proposed marks are distinguished by a dashed border and diagonal hatch as well as amber (#986F0B, the PDF viewer's Proposed colour) — and stay dashed under forced colours; the selected bar gets a thicker dark border and outline; a whole-frame mark says "Whole frame" in text; region overlays carry the exemption caption inside or above the box; muted spans in the waveform are gapped (not only recoloured) in Redacted preview; the side panel shows status, origin badge and effect as text. Charts (fixed 2026-09-25, method 8): a small trend tile draws each series in its own dash (solid, dashed, dotted, dash-dot) with a key of line samples beside the names, and full-size line charts use the same dashes; multi-series bar and donut tiles keep their legends (hovering or focusing an entry picks its series out) and every bar or slice's callout names it in text; report sections render data tables; every chart exposes a data-bearing accessible name. Until then small tiles told series apart by hue alone. UI-1 (2026-11-04): one status colour system (docs/features/StatusColours.md) — every status takes its colour from one map and one palette with light, dark and high-contrast values, so a summary card and the chips it filters always agree; chip text ≥ 4.5:1 and every accent ≥ 3:1 are computed from the tokens for all three themes (statusPalette.contrast.test.ts); a finished-without-completing chip (Cancelled, Withdrawn, Superseded) is outlined rather than filled, so it is not told from a Draft by colour; under Windows forced colours chips, summary cards and due-date badges keep a CanvasText border. |
| 1.4.2 Audio Control | Supports | Nothing plays automatically: <video> / <audio> carry preload="metadata" and no autoplay; playback starts only from the Play button, Space / K, or a scrub release that resumes a recording the user had already started. The control bar exposes labelled Play / Pause, Mute / Unmute and a volume slider (Fluent Slider, keyboard-operable), plus J / K / L speed keys; in Redacted preview muted spans force silence while the user's own mute survives. |
| 2.1.1 Keyboard | Supports | Shell: clickable cards / rows implement role / tabIndex / Enter-Space, grids open rows on Enter (runtime-verified), upload drop zones have a keyboard path, every reorder surface has a keyboard alternative (Alt+Arrow with focus restoration or menu items — including grid column reorder and Alt+Shift+Arrow resize) persisting through the same handlers dragging uses. Long-label picker (2026-10-03 — exemptions, legal authorities, reasons, grounds, outcomes, templates): Enter, Space, Alt+Down or a typed character opens it with focus in its search box; Up / Down, Page Up / Down and Ctrl+Home / End move through the options; Enter chooses (toggles under multi-select, the popup staying open); Escape or Alt+Up closes without a change and returns focus to the field; Tab closes and continues from the field; each multi-select chip has its own Remove button. Code-reviewed and unit-tested; live screen-reader pass pending. PDF viewer: overlay marks are focusable and activatable, with Alt+Arrow move / Alt+Shift+Arrow resize on editable marks through the pointer commit path; "Place redaction box" drops a default-sized box into the same confirm flow as a pointer drag; the side panel's review lifecycle (accept, dismiss, flag, withdraw, approve, bulk) is fully keyboard-operable. Media viewer (the marking UI as rebuilt on 2026-09-23 — the non-modal mark bar and the marks area replaced the mark editor dialog): playback, view mode, captions, descriptions (D or the Descriptions button), find, mark navigation and marks are keyboard-operable. M (or B, or Mark… in the Redact menu) starts a draft: on video the placing bar offers Use whole frame, Same box as last mark and Use a detected region as buttons; the mark bar's In / Out fields accept typed hh:mm:ss.f beside two named "Set In / Out to the playhead" buttons, its effect is a dropdown and its exemption the long-label picker (since 2026-10-03), and Enter saves / Esc discards; Edit mark… on a mark's row focuses the mark bar for that mark. Spans: Alt+Arrow / Alt+Shift+Arrow nudge / trim a focused bar; the marks area's focus row has start and end grips that are slider thumbs (arrow keys one frame, Shift one second, Page Up / Page Down five seconds, Home / End the limits); Shift+I / Shift+O start or end the selected mark at the playhead. Regions: the mark bar's Region button opens typed left / top / width / height (percent of the frame, arrow keys stepping each) with Grow / Shrink 5 %, and R or Adjust region with the keyboard focuses the selected region's edit chrome — arrow keys move it, Shift+arrows resize it (a tracked mark gets a tracking point exactly as a drag gives it). Undo / redo: Ctrl+Z / Ctrl+Shift+Z in the player and timeline, or the Undo / Redo buttons. Since 2026-09-24: the selected mark's tracking points are a toolbar of ◆ buttons with a roving tab stop (arrows move between them, Enter goes to one, Delete removes it, Alt+Arrow moves it one frame, Alt+Shift+Arrow one second) and { / } go to the previous / next point; Re-track from here, Track to fill, Split at the playhead (S), Merge, History of this mark and Revert to this version are buttons and menu items; Ctrl+Space on a focused bar adds it to the multi-selection, which is also the side panel's checkbox selection. The viewer's shortcuts are scoped to the player (stage, mark bar, control bar, marks area); a button, switch or tab keeps Space and Enter, and an item that handles a key (a timeline bar, a grip, a transcript line, a mark row) is not also toggling playback. Code-reviewed 2026-09-23; live screen-reader pass pending. Diagram editor: shapes are focusable buttons — arrows move (to the next grid line while Snap to grid is on), Alt+Arrow resizes, Enter / Space selects, Shift+Enter adds to the selection, F2 renames, Delete removes, Alt+Up / Down reorders swimlanes; on the canvas Ctrl+A, Ctrl+C / Ctrl+V / Ctrl+D, Ctrl+Z / Ctrl+Y and Escape (2.5.0); alignment, Arrange, zoom (buttons beside Ctrl+wheel), Check diagram (a list of links that select the item), Draft with AI and Export are toolbar commands, and a connector added by dropping it on empty canvas can equally be made with the palette and Connect; connectors — their route and attachment sides included — properties and everything else are editable in the List view (three tables). (Corrected 2026-09-23: the 2.1.0 report said Space also misfired in portaled dialogs and menus — Fluent layers stop event bubbling, so they were never affected; the in-viewer item handlers were.) 2.5.0 RC (2026-10-07) — diagram editor v4 / v5: Shift+Enter adds a shape to the selection and Ctrl+A selects them all; arrows move the whole selection; align, distribute, Arrange, zoom and Fit, Check diagram, Draft with AI and Export are toolbar commands; Ctrl+C / Ctrl+V / Ctrl+D copy, paste and duplicate and focus moves to the pasted shape. Corrected: connectors were not keyboard stops, so their colour and bends (in Details) needed a pointer — the List view carries their route and sides but not those; each connector is now a named button (Enter selects it, F2 renames, Delete removes). Fixed: Escape on the canvas or in its label editor also closed the panel around the editor, losing an unsaved subject diagram; it now stops at the canvas. |
| 2.1.2 No Keyboard Trap | Supports | Fluent focus-trap defaults are used for modals and dialogs; panels and dialogs dismiss with Escape and restore focus (runtime-verified). The media viewer is a non-blocking Fluent Modal (Escape closes and saves the playhead); full screen is exited with Escape or the labelled button; the mark bar is non-modal (Tab leaves it), and the approved-edit and re-scan prompts are Fluent Dialogs; the keyboard-shortcuts, details and region / notes callouts take focus and close with Escape or their Close button without closing the viewer (since 2026-09-23); Escape cancels placing, discards a draft, ends keyboard region adjustment or hides the timeline's hover preview without closing the viewer. The viewer iframe is exitable with Shift+Tab (Escape inside the iframe does not close the hosting modal; the close button remains reachable). Six detail panels set forceFocusInsideTrap: false so window re-focus does not yank focus to the panel's first element. |
| 2.1.4 Character Key Shortcuts | Supports | Every single-character shortcut set is active only while keyboard focus is within its owning surface — the criterion's focus-scoping condition — and suppressed during text entry: the PDF viewer's R / H / C / F / [ / ] (useRedactionKeyboard, explicit containment check), the Documents tab's / and f, and the media viewer's Space, , ., J / K / L, F, /, C, D, 1 / 2 / 3, [ ], I / O / M / B / R / N, = / - / \ (since 2026-09-23 active only while focus is in the player — the stage, the mark bar, its control bar and the marks area — never in the header, side panel or transcript, never on a text field, never with Ctrl / Cmd except undo / redo; and the letter, digit and punctuation keys can be switched off in the shortcuts panel for speech input and screen-reader quick keys). All other shortcuts are chorded (Alt+Arrow, Ctrl+A / D / F). |
| 2.2.1 Timing Adjustable | Supports (Microsoft 365 edition); Partially Supports (hosted edition) | Microsoft 365 edition: no session or inactivity limits exist outside Lab mode; authentication renews silently. Hosted edition (2.6.0): a session ends after the organization's inactivity limit (an Administrator chooses 15 – 240 minutes, at most the stamp's maximum — 120 on Realizer's service; re-checked against SessionTimeoutWarning.tsx and HostedSessionPolicyService on 2026-11-07, method 20) and after 12 hours at most (ITSG-33 AC-11 / AC-12). Two minutes before the inactivity end a dialog with a live countdown offers Stay signed in — a single action (Escape does the same), far more than the 20 seconds the criterion requires, repeatable until the 12-hour end; the countdown is announced at 60, 30 and 10 seconds. Five minutes before the 12-hour end a notice says so; that end cannot be extended (a security control), and at the longest inactivity limits fewer than the ten extensions the criterion asks for fit before it — hence Partially Supports. After either end the sign-in page says why, and Sign in again returns to the same page. Lab mode (2.5.0) returns an idle tab to real work after 30 minutes, with a warning and Stay in Lab mode at 28 (see Training). The media playback token (4 h) and the viewer ticket (60 min) self-heal — a media error or viewer load failure re-mints the link and restores the playhead / page position — so nothing is lost. Chunked upload sessions pause on a dropped connection and resume automatically; an abandoned session is swept only after 24 h idle (beyond the 20-hour exception). Success / informational toasts auto-dismiss after 3–6 s but pause while hovered or focused; errors persist until dismissed. |
| 2.2.2 Pause, Stop, Hide | Supports | No moving, blinking, scrolling, or auto-advancing content. Recordings are user-started and pausable; the marks overlay repaints on animation frames only to follow the user-controlled playhead; background polls (3–5 s) update processing / transcription / scan status text and self-stop; a global prefers-reduced-motion rule disables all transitions and animations. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing content; the only animation is standard spinners / fades. Redacted-preview effects (box, blur, pixelate, slate) are static per frame. |
| 2.4.1 Bypass Blocks | Supports | The host (SharePoint / Teams) supplies page-level skip mechanisms. In-app primary navigation is a single-tab-stop tablist followed directly by content; headings and labelled landmarks (including the redaction side panel <aside>) support AT navigation; the media viewer's Hide panel button — offered to every user with a side rail since 2026-09-23 — removes the rail from the tab sequence. |
| 2.4.2 Page Titled | Supports | Page titles are owned by the hosting SharePoint page / Teams tab; in-app panels and modals carry programmatic titles (the media viewer's title is the recording's file name, titleAriaId), and the document-viewer pages emit localized titles. (Observation: in-app SPA navigation does not update the host title.) |
| 2.4.3 Focus Order | Supports | Focus follows DOM order (no positive tabindex anywhere, lint-enforced); modal surfaces use Fluent's initial-focus / trap / restore behaviour; keyboard reordering preserves focus (runtime-verified); PDF-viewer overlays survive a rebuild with focus restored to the same mark (captureOverlayFocus, guarded so the iframe never steals focus from the side panel). Media viewer: opening lands on the header; starting a mark moves focus to the placing bar, a placed region (or Edit mark…, or a double-click on a region or bar) to the mark bar, saving / undoing / redoing to the mark it changed (its region when on screen, else the mark bar), and Discard or Esc back to the player; since 2026-09-23 the keyboard-shortcuts and details callouts are focus-trapping dialogs whose Close button takes focus (in 2.1.0 focus never entered them and Escape closed the whole viewer — corrected), accepting or dismissing a suggestion moves focus to the next suggestion (it used to fall to the page), keyboard region adjustment returns focus where it started, and the workspace body is no longer a tab stop. Since 2026-09-25, [ / ] move focus to the mark they select (its bar in the marks area), so Alt+Arrow or Enter acts on it next; a mark folded into a collapsed group has no bar, and focus then stays where it was. 2.5.0 RC (2026-10-07, 2026-10-13): the places where the pressed control disappeared or disabled itself and focus fell to the page were fixed in two rounds — those listed under 2.5.0 release-candidate changes on 2026-10-07, and on 2026-10-13 the dozen-odd the static review left open: after a bulk reassign, in the SharePoint package update dialog, after the waiting-period warning's Cancel, on the Key dates card's correction actions, on each save of the accessible-format card, after Use this verification, an assignment's plain Submit, the audit removals, closure actions and Raise finding, in a scale editor, after Clear filters, a dismissed announcement and a follow-up row action, focus now stays on the control, moves to the next row or to the control that takes its place (a button that disables itself keeps focus as unavailable). The runtime pass (2026-10-13) found two more — a panel opened from a Training hub row, and Log review outcome's Cancel, returned focus to nothing — both fixed and re-checked on dev. |
| 2.4.4 Link Purpose (In Context) | Supports | Links and row actions are contextualized by their accessible name or the enclosing row / card; "Download original" is a labelled button-link; transcript segments are named by their timecode, speaker and text. |
| 2.5.1 Pointer Gestures | Supports | Only single-pointer clicks and drags are used; no multipoint or path-based gestures (Ctrl+wheel zoom over the marks area has buttons and a slider beside it; on the diagram canvas, toolbar zoom buttons and Fit). Drawing a region, moving or resizing it by its grips, moving a mark, scrubbing, range-selecting on the ruler, trimming a bar or a focus-row grip and dragging a diagram shape are start / end-point drags (not path-dependent). Each has a non-drag equivalent (for regions since 2026-09-23: click one corner then the opposite, typed fields, Grow / Shrink, or the arrow keys — see Table 2b, 2.5.7). |
| 2.5.2 Pointer Cancellation | Supports | Activations complete on the up-event. Down-event listeners initiate drags (essential) or manage focus; the timeline's pointer-down starts a live scrub whose frame follows the pointer (essential to scrubbing) and a bar drag commits only on release, with a plain click reverting to a seek. The marks overlay commits a draw or move on pointer-up (pointer events since 2026-09-23, so pen and touch work) and discards drags below a size / distance threshold; a press that does not move is a corner click. |
| 2.5.3 Label in Name | Supports | Accessible names and visible labels are sourced from the same localized strings; controls that add context (status chips, per-row toggles, timeline bars: "exemption · span") contain the visible text within the accessible name. Corrected 2026-09-23: the media viewer's file-name button was named "Show recording details" without the file name it displays; its name now starts with the file name. The mark bar's two playhead buttons (⇤ / ⇥ icons) are named "Set In / Out to the playhead (time)"; icon-only toggles (Captions, Descriptions, Show the effect, Snap) have tooltips that match their names — say "click Descriptions" to a voice-control tool. 2.6.0 (UI-2, 2026-11-04): axe-core 4.14 now checks this criterion (label-content-name-mismatch) and found four patterns the review had missed — fixed: the summary cards of eight dashboards (named 6 Active requests while their DOM read 6Active requests: a space now separates the count and the title), the document preview's and the redaction viewer's file-name button (named Show document details without the file name — it now starts with the name, as the media viewer's did since 2026-09-23), and the redaction list and media mark rows (their name now carries every word the row shows, in order — page or span, effect, label, status, origin, author, comment count — then Locked, Flagged and the alternate exemptions; their badges now wrap instead of being clipped, so the status and origin a narrow panel cut off are shown), and — found once those were fixed — the Risks register's source chips (Audits, 3 risks read Audits3; a space now separates label and count, as in the Documents tab's file-type chips). Checked in all 11 languages by labelInName.test.tsx and by axe-core 4.14.0 on every screen of the demo's Playwright run. Method 24 (2026-11-10): the title row's language button was read as showing the current language's code (EN) under a name without it — the code hands the button that text — but Fluent's icon button never draws a text, so the button is the globe alone, like the rest of the title row, and its name, Select display language, is its whole label: there are no visible words for the name to contain. The dead text is gone, and labelInName.test.tsx pins the button as icon-only, named by that string, in all 11 languages. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-actuated functionality. |
| 3.1.1 Language of Page | Supports | The host page declares the document language; the product defaults its UI locale to the host culture and tags its own root when the user selects a different language (see 3.1.2). Viewer iframe pages declare their own <html lang>. All media-viewer strings exist in the 11 supported locales and, since 2026-09-23, are translated in all of them (corrected: about 80 older media, upload-queue and release-decision strings — the transcript panel, effect names, mark labels, processing states — were English copies in the Danish, Dutch, Finnish, German, Italian, Polish, Portuguese, Spanish and Swedish files, so an untagged English phrase appeared inside a page in another language; the voice-distortion, frame-text and tracking strings had lost their diacritics in ten locales). |
| 3.2.1 On Focus | Supports | The only onFocus handlers re-open a combobox suggestion list and pause a toast's dismiss timer; no context changes on focus. |
| 3.2.2 On Input | Supports | No input auto-submits or navigates; all commits are explicit button activations. Changing the playback-speed dropdown, the view-mode tabs or the volume slider changes a setting of the same surface, not the context. |
| 3.3.1 Error Identification | Supports | Validation and save errors are identified in text via Fluent errorMessage (programmatically associated, announced) and MessageBars inside always-mounted aria-live regions; the reasons a submit button is disabled are rendered as inline text in polite live regions. Media viewer: the mark bar reports an unparseable timecode on the In or Out field itself (Fluent errorMessage, since 2026-09-23) and keeps an inverted span from being saved; a failed save, retry, scan or track surfaces the server's reason; a description-track import names why a file was refused (not WebVTT, no descriptions, too large); the table editor flags an incomplete row with role="alert" naming the missing columns; the working-document editor shows a Saving / Unsaved / Saved / Error status. Background loads and saves (2026-09-25): every catch handler that did nothing (831 in 258 files) was reviewed. About 240 hid a failure a person would act on differently — a list, picker or section that looked empty ("no match", "no verification methods", "all clear" on a closure tab whose checks had failed), a change that silently was not saved, a click that opened nothing, a spinner that never ended — and now say so, in the surface's own error bar or as a notification naming what could not be loaded; a poll reports its first failure once and keeps polling, and the same notice is not stacked. Left silent on purpose, each with its reason in the code: best-effort work whose failure changes nothing a person does (saving the read or playback position, telemetry, prefetch, an avatar photo, clipboard and stored-preference fallbacks). 2.5.0 RC: the static review (2026-10-07) found the shared date picker showing a blank message for an empty required date, a date out of range or one it cannot read (Snooze until, Remind me on, Correct received date), with no format hint for a typed date; it now says Enter a date., names the range in the picker's own format, and answers a mistyped date with the format and an example (2026-10-07). Since 2026-10-13 an incomplete Earlier rule on a request type stops Save with a message on the field instead of being dropped, and an error while an audit's finding or evidence-request dialog is open is shown in that dialog, not behind it. Open, minor: about seventeen people pickers still say No results when the search itself failed (five — follow-ups, section users, groups, bulk reassign and training roles — say the search failed since 2026-10-13). |
| 3.3.2 Labels or Instructions | Supports | Visible persistent labels are the norm; required fields use Fluent required (asterisk + aria-required); complex flows carry instructions (the in / out strip, the placing bar's prompt, the mark bar's status line saying what an edit will do, the shortcuts callout, the description import's format hint); every control has a programmatic name. Since 2026-09-25 (method 8): the fields whose only visible label was a placeholder have visible labels — the finding explanation, a compliance item's note and evidence, a discovery survey's places and units, the mailbox search, the Redactions panel's status, flag, exemption and page filters, the reopen reason — and every search box keeps its magnifier while it has focus, so it is not left with a placeholder that disappears on the first key. Composers (comments, notes, Ask AccessPoint) are named by the Send / Add button beside them and the card heading above them. (The mark bar's In / Out fields carry their hh:mm:ss.f format as a tooltip since 2026-09-23.) |
| 4.1.1 Parsing (WCAG 2.1 only — obsolete and removed in WCAG 2.2) | Supports | All markup is TSX (duplicate attributes / malformed nesting are compile errors); the only dangerouslySetInnerHTML (two, in the diagram editor) draws the product's own built-in icon glyphs, fixed SVG markup shipped with the web part; generated ids use Fluent's unique-id utilities; the viewer and editor pages are server-templated HTML whose dynamic elements are created through the DOM API (no string-concatenated markup). |
| 4.1.2 Name, Role, Value | Supports | Fluent components expose correct roles / values; icon-only buttons and per-row toggles carry explicit ariaLabels; custom picker rows expose checkbox state; both type-ahead search controls implement the ARIA 1.1 combobox pattern (runtime-verified). The long-label picker (2026-10-03; code-reviewed and unit-tested, live NVDA pass pending): the field is a select-only combobox named by its label, with aria-haspopup="dialog", aria-expanded, aria-required and aria-invalid (the error described), whose value is the chosen option's FULL label even where CSS cuts it; the popup is a dialog named like the field, its search box an editable combobox (aria-autocomplete="list") driving a listbox by aria-activedescendant, described by its keyboard hint; each option is named by its full label, described by its explanation and carries aria-selected (aria-multiselectable under multi-select); option groups are role="group" named by their heading; result counts announce politely; multi-select choices are a list named "Selected: {field}" whose Remove buttons name the option. PDF viewer: overlays are labelled, focusable role="button" controls (Proposed marks announce as suggestions with their exemption). Media viewer: the timeline's scrub lane is role="slider" with aria-valuemin / max / now / valuetext (whole seconds, "0:12 of 3:45"); the marks lane is a labelled group BESIDE it (until 2026-09-23 the bars sat inside the slider, whose children ARIA treats as presentational); bars are role="button" with aria-pressed selection and an "exemption · span" name; the focus row's start and end grips are role="slider" thumbs with a timecode aria-valuetext; the mark bar is a group named by its mark and the selected region's edit chrome a group named "Region of the selected mark" with its keyboard instructions as description; the Captions and Descriptions toggles and the marks area's filter chips expose aria-pressed (since 2026-09-25 — until then Fluent dropped it, because the buttons were not marked as toggles; found by the NVDA pass, method 7); the speed dropdown, volume slider, transcript search and every icon button are named; the details and shortcuts buttons expose aria-expanded, and both callouts are named focus-trapping dialogs; media marks' bulk-select checkboxes are named by span, effect and exemption (they all read "P.1" before); the side-panel row's expand button no longer contains the checkbox and the Accept / Dismiss buttons; the flag and lock icons are named; the upload queue's buttons include the file name and Pause / Resume is one button; the Teams-recordings picker exposes one checkbox per row. Runtime pass (2026-09-25, method 6): every notice's close button, 42 custom-header side panels, 5 dialogs (among them the working-document editors, the gap this row used to record) and 10 progress bars were unnamed and are named now; three kinds of row or card that were buttons containing buttons are restructured. Since 2026-09-25 (method 8): the five Fluent split buttons are two buttons each in a named group, and the rows of lists reordered by dragging are grid rows that take focus themselves (Enter opens one) instead of sitting inside a focusable button with the row's own Edit, Delete and Move buttons; 40 more custom-header panels (most Settings sub-panels) are named by their header text, found by the runtime re-scan the same evening. 2.5.0 RC (2026-10-07): fixed — the diagram toolbar's toggles and a selected shape, swimlane or connector expose their state; the toolbar's overflow button is named; the setup page's Deploy to Azure was a button inside a link; grouped choice-field tabs drew an empty tab panel; the selection column's header was a second inert Select all; the Only you chip's hint was an aria-label on plain text. Fixed 2026-10-13: in the Lab library, the connector browser and the SharePoint picker each record row was a checkbox containing its Details button (whose children ARIA makes presentational); the checkbox and the button now sit side by side. Runtime pass (2026-10-13): the complaints report's month bars and age bands put their figures in an aria-label on an element with no role, which is never read (axe aria-prohibited-attr); they are images named by those figures. |
Table 2: Level AA — the criteria WCAG 2.2 and WCAG 2.1 share
| Criterion | Conformance | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The product presents no live time-based media. |
| 1.2.5 Audio Description (Prerecorded) | Partially Supports | Since 2026-09-23 a recording can carry an imported text description track (WebVTT kind="descriptions"), which the viewer plays through a polite live region behind a visible Descriptions switch (see 1.2.3) and which travels with the released recording as a redacted .descriptions.vtt (a description overlapping a muted or bleeped span reads [Withheld — …], naming the provision, since 2026-09-25). Released MP4s also carry every audio track of the original — a described-audio track included, with the same audio redaction and its audio-description flag. Gaps: the viewer plays only an original's first audio track (the browser exposes no audio-track selection), so a described-audio TRACK in the original cannot be heard in the viewer; the product writes no descriptions itself — an organization that must describe released records supplies the track. Code-reviewed 2026-09-23; live screen-reader pass pending. |
| 1.3.4 Orientation | Supports | Nothing restricts display orientation (no orientation locks or restricting media queries in the app or Teams manifest; full-screen video follows the device). |
| 1.3.5 Identify Input Purpose | Supports | Nearly all data-entry fields concern third-party requestors (out of this criterion's scope). The fields that collect the signed-in user's own information — the attestation signature name and title — carry autocomplete="name" and autocomplete="organization-title". |
| 1.4.3 Contrast (Minimum) | Supports | Text colour is engineered to AA with computed ratios in both themes: the central status-badge palette measures 5.77–8.23:1 (light) and 6.94–8.21:1 (dark); theme status-token pairs (--apWarningText 4.75:1 on tint / 5.23:1 on white, --apSevereText 5.52:1, dark ≥6.5:1) are used by the media chips and hygiene pills; body text uses theme slots (≥6.4:1); informative secondary text uses neutralSecondary (6.0:1 on the timeline lane); timeline hover readouts are white on 80 % black; user-configured exemption / tag colours are never used as text colour. Corrected 2026-09-23: the playing transcript segment's timecode measured 3.77:1 on its highlight (4.12:1 on the find highlight) — it now uses themeDark (5.9:1 / 6.5:1); and the exemption caption painted inside a region measures ≥ 7.0:1 (white on 65 % black over even a pure-white frame), not the ≈2.6:1 the 2.1.0 report estimated, so no change to the pill is needed. Corrected 2026-09-25 (runtime pass): the lifecycle rail's names for stages not yet reached measured 2.63:1 and now use neutralSecondary (6.1:1). Tenant-configured colours and uploaded content remain authored content outside product control. 2.5.0 RC (2026-10-07): fixed — in the dark theme a diagram's labels were near-white on its fixed light shape colours (the drawing is now light paper in every theme); a selected source chip on the Risks tab (and a selected document-type chip) drew theme-blue text on its blue tint, about 3.8:1 (now the body text colour); the path editor's "not recognized" text used a colour the dark theme does not adjust. Their dark-theme ratios are computed from the theme's values; the runtime pass of 2026-10-13 ran in the light theme and did not measure them. 2.6.0 (UI-1 / UI-2, 2026-11-04): the status palette has light, dark and high-contrast values (chip text 5.77–8.23:1 light, 6.94–8.21:1 dark, ≥ 10.4:1 high contrast), and the message tints are now hues of it: tint text on its tint 5.96–8.23:1 (light), 6.94–8.21:1 (dark), 6.90–10.02:1 (high contrast: the hue's dark fill with its bright text — they used the dark pair before), and on every page surface ≥ 6.07:1 (light), ≥ 7.61:1 (dark) and ≥ 10.41:1 (high contrast) — the old pairs measured 4.75:1 (--apWarningText) and 5.52:1 (--apSevereText) on their tints. Computed from the tokens by statusPalette.contrast.test.ts; axe-core 4.14.0 in the demo's Playwright run checks the light theme. |
| 1.4.4 Resize Text | Supports | Typography scales with browser / OS zoom; no fixed-height text clipping was found; truncation is ellipsis / line-clamp with the full content available elsewhere; tab bars collapse into an overflow menu on resize; the document preview header and (since 2026-09-23) the media viewer header hide action text (icons + tooltips remain) at narrow widths, and the media viewer scrolls rather than clipping (see 1.4.10). |
| 1.4.5 Images of Text | Supports | No images of text in the UI; the only text-bearing images are exempt brand logotypes (SVG). Captions painted on the redacted-preview canvas mirror what the release burn writes into the file (essential to previewing the release) and the same text is available as real text in the side panel. |
| 1.4.10 Reflow | Supports | Detail panels open full-viewport; ~19 breakpoint rules collapse toolbars; shell containers set min-width: 320px; wide report matrices scroll in their own containers; data grids scroll horizontally (permitted for data tables); the report-builder workspace clamps to min(1180px, 100vw) (runtime-verified). Two-dimensional content is exempt by design: the PDF canvas and the video stage, each paired with a user-togglable side rail (min 320 px, hidden with "Hide panel"). Media viewer (corrected and fixed 2026-09-23 — the 2.1.0 report named only the ≈450 px control bar; the larger failures were a ≈740 px header of non-shrinking actions, a 320 px rail open by default and overflow: hidden on the modal, which left Close / Hide panel / Download focusable but invisible below ≈830 px and gave the player 0 px at 320 px): below 720 px the viewer fills the screen and scrolls, its header wraps (labels become icons, the view-mode tabs overflow into a menu), the rail stacks under the player and starts collapsed, every user with a rail can hide it, the control bar wraps with the timeline on its own row, the mark bar's rows and the marks area's header wrap, and the region / notes callouts and the approved-edit and re-scan dialogs never exceed the viewport. Runtime-verified at 320 CSS px on 2026-09-25 (method 6): no page-level horizontal scrolling on any dashboard, request-panel tab or the media viewer. The long-label picker's popup (2026-10-03) prefers 560 px but is never wider than the viewport less a 16 px gutter on each side (288 px at 320 CSS px), and its options wrap instead of truncating (code-reviewed; unit-tested width rule). |
| 1.4.11 Non-text Contrast | Supports | Meaningful graphics meet 3:1 in both themes: unread dot 4.53:1, heat-map marks, decision-chip borders, stock Fluent control borders 6.46:1, the catalogue default-star token 4.55 / 9.55:1, state icons 6.46:1, the combobox active-option indicator (2 px theme-primary outline, 4.5:1), the long-label picker's highlighted option (a 3 px theme-primary bar, 4.05:1 on its row's neutralLighter fill in the default theme, and an outline under forced colours; 2026-10-03), PDF-viewer Proposed overlays (2 px dashed #986F0B, 4.55:1 on white) and the 3 px #0078D4 focus ring; the media playhead (themePrimary, 4.5:1 on the lane) and the default mark colour (#d13438, 4.7:1). Media (fixed 2026-09-23): a Proposed mark's dashed border and hatch on the timeline, and its redline outline over video, use #986F0B (4.55:1 on white — the PDF viewer's Proposed colour; the former #e8a33d measured 2.05:1 on the light lane); the side panel's flag icon uses --apWarningText (was 2.05:1); a focused timeline bar gets a 2 px themePrimary ring with a white halo; region grips are white squares with a dark ring and the region chrome a white dashed edge on a dark ring, visible on light and dark frames. Under Windows forced colours (since 2026-09-23 — not a WCAG requirement, recorded here because it is where graphics would otherwise vanish): the playhead, the played underline, the selection and anything being changed use Highlight; bars, density marks, ticks and outlines CanvasText with borders; grips ButtonFace / ButtonText; the region chrome CanvasText dashes on a Canvas ring; the canvas overlay and the waveform paint in the resolved system colours. Code-reviewed 2026-09-23; live forced-colours pass pending. Tenant exemption colours on bars are authored content. 2.5.0 RC (2026-10-07): fixed — a diagram's connectors measured about 2.1–2.5:1 on the dark-theme canvas (light paper now); the done marks in Get started and My training, and the Lab mode band's Help icon on hover (about 1.2:1 in the dark theme), now use the theme's status tokens. 2.6.0 (UI-1 / UI-2, 2026-11-04): every status accent — row border, dot, bar, chart series, the outlined chip's hairline — is ≥ 3:1 on every page surface (light ≥ 3.16:1, dark ≥ 4.17:1, high contrast ≥ 10.4:1), and so is a message tint's text where it serves as a KPI accent or an icon (≥ 6.07:1). The Settings colour swatches are the palette's accents (≥ 3:1 on the panel) with a 2 px brand ring for the chosen one; the Muted swatch is drawn as a ring, like its chip. Computed by statusPalette.contrast.test.ts. |
| 1.4.12 Text Spacing | Supports | Layouts are content-height driven; applying the 1.4.12 spacing overrides expands pills, cards, chips and rows without clipping or overlap (media chips sit on their own wrapping row; the transcript list and the shortcuts table are flow content). |
| 1.4.13 Content on Hover or Focus | Supports | Hover-triggered content routes through Fluent tooltips — hoverable and persistent by design, and dismissable with Escape (runtime-verified). Timeline bars carry tooltips; transcript match state is inline text. Observation: the timeline's scrub-lane hover preview (sprite thumbnail + timecode) is pointer-only and disappears when the pointer leaves the lane; it floats above the lane over the lower edge of the stage (where captions render), never over a control, its timecode duplicates the readout, and since 2026-09-23 Escape dismisses it wherever focus is in the viewer, before any other meaning of the key, without closing the viewer (a11y audit M-24; in full screen the browser takes the first Escape to leave full screen). Some tooltip hosts are non-focusable text spans, so their content appears on pointer hover only; the underlying information remains available through the element's accessible name. The long-label picker's field (2026-10-03) shows the full label and explanation in a Fluent tooltip on hover and on focus; the same full label is the field's value for assistive technology. |
| 2.4.5 Multiple Ways | Supports | Records and views are reachable via persistent tab navigation, a global cross-entity search, notification-feed links, and shareable deep links; a workspace content-search hit opens a recording at the matching spoken moment; site-level navigation is host-provided. |
| 2.4.6 Headings and Labels | Supports | Headings and labels are descriptive and localized; panel titles name the record or task; the media viewer is titled with the recording's file name, its mark bar is named "New mark" for a draft and by the mark's effect and exemption otherwise, and its dialogs are "Edit an approved mark?" / "Scan again?"; timeline bars and side-panel rows are labelled with exemption, span and effect (the effect in the UI language since 2026-09-23); the mark bar's two playhead buttons are named for the field they set, the description lane is labelled "Description", and a release variant's delete confirmation names the variant. |
| 2.4.7 Focus Visible | Supports | Fluent components keep default focus rectangles; class-styled custom interactive rows carry explicit 2 px :focus-visible outlines; PDF-viewer overlay marks carry an explicit 3 px :focus-visible outline; transcript segments, table cells and the timeline slider itself rely on the browser-default indicator (nothing suppresses it). Media (fixed 2026-09-23): a focused timeline bar shows a :focus-visible ring distinct from its selection border (the inline 1 px white outline that replaced the focus ring is gone); the workspace body is no longer an invisible tab stop (tabIndex -1); the timeline slider, the mark bar, the placing bar, the focus row's grips, the region edit chrome and the side-panel row buttons carry explicit :focus-visible rings, in Highlight under forced colours. Diagram editor (fixed 2026-09-25, method 8): a shape or swimlane header that takes keyboard focus draws a dark dashed ring around itself, distinct from the blue selection outline and in the theme's text colour, so it holds its contrast in light and dark themes; until then the only indicator was the selection stroke, which appeared after Enter / Space. |
| 3.1.2 Language of Parts | Partially Supports | Mixed-language content carries lang markup: the web part root is tagged with the active UI language (covering a user-selected language that differs from the host page's declaration — runtime-verified), translated-field display and editing surfaces are tagged with each content's language, letters composed in the requestor's language are tagged with the merge language, language names carry their own lang, and full-page fallback views are tagged; the caption track declares srclang; transcript segments carry the recording's language (lang, since 2026-09-23 — a French recording reviewed in an English UI was read with English rules), and the side panel's effect badge is in the UI language (it was the English enum in every language); the portal inbox's AI clarity questions carry the language they were generated in — the submission's (since 2026-09-23, portal audit PA-24). Gap: a letter submitted for sign-off by a version before the merge language was stored has no language of its own; its preview is marked with the tenant's default language (since 2026-09-25; it was English), which is wrong when that letter was written in another language. 2.5.0 RC (2026-10-07): fixed — panels, dialogs, menus, callouts and tooltips render outside the app's root, so they inherited the SharePoint page's language; every layer now carries the language the app is shown in (the runtime-verified root tagging above covered the root only). A blocking dialog's close button said "Close" in English in every language; the error page carries its language; a statistical template's Title in French boxes are marked French. Fixed 2026-10-13: where the page's culture has no AccessPoint language (Japanese, for example) the app shows English and is now tagged English — its root, every panel and dialog and the error page — and the English spelling options' sample words are marked English. |
| 3.2.3 Consistent Navigation | Supports | Navigation is rendered from single shared components (app shell, panel navigation header, shared catalogue list, WorkItemHeader), so ordering and placement are consistent by construction; the media viewer mirrors the document viewer's header (view-mode tabs, download, Hide / Show panel, close) and reuses its side panel. |
| 3.2.4 Consistent Identification | Supports | Same-function controls are implemented once and reused with centralized localized labels and a documented verb convention; media marks use the same accept / dismiss / flag / withdraw / approve controls as page redactions. |
| 3.3.3 Error Suggestion | Supports | Error messages state the correction (date-range, over-length with limit and count, URL format, timecode format and order, incomplete-row column names); missing required fields are enumerated by name; the bulk data importer returns a downloadable per-row error report; a rejected region track names the server's reason (tracker unavailable, track not ready). |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Destructive operations (bulk delete, retention purge, remove-from-response, withdraw with reason, delete a release variant) require explicit confirmations, and the server independently re-checks purge eligibility; a re-scan that would discard unreviewed proposals asks Replace / Keep both / Cancel; data import is gated behind a reviewable validation report; e-signed attestations present the full signed text and pass through second-party approval; fee payments are recorded via an explicit confirm dialog; response packages can be blocked while unreviewed proposals exist; working-document edits autosave to a draft so nothing is lost on close. |
| 4.1.3 Status Messages | Supports | Save / validation outcomes, toasts, and long-running states announce through a deliberate live-region pattern (285 aria-live regions in the 2.5.0 release candidate) plus MessageBar's native status / alert semantics; every Spinner sets ariaLabel (lint-enforced). Media: "Preparing preview", "Transcribing", "Scanning frames", "Tracking a mark" and hygiene pills are role="status" chips; the viewer's Mark saved / Span updated / Tracking point added / scan-progress notices are MessageBars; the transcript match counter is aria-live="polite"; the timecode readout is deliberately aria-live="off". Since 2026-09-23: with the Descriptions switch on, each description of an imported description track is announced once through a polite live region in the track's language (the region mounts only while the switch is on, so nobody hears descriptions they did not ask for); the mark bar's status line ("Nothing is saved until you choose Save mark", "adjusting it accepts it") is polite; "Transcript ready, n segments" is announced when transcription finishes while the viewer is open; accepting or dismissing a suggestion announces the outcome and how many are left; work still running is an info notice and only a finished job a success notice (a scan or track the viewer stops polling says it is still running instead of announcing a finish); only in-flight row chips are status regions; and the upload queue announces each file's state changes and each quarter of a long upload through one polite line instead of every progress tick. Refinement, not a failure: the global search conveys result availability through combobox state rather than an explicit result-count announcement. 2.5.0 RC static review (2026-10-07): fixed — the training guide's step-done announcements and the Lab mode inactivity warning sat outside the open case panel, which hides the rest of the page from assistive technology; a follow-up verdict, a subject diagram save, Mark complete, the Check diagram result and an AI draft's summary were not announced. Fixed 2026-10-13: the received-date correction's preview (old → new dates, on time or late, the second approval) is announced from a polite region that is in place when the dialog opens; the package update's steps are announced with their names; the Risks tab announces its count once the list is complete; going over the bulk-selection limit, a portal delivery's Copy link (Copied) and saving the assistant history period (Saved and the period) are announced; the Requests register's bulk bar announces its count like the other registers' (found by the runtime pass); the administrator banners are no longer live regions announced on every load. |
Table 2b: the six Level A / AA criteria WCAG 2.2 adds — the whole application (assessed 2026-09-25)
These apply to WCAG 2.2 only. The media viewer was first assessed against them on 2026-09-23 (three failed then and were fixed: 2.4.11, 2.5.7, 2.5.8); the rest of the application on 2026-09-25 (method 8), where 2.5.7 failed on the reorderable lists, the grid's columns, the diagram editor and the PDF viewer's boxes, 2.5.8 on a handful of small buttons and the PDF viewer's grips, and 2.4.11 on the upload tray and one sticky bar — all fixed the same day. Code-reviewed and unit-tested; the runtime re-scan is listed under Known limitations.
| Criterion | Conformance | Remarks and explanations |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) (AA) | Supports | Panels and dialogs are Fluent layers that take focus with them. The floating upload tray (uploads whose case is closed) moves to the other bottom corner when the control that takes focus is under it, and folds to one line when it would cover it in either corner (trayPlacement, unit-tested). Sticky bars: the requestor contact form's Save / Cancel bar sits over a 72 px scroll padding, so a field Tab reaches scrolls clear of it; the report builder's sticky table header sits over cells with nothing focusable; the portal-appearance preview is beside the form, never over it. Toasts are brief (3–6 s), pause while hovered or focused, and at 480 px and below can sit over a panel's footer for those seconds. The busy overlay is 45 % opaque, so focus shows through it. Media viewer: full screen takes the WHOLE viewer, and while it is full screen every new Fluent layer (the approved-edit and re-scan prompts, the region and notes callouts, menus, tooltips) renders inside it; the mark bar is docked between the picture and the control bar, never over them; the placing bar floats at the top of the paused frame, above nothing focusable; below 720 px nothing is clipped off-screen (1.4.10). |
| 2.5.7 Dragging Movements (AA) | Supports | Every drag has a single-pointer alternative that does not drag. Lists reordered by dragging (twenty-one: the settings catalogues and option lists, custom fields and their options, document tags and categories, reporting brackets, dashboard and workspace views, the column-order control, the response package): Move up / Move down buttons on each row (24 px), calling the same reorder as the drag and Alt+Arrow. Request grid columns: the grip in each column header is a button with Move left, Move right, Wider and Narrower. Diagram editor: a shape is added by clicking the palette, connected by Connect from here then a click on the target, moved and resized by the Details pane's X, Y, Width and Height fields; a bend is added by clicking a segment's handle and placed by its X / Y fields; a swimlane is resized by its Height field and moved by Move up / Move down. PDF viewer: a box is drawn by clicking or with Place redaction box; a grip clicked without moving is armed, and the next click on the page puts that corner or side there (two opposite corners move the whole box), Escape cancels. Documents: Move to folder instead of dragging onto a folder; pinned report tiles have Move earlier / later. Media viewer (2026-09-23 / 24): a span by typed In / Out or the two "set to the playhead" buttons in the mark bar, Start / End at the playhead in a mark's menu, or the focus row's grips with the arrow keys; drawing a region by clicking one corner and then the opposite, Use whole frame, Same box as last mark or Use a detected region; moving or resizing a region by the typed left / top / width / height or Grow / Shrink 5 %; a tracking point by Move this point to the playhead; the Shift+drag marquee by Shift / Ctrl-click or Select marks in the in / out range; zooming by the marks area's buttons and slider. 2.5.0 RC (2026-10-07) — diagram editor v4 / v5: the selection box has Shift / Ctrl-click and Shift+Enter / Ctrl+A, and — because a modifier click needs a key, so it is not counted as the single-pointer alternative — since 2026-10-13 a toolbar toggle, Select several, with which a plain click adds a shape to the selection or takes it out (unit-tested); moving a group has the arrow keys and the X / Y fields; a shape added by dropping a connector on empty canvas equals the palette and Connect; alignment guides only assist a drag. |
| 2.5.8 Target Size (Minimum) (AA) | Supports | Buttons are Fluent's (32 px) or at least 24 × 24 since 2026-09-25: the Move up / Move down and grid-column buttons, Manage shared views' move buttons (were 24 × 18, stacked), five 22 px and one 18 px icon buttons, the relevance column's header buttons (22 px), a tag chip's remove × (about 11 × 13; its 24 px target does not grow the chip), and the PDF viewer's eight grips per box (9 px drawn, now 24 px hit areas). Filter rows are at least 24 px. Inline links sit in text (the inline exception). The request grid's 6 px column edge falls under the equivalent exception (Wider / Narrower on the column's grip button). Media viewer: control-bar buttons 32 × 32, the focus row's grips and the region's eight grips 24 × 24 hit areas, Accept / Dismiss 24 × 24, transcript segments at least 24 px high, and the timeline's group toggles (16 px tall) at least 32 px apart since 2026-09-25; the 12 px bars in the marks area and their 10 px trim edges fall under the equivalent exception — every mark is a full-size row in the side panel whose Edit mark… opens it in the mark bar, where selecting, moving and trimming have full-size controls. 2.5.0 RC (2026-10-07): the diagram's add-a-bend handle (8 px drawn) now has a 24 px target. |
| 3.2.6 Consistent Help (A) | Supports | Help is the same button in the same place everywhere it is offered: at the top right, just before Close, on every panel and dialog header (the shared panel navigation, the work-item header, the case panels, the create dialogs) and in the dashboard toolbar; it opens the help page for where the user is. (The notification feed puts its Settings button between Help and Close; the relative order of Help and Close is the same.) The media viewer offers no help of its own. |
| 3.3.7 Redundant Entry (A) | Supports | A request created from a portal submission or an e-mail is pre-filled, including the linked contact; an existing contact is picked rather than typed again; a payment defaults to the balance and a refund to what is not yet refunded. Media: a new mark takes the pending In / Out (or the playhead and five seconds) and keeps its fields while its region is placed; Same box as last mark reuses the last region; Edit mark… shows the mark's own values. |
| 3.3.8 Accessible Authentication (Minimum) (AA) | Not Applicable | Sign-in is the host's: Entra ID through SharePoint or Teams. (The public portal's own sign-in is in Table 3.) The hosted edition (2.6.0) signs in through Microsoft's identity platform too, with no password, code or puzzle of AccessPoint's own — see Hosted edition. |
Accessibility features and known limitations — media records
What the media viewer provides.
- Keyboard playback and navigation: Space / K play-pause; ← → seek 5 s (Shift for 10 s);
,.frame step; J / L slower / faster; Home / End; F full screen (the whole viewer);/focuses find-in-transcript; C toggles captions; D toggles descriptions; 1 / 2 / 3 switch Original / Redline / Redacted preview;[]previous / next mark; = / - / \ zoom the marks area; N snapping; R adjusts the selected region. The shortcuts work while focus is in the player (stage, mark bar, control bar, marks area) and leave Space and Enter to buttons, switches and tabs. A "Keyboard shortcuts" link opens a focus-trapping dialog (Close button, Escape closes only it) with a table of the shortcuts that apply to the user's permissions and view, and a switch that turns the single-key shortcuts off. Esc first hides the timeline's hover preview, wherever focus is in the viewer. - Timeline and the marks area: the scrub lane is an ARIA slider with whole-second
aria-valuetext("0:12 of 3:45") and a density band of the marks. The marks have their own collapsible area under the player (since 2026-09-23 — it replaced the timeline's marks lane): zoom buttons and a slider, lanes (packed, by kind, one row per mark),aria-pressedfilter chips that filter the side-panel list too, each mark a named button ("exemption · span") with a visible focus ring — a focused editable bar moves with Alt+← / → (100 ms) and trims with Alt+Shift+← / → — and a focus row for the selected mark whose start and end grips are slider thumbs (arrow keys one frame, Shift one second, Page Up / Page Down five seconds, Home / End the limits, the timecode as value text). Proposed marks are dashed and hatched in#986F0B; tracking keyframes are pips. - Marks by keyboard — the mark bar: I / O set in / out points (the in / out strip shows them and how to finish); M, B or Mark… starts a draft — on video the placing bar asks for the region (drag, click two corners, or the buttons Use whole frame, Same box as last mark, Use a detected region), then focus moves to the non-modal mark bar under the picture: effect and exemption dropdowns, In / Out fields that accept typed
hh:mm:ss.f(format as tooltip; errors on the field) with two named "set to the playhead" buttons, a Region button with typed left / top / width / height and Grow / Shrink 5 %, notes, Follow subject, Check, and Save mark (Enter) / Discard (Esc). Edit mark… on a mark's row (or a double-click) opens it in the same bar; its status line says what an edit will do. R (or Adjust region with the keyboard) focuses the selected region's edit chrome: arrows move it, Shift+arrows resize it, one save shortly after the last key. Ctrl+Z / Ctrl+Shift+Z undo and redo (and Undo / Redo buttons). - Captions and transcript: native
<track>captions withsrclang(browser / OS caption styling and full-screen retention apply), for everyone who may play the recording (speaker names replaced for a user without the requestor-PII permission); a transcript drawer with speaker and timecode per segment, click / Enter to seek,aria-currenton the playing segment, the recording'slang, find with previous / next and a polite match count, the on-screen text the frame scan read, an on-demand AI summary, and Transcribe / import states. - Audio description (since 2026-09-23): a recording's uploader or a document manager imports a text description track (WebVTT
kind="descriptions") from the recording's details; anyone who may play it turns on Descriptions (a toggle button beside Captions witharia-pressed, or D; remembered per browser) and each description appears in a lane under the picture and is read once through a polite live region in the track's language. Video and audio records alike. - Audio-only records: a waveform lane (
role="img") plus the transcript as the text alternative; the timeline and controls are identical to video. - Status: every processing, transcription, scan, tracking, malware and upload state is a text chip or live region; a "Resume at hh:mm:ss" offer restores a previous session; long uploads pause and resume automatically with pause / resume / cancel controls.
- Redaction review: the shared side panel lists every mark with span, effect, exemption, status, origin, flags, comments and the full action set, all keyboard-operable; accept / dismiss of machine proposals and Preview-with-proposals are one click away and announced, and after each decision focus moves to the next suggestion.
- Reflow: below 720 px the viewer fills the screen and scrolls, the side panel stacks under the player (collapsed at first, and anyone can hide it), and the control bar, the mark bar and the marks area's header wrap.
- Forced colours (since 2026-09-23): under Windows high contrast the timeline, the marks, the grips, the mark bar, the chips and the region chrome take the user's system colours with visible borders (Highlight for the playhead, the selection and anything being changed), and the canvas overlay and the waveform paint in the resolved system colours.
- Voice control: every control is named by its visible label or its tooltip ("click Descriptions", "click Save mark", "click Edit mark", "click Set In to the playhead"); single-key shortcuts can be switched off so dictation does not trigger them.
- Released recordings: redacted captions (
.vtt, and a caption track in the MP4) and a redacted text transcript (.txt) travel with every released recording that has a transcript, and a redacted description track (.descriptions.vtt) with every one that has an imported track; a released MP4 carries every audio track of the original through the same audio redaction (see Generated outputs). A tenant can switch the text files off.
EN 301 549 V3.2.1 clause 7 (video and audio) — assessed 2026-09-23.
| Clause | Media viewer | Released media |
|---|---|---|
| 7.1.1 Captioning playback | Supports — native caption track for everyone who may play a video (speaker names masked without the requestor-PII permission); audio-only records use the transcript drawer | Supports — .vtt beside every released recording with a transcript, and a caption track in the MP4 |
| 7.1.2 Captioning synchronization | Supports — WebVTT cues from the transcript's timing | Supports — the same cues, clipped to the recording's duration |
| 7.1.3 Preservation of captioning | Not applicable to the preview in practice: the preview plays the transcript's captions; a source's embedded caption streams are not carried into the preview | Supports for the product's own captions (redacted); captions embedded in the original are deliberately dropped because they would carry the words of muted spans |
| 7.1.4 Captions characteristics | Supports — native <track>, so browser / OS caption styling applies | Player-dependent (sidecar and mov_text track) |
| 7.1.5 Spoken subtitles | Not applicable | Not applicable |
| 7.2.1 Audio description playback | Partially supports — an imported text description track (WebVTT kind="descriptions") plays through a polite live region and a visible lane, for everyone who may play, video and audio; a described audio track in the original cannot be selected (the preview plays the first audio track). Code-reviewed 2026-09-23; live screen-reader pass pending | Supports — the redacted .descriptions.vtt beside the recording, and every audio track of the original with the described one flagged (visual_impaired, descriptions) for the requester's player to offer |
| 7.2.2 Audio description synchronization | Supports — each description is read at its cue's start from the track's timing | Supports — the same cues, clipped to the recording's duration; a cue under a muted or bleeped span becomes the placeholder |
| 7.2.3 Preservation of audio description | Does not support for a described audio track in the original (not playable in the preview — the release carries it); the imported text description is preserved | Supports — since 2026-09-23 every audio track of an MP4 release goes through the same audio redaction and keeps its described flag (an MP3 release holds one track, the first); the text description travels as .descriptions.vtt |
| 7.3 User controls for captions and audio description | Supports — a Captions button (video) and a Descriptions button (video and audio) at the level of Play, both toggle buttons with aria-pressed, plus C and D. Descriptions code-reviewed 2026-09-23; live screen-reader pass pending | Not applicable (no player) |
Fixed on 2026-09-23 (code; audit IDs in brackets). Captions and transcript for everyone who may play the recording, speaker names masked without the requestor-PII permission, and the captions-token defect that stopped the track loading for anyone [M-01]; redacted captions, caption track and transcript with every released recording [M-02]; reflow at 320 px / 400 % [M-03, M-14]; full screen over the whole viewer with dialogs inside it [M-04]; shortcut scope and Space [M-05, M-34]; keyboard and click-click region geometry, pointer events [M-06]; Edit span… (now Edit mark… in the mark bar) [M-07]; focus indicators [M-08]; Proposed and flag contrast, named flag / lock icons [M-09]; transcript timecode contrast [M-10]; file-name button name [M-11]; readable callouts that close alone [M-12]; distinct Playhead buttons [M-13]; focus and announcement after accept / dismiss [M-15]; transcript lang, localized effect badge [M-16]; media checkbox names and row structure [M-17]; on-screen text in the drawer [M-18, in part]; slider / marks-lane semantics [M-19]; no Captions button on audio [M-20]; whole-second slider value [M-21]; honest progress notices [M-22]; "Transcript ready" announced [M-23]; Escape dismisses the hover preview — from anywhere in the viewer and before any other meaning of the key [M-24]; 24 px transcript segments [M-25]; release-variant grouping, headings and delete title [M-26, M-27]; upload-queue announcements, names and one Pause / Resume button [M-28]; status chips [M-29]; +n badge colours [M-30]; field-level editor errors and format hint [M-31]; one checkbox per Teams-recording row [M-32]; waveform name [M-33].
Added later on 2026-09-23 (code-reviewed; live screen-reader pass pending). A text description track — import, delete, the Descriptions switch and D, a polite live region in the track's language — and a redacted .descriptions.vtt with every released recording that has one (roadmap 14; 1.2.3, 1.2.5; EN 7.2, 7.3) [M-18]; every audio track of an original carried into an MP4 release through the same audio redaction, the described one flagged; Windows forced colours for the timeline, the marks area and its grips, the mark bar, the region chrome, the chips, the canvas overlay and the waveform; a tenant switch for the released caption, transcript and description files (Settings → Feature toggles, default on); the mark bar's In / Out fields now keep a typed time that would end before it starts and say why instead of silently restoring the old value (3.3.1); C and D listed in the shortcuts table for everyone who may play; the media viewer, upload queue and release-decision texts that were still English in nine languages translated, and stripped accents restored (3.1.1).
Corrections to the 2.1.0 report (2026-09-23). The media re-audit found seven claims wrong; each row now says so.
- 2.1.1 — Space did not misfire in portaled dialogs and menus (Fluent layers stop event bubbling); it did misfire on in-viewer items, which ran their own action and toggled playback.
- 2.4.3 / 4.1.2 — the shortcuts callout was not a usable named dialog: focus never entered it (or the details callout), and Escape closed the whole viewer.
- 1.4.3 — the on-frame caption pill measures ≥ 7.0:1, not ≈2.6:1 (roadmap item 8 withdrawn).
- 1.4.10 — the larger failures were the ≈740 px header, the 320 px rail open by default and
overflow: hiddenon the viewer, not only the ≈450 px control bar. - 1.4.3 "Supports" missed the playing transcript segment's timecode (3.77:1).
- 2.5.3 "Supports" missed the file-name button, whose name did not contain the file name.
- Scope — the viewer needs WCAG 2.2 (2.4.11, 2.5.7 and 2.5.8 failed) and EN 301 549 clause 7, which the 2.1.0 report did not cover (now Table 2b and the clause 7 table above).
Known limitations (open).
- Audio description is a text track someone writes and imports: the product does not generate descriptions, and a recording without an imported track has nothing but on-screen text to describe its visual content (1.2.3, 1.2.5) [M-18]. The preview plays only an original's first audio track, so a described audio track can be released but not played or reviewed in the viewer (the browser exposes no audio-track selection); the reviewer checks the other tracks in a desktop player before release (User Guide).
- Captions are speech-recognition output unless a Teams or imported transcript exists; the product does not verify their accuracy (1.2.2).
- A region mark (a box, blur or pixelation) does not change the description track — only muted, bleeped and withheld spans do — so a description naming what a region hides must be corrected and re-imported before release. (Released captions of a voice-disguised passage keep its words behind
[voice disguised], since the words stay audible — a deaf requester gets what a hearing one hears.) - (Closed 2026-09-25.)
[/]now move focus to the mark they select, so Alt+Arrow or Enter acts on it next (2.4.3; roadmap item 1). - The scrub-lane hover preview can still cover the bottom of the picture, where captions render, while the pointer rests on the timeline; Escape now dismisses it from anywhere in the viewer (1.4.13 observation) [M-24 fixed].
- Windows forced colours / high contrast are supported in code since 2026-09-23 but have not been checked with a real high-contrast theme (the canvas overlay and the waveform paint system colours they resolve at run time).
- An MP3 (audio-only) release carries the first audio track only — the format holds one.
Needs a manual assistive-technology and runtime test. The automated NVDA pass of 2026-09-25 (method 7) covered the Tab walk through the viewer, the timeline slider, a filter chip and Escape, and the 320 px pass (method 6) the viewer's reflow at 320 CSS px; the rest of the list is still open.
- NVDA + Chrome, JAWS + Edge, Narrator + Edge, VoiceOver + Safari: the scrub-lane slider and the marks area (lanes, filter chips, the focus row's grip sliders); whether a focused slider is re-announced during playback (whole-second value text); spoken feedback for Alt+Arrow ("Span updated"), for the grips and for R region adjustment (the polite geometry readout); the mark bar's status line and field errors; the focus-trapping callouts under the viewer's
aria-modal, especially with VoiceOver; the "Suggestion accepted, n left" announcement and focus landing on the next suggestion; "Transcript ready" while the viewer is open. - Audio description: with each screen reader, turn Descriptions on during playback and while paused — each description must be read once, in the track's language, without interrupting the reader's own speech, and the switch's pressed state must be announced; a description already under the playhead when the switch is turned on; seeking into and out of a long description; import and delete from the details callout.
- Caption rendering: OS caption styles (Windows Settings → Captions; macOS) in Chrome, Edge and Firefox; captions in full screen (now the whole viewer); the masked track for a user without the requestor-PII permission; where captions fall relative to Redacted-preview regions, the hover preview and the descriptions lane.
- The released files: the MP4's soft caption track in VLC, Windows Media Player / Films & TV and QuickTime (language, on / off); the
.vttpicked up beside the file; the.txtand the.descriptions.vttread by a screen reader; an original with two audio tracks (one described) released as MP4 — both tracks present in VLC's audio-track menu, the described one flagged, the same spans muted or bleeped on each (ffprobe the dispositions). - Shortcut conflicts: letter shortcuts (including D, B, N, = - \) against screen-reader browse-mode quick keys with the single-key switch on and off; Space in NVDA focus mode on the slider.
- Full screen + keyboard: F, then M, Tab and Escape — the mark bar must be visible and focused inside full screen.
- 320 px / 400 % and 200 % zoom (1366 px laptop): header, stacked rail, wrapped control bar, the mark bar with its region fields, the marks area and the descriptions lane, and 320 × 256.
- Touch and pen: two-corner drawing and moving a region; the timeline scrub; the grips.
- Voice control (Dragon, Windows Voice Access): "click <file name>", "click Set In to the playhead", "click Edit mark", "click Save mark", "click Descriptions".
- Windows forced colours / High Contrast (Aquatic, Desert, Dusk, Night sky) and the Edge DevTools
forced-colors: activeemulation: the playhead and played underline, mark bars and the density band, the focus row and its grips, the region chrome and the Redline overlay, the waveform, the chips, the mark bar and the descriptions lane (limitation 6). - Escape order: with the hover preview showing and focus in the mark bar, the details callout's trigger or the transcript, the first Escape must only hide the preview.
DPIA validation surfaces — WCAG 2.2 AA (2.5.0, code-reviewed 2026-10-05)
Scope. The surfaces DPIA validation adds to the web part in 2.5.0: the assessment's Validation tab (the opinion cards, the decision card, Ready to approve?) and its dialogs (request, record, record on someone's behalf, not sought, the response, the decision, resubmit); section evaluation (the chips on sections and questions, the Evaluate dialog, the rework banner, the reviewer's summary on the Review tab, Send back); the Regulator consultation card on the Closure tab and its dialogs; the risk map and risk overview on the Risks tab; the screener's screening-list question; Settings → Screening lists; and the JSON configuration fields of assessment types and templates. User Guide §10 Validating a DPIA.
How it was evaluated. A code review against WCAG 2.2 Level A and AA on 2026-10-05 of the 2.5.0 batch, checking the
obligations the DPIA validation contract sets (§13.4) and the Jest suites that assert them (validationTab,
opinionDialogs, decisionDialog, sectionEvaluation, regulatorConsultationCard, riskMap, riskOverview,
screenerList, screeningListsPanel, configJson). These surfaces have not had a runtime axe scan, a 320 px reflow
pass or a screen-reader pass yet (listed at the end of this section); Tables 1, 2 and 2b above predate them.
| Criteria | Conformance Level | Remarks |
|---|---|---|
| 1.1.1 Non-text Content (A) | Supports | Every chip pairs its icon (hidden from assistive technology) with its text (ValidationChip); the risk markers inside a map cell are hidden, the cell's name spells them out; the risk overview diagram opens read-only with a Text version (its swimlanes, shapes and connectors as lists) as the text alternative — corrected 2026-10-07: until then it had no List view in read-only mode and no text alternative. |
| 1.3.1 Info and Relationships (A) | Supports | The two risk maps are role="grid" with row and column headers, labelled by their title and described by the keyboard instructions; the Risk / Before / After / Change table (with a caption) carries the same content. In the PDFs (the CNIL PIA report, and any summary or assessment PDF whose risk matrix asks for the map) each map is a table with a caption naming the side and its axes, scoped column (likelihood) and row (severity) headers and the level and risk markers as cell text, followed by the same Risk / Before / After / Change table; the CNIL report's headings run h1 → h2 → h3 and its fact tables use row headers. The decision's attestations are real checkboxes in a fieldset / legend; outcomes, positions, reasons, grounds and ratings are labelled radio groups; each condition, action and recommendation row is a named group; the screening-list question is a fieldset whose legend is the list's title, its entries wrapped, never truncated, each detail a disclosure. |
| 1.4.1 Use of Color (A) | Supports | Opinion, decision, evaluation and consultation states are chips with text and an icon; a map cell's level is in its name (severity, likelihood, level, count, risks) and in the table, the colour only repeats it; blockers are text links. |
| 1.4.11 Non-text Contrast (AA) | Supports | Markers are white chips with a neutralPrimary border; the cell colours use the shared status palette measured for Table 2 and carry no information the cell name and the table do not. Not yet measured at runtime on these surfaces. |
| 2.1.1 Keyboard (A) | Supports | Every action is a Fluent button or link. Each map grid is one tab stop with roving focus: the arrow keys move between cells, Home and End along a row, Enter or Space lists the cell's risks in a dialog that takes focus. Use another authority's list uses the shared keyboard-operable picker (LongLabelPicker). |
| 2.4.3 Focus Order (A) | Supports | The dialogs share one frame (ValidationFormDialog, a blocking Fluent dialog) that traps focus and returns it to the control that opened it; they render inside the assessment panel, so closing one never closes the panel. The map's risk list returns focus to its cell. |
| 2.4.6 Headings and Labels (AA) | Supports | Cards and dialogs are titled with the step, decision or consultation they record (Request: …, Record the decision, Evaluate: …); every field has a visible label. |
| 2.5.3 Label in Name (A) | Supports | Accessible names start with the visible label (Evaluate is named Evaluate {section}). |
| 2.5.8 Target Size (Minimum) (AA) | Supports | Map cells are buttons of at least 48 × 48 px and their markers 24 × 24 px; the remaining controls are Fluent buttons (32 px) or icon buttons of the same size. |
| 3.2.6 Consistent Help (A) | Supports | Help is the panel header's Help button (the Validation tab opens assessment-validation); the consultation card, the evaluation dialog and the risk map carry the same Help button where the shared header is not in view. |
| 3.3.1 Error Identification (A) | Supports | A refused save names the problem in text in the dialog, and an approval refusal lists its blockers, each linked to where it is fixed; every refusal code has its localized message. A configuration field shows the JSON parse error before saving. |
| 3.3.2 Labels or Instructions (A) | Supports | Instructions sit with the fields: who can be asked, the signed document needed on someone's behalf, describe groups, never name individuals, an aggregated summary rather than raw responses, the criteria threshold of a list, an exemption applies only when no mandatory criterion is met, why the decision is unavailable to the current user. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Supports | The decision commits the organization: every attestation must be ticked, reasons are required where they are, the dialog lists what is missing before it records; Abandon states that it closes the assessment. Records are create-once — a correction is a new record and the earlier one stays listed. |
| 3.3.7 Redundant Entry (A) | Supports | Request changes is prefilled from the reviewer's evaluations and Send back copies them into the instructions; documents are picked from the assessment's own documents rather than uploaded again. |
| 4.1.2 Name, Role, Value (A) | Supports | Fluent controls expose their roles and states; map cells are named buttons with aria-haspopup when they hold risks; icon buttons carry names. |
| 4.1.3 Status Messages (AA) | Supports | Ready to approve? is a polite live region, so blockers appearing or clearing are announced without moving focus. |
Needs a runtime or assistive-technology test (none has been run on these surfaces).
- NVDA + Chrome on the two risk-map grids (grid navigation, the cell names, the risk list and focus returning to its cell) and on the decision dialog (the outcome and next-step groups, the attestation fieldset, the condition rows, a refusal's blockers) — the DPIA validation contract's DV-12 obligation.
- An axe scan, a 320 CSS px reflow pass (the two maps side by side wrap to one column) and 200 % zoom on the Validation tab, the consultation card, the evaluation dialog and the Risks tab.
- The PDF/UA checker and an NVDA read of a generated CNIL PIA report (the map tables' headers and captions, the reading order of part 4); like the other assessment summaries it is converted by the document worker and has not been measured.
- Windows forced colours: a map cell's level colour is a background, so under forced colours the level is carried by the cell's name and the table only.
Public intake portal — WCAG 2.1 AA and WCAG 2.2 AA (self-assessed 2026-09-15; audit fixes 2026-09-23)
The public intake portal (AccessPoint.Portal) is the one surface a member of the public uses: a separate, internet-facing web app with server-rendered HTML, one page script and no inline script or style (the Content Security Policy forbids both). The portal is first published in 2.5.0. This section covers it as assessed on its pre-release code on 2026-09-15, updated on 2026-09-23 with the fixes for the second portal audit (see Portal accessibility audit (2026-09-23) below) and with the changes made before release (see Changes before release (2.5.0)): the landing page, the intake form (standalone and embedded, single-page or step by step), the emailed-code step, the receipt, request tracking and See all your requests, secure delivery with its accessibility statement, the reading room, the pay and pay-return pages, the unavailable and not-found states, the error page, the session time-limit notices, and the embed widget (inline and pop-up). The requester e-mails the portal causes are reported under Generated outputs. Form labels, help, options and a tenant's appearance overrides are authored content; the product's defaults and mechanisms are what is assessed.
Why WCAG 2.2 for the portal. WCAG 2.1 AA is the level the portal's public-sector customers are most often held to (for example the US ADA Title II web rule and the EU Web Accessibility Directive through EN 301 549 V3.2.1), Québec's SGQRI 008 3.0 already adds selected WCAG 2.2 criteria, and EN 301 549 V4.1.1 (published September 2026, not yet cited as the legal reference) adopts WCAG 2.2. The portal is therefore assessed against the six WCAG 2.2 Level A / AA additions as well; they are marked (WCAG 2.2) in Table 3.
How the portal was evaluated
- Static review of every Razor page,
portal.js,portal.css, the widget script, the eleven string bundles and the requester mail renderer. - Rendered markup from the in-process test host that
tests/AccessPoint.Portal.Testsuses, with a form exercising every field type, fallback-language text and a French page.AccessibilityMarkupTestspins what can be read from the HTML and stylesheet: autocomplete purposes, the checkbox-group fieldset, id and label / description reference integrity, language of parts, the script's error and status hooks, the language menu, the default colour contrast in both themes (recomputed fromportal.css) and the narrow-screen layout rule — and, after the open items below were closed, the form'sh1outside the steps,aria-requiredon a required file field, the time limits rendered from the deployment settings with placeholders (not numbers) in all eleven bundles, the forced dark palette equal to the dark palette, the markers a language change replaces, and the frame messages (a named target origin; origin and source checks in the widget).HttpTestsandServiceTestscover the error pages, the session timing and extension endpoints, and the required-attachment enforcement. - Runtime pass in a headless browser against that host served locally with in-memory data (no tenant, no mail sent): axe-core 4.13 (WCAG 2.0–2.2 A / AA and best-practice rules) on nine pages in both light and dark colour schemes, and on the receipt, case, delivery and pay views after verification; scripted keyboard and focus checks through every flow (empty and invalid submits, the error summary and its links, file removal, resend, a pasted code with spaces and a dash, verification, receipt, case / delivery / pay views, acknowledgement, and expired-session paths); accessible names, descriptions and states read from the browser's accessibility tree; reflow at 320 CSS px; the WCAG 1.4.12 text-spacing overrides at 320 and 1280 px; measured target sizes; and the widget on a second origin, inline (Tab into and out of the frame, frame resizing) and as a pop-up (inert page, localized labels, Escape). A second pass the same day, after the open items were closed (same host; 30-, 2- and 1-minute sessions): the session warning, Stay signed in, a download sliding the session, the end, Start again and a language change while ended (also at 320 px, in French); the required-attachment flow (no file, an active-content file refused, a retry that reuses the submission, the code sent after the upload); a language change on the code step (partly typed code kept) and on the receipt; a French request view (status label tagging, letter purpose); a lock after five wrong codes; the error page (unknown address, with
?lang=fr, requested directly); Escape inside the pop-up frame, a forged close message from the host page, and Escape in an inline frame; the forced dark theme in a light-preferring browser, standalone and in both embeds (screenshots reviewed); axe on ten pages in both colour schemes and in the forced dark theme, on the French receipt and request view, and on both session notices — no violations. - Contrast computed from the stylesheet values with the WCAG relative-luminance formula.
Not performed: live screen-reader sessions (NVDA, JAWS, VoiceOver, TalkBack), Firefox, Safari and mobile browsers, Windows forced-colours mode, real-device zoom, and a browser pass on a deployed portal (the local build carried the changes below; the dev deployment did not yet).
Fixed during this assessment (2026-09-15)
- Focus indicator (1.4.11, 2.4.7): the 3 px
#ffbf47outline measured 1.64:1 against the white page. Focus is now a two-colour ring — the outline plus a 2 px#0b0c0cinner ring, 11.9:1 apart, so one of the two always has 3:1 against whatever it touches (technique C40). - Control boundaries and placeholders (1.4.11, 1.4.3): input, select and textarea borders measured 1.54:1 (light) and 1.84:1 (dark); they now use
--ap-control-borderat 4.55:1 and 6.0:1. Placeholder text uses the muted token; the browser's own placeholder grey measured 4.0:1 on the dark background. - Multiple-choice fields (1.3.1, 3.3.2, 4.1.2): the checkbox group was named by its own option text, its visible label pointed at a non-labellable element, and its help and error were not associated. It is now a
fieldsetwhoselegendis the label (with "required" written out for assistive technology) and whosearia-describedbycarries the help and error. Ids are no longer built from option values (which may contain spaces) or from field ids that could collide with help ids. - Input purpose (1.3.5): fields mapped to the requester's name, given name, family name, organization and preferred language had no
autocompletetoken; they now carryname,given-name,family-name,organizationandlanguage. A field about someone else carries none. - Language of parts (3.1.2): form text shown in a fallback language (for example an English-only label on a French page) is tagged with
lang; the widget's frame title and Close button follow the host page's language. - Errors (3.3.1, 3.3.3): a submit with problems moves focus to an error summary that lists each problem as a link to its field; a corrected field's error is emptied (screen readers otherwise kept reading the old error through
aria-describedby); minimum length and date limits are stated; the tracking, delivery and pay lookups no longer ignore an empty or mistyped submit; attachments that failed to upload are reported on the code step (the message used to be hidden together with the form); an expired session is reported as such (it read "records no longer available" or "payment not available"); a failed receipt confirmation is reported. - Focus (2.4.3): The browser moves focus to the page when a focused button is disabled, so Submit, Resend, Download, Acknowledge and Pay now mark a busy or finished state with
aria-disabled; removing an attached file moves focus to the neighbouring Remove button or the file picker; a view that fails to load still takes focus. - Status messages (4.1.3): "Sending your request…" and upload progress are announced (the live region used to start hidden); "A new code has been sent" is shown as well as announced; removing a file is announced; duplicate announcements were removed.
- Code entry (3.3.8, 1.3.1): a pasted code with spaces or a dash is accepted (the field cut it at 9 characters); the step's instructions (on the intake form, the masked address and the code's lifetime) are the field's description, read when focus arrives.
- Reflow (1.4.10): a duplicated description-list rule overrode the single-column layout below 480 px.
- Other: page titles follow the step ("Check your email", "Your request has been received"); the verify step's heading reads "Check your email" on every surface; the language menu keeps the rest of the address (it dropped, among others, the pay-return session); the pop-up widget makes the host page inert while it is open (2.4.3, 2.4.11).
Open items closed later the same day (2026-09-15)
- Session time limit (2.2.1): a verified session (30 minutes without activity, 8 hours at most — deployment settings) now warns before it ends. Three minutes ahead (half the session when a deployment sets one shorter than six minutes) a notice appears above the details with focus on Stay signed in, whose description is the message with the end time. It extends the session through
POST /api/session/extend— the guard header and the status rate limit like every other call, only the cookie's own session, never past the 8-hour cap; within the last window the warning says the session cannot be extended again. Every call that uses a session reports the time left in a response header, and before it warns or ends the page asksGET /api/session, which never slides the session, so an open page cannot keep itself signed in and a session extended in another tab is not ended here. When the session ends, the verified details are hidden and focus moves to Start again, which returns to the lookup with the reference and address the requester typed (kept in the page's memory only). The code lifetime and the lock after five wrong codes are no longer written into the strings: they come from the deployment settings, worded with each language's own number grammar. - Error pages (2.4.2, 3.1.1, 3.3.1): an address no page matches and an unhandled error on a page are answered with the portal's localized error page ("Page not found" or "Something went wrong", with a title, an
h1and a link home), keeping the 404 or 500 status, the security headers and the failed address's own?lang=. It renders even when the settings store is what failed and never shows exception detail. The JSON API, the health check and the widget files keep their own responses; an unhandled API error answers{"error":"ServerError"}. - Headings (1.3.1, 2.4.6): the form's
h1sits outside the steps, so the code and receipt steps keep it above theirh2. - Pop-up Escape (2.1.1, 2.1.2): Escape pressed inside the embedded frame closes the pop-up and returns focus to the opener. The frame posts
{type:'ap:close'}to the host page's origin only; the widget accepts it only from the portal origin and its own frame's window, so a message posted by the host page itself is ignored (runtime-verified). The Close button now draws its own colours: it inherited the host page's black text and sat over the frame's dark canvas when the form was dark (1.4.3, 1.4.11). - Language change after sending (3.1.1): on the code step, the receipt, a verified view and the ended-session notice, the language menu fetches the page in the new language and replaces its text in place. The step, a partly typed code, the submission being confirmed and the session survive; focus returns to the step and the address bar follows. Nothing is written to browser storage. This was chosen over hiding the menu on those steps: the requester keeps the choice of language on every step, and no verification data leaves the page's memory.
- Required file fields (3.3.1, 3.3.2): the asterisk is enforced. The page refuses to send without a file (the summary names the field; the file input carries
aria-required); the server sends the e-mailed code for a form with a visible required file field only once a completed file has arrived, and refuses verification without one before the code is checked. A required attachment that fails or is refused keeps the requester on the form with the file named in its field's error, and pressing Send request again uploads into the same submission (no second reference or code); an optional attachment that fails is still reported on the code step. Uploads continue past a failed file, and the per-file calls moved to the upload rate limit: under the intake limit the third attachment of a request was refused. - Forced dark theme (1.4.3, 1.4.11): an appearance
themeofdarknow applies the same dark palette as a browser dark preference (a test pins the two value sets together) and is rendered by the server, so it applies before the script runs;color-schemefollows a forced theme. - Language of parts (3.1.2): a status label shown in English because the tenant has no translation for the page language is tagged
lang="en"; a shared letter's correspondence purpose is shown in the page language ("Réponse finale") instead of its code; a letter subject is tagged when the projection gives its language. - Language of letter subjects and delivery titles (3.1.2): a communication now records the language a letter was composed in (the correspondence composer, including a letter held for sign-off, and Generate letter send it;
RequestorCommunications.LanguageCode), and the request projection carries it, so a shared letter's subject is tagged on a page in another language. A delivery title staff give is recorded with the tenant's base content language (portal.Deliveries.TitleLanguage, the default language's primary subtag), in which staff write titles by convention, and tagged the same way. A delivery created without a title no longer stores the English "Records for …": the request and delivery views show the portal's own title in the page language ("Documents relatifs à A-2026-000123"), and the delivery view is now asked for in the page's language like the request view. (The staff app's Deliver dialog always sends a title — the export name it pre-fills unless staff type another — so an untitled delivery comes from an API call.) Covered by server, service and page-script tests; not part of the browser passes above. - Required file fields, each on its own (3.3.1): each uploaded file records the file field it was attached to (
portal.SubmissionFiles.FieldId; the upload call refuses a field that is not a file field of the form), and the server sends the code for, and confirms, a request only when every visible required file field holds a completed file of its own — two files attached to one field no longer satisfy two required fields. A submission holding a file uploaded by a page loaded before this change (which sends no field) is still checked by counting files, so nothing in flight is refused. Covered by service and HTTP tests; not part of the browser passes above. - Other: verified views set the page title ("Check a request", "Your records", "Pay a fee"); the request view and the pay session send the page's language to the API instead of relying on the language cookie, which a browser blocking third-party cookies does not keep in an embed.
Portal accessibility audit (2026-09-23) — what was fixed, and what still needs a live test
A second audit against WCAG 2.2 AA (static review, read-only requests to the dev portal, the shipped page scripts run in jsdom, headless Chrome at 320 px) found 27 new items — 7 Medium, 20 Low (PA-01 to PA-27) — and two wrong rows in Table 3 (1.3.2 and 2.4.3, corrected below). The fixes were verified by running the page scripts in jsdom against pages rendered by the portal's own test host (focus, announcements, titles, aria-* state after each action) and are pinned by PortalAccessibilityAuditTests, AccessibilityMarkupTests and GuidedIntakeRenderingTests; none has yet been checked with a live screen reader, in forced colours or on iOS (see the last list).
Fixed (Medium):
- PA-01 / PA-08 — language change on the single-page form and the ended-session notice (2.4.3, 4.1.3, 2.4.2, 3.1.1). The swap replaced the header holding the focused language link, so focus fell to the page and nothing was said. Now: a step the script draws again takes focus (the code field, the receipt, a view, a step heading, and — new — Start again on the ended or signed-out notice, read in the new language); otherwise focus goes to the same language link in the new header (or the page
h1) and "This page is now in English." is announced once, in the new language. The page<title>follows the language. - PA-02 — "Add detail", a fee answer or a withdrawal lost focus and its confirmation (2.4.3, 4.1.3). The panels are drawn once per view; after a send only "Messages you have sent" is drawn again. The confirmation sits above the panel's form, takes focus and stays; the form empties for another message (a withdrawal's form goes, since it is sent once). A reply no longer inserts a second panel and a second clarity aside with a duplicate id.
- PA-03 — file fields said nothing about what they accept (3.3.2, 3.3.3). Under every picker, rendered by the server from the tenant's settings (the same values the upload path enforces): the accepted types, the per-file and all-files caps and how many files the picker takes — "Accepted file types: PDF, DOCX, … Each file can be up to 100 MB, and all files together up to 500 MB. You can attach up to 10 files." — in its
aria-describedby, on the form and the case page's message panel alike. The refusal names the number ("You can attach at most 3 files here."). - PA-04 — time-period errors pointed at the first radio (3.3.1, 1.3.1, 2.4.3). The error is marked on, and the summary link focuses, the control that is wrong: the Year box, or the month or year of the span that is missing or not four digits (the From year for a period that is too early, the To month for an end before the start). Every nested box carries the field's error in
aria-describedby; no radio is marked invalid. A year or a half-typed span now says what the box needs ("Enter a year between 2000 and 2026.", "Enter both the month and the year."). - PA-05 — long names and references scrolled the page sideways at 320 px (1.4.10). Text in a card wraps (
overflow-wrap), and names in flex rows (attached files, delivery files, letters, references, message files) shrink withmin-width: 0; overflow-wrap: anywhere. Not yet re-measured in a browser at 320 px. - PA-06 — the payment provider's page was undocumented (conformance requirement 3, complete processes). The provider's hosted page is outside AccessPoint:
docs/payments/README.md→ Accessibility of the provider's page says what AccessPoint does (the amount on the Pay button, the page language passed where the provider takes one, the return page) and lists what the tenant must check with its provider — its ACR / VPAT for the hosted page, keyboard and screen reader, language, time limits, zoom and forced colours, authentication challenges and the return trip. The pay page now says on every step that there are other ways to pay, with the tenant's Help address when set. - PA-07 — closing the pop-up discarded unsent answers without warning (3.3.4). The frame tells the host page only whether the form holds anything not yet sent or confirmed (
{type:'ap:dirty', value}— never the answers). Closing it then (×, Escape in the host page or inside the frame) opens a small dialog of the widget's own (role="alertdialog", notwindow.confirm) in the host page's language, whose default and Escape keep the form; the frame and × are inert meanwhile.
Fixed (Low): PA-09 the error summary is a group named by an h2 ("There is a problem") and the title reads "Error: …" while it shows · PA-10 a checkbox group's error is on the group (its fieldset's description, a bar beside it), never aria-invalid on option 1 · PA-11 the fee answer's radios and the withdrawal's confirmation box carry the error in their descriptions and the failing one is aria-invalid; the withdrawal reason is marked required · PA-12 the time-period read-back is a status message and part of the group's description (kept in the tree while empty; written only when it changes) · PA-13 a half-typed date says "Enter the full date: day, month and year." instead of a YYYY-MM-DD the browser does not show · PA-14 no maxlength cuts a paste short: the limit is checked on Send and the error states it and the count typed; an author's limit is stated under the field · PA-15 a count of the attached files is part of the picker's description · PA-16 the message panel's picker has an error of its own · PA-18 the widget titles the frame by the form's kind ("Complaint form", "Privacy concern report"), and the Settings snippet carries data-ap-kind · PA-19 the embedded footer draws its own surface, so its links keep their contrast on any host background · PA-20 the error summary, the plain form message, the code step and the receipt ask an embedding host to scroll to them (ap:scroll) · PA-21 landing cards never exceed the column (minmax(min(16rem, 100%), 1fr)) · PA-22 the reading-room searches take the theme's 16 px, 44 px control · PA-23 "Receipt confirmed on {date}" is a success line that takes focus, not the label of a dimmed disabled button · PA-25 the landing reference lookup checks itself like the other lookups, in the page's language · PA-26 the honeypot is named so no autofill vocabulary matches it and carries the password managers' ignore flags · PA-27 year boxes are type="text" inputmode="numeric", not type="number".
Closed later the same day (2026-09-23): the three items first left open, and one from the media audit. Server and page-script tests only (DeliveryAccessTests, ClarityTests, SubmissionServiceTests, PortalAccessibilityAuditTests, the API's PortalClarityTests, the web part's PortalClarityAskedCard test); not yet in a browser.
- PA-17 — the delivery page asked for the address again right after a request-page verification (3.3.7). A verified request session (or See all your requests) now opens the records released on that request: Open under Records for you shows the files, with no address and no second code. The server checks, on every call, that the delivery belongs to that request and was sent to the address that verified; a delivery sent to anyone else (a representative), another request's delivery — even the same person's — and a delivery link opened with no session still ask for the delivery's own code, and a delivery session still opens that one delivery only. The design and why it was chosen over sending a code in one click or minting a delivery session:
docs/ShippedFeatures.md→ Portal audit follow-ups. - PA-24 — the AI clarity questions carried no language (3.1.2). They are now asked for in the language the requester used the form in and stored with it; on a page read in another language each question carries that
lang(the "(AI suggestion)" label beside it stays in the page language), and the staff inbox tags them the same way. Questions written before the change have no recorded language and stay untagged. - PA-26, the server half — a filled honeypot refused the request (3.3.8, 3.3.1). Something in the hidden field now makes the server ask for the proof of work instead, and the page solves it (the same invisible check as the Altcha setting, whatever the tenant's setting), so a person whose autofill or voice-control tool filled the field can still send the request. A bot that fills the field and does not solve the challenge is refused as before; the submission records that the check was asked for.
- Media audit — the delivery page did not say what the files are (1.1.1, 3.3.2 advisory). Under the file list, About these files says, for the kinds that delivery holds only, how to open them: PDFs; ZIP files; recordings as MP4 (H.264/AAC) or MP3, which play in common players such as VLC, Windows Media Player and QuickTime; and a captions file (
.vtt) and plain-text transcript (.txt) with a recording's name, which most players load automatically. In all eleven languages, worded after the export's delivery note.
The advisories (static role="alert" cards, the program-area "Not sure" behaviour, a half-written reply lost when a session ends, the embedded frame's language, the remaining focus-plus-announce pairs) are unchanged.
Needs a live test before any of the above is claimed beyond jsdom and the stylesheet (suite POR-A11Y, docs/FunctionalTestPlaybook.md; publish a QA-FT- form first):
- NVDA + Firefox and JAWS + Chrome: the language change on the single-page form (focus on the link, the announcement, no double reading) and on the ended notice; the error summary read on focus (group name, heading, list); the Year box and span boxes read with their error; the fee radios and the withdrawal box read with theirs; the confirmation after Add detail / fee / withdrawal read once; the time-period read-back announced without chattiness.
- VoiceOver + Safari on macOS and iOS, embedded:
ap:scrollbringing the error summary, the code step and the receipt into view; the pop-up's confirm dialog (focus, Escape, inert frame) and its return of focus. - TalkBack + Chrome: the file picker's count and limits after choosing files; the date message.
- Windows forced colours: the group error bar, the confirm dialog's buttons and border, the embedded footer, the success lines.
- Headless or real browser at 320 px and 400 %: long file names, references and message file lines (PA-05), the landing cards (PA-21), the search fields (PA-22).
- The payment provider pages, per
docs/payments/README.md— the tenant's to run with its provider. - The items closed later on 2026-09-23: Open under Records for you right after verifying on the request page (the files show with no address step, focus lands on the view, the session clock and sign-out work, the request page still opens afterwards) and the same delivery from its e-mailed link in a fresh browser (the address step); a French request's AI clarity questions read on an English page with NVDA and VoiceOver (French rules for the question, English for the label); the hidden field filled by Chrome, Edge and Safari autofill, 1Password, Bitwarden and a voice-control form fill, and the request still sent; About these files read on a delivery with a PDF, a video, its captions and transcript.
Changes before release (2.5.0)
Made after the audit and before the portal was first published; covered by the portal's server and page-script tests, not yet in a browser pass.
- The step layout never sends by surprise (3.2.2, 3.3.4). On a step-by-step form the Send request button showed on every step (a stylesheet rule overrode the
hiddenattribute), and Enter in a field on a step sent the whole form. Send request now shows only on the last step, and Enter in a field means that step's Continue. - No required question with nothing to choose (3.3.2, 3.3.1). A question that offers no options — program areas the organization does not show, a request-type question with nothing to pick — is hidden and never required, on the page and on the server; a program-area question cannot be marked required, because Not sure always answers it.
- Time-period read-back (3.3.3). The last 12 months or 2 years read back the right dates across 29 February.
- Reading room datasets (1.1.1, 2.4.4). A publication that released spreadsheets lists each one by name and size and says what it is — a spreadsheet of the record's values, or CSV files in a ZIP — in the page's language.
- The accessibility statement (accessible releases). The delivery page says what the package's accessibility check found and how to ask for another format; the reading room says the same to the public (see Generated outputs).
Table 3: Public portal — WCAG 2.1 Level A and AA, and the WCAG 2.2 additions
| Level | Supports | Partially Supports | Does Not Support | Not Applicable |
|---|---|---|---|---|
| WCAG 2.1 A (30 criteria) | 24 | 0 | 0 | 6 |
| WCAG 2.1 AA (20 criteria) | 16 | 1 | 0 | 3 |
| WCAG 2.2 additions (2 A, 4 AA) | 5 | 0 | 0 | 1 |
Complete processes (conformance requirement 3). Paying a fee continues on the payment provider's hosted page (Stripe Checkout, Paymentus, a generic hosted page). That page is the provider's and is not assessed here; AccessPoint records no provider's conformance. The tenant checks its provider's page before turning electronic payments on (docs/payments/README.md → Accessibility of the provider's page), and the pay page names another way to pay on every step (since 2026-09-23).
| Criterion | Conformance | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content (A) | Supports | The portal draws no images of its own. A tenant's optional logo (2026-09-17) is decorative — alt="" — because the institution's name follows it in the header as text. The pop-up's "×" button has a localized accessible name; decorative separators are hidden from assistive technology; the honeypot field is aria-hidden and out of the tab order. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (A) | Not Applicable | No time-based media is presented; released recordings are downloads (see Generated outputs). |
| 1.2.2 Captions (Prerecorded) (A) | Not Applicable | As 1.2.1. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (A) | Not Applicable | As 1.2.1. |
| 1.3.1 Info and Relationships (A) | Supports | Banner, navigation, main and contentinfo landmarks; one h1 per page with h2 steps; form sections and checkbox groups are fieldset / legend; every control has a <label for>; help and errors are associated through aria-describedby; required fields carry aria-required (groups spell it out); key / value data uses dl; lists are lists. Id and reference integrity is pinned by tests. The form's h1 stays visible on the code and receipt steps (since 2026-09-15; it used to be hidden with the form). Guided intake (2026-09-22): the time period is a radio fieldset whose month-and-year spans are labelled fieldsets of a month <select> and a year <input type=number> (no calendar widget); a worked example is a role="group" named Example with visible Less specific / More specific labels; the completeness checklist is a list whose marks carry visually hidden Given / Not given text; the step list is an ol with aria-current="step"; check-your-answers is a dl per step; the review's and the checklist's Change links are named Change {field}. Since 2026-09-23 (audit PA-04, PA-09, PA-10, PA-12, PA-15): the error summary is a group named by its h2; a checkbox group's error belongs to the group (its fieldset's description), not to its first option; each Year and month box of a time period is described by the field's error, and the resolved dates are part of the group's description; a file picker's description holds its limits and a count of the files attached. |
| 1.3.2 Meaningful Sequence (A) | Supports | DOM order is reading order: label, control, help, error. The error summary sits at the top of the form, above the first section (in the step layout, above the open step), and receives focus when it appears. (Corrected 2026-09-23: this row used to say the summary sat directly above the submit button.) |
| 1.3.3 Sensory Characteristics (A) | Supports | Instructions name fields and actions; the summary heading's "highlighted fields" is backed by the named list of problems. |
| 1.4.1 Use of Color (A) | Supports | An invalid field shows error text, a thicker border and aria-invalid; required fields use an asterisk explained above the form; links are underlined; the current language is bold and aria-current. |
| 1.4.2 Audio Control (A) | Not Applicable | No audio. |
| 2.1.1 Keyboard (A) | Supports | Native links, buttons and form controls only. The runtime passes used keyboard events for submitting, the error-summary links, file removal, resend, code entry, acknowledgement, Stay signed in, Start again, the pop-up (open, Tab, Shift+Tab, Escape in the host page and inside the frame) and Tab / Shift+Tab through the embedded frame; the remaining steps were driven by script. A customer who supplies their own pop-up opener must make it a button. |
| 2.1.2 No Keyboard Trap (A) | Supports | Tab and Shift+Tab pass into and back out of the embedded frame (runtime-verified); the pop-up closes with its button or with Escape — pressed in the host page or inside the frame — and returns focus to the opener (runtime-verified). |
| 2.1.4 Character Key Shortcuts (A) | Not Applicable | No single-key shortcuts. |
| 2.2.1 Timing Adjustable (A) | Supports | A verified session ends after 30 minutes without activity and 8 hours at most (deployment settings). Three minutes before the end (half the session when a deployment sets one shorter than six minutes) a notice takes focus on Stay signed in, a single action that extends the session up to the 8-hour cap — at least fifteen extensions at the default settings, beyond the criterion's ten; in the last window the notice says no further extension is possible. When the session ends the details are hidden and Start again keeps the reference and address. The e-mailed code (10 minutes) and the lock after five wrong codes (15 minutes) are deployment settings, stated on the intake code step and in the lock message; they protect a one-time credential and are treated as essential, and a new code can be requested at any time without losing the submission (up to five an hour). Runtime-verified with 2- and 1-minute sessions (the last-window notice with the server's final flag simulated in the page; the 8-hour cap itself by a server test). |
| 2.2.2 Pause, Stop, Hide (A) | Supports | Nothing moves, blinks or scrolls; the pay-return page replaces its one status line when the payment is confirmed. |
| 2.3.1 Three Flashes or Below Threshold (A) | Supports | No flashing content. |
| 2.4.1 Bypass Blocks (A) | Supports | A "Skip to content" link, visible on focus, targets main; landmarks as in 1.3.1. |
| 2.4.2 Page Titled (A) | Supports | "Page purpose · organization" on every page; the title follows the step ("Check your email", "Your request has been received", "Check a request"); the error page reads "Page not found" or "Something went wrong". Since 2026-09-23 (PA-08, PA-09): the title follows an in-place language change (it used to stay in the old language on the single-page form), and reads "Error: …" while the form's error summary shows (jsdom-verified). |
| 2.4.3 Focus Order (A) | Supports | Focus follows DOM order and moves to the new step, the error summary, or the field a message describes; busy or finished buttons stay focusable (aria-disabled). A session warning moves focus to Stay signed in and back to where it was when the warning goes; an ended session moves focus to Start again, and Start again to the lookup's first empty field or its send button. Runtime-verified for the code step, receipt, case / delivery / pay views, the summary, lookups, file removal, resend, acknowledgement and the session notices; a view that fails to load takes focus (code review). Step layout (2026-09-22): opening a step moves focus to its legend (read once — no announcement as well), a Change link moves it to the field it named, the review step to its heading; the browser's Back button moves between steps the same way; verified in jsdom for both layouts. Language change — corrected 2026-09-23 (PA-01): this row used to say focus returns to the step after a language change; that held for the step layout, the code step, the receipt and the verified views, but on the single-page form and on the ended / signed-out notice focus fell to the page. Now a step drawn again takes focus (on the notice, Start again), and otherwise focus stays on the same language link in the new header (or the page heading) and the change is announced once in the new language. Sent messages (PA-02): after Add detail / a reply, a fee answer or a withdrawal, the confirmation takes focus and stays while the list is redrawn (it used to be deleted, leaving focus on the page). Both jsdom-verified; not yet with a live screen reader. |
| 2.4.4 Link Purpose (In Context) (A) | Supports | Link text is specific ("Check the status of this request", "Back to your request"); "Open", "Pay" and download links sit in the list item that names the delivery, fee or file; Download and Remove buttons include the file name. |
| 2.5.1 Pointer Gestures (A) | Supports | Single clicks only. |
| 2.5.2 Pointer Cancellation (A) | Supports | All actions run on click (the up event). |
| 2.5.3 Label in Name (A) | Supports | Accessible names start with the visible label ("Remove report.pdf", "Download report.pdf"). While a download link is prepared the button briefly reads "Preparing…". |
| 2.5.4 Motion Actuation (A) | Not Applicable | No motion input. |
| 3.1.1 Language of Page (A) | Supports | <html lang> is the language the page is served in, chosen from the tenant's offered languages; the error page follows the failed address's ?lang=; a language change on a step drawn by the script updates lang with the text (runtime-verified). |
| 3.2.1 On Focus (A) | Supports | Focus never changes context. |
| 3.2.2 On Input (A) | Supports | A conditional question appears in place after the answer that reveals it; language changes are links (on a step the script drew, the chosen language replaces the text in place); nothing submits on input. |
| 3.3.1 Error Identification (A) | Supports | Every problem is described in text beside its field and in the focused summary; lookups, uploads, codes, expired sessions and failed calls each say what went wrong. A required file field without a file, and an attachment that failed or was refused, are named in the field's error and the summary; the server refuses to send the code for, or confirm, a request whose required attachment is missing. An unknown address or a server error shows a page that says so. By design a submission refused by the bot defence says only that it could not be sent, so the message never reveals which defence fired. Since 2026-09-23 (PA-04, PA-10, PA-11, PA-16, PA-25): the error is marked on, and the summary link focuses, the control that is wrong — a time period's Year or month box, not its first radio; a checkbox group's error is the group's, never option 1's; the fee answer's radios and the withdrawal box carry their errors; the message panel's file picker has an error of its own; the landing reference lookup shows its error beside the field instead of the browser's bubble. The honeypot is renamed so autofill does not fill it (PA-26), and since later that day a filled one no longer refuses the request: the server asks for the invisible proof of work instead, which the page solves, so the requester never sees an error for it. |
| 3.3.2 Labels or Instructions (A) | Supports | Visible labels; the required-field note above the form, now enforced for file fields too; per-field help from the form author; the code step's instructions are read with the code field (on the intake form they include the masked address and the code's lifetime, taken from the deployment settings; the tracking, delivery and pay steps say an 8-digit code is on its way, and the e-mail states the lifetime). Since 2026-09-23 (PA-03, PA-11, PA-14): every file picker states the accepted types, the per-file and all-files caps and how many files it takes — from the tenant's settings, in its description; an author's length limit is stated under the field; the withdrawal reason is marked required. |
| 4.1.1 Parsing (A, WCAG 2.1 only) | Supports | Server-rendered markup with unique ids (pinned by tests); script builds elements through the DOM API. Obsolete and removed in WCAG 2.2. |
| 4.1.2 Name, Role, Value (A) | Supports | Native controls; checkbox groups named by their legend; aria-invalid, aria-required, aria-current and aria-disabled states; the pop-up is a named role="dialog" with aria-modal; the frame has a title. Since 2026-09-23: the frame's title names the form's kind ("Complaint form", "Privacy concern report" — PA-18; the Settings snippet carries data-ap-kind); the pop-up's discard question is a role="alertdialog" named by its text (PA-07). |
| 1.2.4 Captions (Live) (AA) | Not Applicable | No live media. |
| 1.2.5 Audio Description (Prerecorded) (AA) | Not Applicable | No time-based media. |
| 1.3.4 Orientation (AA) | Supports | No orientation lock. |
| 1.3.5 Identify Input Purpose (AA) | Supports | Fields mapped to the requester's name, given and family name, organization, e-mail, phone, address and preferred language carry the matching autocomplete token; the code field is one-time-code. A field the author leaves unmapped carries none unless it is an e-mail, phone or address field. |
| 1.4.3 Contrast (Minimum) (AA) | Supports | Light / dark: body text 17.2 / 16.2:1; muted text 6.95 / 8.64:1; links and secondary buttons 8.66 / 7.86:1; primary buttons 8.66 / 8.26:1; errors 6.54 / 7.25:1, on the alert background 5.72 / 6.60:1; success 5.46 / 6.89:1; placeholders use the muted colour. The session warning is body text on the information background (15.4 / 12.8:1), the ended notice body text on the alert background (15.1 / 13.2:1); an appearance theme of dark uses exactly the dark values; the pop-up's Close button is #1b1b1b on #fff (17.2:1) whatever the frame's theme. axe reported no contrast failures in either scheme or in the forced dark theme. Since 2026-09-23 (PA-19): an embedded frame's footer (Help, Privacy notice) — the one text outside the card — draws its own surface colour, so its links and muted text keep the pinned ratios whatever the host page or the pop-up's white panel shows behind the transparent frame (they measured 2.11:1 and 1.92:1 in a dark frame over the white panel); the pop-up's discard question is #1b1b1b on white with #1f4e79 buttons (8.66:1). "Receipt confirmed" is now a success line (5.46 / 6.89:1) rather than the label of a disabled button at 60 % opacity (3.12:1 — PA-23). Colours a tenant overrides through the appearance object are authored content; Settings warns, without blocking, when a pair falls below 4.5:1 for text or 3:1 for form-field borders and focus rings, in each palette the override can land on — since 2026-09-17 also header text on the header background, links on the page and on cards, and typed text and placeholders on the field background (each new variable defaults to an existing colour, and those default pairs are pinned by the same test). |
| 1.4.4 Resize Text (AA) | Supports | rem-based sizes, no fixed heights; the embedded frame resizes to its content. Since 2026-09-23 (PA-22) the reading-room search fields take the same 16 px, 44 px themed box as every other field (they rendered at the browser's 13.3 px). |
| 1.4.5 Images of Text (AA) | Supports | None of the portal's own. A tenant's optional logo may be a logotype (exempt); the name it stands beside is text. |
| 1.4.10 Reflow (AA) | Supports | No horizontal scrolling at 320 CSS px on the form, receipt, case, delivery and pay views, the error page and both session notices (runtime-verified); key / value lists become one column below 480 px; long references and hashes wrap. The 2026-09-23 audit measured two exceptions — a long unbroken file name made the page 466 px wide, and a tenant request number with underscores 384 px (PA-05) — and landing cards 2 px wider than their column (PA-21): text in a card now wraps, names in list rows and references shrink with overflow-wrap: anywhere; min-width: 0, and cards are minmax(min(16rem, 100%), 1fr). Stylesheet and tests only; the 320 px / 400 % measurement is to be repeated. |
| 1.4.11 Non-text Contrast (AA) | Supports | Control borders 4.55 / 6.0:1; invalid-field border 6.54:1; button borders 8.66:1; the two-colour focus ring as described above; the pop-up's Close button is a white square with a 1 px #6e7781 border (4.55:1 against white), so it stands out over a light or a dark frame. Native checkboxes are drawn by the browser; since 2026-09-17 (stylesheet and tests, not yet re-measured in a browser) they take the theme's primary colour through accent-color, the choice-list arrow and the date field's calendar button are drawn in the text colour, and in forced-colours mode the system draws the list and the calendar button again. |
| 1.4.12 Text Spacing (AA) | Supports | With the 1.4.12 overrides applied at 320 and 1280 px, nothing overflows or is clipped (runtime-verified). |
| 1.4.13 Content on Hover or Focus (AA) | Not Applicable | No tooltips or content shown on hover or focus. |
| 2.4.5 Multiple Ways (AA) | Supports | The landing page lists every published form and the request lookup; delivery and pay pages are reached from the request page and from the e-mails that announce them; the rest are steps in a process. |
| 2.4.6 Headings and Labels (AA) | Supports | Headings name the page and the step ("Check your email", "Records for you", "Your session is about to end", "Page not found"); labels come from the form author or the portal's own strings in eleven languages. |
| 2.4.7 Focus Visible (AA) | Supports | Every link, button and control shows the two-colour ring on focus; containers that receive focus after a step change show the browser's own indicator. |
| 3.1.2 Language of Parts (AA) | Partially Supports | Language names carry their own lang; form text shown in a fallback language is tagged; a request's status label shown in English because the tenant has no translation for the page language is tagged lang="en"; a shared letter's correspondence purpose is shown in the page language; the widget's title and Close follow the host page (runtime-verified on a French page). Since 2026-09-15 (server and page-script tests, not yet in a browser): a shared letter's subject is tagged with the language the letter was composed in; a delivery title staff wrote is tagged with the language the Deliver dialog was used in (the staff member's display language, which the pre-filled export name also uses; the tenant's base content language when an API caller names none); a delivery created without a title shows the portal's own title in the page language instead of an English one. Gap: a letter composed before letters recorded their language shows its subject untagged (letters logged rather than composed show their purpose in the page language, never a subject), and a title a staff member deliberately types in a language other than their display language is tagged with the display language. Since 2026-09-23 (audit PA-24; server, page-script and web-part tests, not yet in a browser): the clarity assistant's AI questions are asked for in the language the requester used the form in and stored with it (portal.Submissions.ClarityLanguage), and on a page read in another language each question carries that lang while the "(AI suggestion)" label stays in the page language; the staff inbox tags them the same way. Questions written before then have no recorded language and are shown untagged, and the language is the one the model was asked for — a model that answers in another language is not detected. The requester e-mails are reported under Generated outputs. |
| 3.2.3 Consistent Navigation (AA) | Supports | One layout for every page. |
| 3.2.4 Consistent Identification (AA) | Supports | The code step, lookups and buttons use the same strings on every surface. |
| 3.3.3 Error Suggestion (AA) | Supports | Messages say what would be accepted: a valid e-mail address, at least N characters, a date on or after / before a given date, the author's own message for a pattern, the reference exactly as shown on the receipt. Since 2026-09-23: an answer that is too long says the limit and how many characters were typed (PA-14 — the hard maxlength that cut pastes short is gone); a file refused for the count names the number (PA-03); a half-typed date asks for "the full date: day, month and year" rather than a YYYY-MM-DD the browser's field does not show (PA-13); a time period's year names the years accepted and a half-typed span asks for both month and year (PA-04). |
| 3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Supports | A request is checked before it is sent and can be corrected, and it counts only once the requester confirms the e-mailed code; a payment shows the amount on the "Pay …" button before the provider's page; receipt confirmation is an explicit action. Since 2026-09-23 (PA-07): closing the pop-up widget while it holds unsent answers or files, or a request not yet confirmed, asks first — the default keeps the form — instead of discarding everything. The provider's own payment page is outside this assessment (see Complete processes above). |
| 4.1.3 Status Messages (AA) | Supports | One polite live region carries step changes and outcomes; the progress line is a live region from page load; resend, removal, download and acknowledgement outcomes are shown and announced once; "Your session has been extended" is announced; the session warning and the ended-session notice take focus, their message read as the focused button's description, rather than relying on a live region; the pay-return status is a status region. Since 2026-09-23: an in-place language change is announced once, in the new language, when no redrawn step takes focus (PA-01); the time period's resolved dates are a status message (PA-12); the confirmation after a message, fee answer or withdrawal takes focus and is not announced as well (PA-02). jsdom-verified; the announcement timing is for the live screen-reader pass. |
| 2.4.11 Focus Not Obscured (Minimum) (AA, WCAG 2.2) | Supports | Portal pages have no sticky or fixed content — the step layout's Continue / Back sit at the end of each step, never in a sticky footer; the pop-up makes the host page inert, so focus cannot move under its overlay (runtime-verified). An embedded step-by-step form posts ap:scroll so the host scrolls the frame's top into view when a step opens — below a host page's own sticky header when the embed gives its height in data-ap-scroll-offset (since 2026-09-25); since 2026-09-23 (PA-20) so do the error summary, a form message, the code step and the receipt, in either layout — whether iOS Safari follows it is for the live pass. |
| 2.5.7 Dragging Movements (AA, WCAG 2.2) | Not Applicable | Nothing is dragged; files are chosen through the browser's file picker. |
| 2.5.8 Target Size (Minimum) (AA, WCAG 2.2) | Supports | Buttons are at least 44 px high and link-style buttons 32 px. Measured: the only targets under 24 px are inline text links (language menu, footer), which meet the spacing exception, and unstyled native checkboxes and the file input, which the browser draws; the pop-up's Close button measures 30 × 31 px. Since 2026-09-17 (stylesheet, not yet re-measured) checkboxes are 24 × 24 px, the file chooser's button is at least 44 px high and the date field's calendar button is 24 × 24 px. |
| 3.2.6 Consistent Help (A, WCAG 2.2) | Supports | When the tenant configures them, the privacy notice and the Help (e-mail) link sit in the same footer position on every page; an embedded form relies on the host page's help. |
| 3.3.7 Redundant Entry (A, WCAG 2.2) | Supports | The code step reuses the address from the form; the receipt link carries the reference to the tracking page; the pay page accepts the tracking session; after a session ends, Start again keeps the reference and address typed earlier; sending again after an attachment problem reuses the submission already made; the step layout's check-your-answers page and Your request so far reuse what was typed, and a language change keeps every answer (the form relabels in place). Entering a new code to open a new session is required for security (the criterion's exception). Records (audit PA-17, closed 2026-09-23; server and page-script tests, not yet in a browser): right after verifying on the request page (or through See all your requests), Open under Records for you shows the files with no address and no second code — the verified session opens the deliveries of its own request sent to its own address, re-checked on every call. A delivery opened from its e-mailed link without such a session, or sent to another address, asks for the address and a code: new information for a new session, the security exception. (This row was Partially Supports from the audit until the fix.) |
| 3.3.8 Accessible Authentication (Minimum) (AA, WCAG 2.2) | Supports | Verification is an e-mailed code that can be pasted (spaces and dashes are ignored) with autocomplete="one-time-code" and inputmode="numeric"; the e-mail field supports autofill; the anti-bot proof of work runs invisibly, with no puzzle or CAPTCHA. Since 2026-09-23 (PA-26) the hidden anti-bot field is no longer named "website" and carries the ignore flags of the common password managers, so an autofill tool that fills every field no longer trips it; and should one fill it anyway, the server asks for the invisible proof of work instead of refusing, and the page solves it, so the requester is never locked out (both to be confirmed with Chrome, Edge and Safari autofill, 1Password, Bitwarden and a voice-control form fill). |
Known limitations — public portal (open)
- JavaScript is required. The intake, tracking, delivery and pay pages submit through the page script. Without it, the form's
<noscript>notice names the other ways to ask that the tenant configured — the support e-mail and, since 2026-09-22, a postal address (Settings → Public portal) — so the right of access never depends on a browser (portal experience review E-8.3). WCAG accepts accessibility-supported scripting, but the design's server-first intent is not met. - Language of parts (3.1.2) — what staff write in another language. Since 2026-09-15 a shared letter's subject carries the language the letter was composed in and a delivery title the tenant's base content language (see Open items closed later the same day). Still open: a letter composed before letters recorded their language has none, so its subject is shown untagged when it is shared (a letter logged rather than composed shows its purpose in the page language, never a subject); and a delivery title is tagged with the language the Deliver dialog was used in, so a title a staff member deliberately types in another language is tagged with their display language.
- Code lifetime and lock (2.2.1). The e-mailed code (10 minutes by default) and the lock after five wrong codes (15 minutes) end without an advance warning; both are treated as essential security limits, and a new code can be requested at any time without losing the submission.
- Pop-up widget. An opener the customer supplies must be a real button.
- Downloads open in the top window. The link is inserted beside its button and focused, but the navigation itself is not announced.
- (Closed 2026-09-22.) A language change on the form relabels it in place and keeps every answer, on the form as on the steps after sending (implementation decision I-17; see 3.3.7 above). Earlier builds reloaded the page and lost answers not yet sent.
- (Closed later on 2026-09-23.) The three audit items first left open — PA-17 (a request session now opens its own request's deliveries; 3.3.7 back to Supports), PA-24 (the clarity questions are generated in, and tagged with, the submission's language) and PA-26's server half (a filled honeypot asks for the proof of work instead of refusing) — are fixed. Everything fixed for that audit was verified in jsdom and by tests, not yet with assistive technology — the list, with these items as its seventh entry, is under Portal accessibility audit (2026-09-23).
- Payment provider pages are the provider's and are not assessed here (see Complete processes above Table 3); the tenant's checklist is in
docs/payments/README.md. - Not yet assessed with a live screen reader, in Firefox, Safari or on mobile, or in forced-colours mode. The manual procedure is written —
docs/FunctionalTestPlaybook.mdsuite POR-A11Y (manual): NVDA with Firefox, VoiceOver with Safari on macOS and iOS (including focus moving into the embedded frame afterap:scroll, review A-10), TalkBack with Chrome, and Windows forced colours — and has not been run. The session notices, the error page and the in-place language change were verified in a headless browser only, and not yet on a deployed portal; the letter-subject and delivery-title tagging and the per-field required-file check (2026-09-15) by tests only.
Training — Lab mode, guided learning and team exercises (2.5.0)
New in 2.5.0 (docs/UserGuide.md → Training your team): the Lab mode switch and band, training cases with their guide, Guide me tours on the real screens, first-time tips and Get started on My Day, the training progress table, and the team exercise console with its debrief. Assessed on 2026-10-05 by code review and the web part's unit tests (components/learning/ShowMeHost.test.tsx, GetStartedGroup.test.tsx, TrainingPaths.test.tsx, ExerciseConsole.test.tsx, tours.test.ts and the Lab mode tests components/training/TrainingMode.ui.test.tsx, TrainingCases.ui.test.tsx, trainingCues.test.tsx); the live screen-reader pass (playbook TRN-A11Y, NVDA + Firefox with a JAWS spot check) is the owner's and has not been run yet — until it is, read every row below as code-reviewed and unit-tested, and, since 2026-10-13, scanned with axe, measured at 320 and 640 CSS px and walked from the keyboard (method 15), but not heard with a screen reader.
Table 4: Training surfaces — the criteria they touch
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| Guide me callout · 1.3.1, 4.1.2 | Supports | A non-modal callout (Fluent TeachingBubble, role="dialog", aria-modal="false") labelled by its title; while a step shows, its text is added to the highlighted control's aria-describedby (the control's own description is put back afterwards); Step n of m, Next, Back and Close the tour / Done are named buttons. |
| Guide me callout · 2.1.1, 2.1.2, 2.4.3 | Supports | Operable from the keyboard alone: focus moves to the step's title when the tour starts and at every step; the bubble's focus trap is switched off, so Tab reaches the highlighted control and Shift+Tab comes back to the callout; Escape closes the tour only — never the panel beneath — and returns focus to where the tour started; since 2026-10-07 an open dropdown, menu or dialog over the tour takes the first Escape, and a tour that followed the person into a panel leaves focus in that panel (the highlighted control) instead of behind it. Corrected 2026-10-07: five tours open the menu or panel their first step is on (the Training menu for the training settings tour, the privacy program's inventory for four program tours) — none opens a case; and since 2026-10-07 a tour moves on, and moves focus to the next step's title, when the person opens the panel that step is on. Checked at runtime on 2026-10-13 (keyboard, no screen reader): the tour starts with focus on the step's title, and Escape returns focus to Guide me; whether the focus move on following a panel races the panel's own first focus has not been heard with a screen reader. |
| Guide me callout · 2.4.7, 1.4.11 | Supports | The highlighted control gets a 2 px outline at 3:1 or more against its surroundings, in addition to the callout's text — the highlight is never colour alone. |
| Guide me callout · 2.4.11, 1.4.10 | Supports | The callout is placed beside the control and never covers it; at narrow widths (320 px) it docks below the control. |
| Guide me callout · 2.2.2, 3.2.1 | Supports | The scripted scroll to the control honours prefers-reduced-motion. A step whose control is not on the screen yet says so in text (This part of the screen is not open yet…) and waits; nothing changes context by itself — the tour advances only when the person opens the panel the next step is on (2026-10-07). |
| First-time tips · 2.4.3, 3.2.1, 4.1.3 | Supports | Each tip is a role="note" with Guide me and Not now, read in browse mode; it never takes focus and is not a live region, so it never interrupts. |
| Get started (My Day) · 1.3.1, 1.4.1, 1.4.10, 2.1.1, 4.1.2, 4.1.3 | Supports | A headed group with its count in text (Get started — n of m topics done); each topic is a level-4 heading holding a native button with aria-expanded and aria-controls (Enter and Space open and close it), its progress in words (n of m done) beside a decorative bar — never colour alone — and Done in text when finished; its steps sit in a region labelled by that button; each step's buttons are named with the step (corrected 2026-10-07: Guide me and Practice were described by the step, not named with it — they are now Guide me: <step>); Done <date> is text; Mark complete moves focus to the topic's button and says Done: <step> in the topic's status region (2026-10-07 — it removed the focused button and was silent); the row wraps at 320 px and the colours are theme variables (the done mark uses the success token since 2026-10-07; it fell under 3:1 in the dark theme). |
| Training case guide · 1.3.1, 4.1.2, 4.1.3 | Supports | Native checkboxes named by each step's title with its body as the description; Done — checked automatically in text; the progress (n of m steps done) is announced politely (role="status"). Since 2026-10-06 it shows three steps at a time and re-reads the case every 10 seconds; a step that ticked itself is announced through the guide's own status region (2026-10-07 — it was sent to the app's announcer, which the open case panel hides from assistive technology), several ticks in one announcement; Go to tab and Keep exploring return focus to Open guide; the paging buttons keep focus at either end and the shown range is announced. |
| Training case guide — scripted people (2.6.0, TM-1B) · 1.3.1, 2.4.3, 4.1.2, 4.1.3 | Supports | Built for 2.6.0, not part of the 2.5.0 release this table evaluates; code-reviewed and unit-tested (TrainingGuideAnswers.test.tsx), not yet scanned, measured or heard. The guide's scripted answers are two sections labelled by their level-4 headings, Waiting for and Answers received, each a list of plain text lines (Jamie Okonkwo’s reply — expected {date}, exercise time; Jamie Okonkwo replied on {date} (brought forward); … did not answer: they do not write again) — the reason a reply will not come is words, never a code or a colour. Have it arrive now is a native button whose accessible name adds whose answer it brings (Have it arrive now: Jamie Okonkwo’s reply); it is disabled with allowDisabledFocus while a request is in flight. When the answer arrives its button is gone, so focus moves to the Answers received heading (tabIndex=-1); a refusal leaves the button and focus where they were and shows an error message bar. An arrival — brought forward or come due while the person works — is announced politely through the guide's own status region (Jamie Okonkwo replied.), before any step it helps tick, in one announcement. With the guide closed, the banner's text line Waiting for: … keeps it in sight. Nothing moves or times out. |
| Scripted reply badge · 1.4.1, 1.3.1 | Supports | 2.6.0 (TM-1B): a reply a scripted requestor wrote in Lab mode carries the text badge Scripted reply on its card on the Requestor tab and in its details panel — words beside the training icon, which is decorative (aria-hidden), never colour alone. |
| Team exercise planning — who plays each person in the scenario (2.6.0, TM-1C) · 1.3.1, 3.3.2, 4.1.2 | Supports | Built for 2.6.0; code-reviewed and unit-tested (PartyDesk.test.tsx), not yet scanned, measured or heard. Under the level-4 heading People in the scenario, each role that plays a scripted person is a labelled dropdown (Who plays Requestor) with two options in words, A colleague and Scripted — {name}; a role with no script says so in text (only a colleague can play this role). Choosing the script removes that role from the participant role picker, so a refusal never depends on colour or position. |
| Team exercise console — people in the scenario, Remind and Let the script answer (2.6.0, TM-1C) · 1.3.1, 2.4.6, 3.3.4, 4.1.2, 4.1.3 | Supports | Built for 2.6.0; unit-tested, not yet scanned. The lead's People in the scenario section (level-3 heading) lists each role with {name}: played by a colleague or {name}: answered by the script, and what a colleague owes as text lines (Waiting for an answer since {date} · reminded). Remind and Let the script answer are buttons whose accessible description names the role; Let the script answer opens a blocking confirmation dialog naming the person before anything changes, and focus returns to the console. Each result is announced politely through the panel's live region (Reminder sent: Requestor., The script now plays Jamie Okonkwo.). |
| The party desk (2.6.0, TM-1C) · 1.3.1, 2.4.3, 3.3.1, 3.3.2, 4.1.2, 4.1.3 | Supports | Built for 2.6.0; unit-tested (PartyDesk.test.tsx), not yet scanned. Your desk (level-3 heading) says in text who the colleague plays (You’re playing Jamie Okonkwo, the requestor.); Waiting for your answer and Letters are level-4 headings over lists. Each answer form has labelled fields (Subject, Your reply — required; for a third party a required Your position dropdown whose options are the Consultations tab's own words, and Your representations), the records to send are a labelled checkbox group (fieldset/legend), and Send stays disabled until the form can be sent. Sending announces Sent. The team sees your answer on the case. in a polite live region and moves focus to the Letters heading (tabIndex=-1); a refusal shows an error message bar with words, never a code. Open the letter buttons carry the letter's subject as their description. A handover or an ended exercise is said in an information bar, and the answer buttons are gone. Nothing moves or times out. |
| The party desk of a complaint — the complainant's reply and the regulator's next step (2.6.0, TM-1D) · 1.3.1, 2.4.6, 3.3.1, 3.3.2, 4.1.2 | Supports | Built for 2.6.0; unit-tested (PartyDeskComplaint.test.tsx), not yet scanned. The desk of the complainant is the requestor's (You’re playing Sam Lee, the complainant., Write a reply). The regulator's contact's desk names the office in text after who they play; each owed step is a list item headed in words — The complaint has started, the letter's subject, or The organization recorded: Records produced — never a code. Send the regulator’s next step opens a form with a required What the regulator does dropdown whose options are actions in words (Request the records, Make an order …), a labelled Title on the timeline, Subject and the required What the regulator says, and the records group (fieldset/legend); Send stays disabled until an action and the words are given. Sending, refusals and focus behave as the requestor's desk. |
| Scripted reply badge on a complaint (2.6.0, TM-1D) · 1.4.1, 1.3.1 | Supports | A message the scripted complainant or regulator's contact wrote in Lab mode carries the text badge Scripted reply on the complaint's Correspondence tab — words beside the decorative training icon, never colour alone. |
| A complaint entry's party — Correspondence with (2.6.0, TM-1D's follow-up) · 1.3.1, 2.4.6, 3.3.2, 4.1.2 | Supports | Built for 2.6.0; not yet scanned. Log correspondence on a complaint keeps its labelled Correspondence with dropdown (Fluent UI Dropdown), whose options now name the party — The complainant, The regulator — so they read correctly for an incoming message too. On the complaint's Correspondence tab, an entry that stores its party shows Correspondence with: The regulator in text beside a decorative icon (aria-hidden), never by colour or the icon alone. |
| Scripted attestation and simulated custodians (2.6.0, TM-2B) · 1.3.1, 1.4.1, 4.1.2, 4.1.3 | Supports | Built for 2.6.0; unit-tested, not yet scanned. A scripted attestation's read-only view starts with a role="note" banner whose text says Scripted attestation and Nobody signed this… — words, the icon decorative (aria-hidden), never colour alone. In Lab mode the Add assignment custodian picker lists the case's simulated people first, each suggestion's secondary text ending in the visible tag Simulated, offered on focus with no typing. The guide's Waiting for and Answers received lines and the polite arrival announcement name a search or a task in words (Maria Okafor’s search, Maria Okafor submitted the search.). TM-2C: the review approver pickers (start a review, assign an approver) and the advisor picker offer the case's simulated people the same way, and the guide names a review or an advice in words (… decided the review step., … gave their advice.). |
| Scripted response badge · 1.4.1, 1.3.1 | Supports | 2.6.0 (TM-1C): a consulted party's response that a script wrote in Lab mode carries the text badge Scripted response beside its received date on the consultation — words beside the decorative training icon, never colour alone. |
| Simulated people in Lab mode's other pickers (2.6.0, TM-2C – TM-3A; the opinion picker since the close-out, TM-Z) · 1.3.1, 1.4.1, 4.1.2 | Supports | Built for 2.6.0; unit-tested (opinionPickerSimulated.test.ts among others), not yet scanned. The approver pickers (Start review, Assign approver), the advisor picker, the section-delegation picker, the work pickers (investigator, evidence provider, action owner, treatment task) and Request opinion's provider picker list the case's simulated people first, each suggestion's secondary text ending in the visible tag Simulated (the opinion picker shows the character's job title and unit instead of its placeholder address); the initials are decorative. Never colour alone. |
| Scripted colleagues in the guide — the coordinator, the senior official, the opinion provider (2.6.0, TM-2D – TM-2F, TM-Z) · 1.3.1, 4.1.3 | Supports | Built for 2.6.0; unit-tested (TrainingGuideAnswers.test.tsx, ScriptedOpinionProvider.test.ts), not yet scanned. The guide's Waiting for and Answers received lines and the polite arrival announcement name each act in words (The work Jordan Ellis gives you, Jordan Ellis’s decision on your work, Priya Raman’s sign-off of the letter, Annelie Brookvar’s opinion); a decision or an opinion a simulated person records shows a capacity ending Simulated (Lab mode) in text; when a scripted act cannot happen the reason is words (their part on the case does not allow it), never a code. The gallery card's Needs sign-off switched on for … is text. |
| Let the script answer — its refusals (2.6.0, TM-Z) · 3.3.1, 4.1.3 | Supports | Built for 2.6.0; unit-tested (handoverRefusalText.test.ts), not yet scanned. A refused handover is announced in the console's polite region in its own words — You cannot let the script answer for this person: … or The request is closed, so its open work cannot be handed to the script… — never the generic refusal or a code, and nothing changes. |
| Lab mode · 1.4.1, 1.3.3, 4.1.2 | Supports | The mode is signalled three ways: a band that is a region named Training holding real text, a distinct accent colour (a theme token, set for dark mode too) and a [Training] prefix on the page title. The toolbar's Training button is an icon button whose accessible name says when Lab mode is on (Training — Lab mode is on), with aria-haspopup="dialog" and aria-expanded; it opens the Training hub (a dialog panel whose rows are buttons with a visible label and description — the description is read since 2026-10-07 — and whose Lab mode card states in a polite status region whether Lab mode can open and why not). Opening Lab mode from the hub moves focus to the band's heading and announces Lab mode on once; leaving returns focus to the Training button, or at 768 px and narrower (where that button is hidden) to the header's More actions, whose Training item also says when Lab mode is on (2026-10-07). Since 2026-10-13 a hub row hands focus to the Training button before its panel opens, so closing that panel — or the hub reopened with the panel's Back — returns focus there instead of to the page (checked on dev). |
| Lab mode · 2.2.1 Timing Adjustable | Supports | Lab mode is the product's only inactivity limit: after 28 minutes without input a warning offers Stay in Lab mode (two minutes to act — more than the 20 seconds the criterion requires); at 30 minutes the tab returns to real work and says so. Nothing is lost: training cases persist, and the person can open Lab mode again at once. Fixed 2026-10-07: the warning sat in the app's tree, which an open case panel — the usual state while practicing — hides from assistive technology; it now opens in a layer of its own, created when it appears, so it is announced over the panel (not yet heard with a screen reader with a case panel open). |
| Progress table · 1.3.1 | Supports | One real <table> per path with a <caption> (the path's title), column headers (scope="col") and the person as the row header (scope="row"); the actions column has a screen-reader-only header. |
| Progress table · 1.4.1, 1.4.10 | Supports | Each cell's status is text (Not started, In progress, Done with the date), never colour alone; the table sits in a labelled, focusable region that scrolls horizontally on its own (permitted for data tables), so the page does not scroll sideways at 320 px. |
| Progress table · 3.3.4 | Supports | Withdraw asks first and names the person and the path (What they have done stays done); Export CSV gives the same data in a plain format. |
| Exercise console · 1.3.1, 2.4.6 | Supports | Headings structure the console (the exercise as a level-2 heading; participants, injects, the clock and the debriefs below it); the clock buttons are a group named Exercise clock; each inject shows its title, who it is for and when it is suggested in text. |
| Exercise console · 4.1.3, 3.3.1 | Supports | Starting, releasing an inject, moving the clock and ending are announced once through a polite live region; a refusal names its reason in text (the missing roles, another exercise holding the clock, a state that moved on since the page loaded). |
| Exercise console · 3.3.4 | Supports | End exercise asks first; the clock only moves forward and says so (The clock only moves forward.). |
| Debrief · 3.3.2 | Supports | Each question is a labelled field; the form says who reads the answers (Your own answers. The lead reads everyone's; nobody else does.). |
Training content. The scenarios' records are fictional PDFs AccessPoint generates in the case's language; they follow the Generated PDFs row below. Scenario guides, paths and tour texts exist in all 11 supported languages (the federal and Ontario request scenarios in English and French).
Native document viewer and Working Files editors (2.5.0)
In 2.5.0 the document viewer and the Working Files editors are AccessPoint's own code (see Product description and scope, items 2 and 4): the redaction and preview viewer, the Word editor and the spreadsheet grid. They were scanned automatically (method 12) and measured on the dev tenant with NVDA at 200 % zoom (method 13). The rows of Tables 1, 2 and 2b that describe the PDF viewer's marks — named buttons, the focus ring, Enter / Space, Alt+Arrow move and Alt+Shift+Arrow resize, Place redaction box, the 24 px grips and the click-to-arm alternative to dragging — describe code that was carried into the native viewer and checked again there.
| Criterion | Viewer | Word editor | Spreadsheet |
|---|---|---|---|
| 1.3.1 Info and Relationships (A) | Supports — pages are named regions; thumbnails are buttons naming the page and its redactions (Page 1 — 2 redactions, current page); the find bar is a search landmark | Supports — the document is a named multi-line text box with its keyboard help as description (heard with NVDA); headings carry their level and a letterhead is labelled read-only (code and browser tests) | Supports — a grid named Spreadsheet cells whose rows and columns are the spreadsheet's own (NVDA reads B2: 120, row 2, column 2); every cell's name carries its address; the sheets are a tab list. Fixed during the pass: rows were read one too high (method 13) |
| 1.4.3 Contrast (Minimum) (AA) | Supports — every control at least 4.5:1 | Supports — every control at least 4.5:1; hidden-text passages 5.9:1 (fixed, method 12) | Supports — every enabled control at least 4.5:1 (Delete sheet is 2.51:1 only while disabled, which the criterion exempts) |
| 1.4.10 Reflow (AA) | Supports — at 200 % the toolbar and the find bar wrap to two rows; the page itself is two-dimensional content | Supports — at 200 % the toolbar wraps to two rows; the page keeps its paper width and scrolls sideways, like a word processor's print layout (two-dimensional content) | Supports — the grid scrolls inside its own region (a data table) |
| 1.4.11 Non-text Contrast (AA) | Supports — applied mark border 4.93:1, proposed mark 4.55:1, focus ring 4.53:1 against the page | Supports — 3 px focus ring | Supports — the active cell's 2 px border about 7.1:1 |
| 2.1.1 Keyboard (A) | Supports — toolbar, panes, find, every mark (Enter / Space, Alt+Arrow, Alt+Shift+Arrow) and Place redaction box | Supports — Alt+F10 moves to the toolbar, the arrow keys along it, Escape back to the document. Fixed during the pass: Left / Right on a dropdown changed its value | Supports — arrows, Shift and Ctrl selection, F2, Enter, Tab, Delete, Ctrl+A, undo and redo, find; Left / Right on a toolbar dropdown moves focus (same fix) |
| 2.1.2 No Keyboard Trap (A) | Supports — in SharePoint, Tab leaves the viewer frame for the dialog's own controls and comes back | Supports — the editor's dialogs keep Tab inside until Escape or a button closes them, then return focus | Supports — as the Word editor |
| 2.4.3 Focus Order / 2.4.7 Focus Visible (A / AA) | Supports — toolbar, then the document region, then each mark in page order, each with its ring. Fixed during the pass: each page's text layer was an invisible Tab stop | Supports | Supports |
| 2.4.11 Focus Not Obscured (Minimum) (AA) | Supports — the toolbar sits outside the scrolling document, so nothing covers a focused mark or thumbnail at 200 % | Supports — the focused control stays visible at 200 % | Supports — arrowing to any cell at 200 % scrolls it fully into view, never under the row or column headers |
| 2.5.3 Label in Name (A) | Supports — a mark's name starts with the caption painted on it (fixed during the pass; it used to be the exemption's code only) | Supports | Supports |
| 2.5.7 Dragging Movements / 2.5.8 Target Size (AA) | Supports — drawing, moving and resizing have keyboard and click-to-arm alternatives; 17 controls measured, none under 24 × 24 px | Supports — 24 controls measured, none under 24 × 24 px | Supports — column width and row height by dialog; 31 controls measured, none under 24 × 24 px |
| 3.1.1 / 3.1.2 Language (A / AA) | Supports — <html lang> and a localized title (Redaction Viewer) in the 11 languages | Supports — as the viewer, plus the editor's lang for spelling | Supports |
| 4.1.2 Name, Role, Value (A) | Supports — no unnamed control; toggles expose aria-pressed / aria-expanded | Supports — one toolbar with one tab stop; toggles expose aria-pressed | Supports — aria-activedescendant follows the active cell |
| 4.1.3 Status Messages (AA) | Supports — the find result is spoken as a status (1 of 1) | Supports — a save's outcome (Saved, Save failed) is announced through the editor's own polite live region, and the dialog's header shows the state beside the file name (code-reviewed; the NVDA pass did not include a save) | Supports — moves, copy, paste, sheet changes and a save's outcome are announced through the same kind of live region (code-reviewed; not yet heard with NVDA) |
Still open: the editors' save announcements and the spreadsheet's announcements after an edit and its sheet tabs with a screen reader; JAWS and VoiceOver; a session by a person who uses a screen reader daily (roadmap item 7).
Spreadsheet layout and hidden content (2.5.0)
The surfaces that show what a converted spreadsheet, Word or PowerPoint file hides (docs/UserGuide.md → Spreadsheets and hidden content): the Hidden content chip on a document's row; Review hidden content…, which lists the findings by sheet or part and records the acknowledgement (a checkbox and a reason); the viewer's Parts section (Go to, Withhold all pages…) and the Page layout… dialog; Settings → Document conversion; Release as on a released workbook; and the grid review, which opens the original workbook read-only in the native spreadsheet grid so cells can be marked from the keyboard.
Evidence. axe-core 4.10 on the dev tenant on 2026-10-01 (method 14): Settings → Document conversion, the review dialog for a workbook and for a Word record, and the viewer with the Parts section and its withhold form open — one finding fixed (axe's best-practice heading-order: the review dialog's group headings skipped a level). The bands the viewer draws over parts are hidden from assistive technology and the side column states the same facts in text. In the grid review each marked cell's name says whether it is withheld, proposed or hidden, so the hatching is never the only signal (1.4.1), and marking a cell is announced through the grid's live region.
Needs a screen-reader pass (not run): NVDA over the review dialog and its acknowledgement, the Parts section, the Page layout dialog and the grid review; a 320 px reflow pass of the dialogs.
Case archiving and storage (2.5.0, code-reviewed 2026-10-05)
Scope. The surfaces case archiving adds to the web part (docs/UserGuide.md → Case archiving and storage and Records and retention): the storage chips on document rows (Archived, Restoring, Preview removed, Disposed of) and the case's storage banner; the Restore dialog (one per case, with its priority, cost and time estimate); Preservation holds on the case panels (place and release) and in Settings; Mark as sent on a response package; Settings → Storage and archiving (the policies, the confirmation when a policy that archives originals is switched on, prices, Pause archiving and its limits, diagnostics); the Storage report's tiers and savings; the Disposition tab of Retention review; and the restore entry in the activity tray.
How it was evaluated. A code review against WCAG 2.2 A and AA on 2026-10-05 (method 14), with the web part's unit tests, which find these controls by their role and accessible name (caseStorage, caseHoldAndSent, storageArchiving, storageSettings, preservationHolds, dispositionReview, reportStorageTiers). No runtime axe scan, 320 px pass or screen-reader pass yet.
| Criteria | Conformance Level | Remarks |
|---|---|---|
| 1.1.1 Non-text Content / 1.4.1 Use of Color (A) | Supports | Each storage chip is text (Archived, Restoring, Preview removed, Disposed of) with its icon hidden from assistive technology; its colour only repeats the text. A policy that archives originals carries a named icon in the policy list, and the same fact is in the list's text. |
| 1.3.1 Info and Relationships (A) | Supports | Policies use the shared catalogue list; holds, diagnostics and the disposition lists are Fluent data grids with column headers; the restore priority, the hold to release and the reopen choice are labelled radio groups; every field has a label. |
| 1.4.13 Content on Hover or Focus (AA) | Supports | A chip's explanation (The original is in archive storage. Restore it to open or download it.) shows in a Fluent tooltip on hover and on focus, and is also part of the chip's accessible name. A chip that is not a button (Restoring, Disposed of, and every chip outside a case panel) shows its explanation in the tooltip on pointer hover; since 2026-10-05 the same explanation follows the visible state as visually hidden text (Restoring. …), because an aria-label on plain text — what it carried before — is not reliably read on an element with no role (unit-tested; to be heard in the NVDA pass). |
| 2.1.1 Keyboard (A) | Supports | Every action is a Fluent button, link, checkbox, toggle or radio; on a case panel an Archived or Preview removed chip is a real button that opens the restore or rebuild for that file. |
| 2.5.3 Label in Name / 4.1.2 Name, Role, Value (A) | Supports | A chip that is a button is named by its visible text, then its explanation and the file name; the hold, Mark as sent and disposition controls are named by their visible labels (Place hold, Release hold, Mark as sent, Clear sent mark). |
| 3.2.6 Consistent Help (A) | Supports | The Restore and Preservation hold dialogs carry the same Help button in their header as the other dialogs; the Settings panels carry it in the shared panel header. |
| 3.3.1 Error Identification / 3.3.3 Error Suggestion (A / AA) | Supports | A refused restore, hold or disposition shows the server's reason in text (the storage refusal codes have their own messages); the settings fields state what they accept (Enter a size from 0 to 1024 MB, Enter a three-letter currency code, such as CAD). |
| 3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Supports | Switching on a policy that archives originals asks for an explicit confirmation of what it commits (the storage account's redundancy) and, where the policy offers disposal, the records-schedule reference; a disposition and the release of a hold need a reason, which is recorded; a restore shows its estimated cost and time before it starts. |
| 4.1.3 Status Messages (AA) | Supports | Saves and refusals in Settings → Storage and archiving, the price and settings editors, Preservation holds and the Disposition tab are announced through polite live regions; a restore that finishes later is followed in the activity tray, whose region announces changes politely. |
Needs a runtime or assistive-technology test (none has been run): an axe scan and a 320 px pass over Settings → Storage and archiving, Preservation holds, the Disposition tab and a case with archived files; NVDA over a chip button, the Restore dialog and its estimate, the hold dialog and the policy confirmation.
Discovery survey, Report Builder and the other 2.5.0 additions
Discovery survey (code-reviewed 2026-10-05). The survey a privacy program sends to program areas (docs/UserGuide.md → The privacy program): the respondent's panel (activities, the mapped sections, the organization's own questions and files), the survey set-up in the program hub and the responses view. The respondent's panel uses the shared work-item header (with Help) and labelled fields; the organization's own questions are answered with the same editors as an assessment questionnaire (choice lists, the long-label picker, dates, tables, diagrams with their List view, file answers), each named by its question; a required question is marked on its label and written out (Required) in the set-up list; the set-up list reorders with named Move up / Move down buttons (2.5.7) and names every icon button with its question; save outcomes are announced politely. Found in the review and fixed the same evening (2026-10-05): when a machine-translated question was switched to show its original wording, the answer types that take their accessible name as a string — the long-label picker (single and multiple choice), dates, tables, diagrams and files — kept the translated question as their name while the visible label showed the original (2.5.3). They are now named with the question as shown, and a unit test names each of them with the translation, then the original after the switch, then the translation again (QuestionAnswerInput.labelInName.test.tsx); the other types were already labelled by the visible label. The survey's Excel export is under Generated outputs. No runtime or screen-reader pass yet.
Report Builder. Since 2.5.0 Report Builder, Report Studio, pinned tiles and Ask AccessPoint show only the registers the viewer may open. A section the viewer may not see says so in text (You don't have access to …) instead of showing an empty chart or table (1.3.1, 3.3.1). Money in more than one currency is totalled per currency, each amount with its own currency, and a note says that amounts are never converted or added across currencies; one-currency money keeps its symbol (1.3.1 — the currency is never left to be inferred).
Other surfaces new in 2.5.0, built from the components and live-region patterns assessed above and not separately scanned or read with a screen reader: the activity tray, which extends the upload tray (a region named Uploads and background jobs, a group per case, a polite live region for changes, and the same placement rule that keeps it off the focused control — Table 2b, 2.4.11); the System health card on My Day and its notice; the privacy program hub; the Storage report; the request Details sidebar's six cards; and the AI impact assessment templates, which are questionnaire content in the existing assessment editor.
2.5.0 release-candidate changes (static review 2026-10-07, runtime pass 2026-10-13)
What this section covers. Everything users meet that changed after the 2026-10-05 edition of this report, and the
2.5.0 surfaces built before it that the report had not described. It was assessed by a static code review against WCAG 2.2
A and AA on 2026-10-07 (method 15) and by the full eslint-plugin-jsx-a11y recommended rule set run over every changed
component (its findings on these surfaces were Fluent Link buttons the rule takes for anchors — no defect), then by a
runtime pass on the dev tenant on 2026-10-13 — axe, the keyboard paths, 320 CSS px and 640 CSS px (200 %); see Runtime
checks (2026-10-13) below. Nothing here has been heard with a screen reader.
Inventory.
- Changed after 2026-10-05: the diagram editor's fourth version (snap to grid, multi-select, align and distribute, undo and Escape on the canvas) and fifth (alignment guides, right-angle connectors, fixed connection sides, copy / paste / duplicate, a shape added by dropping a connector on empty canvas, zoom 25–200 % with Fit, Arrange, Check diagram, Draft with AI, export as PNG or SVG); the privacy subject's Diagrams tab and the diagram question's note; the Training hub (the toolbar's Training button) with My training, paths, exercises and the training reports; Guide me (renamed from Show me) following the person into the panel the next step is on; Get started by topic; the training case guide showing three steps at a time and announcing steps that tick themselves; the Lab library and Lab mode uploads; request pattern review (the Conduct signals card and Settings → Request pattern review); identity verification on the Requestor tab with one-click reuse; Open contact / Open institution; Require attestation and the plain Submit confirmation; assignment records Responsive by default; English spelling; review templates in every language (the globe); the statistical report template form; the screener's checkboxes; the audit wording of an audit's Documents and Closure tabs; the Teams header's tab overflow; five dark-theme colours.
- Built for 2.5.0 before 2026-10-05, first described here: audits — the engagement and contacts cards, evidence requests (tab, panel, the provider's panel), the findings register and finding panel, follow-up verification, control tests, the five audit reports, Settings → Audits and the case numbering tab; follow-up rules, the Follow-ups card, personal reminders and the waiting-period confirmation; computed due dates (How this date was calculated), the received-date correction and its report; the register filter bar, column menus on the case grids, multi-select and bulk reassign, Export view (CSV), the searchable Reports and Settings menus; the Risks tab with its source chips, filters and heat map; the administrator banners and the SharePoint package update dialog; the accessible format card, the case sidebars' card groups, the complaint choice fields and the choice-options editor.
- Host abstraction (P0–P6): the interface moved into a shared UI package behind host interfaces. It adds no element,
role or landmark around the app; the theme's 50 colour variables are byte-identical to 2.4.0's (pinned by tests); the
lint floor (eleven
jsx-a11yrules and the Spinner rule, all at error) covers every file of the package; and the SharePoint host still keeps Enter and Tab from reaching SharePoint's page script (method 10).
Fixed in the release candidate (2026-10-07, code and unit tests).
- 1.1.1: a read-only diagram — an approved or frozen answer, a custom field, the risk overview, a diagram drafted by Ask AccessPoint before it is used — was one image named by its question. It now has a Text version under it: the swimlanes, the shapes (name, kind, swimlane, note) and the connectors (from, to, label) as lists in the UI language. (The DPIA section said the risk overview offered its List view as the text alternative; it did not.)
- 1.3.1 / 2.5.3 / 4.1.2: every per-language box of a translatable field (the globe) is named by the field and the
language (Name (Français)), not by the language alone, so two such fields on one form no longer share a name; the
globe names its field and points at the boxes it shows (
aria-controls); the collapsed field says when it is required. Rows after the first of a question's choice options had unnamed fields; every row is named (Value 2, Label 2) inside a group named by the list. The diagram question note's View link was named by the dialog's title, without "View"; it is View version n. An approver picker in Start review was named by its placeholder (Assign later) on every step; it is Approver — 2. Legal review. - 1.4.3 / 1.4.11: in the dark theme a diagram's labels were near-white on its fixed light shape colours (about 1:1) and its connectors under 3:1 on a dark canvas; the drawing is now light paper in every theme, as it is exported and printed. The Risks tab's selected source chip (and the document filters' selected type chip) drew theme-blue text on its blue tint, about 3.8:1; the text is the body colour. Get started's and My training's done mark, the path editor's "not recognized" text and the Lab mode band's Help icon on hover now use the theme's status tokens (they fell under 3:1 in the dark theme). A translatable field's warning icon uses the warning token.
- 2.1.1: Escape on the diagram canvas (clearing a selection or a connection) and in its label editor also reached the panel around it, which closed — losing an unsaved diagram on the privacy subject. The key now stops at the canvas. Connectors were not keyboard stops, so their colour and bends (in the Details pane) needed a pointer; each connector is now a named button (From: Applicant, To: Intake, application form) — Enter selects it, F2 renames it, Delete removes it. Escape while a dropdown, menu or dialog is open over a Guide me tour closes that layer first, then the tour.
- 2.4.3: focus no longer falls to the page after: a diagram label edit, a keyboard paste or duplicate, or deleting a shape or connector (it goes to the shape, the pasted shape or the canvas); editing, saving or cancelling a subject diagram; Go to tab and Keep exploring in the training guide (back to Open guide); Mark complete in Get started (to the topic's button); leaving Lab mode at 768 px and narrower (to the header's More actions); a Guide me tour that followed the person into a panel and is closed with Escape (it stays in the panel instead of returning behind it); moving a finding in the findings register, a line or band in a statistical template, or reaching the top or bottom of the guide's step pages (the shared move buttons keep focus); Restore defaults and Save in request pattern review and the identity reuse card, and Save on a follow-up verdict (a button that disables itself keeps focus); Log review outcome (focus moves into the form, and the scroll honours reduced motion).
- 2.4.6: Guide me and Practice in Get started are named with their step, as this report said they were; a profile opened from a case is named Requestor details or Institution details from the first render (it was announced as Requestors while it loaded).
- 2.5.8: the diagram's add-a-bend handle (8 px) has a 24 px target.
- 3.1.2: panels, dialogs, menus, callouts and tooltips render outside the app's root and inherited the SharePoint page's language, so a French interface on an English page was read with English rules wherever a panel was open; every layer now carries the language the app is shown in. A blocking dialog's own close button said "Close" in English in every language; it is in the user's. The error page carries its language. A statistical template's Title in French boxes are marked French.
- 4.1.2: the diagram toolbar's toggles (Shapes, Connect, Snap to grid, Check diagram, Draft with AI, Details) exposed no
on / off state, and a selected shape or swimlane no selected state; both are exposed now. The diagram toolbar's overflow
(…) button is named. The setup page's Deploy to Azure was a button inside a link (two tab stops, nested roles); it is
one link. The complaint (and other grouped) choice-field tabs drew an empty tab panel; they are header-only tabs named by
the panel. The selection column's header was a second, inert Select all stop. The Advanced package-update disclosure
points at what it shows, and the assistant-history Edit says whether it is open. The Only you chip's hint was an
aria-labelon plain text (not read, and an axe failure); it is visually hidden text. The Training hub's rows read their description. - 4.1.3: the training guide's step-done announcements went to an announcer the open case panel hides from assistive technology; the guide has its own status region, and several ticks are one announcement. The Lab mode inactivity warning was hidden the same way while a case panel was open (2.2.1 depends on it); it now opens in a layer of its own. Saving a subject diagram, a follow-up verdict and Mark complete say what was done; the Check diagram result and an AI draft's summary were in regions mounted with their text, and are now announced.
- 1.4.10: the diagram's palette, canvas and Details pane wrap at narrow widths (the Details pane holds the alternatives to dragging); the training guide's paging row, Open contact / Open institution, the choice-options rows and the assistant-history edit row wrap.
- Functional, found alongside: moving a finding in the findings register while Show closed was off swapped it with a hidden closed finding, so the register did not change; it now swaps with the finding shown next to it (unit-tested).
Fixed after the static review (2026-10-13, code and unit tests; re-checked on dev where it says so). Every item the 2026-10-07 review left open:
- 2.4.3: focus no longer falls to the page after a bulk reassign (the bulk bar stays while selection is on, its Reassign and Clear selection unavailable but still focusable — re-checked on dev), in the SharePoint package update dialog (Cancel / Close is always there and takes focus when Update goes), after the waiting-period warning's Cancel (back to the control the action came from), after a correction is submitted, approved, rejected or withdrawn on the Key dates card (to Correct received date, or the card's title), on each save of the accessible-format card (back to the tick, switch or date), after Release these values as they are…, Use this verification, an assignment's plain Submit, Raise finding and the audit closure actions, after removing a recommendation, an evidence link or a contact (to the next row, else Add), after Add value, Done or Cancel in a scale editor, after Clear filters (to the first filter; the empty list's button to Filters), after a dismissed announcement (to the next one) and after a follow-up row action (to that row, else the next). Two shared helpers do it: one puts focus on a control once focus has fallen to the page, never taking it from another control; the other keeps a self-disabling button focusable.
- 3.3.1: the date picker's messages were fixed on 2026-10-07 (Enter a date., the range named in the picker's format, a mistyped date answered with the format and an example); an incomplete Earlier rule on a request type stops Save with a message on the field; an audit's finding and evidence-request dialogs show their own errors.
- 4.1.3: the received-date correction's preview is announced from a polite region that is in place when the dialog opens; the package update's steps are announced with their names; the Risks tab announces its count once the list is complete; going over the bulk-selection limit, a portal delivery's Copy link (Copied) and saving the assistant history period (Saved and the period) are announced.
- 1.3.1 (decided): the case panels' card titles — about seventy, in the sidebars and the card groups — are real headings (level 3 beside a tab's section headings, level 4 inside a card group; re-checked on dev — a request's Details tab now has twelve headings where it had two); every grid in the report sections is named by the heading above it (72 grids in 35 sections, and the rest the runtime pass found, below); a statistical template's section errors say where they are (Section 3 — Line 2: …); Threshold reached on the Conduct signals card is said in words as well as by its flag (re-checked on dev).
- 4.1.2 (confirmed and fixed): in the Lab library, the connector browser and the SharePoint picker each record row was a checkbox holding its Details button; they now sit side by side. A failed people or group search says the search failed, not No results, in the follow-up, section-user, group, bulk-reassign and training-role pickers.
- 3.1.1 / 3.1.2: where the page's culture has no AccessPoint language (Japanese, for example) the app shows English and is tagged English — its root, every panel and dialog and the error page; the English spelling options' sample words are marked English.
- 2.5.7 (decided): a modifier click needs a key, so it is not counted as the single-pointer alternative; the diagram toolbar has a Select several toggle with which a plain click adds a shape to the selection or takes it out (unit-tested; one new string in all eleven languages).
- Advisory: the administrator banners are no longer live regions announced on every load.
Runtime checks (2026-10-13). Method 15 lists what was scanned with axe, measured at 320 and 640 CSS px and walked from the keyboard; the reflow passes found no page that scrolled sideways and nothing past the viewport outside a container that scrolls on its own. What the pass found — all fixed and re-checked on dev unless it says unit-tested:
- 1.3.1 (axe best practice, empty-table-header): the … actions column of the Assessments, Incidents, Complaints and Audits dashboards, the Documents tab's selection column and the statistical reports' row-label column had no header text; each has header text now, hidden visually (Actions, Select document, the section's name), and the selection column's header does nothing, so it is not a stop.
- 1.3.1: the label-and-count tables of seven report sections — Volume & sources, Compliance & overdue, Extensions, Consultations & transfers, Assessments, Incidents and the complaints analytics — were unnamed grids; each is named by the heading above it (the shared table helper names a table by its label column when no heading is passed).
- 4.1.2 (axe aria-prohibited-attr, serious): the complaints report's month bars and age bands put their figures in an
aria-labelon an element with no role, which is never read; they are images named by those figures. - 2.4.3: a panel opened from a Training hub row returned focus, when it closed, to the row — gone with the hub — so focus
fell to the page, from every destination; the hub now hands focus to the Training button (at 768 px and narrower, the
header's More actions) before the panel opens, and a hub reopened from a panel's Training crumb returns focus there too.
(Fluent's Panel writes its own
elementToFocusOnDismissover the one in its focus-trap props, which the first fix used.) Log review outcome's Cancel on the Conduct signals card dropped focus to the page; it returns to the button. - 1.3.1 (axe best practice, heading-order): My training and Learning paths and progress went from the panel's title (level 1) to level-3 sections; the panel's title is level 2.
- 4.1.3: the Requests register's bulk bar showed its count without announcing it (the other registers' shared bar did); it uses the shared bar now.
Still open.
- About seventeen people pickers other than the five above still say No results when the search itself failed (3.3.1, 4.1.3; minor — a failure path).
- The dark-theme colours fixed on 2026-10-07 rest on computed ratios; the runtime pass ran in the light theme.
- Advisory: the diagram canvas (
role="application") carries no keyboard instructions until Details is open, and its colour swatches are named by their colour codes; a few focus moves after an action race the panel's own (Guide me following the person into a panel, from the Help panel). - Screen-reader passes over everything in this section — NVDA, JAWS and VoiceOver — and a session by a person who uses a screen reader daily.
AccessPoint Learning coach — How we decide and coach notes (built for 2.6.0, code-reviewed 2026-11-01)
Scope. The first surfaces of AccessPoint Learning (docs/UserGuide.md → How we decide and Our practice: coach notes), built for 2.6.0 and not part of the 2.5.0 release this report evaluates: the How we decide disclosure at the twelve coach points (a request's Details tab, the Add extension panel, the redaction side panel and the floating exemption picker, the fee estimate, the new consultation form, the Close request dialog, the assessment screener, the Risks tab, the Record decision dialog, each open breach notification, the complaint finding and each letter awaiting sign-off), and Settings → Training → AccessPoint Learning → Coach notes: the list of notes, the note editor, its Where it shows picker, the languages side by side and the block editor.
How it was evaluated. Method 17: a code review against WCAG 2.2 A and AA on 2026-11-01, with the unit tests named there. Needs a runtime or assistive-technology test (none has been run): an axe scan and a 320 px pass over an open disclosure (the case panels and the floating picker) and over the note editor; NVDA over the disclosure, the block editor's Move up / Move down and Insert link, and a refused save. Update 2026-11-12: the owner's NVDA pass on hosted stage heard How we decide at a decision point (method 26, SR-15); the coach notes editor and the axe scan and 320 px pass listed here are still open.
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| How we decide · 4.1.2 Name, Role, Value, 1.3.1 | Supports | A disclosure: a native button with aria-expanded and aria-controls pointing at a role="region" labelled by that button (aria-labelledby). The region is in the page while collapsed, with hidden, so aria-controls always resolves. Collapsed by default; it never opens by itself and is never modal. Inside, The rule and Our practice are headings. |
| How we decide · 2.5.3 Label in Name, 2.4.6 | Supports | The button's visible words are How we decide; its accessible name begins with them and adds the decision (How we decide: extending the deadline), so a speech user can say what they see and a screen-reader user hears which decision it is when several are on one screen. The panel's Help is named Help: How we decide. |
| How we decide · 2.1.1, 2.4.3 | Supports | Every action is a Fluent button reachable by Tab (open and close, Try again, Ask AccessPoint about this, Help, Hide coaching here). After Hide coaching here the button is gone, so focus moves to the line that replaces it (role="status", focusable), which says how to bring it back — focus never falls to the page. |
| How we decide · 4.1.3 Status Messages, 3.3.1 | Supports | While it loads, a spinner named Loading the guidance…; a failure is a warning message (The guidance could not be loaded.) with Try again; an empty panel and an option not yet chosen are said in text (There is no guidance for this decision yet., Make a choice above to see the rule for it.). |
| How we decide · 3.1.2 Language of Parts | Supports | A note shown in another language than the reader's (Not yet written in your language.) carries that language in lang. |
| How we decide · 1.4.10 Reflow, 1.4.11 | Supports | The region is ordinary flowing text; in the floating exemption picker it scrolls inside its own bounded area (at most 220 px high). The region's left border is decorative: the heading and the button carry the structure. |
| How we decide · 1.3.1 (advisory) | Supports | A note's own top-level heading is drawn at level 4, the level of Our practice; the notes the jurisdiction packs ship use paragraphs, lists and links. |
| Coach notes list · 2.5.7 Dragging Movements, 2.5.8 Target Size, 2.1.1 | Supports | Notes are reordered with Move up / Move down only (no dragging): 24 × 24 px buttons named with the note (Move up: <first words>); a button disabled at the top or bottom keeps focus (aria-disabled), and after a move focus returns to the moved note's button. Edit / View, Switch on / Switch off and Delete are named with the note too; Delete asks first. |
| Coach notes list · 1.4.1, 4.1.3 | Supports | Whether a note is on is text (Switched on / Switched off); a language it is not written in is listed in text (Not written in: FR), never only in colour. Saves, switches, moves, deletions and refusals are announced through a polite live region. |
| Note editor · 1.3.1, 3.3.2 Labels or Instructions | Supports | The editor is a dialog panel labelled by its title (New coach note — Extensions). Where it shows is a group labelled by its heading, with its rule in text (an empty list does not narrow; several lists must all match); each list is a labelled multi-select, and a code that is not listed is typed in a field labelled Another code for <list>, beside a button named Add: <list>. The languages are a fieldset whose legend lists the languages not yet written; each language is a section labelled by its heading (Français (FR)), marked Not written in text when empty. |
| Block editor · 1.3.1, 4.1.2 | Supports | Each language's text is a fieldset whose legend is the language; each block is a group named by its kind and place (Paragraph 2), with a labelled Block type dropdown and a text field labelled by the kind (Paragraph, Heading) or Item n in a list. A block the editor cannot change is shown read-only through the renderer with a message saying it is kept as it is. |
| Block editor · 2.1.1 Keyboard, 2.5.7, 2.5.8 | Supports | Blocks are reordered from the keyboard with Move up / Move down (the same 24 px buttons, named Move up: Paragraph 2, focus following the block); Remove block, Add item, Remove item n, Add paragraph, Add heading and Add list are buttons. Nothing needs dragging or a pointer. |
| Block editor · Insert link, 3.3.2, 2.1.1 | Supports | A link is written as [words](https://address) — the field's hint says so — or added with Insert link (named with its block, Insert link: Paragraph 2), which opens a modal dialog with two required, labelled fields, Link text and Web or email address, and inserts the link where the caret was in the block's field. Insert stays disabled until both are filled and the address is valid. |
| Block editor and note editor · 3.3.1 Error Identification, 3.3.3 Error Suggestion | Supports | A link that is not https: or mailto: is marked on its own field (aria-invalid, the message tied to the field and announced, Fluent's role="alert"), naming the address and what to change (A link must start with https:// or mailto:. Change: http://…); the Insert link address field says what it accepts. A save is held while such a link remains, with Fix the links marked below, then save again. When the server refuses a save, its words are put on the field they concern — an error message at the top of that language's editor, or on Where it shows — and a summary is announced at the top of the editor. |
| Note editor · 3.2.6 Consistent Help, 4.1.3 | Supports | The editor's header carries a Help button beside its close button, like the other panels; Unsaved changes is shown in text and the saving spinner is named. |
AccessPoint Learning — the Studio, the page editor and the module player (built for 2.6.0, code-reviewed 2026-11-01)
Scope. AccessPoint Learning's L2 surfaces (docs/UserGuide.md → The Studio: writing modules to Completion records, reminders and Team progress), built for 2.6.0 and not part of the 2.5.0 release this report evaluates: the module player; My learning with Browse, earlier cycles, the mentor's Waiting for you and the learner landing; the Studio — the Modules tab, the module editor (save status, the step outline, the step editors, Check and its findings, Preview as learner, the publish dialogs), the Learning paths tab with Who is enrolled (audience rules), the Assets tab and picker, the Translations tab and the overlay editor for pack modules; and the page editor host (ModuleEditorHost) with the page editor it frames.
How it was evaluated. Method 18: a code review against WCAG 2.2 A and AA on 2026-11-01, with the unit tests named there, plus the page editor's automated axe scan and keyboard test in a headless browser. Needs a runtime or assistive-technology test (none has been run; owner-run): NVDA over the player (the outline, Next and the focus on the step heading, the progress announcement, I confirm, the Reflect note), the Studio's outline, findings and save status, the page editor inside the Studio (Alt+F10, Escape out of the frame, the image dialog), and the Translations tab; an axe scan and a 320 px pass over the player, My learning and the Studio. Update 2026-11-12: the owner's NVDA pass on hosted stage covered My learning, the module player and Mark done (SR-16), the Studio's findings on their fields (SR-24) and a module written in French (SR-32) — method 26; the page editor, Assets, the overlay editor, the Translations tab and the runtime scans listed here are still open.
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| Player · 1.3.1, 4.1.2, 2.4.6 | Supports | A dialog panel whose title (the module's) is a level-2 heading. The steps are a nav named Steps holding an ordered list of native buttons named Step n: Kind (with Your organization, Optional or does not count where they apply) and — done / — not done in visually hidden text; the tick icon is hidden from assistive technology and the current step carries aria-current="step". The step is a section labelled by its h3 (Step n of N: Kind); a step's document headings start at level 4. Tests: the outline is a list of named buttons with their ticks…. |
| Player · 2.4.3 Focus Order, 2.2.2, 4.1.3 | Supports | Back, Next and an outline button move focus to the step's heading (tabIndex=-1); nothing moves on by itself — only Next or Finish; the progress ({n} of {m} steps done, and You have finished this module.) is a polite role="status" region, the bar beside it hidden from assistive technology. Tests: Next moves focus to the step heading, progress is announced politely, and nothing moves on by itself. |
| Player · 2.3.3, 2.2.2 | Supports | With prefers-reduced-motion the panel opens and closes without its slide (read once when the player opens). Test: opens without its slide when the person asked for reduced motion (it checks the marker, not the styles). |
| Player · 2.4.6, 2.5.3, 3.3.2 | Supports | Every action is a text button: Mark done (offered only for File, Link, Talk to and — where its tour cannot run — Guide me), I confirm (described by the statement it confirms), Save my note, Open in Lab mode, Start the tour and Show me how (described by the tour or task), Open the file (described by the summary), a Link step's own words (described by Opens in a new tab). The Reflect note is a labelled field (Your note) whose description says only the learner can see it; a saved note is announced. |
| Player · 1.1.1 | Supports | A Look step's image and a page's images carry the author's alternative text (alt="" only for an image marked decorative, which the publish check requires one way or the other), in figure / figcaption; an image that cannot be shown says Image not shown: {alt}. |
| Player · 3.1.2 Language of Parts | Supports (fixed 2026-11-10) | The player's own words — the outline's names, the step heading, progress, Mark done, Back / Next — are in the reader's language, and only what the module says carries the module's language: lang on the summary, the objectives and the step's content (method 21 — before, the whole player was marked with the module's language), and on the module's title in the panel's heading and the trail's last crumb (method 24 — they were unmarked, so a French title was read in the reader's voice; the player's own title, Learning module, stays the reader's). Since the polish pass the same holds INSIDE a step: I confirm, Your answer:, a check's rules and the renderer's own words (a callout's label, Image not shown) are the reader's, while a check's questions, options, answers and feedback, a decision's options and reasons, the Link step's words, the Look step's image, the Practise case's title and its scenario's step titles carry the module's. An Acknowledge statement carries its own. The fallback itself is said in text (This module is not written in {X} yet, so it is shown in {Y}.). An accessible name or description built from the module's words (a File step's summary describing its button) is read in the name's language: ARIA gives a name no language of parts. Tests: shows the module in the default language with a note…, marks only the module's own title with its language…, CheckDecideSteps.test.tsx, PractiseStep.test.tsx. |
| Player · 2.4.3, 3.3.1, 4.1.3 | Supports (fixed 2026-11-10) | After Mark done, I confirm and Save my note focus returns to the control pressed when it is still there and available (a refusal), else moves on to Next — it fell to the page before (method 21); a failed Acknowledge or Reflect write is announced once, by the step (it was announced twice); a load failure is a warning (role="status") with Try again. The file preview opened from a File step is still titled Open the file, not the file's name (no learner route names an asset yet; advisory, 2.4.6). Tests: keeps focus in the player after Mark done and I confirm…, announces a refused acknowledgement once…. |
| My learning · 1.3.1, 2.4.6, 4.1.2 | Supports | Your learning paths, each learning path (a section with its heading), Browse and Waiting for you (n) are headed sections; the modules, the other items and the earlier cycles are named lists (Modules of {title}, Earlier cycles of {title}); Finished (n) and Earlier cycles (n) are native details / summary, collapsed by default; Show the other items (n) is a button with aria-expanded. Start / Continue / Review, Open and Confirm are described by their module or learner (aria-describedby). Status, due, Overdue and Valid until are text; a tick is hidden with done / not done in text. A mentor's confirmation is announced (Confirmed for {name}.). Tests: shows each learning path…, shows the earlier cycles…, a mentor sees exactly the steps waiting for them…; the landing is a region headed at level 2 (LearnerLanding.test.tsx). |
| My learning · 2.4.3, 3.3.1 | Supports (fixed 2026-11-10) | After Confirm the item and its button leave the list and focus moves to the next learner's Confirm, else the one before, else the next control; a Waiting for you list that cannot be read says so with Try again (it showed as empty); a failed Show the coaching I hid again says so in an alert, and after it works focus moves on (method 21). Tests: a mentor sees exactly the steps waiting for them…, says the Waiting for you list could not be read…. |
| Studio · 1.3.1, 2.4.6 | Supports | A dialog panel (title at level 2) with tabs; the module editor's parts are headed (About the module — {language}, Steps, each step, Publish check, Preview as learner — {language}); module rows name their buttons with the module (Open: {name} — View: {name} where it opens read-only, fixed during this review —, Our practice: {name}, Duplicate: {name}, Retire: {name}); dialogs are titled and blocking. |
| Studio · 4.1.3 Status Messages, 2.4.3 | Supports (fixed 2026-11-10) | The save status is a polite role="status": Saving…, Unsaved changes, Saved at {time}, Not saved. Your changes are kept on this page.; a stale save is a warning (Saved by {name} at {time}. This page is read-only until you reload it.) with Reload, and the fields turn read-only. The check's summary (To fix before publishing: {e}. To consider: {w}.) is one polite status holding plain words (never a message bar, which would be a second live region), on the page — empty — before the first check, so the first result is said too; each Check says it again even when it is unchanged, while the re-check after a save is said only when it changes. Check, Preview as learner, Publish and Approve and publish stay focusable while they run (aria-disabled, Fluent's allowDisabledFocus) instead of dropping focus to the page (method 24 — the status was mounted together with its words, so the first Check could be silent, and the disabled button lost focus). The Translations tab's progress (Translating into {language} ({i} of {n})…) is a status region too. Tests: autosaves about four seconds after an edit…, refuses a second tab's stale save…, keeps focus on Check while it runs, and says the summary once…. |
| Step outline · 2.1.1, 2.5.7, 2.5.8 | Supports | Steps are reordered with Move up / Move down only (24 × 24 px, focus kept on a disabled one), and after a move focus returns to the same button on the moved step; Duplicate and Delete (28 × 28 px) are named with the step; the selected step carries aria-current="step"; Add step is a labelled dropdown (Kind of step). Test: reorders the steps from the keyboard and gives focus back to the moved step's button. |
| Step outline · 2.5.3, 1.4.1 | Supports (fixed 2026-11-10) | The move buttons are named with the step's visible label (Move down: 1. Reflect — One; they carried the step's internal key), and the per-step badge says its severity in words (2 to fix · 1 to consider), its colour only repeating it (method 21). Tests: reorders the steps from the keyboard…, an author builds a five-step module…. |
| Findings · 2.4.3, 3.3.1, 3.3.3 | Supports (fixed 2026-11-10) | Each finding is a button reading To fix: or To consider:, its step, field and language, and what to change; selecting it switches to that language and step and focuses the field. Each finding is also its field's description, read with it, and a finding to fix marks the field aria-invalid (Fluent's invalid, without an alert — the check's summary is the one announcement; a finding to consider never marks it): text fields (method 21), and since the polish pass the module's title, summary and objectives, a document field (the block editor's group and its text boxes), the dropdowns, a check's questions and a decision's options. The overlay editor's list of refused findings says To fix / To consider in words. A finding about a step's kind has no field: selecting it opens the step. Tests: an author builds a five-step module… fixes a finding on an image without alt text and publishes, fields.findings.test.tsx, puts a finding on the module's title ON the title. |
| Step editors · 3.3.2, 3.3.1 | Supports | Fields are labelled (required ones marked); a Link step's address that is not https: says Use a secure address that starts with https://. on its field (aria-invalid, announced), and an audience rule's group id is checked the same way; the Look step's alternative text is required with a hint, and the link-text hint warns against click here. A step of a kind this version cannot edit is read-only with a message saying it is kept as it is. |
| Studio · 3.1.2 Language of Parts | Supports (fixed 2026-11-10) | Text written in another language than the interface's carries that language: the module's title, summary and objectives, every step text box and the block editor's text boxes while Writing in another language, and the Translations tab's source words and translation fields (method 21 — none carried lang before, which this row recorded as Does not support); their labels stay in the interface's language. Preview as learner has the preview's lang. Tests: Studio.test.tsx (the title while writing in French), TranslationsTab.test.tsx (lists every text of the draft by language…: the source in English, the field in German). |
| Assets · 1.4.1, 3.3.2 | Supports | A file's scan result and conversion state are text (Being scanned, Scanned: clean, Malicious — remove it, Could not be scanned, Converting…), in the row and in the picker, whose choices are a labelled group (The module's files); Delete: {name} is named. A file in use cannot be deleted: its Delete is disabled without staying focusable, the reason only in a tooltip (advisory). Not covered by a unit test. |
| Translations · 1.3.1 | Supports | The languages table has a caption, column headers and a row header per language; each language's state is text. Each text is a section headed by its name, with the default language's words beside the field (In {language}) and Not written in this language yet in text. Tests: lists every text of the draft by language with its state…, Translate missing saves the page first…. |
| Audience rules · 1.3.1, 2.4.6, 1.4.1 | Supports | A headed section with a Help button; each rule's kind, key, due-after, start and Last read by the sweep in text, its state written out and an inactive rule's reason in words; Switch off: {rule} and Delete: {rule} are named. Test: shows why a rule enrols nobody (directory-off)…. |
| Overlay editor · 2.4.3, 4.1.3 | Supports | Opening a block's editor moves focus to its heading (tabIndex=-1); a block that is on shows the warning This block is switched on: your changes show to learners as soon as you save.; actions are named with the block or step (Add our practice after: 2. Reflect — How?); dialogs (re-anchor, delete) are titled; on / off is text. After Save or Cancel focus returns to the button that opened the editor (fixed 2026-11-10, method 21; it fell to the page). Tests: shows the pack's steps read-only and adds a step…, warns before an author edits a block that is on…. |
| Page editor host · 4.1.2, 2.4.3, 2.1.2 No Keyboard Trap | Supports | The frame is named by its title (Page editor — {language}); while it opens, Opening the page editor… is a status, and after 30 s without the page — or for an address that is not http(s) — The page editor could not be opened. is an alert. Escape in the page hands focus to a visually hidden End of the page editor just after the frame; after an image, file or term picker the host gives the frame focus back; Tab and Shift+Tab are used only for table cells and list levels and otherwise leave the frame. Tests: ModuleEditorHost.test.tsx (takes focus back when the author leaves the page with Escape…, says the editor could not be opened…, focus() gives the frame focus…). |
| Page editor · 4.1.2, 2.1.1, 3.3.1, 1.1.1 | Supports | The editing area is a labelled multi-line role="textbox" (Page content) described by the keyboard help, with the content's lang; the toolbar is a role="toolbar" with one tab stop (arrow keys, Home / End, Escape back), every control named, toggles with aria-pressed, disabled ones focusable. Alt+F10 reaches the toolbar; shortcuts cover bold, italic, code, link, paragraph and headings, lists. A refused change (the size limit, a block that cannot go in a table) is announced in a polite status region; an image without alternative text says so on the page; the link dialog marks a bad address aria-invalid. PageEditorBrowserTests: no axe violation at WCAG 2.2 AA (with and without the image dialog), and every node and mark made from the keyboard alone. A dropped or pasted file is refused without an announcement (advisory). |
AccessPoint Learning — checks, certificates, reports and the L3 screens (built for 2.6.0, code-reviewed 2026-11-03)
Scope. AccessPoint Learning's L3 surfaces (docs/UserGuide.md → Checks and decisions, Certificates and verification, Recertification, Training reports, Content quality and the link check, Glossary and obligations, Training done elsewhere, Audience rules, How we decide and Training cases), built for 2.6.0 and not part of the 2.5.0 release this report evaluates: the player's Check, Decide and Exercise steps (the Exercise's model answer included) and their Studio editors; Your certificates in My learning, Verify a certificate, and a training lead's Revoke certificate, More attempts and certificate download in Team progress; recertification and Team progress's Overdue, Expires and Certified columns with the check results; Reports → Training coverage; the Studio's Quality tab with Check now; the Glossary and Obligations tabs, the term picker and a glossary term in a learner's page; Training done elsewhere; the Suggested by the jurisdiction pack list under Who is enrolled; How we decide's Learn more with the coach note editor's Linked modules; and the model answer under a training case's guide in Lab mode. Settings → Training (TrainingLeadSection) only hosts Team progress and adds nothing of its own.
How it was evaluated. Method 19: a code review against WCAG 2.2 A and AA on 2026-11-03, with the unit tests named there, which find the controls by role and accessible name; no Jest test of these surfaces runs axe. Needs a runtime or assistive-technology test (none has been run; owner-run): NVDA over a Check (the question groups, the numbered selects, and whether the result's announcement and the focus on its heading are both read), a Decide commitment and its comparison, a glossary term in browse and focus mode (whether its definition is read as the description when focus lands, since the description is set as the tooltip opens), Verify a certificate, Team progress's new columns and buttons with table navigation, and the Training coverage grids; an axe scan, a contrast check (the attention colour, Right / Not right, the red Training Lab line) and a 320 px pass over the Check and Decide steps (the comparison is laid out to wrap), Your certificates and Verify a certificate, Team progress with its three new columns, the Training coverage report, the Quality, Glossary and Obligations tabs and their dialogs, and the Training done elsewhere dialog. Update 2026-11-12: the owner's NVDA pass on hosted stage covered a Check with Try again and the last attempt (SR-17), a Decide step (SR-18), the certificate and Verify a certificate (SR-19) and a Glossary refusal (SR-25) — method 26; the other screens listed here and the runtime scans are still open.
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| Check step · 1.3.1, 4.1.2, 2.1.1, 2.5.7 Dragging Movements, 2.2.1 Timing Adjustable | Supports | Each question is a fieldset whose legend gives its number and words (Question n of N: …); one right answer and true or false are native radio buttons, several right answers check boxes (Choose every right answer.), and an order question a native select per item, labelled by the item's words, with its rule in text (Number each item from 1 (first) to {n} (last). Use each number once.). Every control is in the tab order (radios by the arrow keys within their group); nothing is draggable and no element listens for a drag; there is no timer, and the rules say so before the questions (To pass, answer 80% of the questions correctly. There is no time limit.), with a limited check's attempts in the language's own plural forms (You may try once., You may try 2 times. — it said 1 times until method 24). In the Studio's preview the controls are disabled, with Learners answer here…. Tests: is answered with the keyboard alone — radios, check boxes and numbered selects, no timer and no drag handler, says how many attempts a limited check allows in the language's plural forms…, in the Studio's preview shows the questions without a way to answer; plural.test.ts (the eleven languages). |
| Check step · 2.4.3, 4.1.3, 1.4.1 (the result) | Supports | After Check my answers the result is announced once in a polite role="status" (You scored 50%. 80% is needed to pass. Attempts left: 2.) and focus moves to the result's heading (Not passed yet — 50%, tabIndex=-1); the questions follow in an ordered list, each saying Right or Not right in words (the colour only repeats it), Your answer: …, The right answer: … and the author's feedback per option. A check passed earlier (You passed this check with {n}% on {day}.) and one with no attempt left (You have used every attempt this check allows. The person who assigned this training can give you more attempts.) say so in text, without a form; a refused submission is an alert. Tests: announces the result to a screen reader, moves focus to it, and shows each right answer with the feedback, says a passed check stands and a check with no attempt left cannot be answered. |
| Decide step · 1.3.1, 3.3.2, 2.1.1, 2.2.1 | Supports | The case and the question come first; one choice is a radio group labelled Choose what you would do, several a fieldset whose legend is Choose what you would do (one or more); the reasons are a labelled field (the author's prompt, else Your reasons), marked required when the step requires them, up to 2,000 characters. Submit my decision stays disabled until the step's rule is met, and the line above it says what submitting does (Once you submit it, your decision is final and the model answer appears beside it. Only you see your decision.). No timer and no dragging. Test: asks for the reasons when the step requires them. |
| Decide step · 2.4.3, 4.1.3 (the comparison) | Supports | After Submit my decision the comparison is announced politely (Your decision is recorded. The model answer is shown beside it.) and focus moves to its heading (Compare your decision with the model answer); Your decision and The model answer are two sections named by their visible titles, side by side and laid out to wrap one under the other on a narrow screen (not measured); a failure to read the model answer is an alert. Opened again later, the comparison shows without taking focus. Tests: commits the choice and the reasons — final — and only then shows the model answer beside the learner's own, opened again after the decision reads the person's own commitment beside the model answer. |
| Check and Decide · 3.3.4 Error Prevention (test responses) | Supports (fixed 2026-11-10) | Both are test responses. Every question and choice is on one form, editable until it is submitted, and the page says beforehand what submitting does (the check's pass mark and the attempts allowed; Once you submit it, your decision is final…). A check allows unlimited attempts unless its author limits them, and a lead can grant more (More attempts). A submission that cannot be repeated — a Decide commitment, or the last attempt of a limited check — is confirmed first in a titled dialog (Submit your decision?, Use your last attempt?) with Review my answers, and is sent once the dialog has closed and given focus back (method 21). Tests: asks before the last attempt a limited check allows…, commits the choice and the reasons — final —…. |
| Exercise step and the training case's model answer · 1.3.1, 2.4.6, 4.1.3 | Supports | The step names its training case in text (Training case: {title}); Open in Lab mode (Do the exercise again in Lab mode once done) is a named button, and what ticks the step is said in words (This step is ticked when you finish the training case. You cannot tick it yourself.). Before the case is finished the step says A model answer is shown here once you finish the training case.; after, the model answer is a section labelled by its level-4 heading (The model answer) with Open my training case in Lab mode and its hint, and a refusal is an alert. In Lab mode, once a case's guide is all done, the same model answers show under the guide in a section labelled by its level-4 heading, each under From your AccessPoint Learning module {title}. Tests: PractiseStep.test.tsx (once the case is done, reads the model answer and shows it beside a link to the learner's own case in Lab mode, says why when the server refuses…), TrainingCaseBanner.modelAnswers.test.tsx (reads the model answers once the guide is all done and shows them under the guide). |
| Studio — Check, Decide and Exercise editors · 1.3.1, 3.3.2, 1.4.1, 2.5.7, 2.5.8 | Supports | Each question is a fieldset named Question n (focusable, so a finding can lead to it) with a labelled Kind of question dropdown, a required The question and an ordered list named Options of question n: each option has its words (Option n, or Place n in an order question), a The right answer check box (a radio group for true or false) and its feedback with a hint. The pass mark, Limit the attempts and Shuffle questions and options for each attempt are labelled, with A check has no time limit… in text; while writing another language, a message says the questions, options and right answers are set in the default language. The right answer and the model answer's choice are a checked control as well as a green border. Questions and options move with Move up / Move down icon buttons (32 × 32 px) named Move question 2 up, Move option 3 up, beside Delete question n and Remove option n — nothing is dragged. The Decide editor opens with its fiction rule (Write a fictional case: made-up names, example.com addresses and 555-0100 to 555-0199 numbers…) and asks for the reasons through a labelled radio group (The learner's reasons); the Exercise editor's Training case dropdown marks a private pack's case — Lab only and one that cannot be opened — not available now in words. Tests: CheckDecideEditors.test.tsx (adds a question with two options and one right answer…, marks one right answer of a single-choice question and moves options with buttons, never by dragging, places a finding on its question), PractiseEditor.test.tsx. |
| Your certificates · 1.3.1, 4.1.3, 3.3.1, 3.3.4, 2.4.3 | Supports (fixed 2026-11-10) | A section headed Your certificates (level 3 in My training, level 2 on the learner landing) holding a named list; each certificate's learning path, days and Name on the certificate: {name} are text, and a revoked one says This certificate was revoked and can no longer be downloaded. Get the certificate and Download certificate are described by the learning path. Get the certificate opens a blocking dialog, Confirm the name to print, which says the name is confirmed once and cannot be changed; Name to print is labelled, required, pre-filled and limited to 200 characters, and an empty name or a refusal is put on the field (Fluent's errorMessage: aria-invalid, described by the message, role="alert") with focus moved to the field before the message renders, so the field is read and then its error (method 24 — focus stayed on Confirm and get the certificate, or fell to the page after the server's refusal, the button being disabled while it waited). While a certificate is prepared, Preparing your certificate… is a polite status; a download is announced (Your certificate was downloaded.); a failure is a warning with Try again. Tests: CertificatesList.test.tsx (lists each certificate with its days and the action it allows — get, download, or none once revoked, asks for the name to print once, pre-filled from the directory, then issues and downloads the certificate, refuses an empty name in the dialog and words the server's refusal, puts a refused name on its field and moves focus there…). |
| Verify a certificate · 1.3.1, 2.4.3, 4.1.3, 1.4.1 | Supports | A panel (title at level 2) with a labelled Verification code field and Verify in a form, so Enter submits; the link a certificate prints verifies at once. The result is in one polite role="status" region and focus moves to its Result heading; the state is a sentence (Valid, Expired — it was valid until {day}, Revoked on {day}, or that the record is no longer held), its icon hidden from assistive technology and its background colour only repeating it; what the certificate prints is a table with a row header per fact (Name, Learning path, Completed on, Valid until, Modules). Tests: CertificateVerify.test.tsx (shows only what the certificate prints and its state, announced and focused, says revoked on its day, and no longer held with nothing else). |
| Team progress and recertification · 1.3.1, 1.4.1 | Supports | Overdue, Expires and Certified are column headers (scope="col") of the same captioned table, and each cell is a word, a date or a dash — Overdue; the last valid day or Expired {day}, with · recertifying on an open recertification; Certified. A module's cell adds the check results the organization's results setting lets the reader see (Passed / Not passed yet, Score n%, Attempts: n), and the CSV carries the same words. In My learning an open recertification is a line of text under its learning path (Recertification: complete this learning path again by {day} to keep your completion.). Tests: TrainingProgressSection.academy.test.tsx (shows overdue, expires and certified beside each row when they are served), TrainingProgressSection.results.test.tsx (shows nothing under LearnerOnly, passed or not yet with CompletionAndPass, and the score and attempts with Results), MyLearning.recertify.test.tsx. |
| Team progress — Revoke, More attempts, downloads · 2.4.6, 3.3.2, 3.3.4, 4.1.3 | Supports | Revoke certificate, More attempts, Download certificate and Training done elsewhere are text buttons in the person's row (whose header is the person), described by the person and, except Training done elsewhere, the learning path. Revoke asks first in a blocking dialog (Revoke this certificate?) that names both, with a required, labelled Reason (up to 1,000 characters); More attempts names the check in words ({module} — step {n}: {used} of {allowed} attempts used; a labelled radio group, Which check, when there are several), a labelled spin button, How many more attempts (1–10), and a required Reason. Each outcome is announced politely (The certificate of {name} was revoked. They were told why., {name} can try the check again: {n} attempts left., … The download is recorded in the audit trail.); an Administrator's Record training done elsewhere first asks for the person in a labelled picker. Tests: TrainingProgressSection.certificates.test.tsx (revokes a certified row's certificate with a required reason, then says so and reads the columns again), TrainingProgressSection.d7.test.tsx (grants more attempts on a used-up check with a required reason (OD-81), downloads a person's issued certificate for the lead (OD-89), opens the picker for an Administrator, and the dialog for the person chosen). |
| Training coverage report · 1.3.1, 2.4.6, 1.4.1 | Supports | A report panel with no period selector (a state report) and a note on what it counts (As of {day}. A person counts once per learning path…), the shared KPI cards, and three grids under level-3 headings — By learning path, By audience, People — each a Fluent DetailsList named by its heading. Counts are numbers; Overdue, Expired and Revoked figures above zero are also bold and in the attention colour, which only repeats the column's name; a person's state is a word (Overdue, Revoked, with · Recertifying), and an audience is named in words (Assigned by a lead, Named people, a rule's own words). The Checks and Score columns appear only under the results setting that allows them. Tests: ReportTrainingCoverageSection.test.tsx (shows the totals, each curriculum, each audience and the people the reader leads, as of today, adds passed / not yet passed under CompletionAndPass and the score under Results). |
| Studio — Quality tab · 1.3.1, 1.4.1, 2.4.3, 4.1.3 | Supports | Labelled dropdowns choose the module, version, learners and period; the summary is a description list (Learners, Completed, Median attempts at the checks); Questions, Decisions, Links and Languages are sections under level-3 headings, each question or decision under a level-4 heading (Step n, question m) with its rates in words and a table of its options (column headers, the option as the row header, Right answer or Model answer in words); too few learners is said in text (Too few to show…), and each dead link gives its address and what failed in words. Check now is described by its hint and keeps focus while it runs (allowDisabledFocus); Checking the links… and the outcome (Links checked: {n} links, {d} dead.) are said in a polite role="status", the figures reload around the button without removing it, and a refusal says when to try again (… Try again in {n} minutes.). Tests: QualityTab.test.tsx (shows the figures, the questions with the right answers, the decision without reasons, the dead links and the languages, checks the module's links now, reloads the figures, and says when to try again after a check too soon (OD-67)). |
| Studio — Glossary and Obligations tabs · 1.3.1, 4.1.2, 4.1.3, 3.3.4 | Supports | Each tab's list is a table with a visually hidden caption, column headers and the term or obligation as the row header; From says Your organization or Pack: {code} in words, and an obligation switched off says · switched off beside its title. The Shown / Counted switch is a Fluent toggle (role="switch") named with its row (Shown: {term}), Yes / No beside it, and plain text for a reader who cannot change it; Edit / View and Delete are described by the row, and Delete asks first. Saves, deletions and switches are announced politely. The editor is a titled, blocking dialog (New term) with labelled fields — Code with its rule as the description — and a fieldset per language whose legend is the language's own name; a pack's entry opens read-only with a message saying why. Tests: GlossaryTab.test.tsx (lists the pack's terms read-only beside the organization's and saves a new term with its words and definition per language, opens a pack's term read-only — no Save), GlossaryTab.d7.test.tsx. |
| Glossary term in a page · 1.4.13 Content on Hover or Focus, 2.1.1, 4.1.2, 2.5.8 | Supports | The marked words are a native button in the running text (dotted underline, aria-expanded); focus, a click or a tap shows the term and its definition in a role="tooltip" that describes the button while it is open and never takes focus. It stays until focus leaves or the person presses Escape, which closes it without moving focus (dismissible, persistent); it does not open on hover. As a target inside a sentence it falls under 2.5.8's inline exception. A term switched off or missing keeps its words as plain text. Test: GlossaryTermMark.test.tsx (shows the definition on focus, keeps it on a tap, and hides it on Escape and when focus leaves). |
| Training done elsewhere · 1.3.1, 3.3.2, 1.4.1, 4.1.3 | Supports | A blocking dialog titled with the person (Training done elsewhere — {name}). The records are a list named Recorded training, each with its provider, days and basis in words (certificate checked / recorded), who checked and who recorded it, and Edit / Delete described by its title; an unchecked Training Lab certificate is said in words (A Training Lab certificate counts toward a learning path only once a lead has checked it.), not by its red colour alone. The form's fields are labelled (the title, the provider and Completed on required; native date fields); a Training Lab link brings a message with Open the link and the check box I checked this certificate; Delete asks first inside the dialog; saves and deletions are announced politely. Tests: ExternalCompletionDialog.test.tsx (lists a person's records with who checked the certificate, and records a Training Lab certificate the lead checked by hand, says why a lead may not record for this person), TrainingProgressSection.external.test.tsx. |
| Suggested audiences · 1.3.1, 2.5.3, 4.1.3 | Supports | Under Who is enrolled, Suggested by the jurisdiction pack is a section labelled by its heading (level 5), with its rule in text (Nobody is enrolled until you switch a suggestion on…); each suggestion is a list item naming the audience in words; one already taken says Already a rule of this learning path., and one the organization cannot use says why, with no button. Switch on is named Switch on: {audience} — the visible words first — and the outcome is announced politely (Switched on: the rule was added below…). Test: CurriculumEditor.test.tsx (lists the pack's suggested audiences, switches one on with one click as an ordinary rule, and never applies one by itself (OD-138)). |
| How we decide — Learn more · 1.3.1, 2.5.3, 4.1.2 | Supports | Inside the disclosure, Learn more is a level-4 heading over a list of the modules linked to the note; each is a Fluent link without an address (a button) whose visible words are the module's title and whose name adds what it does (Open the module {title}, containing the visible words); About {n} minutes and You've done this lesson are text, the tick hidden. It shows only where the player can open (with the learning features, and never on the compact floating picker). Tests: CoachLearnMore.test.tsx (lists the linked modules the server offers — minutes, You've done this lesson — and opens the player by the module's code, shows no Learn more on the compact floating picker…). |
| Coach note editor — Linked modules · 1.3.1, 3.3.1, 2.5.8 | Supports | A fieldset with legend Linked modules and its hint (… At most five.); the linked modules are a list, each with Remove named Remove {title} ({code}) (24 px high); Add a module is a labelled dropdown, disabled at five with A note links to at most five modules. Remove one to add another.; a module not published or switched off says so in words; the API's refusal is put on the dropdown (aria-invalid, described by the message, role="alert"). Tests: names each linked module, removes one by a button that names it, and adds another from the organization's modules, places the API's refusal of the links on the field. |
| Focus after an action · 2.4.3 | Supports (fixed 2026-11-10) | Every action this row listed on 2026-11-03 now gives focus back to its control or moves it to the next sensible one (method 21): Try again on a check → the check's rules above the new questions; the Studio's question and option Move up / Move down → the moved item's same button, which keeps focus when it turns unavailable (allowDisabledFocus); Confirm and get the certificate and a download → the certificate's Download certificate; Team progress after a revocation, a grant, a withdrawal or This completion stands → the person's row (the table stays on show, aria-busy, while it is read again); Training done elsewhere → the form's first field, Delete (described by its question) or Record training as its views change; a suggestion's Switch on and a linked module's Remove → the next one, else on; the Shown / Counted switches stay enabled while their change is saved. Tests: CheckDecideSteps.test.tsx, CheckDecideEditors.test.tsx, TrainingProgressSection.certificates.test.tsx, ExternalCompletionDialog.test.tsx. |
| Errors on their fields · 3.3.1 (advisory) | Supports (fixed 2026-11-10) | Method 21: This number is used twice. describes its select; a Studio text field's findings are its description; an empty verification code is the field's error (aria-invalid, described, focused); Training done elsewhere moves focus to the first required field left empty; in the Revoke and More attempts dialogs only the reason's own refusal goes on Reason — any other is a message above it. The polish pass: every Studio field with a finding to fix is marked aria-invalid and described by its findings (the Findings row); the Glossary and Obligations editors' refusals are their field's error and the field takes focus — the code, the regime, the source, a language's missing term, definition or title, a code already taken (409), and a refusal naming a language inside that language's group; only a refusal that names no field stays at the top of the dialog. Tests: GlossaryTab.test.tsx. |
| Names, labels and announcements · 1.3.1, 2.4.6, 3.3.2, 4.1.3 | Supports (fixed 2026-11-10) | A check question whose words are a formatted document is described by them (it was a group named only Question n of N); in the Studio each option's The right answer (option n), Feedback on option n (Why it goes in place n) and The model answer's choice (option n) carries its number; the term picker's search has a visible label (Find a term) and the number of terms that match — or No term matches… — is announced politely (method 21; the term picker still has no unit test). Tests: ties "This number is used twice" to its select…, marks one right answer of a single-choice question…. |
| AccessPoint Learning L3 · 3.1.2 Language of Parts | Supports (fixed 2026-11-10) | A glossary definition carries its language (lang on the tooltip); a check, a decision and an Exercise in the player take the module's lang where the module speaks; the Studio's check and decision fields carry the language being written (method 21). Since the polish pass the Glossary and Obligations editors' labels (Term, Definition, Title) are in the interface's language while each language's legend (its own name), text boxes and formatted definition carry that language; a term's or an obligation's words in the tables, taken from another language when the reader's is missing, carry it; and under a training case's guide From your AccessPoint Learning module {title} is in the reader's language with only the title, and the model answer, in the module's. A term inside an accessible name (Shown: {term}, an Edit or Delete button's description) is read in the name's language: ARIA gives a name no language of parts. Tests: GlossaryTab.test.tsx, TrainingCaseBanner.modelAnswers.test.tsx. |
Onboarding, read-only states, the marketing demo and the Training Lab (built for 2.6.0, code-reviewed 2026-11-07)
Scope. Surfaces built for 2.6.0 and not part of the 2.5.0 release this report evaluates. In the product (both editions unless named): the guided welcome dialog and the occasional user's inline Here's your task card (docs/UserGuide.md → the welcome); the hosted edition's session warning and signed-out notice (the criterion itself is 2.2.1 in Table 1); the read-only states — the licence read-only banner (a lapsed or revoked subscription), the Free plan's register banner, a read-only case's one line, a request recorded past the cap, the disabled New with its visible reason and the Reader view a read-only register's case opens in — and the privacy program hub on the Free plan. Beside the product, on Realizer's own hosts and built from the same shared UI: the marketing demo (demo.realizer.io — the welcome card, the Next steps pill, the Tours & pricing panel and the bar collapsed to Menu; docs/DemoDeveloperGuide.md) and the Training Lab (learn.realizer.io — the learner's one-box join with Is that you? and the e-mail code, and the instructor console's Show to the class, New resume code, the Live grid, Results and the New class wizard; docs/TrainingLabRunbook.md). The demo and the Lab are not part of a customer deployment; they are assessed here because the same people meet them before and beside the product.
How it was evaluated. Method 20: a code review against WCAG 2.2 A and AA on 2026-11-07, with the unit tests named there; the demo's surfaces are also scanned with axe-core in its Playwright run, and the welcome dialog with axe-core in Jest. Needs a runtime or assistive-technology test (none has been run): NVDA over the welcome (the heading focus on open, the starts' descriptions, the setup's live region), the session warning's threshold announcements, the read-only banners on a case page, the Lab's join form (the heading focus on each view, Is that you?, the e-mail code) and the Live grid's chips; an axe scan and a 320 px pass over the welcome, the read-only states and every Lab screen. Update 2026-11-12: the owner's NVDA pass on hosted stage heard the welcome dialog (SR-05), the session warning (SR-13), Here's your task (SR-21) and the Free plan's unavailable New (SR-23) — method 26; the Training Lab's screens and the runtime scans listed here are still open.
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| Welcome dialog · 1.3.1, 4.1.2, 2.4.3 | Supports | A Fluent modal labelled by its heading (titleAriaId); the heading takes focus when it opens (tabIndex=-1, the focus trap's first target), so a screen reader starts at the greeting; Fluent returns focus when it closes. Setting up your workspace, What's left to set up and Where would you like to start? are sections labelled by level-3 headings; the help links are a nav named About AccessPoint. Evidence: WelcomeDialog.test.tsx (labelled by its heading, which takes focus). |
| Welcome dialog · 2.1.1, 2.1.2, 2.5.3, 2.5.8 | Supports | Each start is a native button whose name begins with its visible title and whose one-line description (and, for a start that waits, the reason) is tied with aria-describedby; a waiting start is disabled and says why in visible text (Available once {pack} is in.). Escape and Not now close it; nothing traps focus beyond the modal. Targets are 24 × 24 CSS px or more. Evidence: the keyboard case of WelcomeDialog.test.tsx (every ready start focusable, Enter chooses it, Escape is Not now). |
| Welcome dialog · 4.1.3, 2.2.1, 2.2.2 | Supports | The first setup's steps (hosted owner, Microsoft 365 first Administrator) are a polite live region; Taking longer than usual… is a status, a failure a Fluent error bar with Try again, and a finished setup says Ready — refresh to see your configuration with Refresh — the page never reloads under the dialog. Nothing in it times out or moves; no animation beyond Fluent's own, none under prefers-reduced-motion. |
| Welcome dialog · 1.4.10, 1.4.3, 1.4.11 | Supports | At 640 CSS px or less it becomes a full-screen sheet whose content scrolls; above that it is at most 640 px wide and the viewport's height less 32 px. Colours come from the theme tokens only, so dark mode and high contrast follow (code review; not measured at runtime). Axe-core over the dialog in Jest (rules that need no layout) finds nothing. |
| Here's your task card · 1.3.1, 2.4.6 | Supports | A section named by its heading at the page's next level (h3, or h4 where the host asks), never a dialog, never over the work: Here's your task: search your records for this request and submit what you find.; the Get started steps are an ordered list; Show me and Got it are Fluent buttons. Test: WelcomeInlineCard.test.tsx (added 2026-11-10, method 21; axe-core finds nothing). |
| Here's your task card · 2.4.3 | Supports (fixed 2026-11-10) | Got it removes the card and the button with it; focus now moves to the first control after the card — it fell to the page (method 21). Test: Got it records the answer, removes the card and moves focus to the next control. |
| Session warning · 4.1.3, 2.2.1, 2.4.3 | Supports | A blocking Fluent dialog titled You’re about to be signed out (or Your session is ending), its countdown in the subtext; a visually hidden polite role="status" INSIDE the dialog (a modal hides what is outside it) announces the countdown at 60, 30 and 10 seconds only — never every second. Stay signed in is the primary button and Escape does the same; the absolute end's notice offers OK only, once. Fluent moves focus into the dialog and returns it. A failed Stay signed in is an error bar in the dialog. After the end, the signed-out notice is a warning bar saying why (You were signed out after {n} minutes of inactivity.) with Sign in again. Evidence: SessionTimeoutWarning.test.tsx (the thresholds, one activity call, the other tab), SessionSignedOutNotice.test.tsx. |
| Licence read-only banner · 1.3.1, 4.1.3, 3.3.2 | Supports | A Fluent severe-warning bar above every page that says why in one sentence with the date (AccessPoint is read-only: your subscription expired on {date}… / Realizer revoked this subscription on {date}…). An administrator's actions are text buttons (Renew the subscription or Contact Realizer, and Check again, disabled while it checks with Checking…); the check's result (Still expired — checked just now., Checked less than a minute ago…, a failure) is a polite role="status" inside the bar. Everyone else reads whom to ask, by name. Evidence: LicenseReadOnlyBanner.test.tsx. |
| Free plan banners and disabled New · 1.3.1, 3.3.2, 4.1.2, 1.4.1 | Supports | A read-only register's list carries an information bar (Read-only on the Free plan. Everything here stays to read and export. Choose a plan to add or change {register}.), with Choose a plan for an administrator and Ask an administrator to choose a plan. in the sentence for everyone else; a read-only case shows one line saying the same of the case, and a request past the cap a warning line (Recorded. The Free plan includes 5 requests a year; choose a plan to work on this one.). A New the plan refuses stays visible, disabled but focusable (allowDisabledFocus), with its reason as visible text beside it (Read-only on the Free plan. / Read-only until the subscription is renewed.) tied by aria-describedby — never a tooltip alone, never colour alone. The bars render nothing where nothing is read-only (an older API, the demo, Lab mode). Evidence: ReadOnlyRegisterBanner.test.tsx (the reason as visible text named by aria-describedby). |
| Reader view · 1.3.1, 3.2.4, 2.4.6 | Supports | A case of a read-only register — or every register while the licence has lapsed — opens as the same page a Reader sees: the person's context without the case-work permissions, so the editing controls are not rendered, under the case's one line explaining why. The page's structure, names and order are the ones a Reader already meets. Evidence: readerView.test.tsx. |
| Privacy program hub on the Free plan · 1.3.1, 3.3.2 | Supports | The hub carries the register's banner (… Choose a plan to add or change Privacy program.); its inventory follows the assessments rule, so on Free (5 assessments a year worked in full) New subject and New vendor stay available; when the assessments only read too — or the licence has lapsed — New is disabled and focusable with Read-only on the Free plan. (or the licence's reason) beside it, tied by aria-describedby. Evidence: ProgramHub.readOnly.test.tsx. |
| Demo welcome card · 1.3.1, 2.4.3, 2.1.1, 2.5.8 | Supports | A Fluent modal labelled by its heading and described by its lead (titleAriaId, subtitleAriaId); focus starts on the first role start; Escape, Close (an icon button named Close), Just let me explore or a press outside close it. The three role starts are native buttons, at least 64 CSS px tall, whose name reads their title, who it is for and what it does, in that order; Tours, pricing and proof is a link. The jurisdiction line says Running under {Act} · {n} business days to respond in words. Under Windows forced colours the starts keep a border. Evidence: axe-core over the welcome card and the welcome card at 390 px in e2e/funnel.spec.ts; noWelcome.test.tsx. |
| Demo Next steps pill · 1.3.1, 2.4.11, 2.5.3, 4.1.3 | Supports | A region named Next steps holding Book a live demo (on a phone over a panel a round button whose name stays Book a live demo) and a menu button named More next steps. It shows only while the bar's own button cannot be used, and showing or hiding (the hidden attribute) never moves the focus and announces nothing; it stays while it holds the focus or its menu is open. It covers only the bottom-left corner: the page keeps a gutter as tall as the pill so the last row scrolls clear, and over a panel it sits above the panel's footer, so a focused control is not hidden behind it (2.4.11). Copied after Copy a link is a polite status. Evidence: DemoCtaPill.test.tsx (visibility, focus held, placement over the viewer and panels); axe-core over the pill over a request in e2e/funnel.spec.ts. |
| Demo Tours & pricing panel · 1.3.1, 4.1.3, 3.3.2 | Supports | A Fluent panel titled Tours, pricing and proof (headerText), its close button named, light-dismissable; its parts are sections labelled by level-2 headings (tours grouped under level-3 headings), the trust strip a named list, the current tour marked aria-current. What it would cost is a labelled field with its hint, and its answer (the band and its yearly figure, or Enter a number of employees.) is a polite role="status"; Share this demo's copy result is a polite status. Evidence: axe-core over Tours & pricing at 390 px in e2e/funnel.spec.ts. |
| Demo bar collapsed to Menu · 4.1.2, 1.4.10 | Supports | At 500 CSS px or less the bar keeps its title and one Menu button with aria-expanded and aria-controls naming the part it opens (the notice, the jurisdiction chip and picker, Tours & pricing, Restart); nothing scrolls sideways. Evidence: axe-core over the bar's menu at 390 px in e2e/funnel.spec.ts. |
| Lab join form · 1.3.1, 2.4.3, 3.3.1, 3.3.2 | Supports | One form per view, each headed by a level-1 heading that takes focus when the view changes (or on an error), so a screen reader hears where it is; Enter submits every form (noValidate, the page's own checks). The class or resume code is one labelled field with its hint, upper-cased and dashed as typed, spell-check and auto-capitalizing off; a form-level error is an error bar with role="alert", a field's error is on that field (Fluent's message, announced). Is that you? is a warning bar (Someone called {name} has already joined this class. Is that you?) with two named buttons, Yes, I've joined before and No, join as someone new; status lines are a polite role="status". The notice is a disclosure button with aria-expanded / aria-controls. Evidence: join.test.tsx. |
| Lab join — the e-mail code · 3.3.8 Accessible Authentication (Minimum), 1.3.5 | Supports | The address field is type="email" with autoComplete="email"; the 6-digit code comes right after it, autoComplete="one-time-code", numeric input, pasteable — no cognitive test, nothing to transcribe from memory; Change email and Send the code again (a countdown before it is offered again) are buttons beside it; the name field is autoComplete="name". A device that joined before says Welcome back and asks only for the resume code (in an e-mail class, the address and its code). Evidence: join.test.tsx. |
| Lab course home — the instructor's code notice · 4.1.3, 2.2.1 | Supports | The one-time notice that an instructor gave the learner a new code is a dismissable warning bar whose close button is named; nothing on the course home times out. Evidence: courseHome.test.tsx. |
| Lab console — Show to the class · 1.1.1, 2.1.2, 1.4.4 | Supports | A full-window Fluent modal labelled by its level-1 heading; Escape or Close (named) returns, and full screen is left with it. The QR code is an SVG with role="img" named by the link it opens, and the same address is printed as text beside it, so nobody needs to scan. The class code is text, in large letters. Evidence: classCode.test.tsx. |
| Lab console — New resume code · 2.4.6, 3.3.4, 4.1.3 | Supports | Each learner's New resume code link is named with the learner, its visible words included (Give {name} a new resume code); a blocking confirmation asks first; the code is then shown once in a dialog titled with the learner, with Copy code and a polite status saying what was copied. |
| Lab console — the Live grid · 1.3.1, 1.4.1, 2.1.1 | Supports | A table with column headers (scope="col") and the learner as each row's header (scope="row"); each step's header is focusable and named Step {n}: {title}. A step's state is a chip — an icon and a visible word (Passed, Done, Not passed, Not confirmed) — exposed as an image named in words; an empty cell is named Not yet. A legend, a group named What the cells mean, explains each chip in words. Evidence: secondPass.test.tsx. |
| Lab console — the Live grid's names · 2.5.3 (advisory) | Partially Supports | The chips are not controls, so Label in Name does not bind them, but for two states the word read out differs from the word shown: Done is read Completed, Not passed Not yet passing, and Not confirmed is read as its full sentence. A screen-reader user and a sighted colleague talking about the same cell use different words. |
| Lab console — Results · 1.3.1, 1.4.1 | Supports | Each exercise is a section named by its title; the summary comes first: each step's bar is an image named by its counts in words (Passed 4, Not passed 1, Not yet 2), the visible counts beside it hidden from assistive technology (said once, not twice); the numbers follow in a table with column and row headers. How these are counted is a disclosure with aria-expanded. Evidence: secondPass.test.tsx. |
| Lab console — New class wizard · 1.3.1, 3.3.1, 3.3.4 | Supports | The steps are an ordered list with aria-current="step" on the current one; the step's heading says Step {n} of {N}: {name}; a date that is not valid, or a class longer than the workspace allows, is an error on the date field itself; the review lists every choice with Change named for the step it returns to (Change: {step}); Back keeps what was entered. Evidence: secondPass.test.tsx. |
| Lab console — New class wizard · 2.4.3 (advisory) | Partially Supports | Next and Back change the step without moving focus or announcing it: focus stays on the button, and the new step's heading is not read until the person moves to it. |
Added to the demo on 2026-11-10 – 11. The register welcome a register's guided link opens on (DemoSampleWelcome.tsx — the risks, incidents, complaints and audits samples), Tours & pricing's More of AccessPoint (one tour for each register the visit does not show) and Show every module, and the welcome card's line that moves focus to More of AccessPoint. Each is scanned with axe-core (WCAG 2.2 AA tags) in the demo's Playwright run: moduleTours.spec.ts (Tours & pricing offering every register and with every register, the audit tour on the contacts, the risks welcome, the audits welcome at 390 CSS px, Tours & pricing from the welcome card) and funnel.spec.ts (the welcome card). The scan now waits until the page has been still for two checks 150 ms apart (e2e/support.ts), so a row that fades in after its data arrives is not measured mid-fade — the release picker's state cell had read #908f8d mid-fade in 2 runs of 8. No screen-reader pass of these.
Rolling releases, dated settings, the Reports menu and AI deployments (built for 2.6.0, assessed 2026-11-10)
Scope. Surfaces built for 2.6.0 and not part of the 2.5.0 release this report evaluates: rolling releases (Documents → Releases: the releases and the release schedule, a release's index, Build the next release and its picker, the package options, Send release…; docs/UserGuide.md → Releases); dated settings (an exemption's and an extension reason's Available from / Available until, a fee schedule's Fee change on a date, an assessment type's Mandatory from); the Reports menu listing only the reports a person can open, and its pinned tile that says You don't have access to this report.; and Settings → Features & AI → AI Assist → Your own AI deployments.
How it was evaluated. Method 21: in a real browser through the marketing demo for the releases and the Reports menu (axe-core 4.14 at 1440 × 900 — the flows in English and French, the Releases sub-tab in all eleven languages — at 1366 × 768 and 320 CSS px, target size, the keyboard); in jsdom with axe-core and by code review for dated settings and AI deployments (not in the demo). Needs a runtime or assistive-technology test (none has been run): NVDA over Send release (the held release's warning, the delivery and letter choices) and the release picker; an axe scan and a 320 px pass of dated settings and Your own AI deployments on the dev tenant. Update 2026-11-12: the owner's NVDA pass on hosted stage covered the Releases tab, a release's index, the picker and Send release… (SR-20), redaction discussion (SR-22), a media mark's card (SR-27), the Reports menu (SR-28) and dated settings (SR-29) — method 26.
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| Releases · 1.3.1, 4.1.2, 1.4.1 | Supports (fixed 2026-11-10) | The releases, the schedule and a release's index are tables with column headers, each named (Release schedule, Index — Release 2); a release's state is a word (Built, not sent, Held until its instalment is paid.), a missed date is said in words (Release 2 was estimated for … and is 2 day(s) overdue.) and colour only repeats it. In the release picker each record's choice is a combo box named In this release: {record} and described by the notes under it — Already in Release {n}: it goes out again unchanged., or why the record cannot be chosen (method 24 — they were text below it, which a screen reader moving from control to control never heard; correction.test.tsx). axe-core finds nothing on the Releases sub-tab in all eleven languages, and on an index, Send release (held and ready), the picker and the package options in English and French (releases.spec.ts, releaseBuild.spec.ts, releaseAnyRequest.spec.ts, uxAudit.spec.ts). |
| Releases · 1.4.10 Reflow, 2.1.1 | Supports (fixed 2026-11-10) | At 320 CSS px the actions stack and nothing scrolls the page sideways. Found and fixed: a release's index scrolled sideways in an area no keyboard could reach (axe scrollable-region-focusable), the schedule pushed the whole Releases tab sideways, and the Documents toolbar's Create or upload ran past the panel's edge. Each table now scrolls in a named, focusable area of its own (the arrow keys scroll it), and the toolbar's buttons wrap. uxAudit.spec.ts measures it. |
| Releases · 2.1.1, 2.4.3, 2.5.8 | Supports | Send release and the release picker open with Enter and give focus back to their button on Escape; every control is 24 × 24 CSS px or has the spacing 2.5.8 allows, at 1366 and 320 CSS px (uxAudit.spec.ts). |
| Releases · 3.3.1, 3.3.4, 4.1.3 | Supports | A release that cannot be sent says why in a warning above the form (This release is held until its instalment … is paid. Record the payment, waive the instalment, or ask a senior official to send it anyway.); the product's refusals (one release in preparation, Choose at least one record, a date in the future) are worded; sending is one confirmed action that says what it does to the response date. |
| Releases · advisory | — | Since the polish pass (2026-11-10) each Bates number stays whole at narrow widths — a range wraps at its dash, never inside a number (measured at 320 CSS px in uxAudit.spec.ts); the release schedule's counts take each language's plural forms (1 day overdue, 2 days overdue; Polish's three forms) instead of day(s). The schedule's Told to the requestor column, a tick or nothing, says Yes or No since method 21. |
| Reports menu · 1.3.1, 2.4.6, 1.4.10 | Supports | The menu lists only the reports the person can open; a pinned tile the person can no longer open says so in words, with its menu to remove it. axe-clean at 1440 and 320 CSS px (reports.spec.ts, uxAudit.spec.ts). |
| Dated settings · 1.3.1, 3.3.2 | Supports (fixed 2026-11-10) | Available from / Available until are one group named Available whose explanation describes both dates (it was the second field's description alone); a fee schedule's earlier amounts — labelled like the current ones above them — are a group named Amounts for requests received before that day (the heading was styled text). Mandatory from has its explanation as its description. AvailabilityFields.test.tsx (axe included). |
| Dated settings · 3.3.1, 3.3.3 | Supports (fixed 2026-11-10) | A last day before the first is said on its field (The last day is before the first. Change one of them., aria-invalid, announced) and Save waits until it is corrected. |
| Your own AI deployments · 1.3.1, 2.4.6 | Supports (fixed 2026-11-10) | The section's title is a heading under its group's, and every group title of Features & AI is now a heading (they were styled text). Each lane's field is labelled with its hint; Test is named for its lane (Test the everyday deployment, the visible word first in most languages, and contained in every one); the result is a message in words (Answered by …, or why not). |
| Your own AI deployments · 1.4.3, 1.4.11 | Supports (fixed 2026-11-10) | Theme tokens only: the Deployed chip's text was a fixed hex that ignored the dark theme and now uses the theme's success colour. |
Hosted edition — the global entry, sign-up, organizations and hosted settings (built for 2.6.0, assessed 2026-11-10)
Scope. Surfaces built for 2.6.0 and not part of the 2.5.0 release this report evaluates, all on Realizer's hosted service (app.realizer.io; docs/hosted/README.md): the global entry (the region page, the chooser after the sign-in, Regions unavailable), the regional web host's own pages (You are signed out of AccessPoint, Sign-in did not complete, the 404), the live client's own screens (the sign-in and sign-up landings; Create organization with Data region, the Terms line, the colleague offers and Ask to join; Create another organization and its two kinds; the organization picker, the header's organization switcher and account menu; the invitation; Your session has ended and the organization dialogs) and the hosted parts of the application: the welcome's trial and Free lines, the trial banner, Extend 30 days, the Free plan's banner and read-only lines, the allowance banners and usage meters, the session warning, Settings → Features & AI → AI processing outside {geography}, Settings → Users & roles → Colleagues (Requests to join), Who can join and Signing out, Settings → Organization → E-mail (the Reply-To and its code) Settings → Public portal's plan line and portal address, and — hosted pricing P3, merged the same night — Settings → Subscription with Bundles and storage, the buy dialog and its one-click entry points (the allowance banners, the request's waiting line, the New assessment refusal).
How it was evaluated. Method 22: the live client and the server-rendered pages in a real browser (axe-core 4.14 with contrast, 1366 × 768 and 320 CSS px in all eleven languages, the server pages in both colour schemes); the application's hosted parts in jsdom with axe and by code review. Needs a runtime or assistive-technology test (none has been run): NVDA over sign-up, Create organization (the colleague offers, the jurisdiction search's count, the pack notice), the picker, the invitation, the session warning and Your session has ended, and the buy dialog's answers with the link to Stripe's invoice page; an axe scan and a 320 px pass of the banners, Settings' hosted sections and Settings → Subscription on stage. Update 2026-11-12: on hosted stage, in-page checks with the keyboard (2026-11-10) and a 320 CSS px reflow pass (three defects, fixed — method 25), and the owner's NVDA pass over the journey from the region page to signing out, Subscription and the buy dialog, AI processing outside Canada, the session warning and invitations (method 26, SR-01 – SR-14, SR-30).
| Surface · criterion | Conformance | Remarks and explanations |
|---|---|---|
| Global entry and the web host's pages · 3.1.1, 2.4.2, 1.3.1, 2.4.4 | Supports | Server-rendered, no script, in the visitor's language (lang from the sign-up link, else Accept-Language; the eleven) with <html lang> and a localized title; one main and one level-1 heading; the regions are a named list whose regions are level-2 headings with their residency lines as a list; every link names where it goes (Continue in Canada, Open AccessPoint in Canada, Try again). Evidence: HostedPagesAccessibilityTests (every page in every language), axe in the browser. |
| Global entry and the web host's pages · 1.4.3, 1.4.11, 1.4.10, 2.4.7 | Supports (fixed 2026-11-10) | The brand guide's colours in the light scheme and their own dark set, both measured by axe in the browser; forced colours keep borders. The focus ring is 2 px with an offset — in the dark scheme it kept the light ring's #006CBE, 2.9:1 on a dark card, and is now #7CC0F5 (8:1). Nothing scrolls sideways at 320 CSS px in any language. |
| Sign-in and sign-up · 3.3.8, 3.3.7 | Supports | Sign-in is Microsoft's identity platform through the web host (or the entry): AccessPoint asks for no password, code or puzzle of its own. What the demo or the region page chose (the jurisdiction pack, the language) travels to Create organization, which starts with it (the acknowledgement is never pre-ticked); Choose another region goes back with the same choices. |
| Create organization · 1.3.1, 4.1.2 | Supports (fixed 2026-11-10) | A form named by its heading; Data region is a read-only field with its explanation and Choose another region; the jurisdictions are a fieldset whose legend and hint name it, each country a group of radio buttons named by the country (the group wrapped its list's items, axe listitem — fixed), each radio named by its pack; the chosen one is said above the list (Selected: …, polite). The pack notice is a warning bar above its acknowledgement checkbox. Evidence: uxAudit.test.tsx, axe in the browser. |
| Create organization · 3.3.1, 3.3.2, 4.1.3 | Supports (fixed 2026-11-10) | Each field has a visible label and its hint as its description; an empty name is the field's error and takes focus, with Some fields need your attention. above; a refusal is an error bar in words (Organizations can't be created right now…). The search now says how many jurisdictions match (polite status). |
| Create organization · 2.4.3, 2.4.6, 3.1.2, 1.3.1 | Supports (fixed 2026-11-10) | Ask to join is described by its organization's sentence; once sent, focus moves to Request sent — {organization}'s Administrators will decide.; Create organization keeps focus while it works. The Default language names (Français, Deutsch …) carry their own language. Since the polish pass the colleague offers sit under a level-2 heading of their own, Join your colleagues, at the level of Create a separate workspace: the page's two paths are equal. |
| Create another organization · 1.3.1, 2.4.3, 3.3.2, 2.1.1 | Supports (fixed 2026-11-10) | The two kinds are a radio group named by its question (it sat between a list and its items — fixed), each with its line as its description; at the account's cap the choice says so with Open your organizations. In the header's panel, Continue gives the form's name field the focus (it fell to the page). The kind not yet offered stays focusable since the polish pass — on the Tab and arrow keys' path, aria-disabled and described by its reason in words — and choosing it does nothing (it was a disabled radio a keyboard user tabbing through never met). |
| Picker, switcher and account menu · 2.5.3, 2.4.3, 1.4.10, 1.4.1 | Supports (fixed 2026-11-10) | Organizations are full-width buttons with Administrator or Work account needed in words, never by colour; while one opens the others say they are unavailable and focus stays on the one pressed. The switcher is named Organization: {name}. Switch organization; the account button Account: {name} — its visible initials were outside that name (axe label-content-name-mismatch) and are now drawn by the style sheet. At 320 CSS px a long Work account needed (Spanish, Portuguese) goes under the name instead of past the edge. |
| Invitation · 2.4.3, 3.3.1 | Supports (fixed 2026-11-10) | Who invited and who is signed in, in words; another account or a work account needed is said before Accept with Switch account; a dead link says so in its heading. A refusal that takes Accept away, and Try again, move focus to the heading (it fell to the page). |
| Session · 2.2.1 | Partially Supports | As Table 1's row: Stay signed in two minutes before the inactivity end, announced at 60, 30 and 10 seconds; the 12-hour end cannot be extended (a security control). After either end the page never navigates away — Sign in in a new tab, then Continue, keeps everything typed. |
| Session · 2.4.3, 4.1.3 | Supports (fixed 2026-11-10) | Stay signed in and the session dialog's Continue keep focus while they work, so You couldn't be kept signed in… or You're still signed out… leaves the keyboard on them. |
| Trial and Free banners, Extend 30 days · 1.3.1, 4.1.3, 2.4.3, 3.3.2 | Supports (fixed 2026-11-10) | Fluent message bars in words with the date in the reader's format (Your free trial ends in 23 days (29 November 2026).), a warning in the last week that says what follows; the Free banner says what stays and, where the allowance is shared, that it is shared — never who drew from it. Choose a plan for an administrator, Ask an administrator for a member. Extend 30 days is a blocking dialog with an optional reason (a radio group) and its button keeps focus while it works; once extended, focus moves to Choose a plan (the banner's Extend is gone). Since the polish pass the extended trial's banner says in its last week, as the countdown does, that the organization then moves to the Free plan. |
| Allowance banners and usage meters · 1.3.1, 4.1.2, 1.4.1 | Supports (fixed 2026-11-10) | Running low and used up in words with their figures for an administrator (running low says when more arrive — {n} left; the next ones arrive on {date}. — since the polish pass; it read as if the units ended that day), one figure-free line for a member; each meter is a progress bar named by its kind whose value is its sentence (the storage meter said only a percentage — it says 7.5 of 10 GB used); overage is said in words beside the bar, never by colour alone. Evidence: UsageMeters.test.tsx. |
| AI processing outside {geography} · 1.3.1, 2.4.3, 3.3.4 | Supports (fixed 2026-11-10) | A section headed at level 4 (it was styled text) with its state in a message bar in words, one dated and versioned disclosure, an acknowledgement checkbox before Allow, and Withdraw consent confirmed first — reversible either way. Focus follows the swap of controls (it fell to the page). |
| Colleagues · 2.4.6, 2.4.3, 4.1.3 | Supports (fixed 2026-11-10) | The switch, its explanation and Requests to join as a named list; each request's role, Approve and Decline are described by who asked (they read the same for every request); after an answer focus moves to the next request's Approve, else the list's heading; results are said in the panel's status. |
| Who can join, Signing out, the portal address · 2.4.3, 3.3.4 | Supports (fixed 2026-11-10) | A change that would block members names them and asks first. Save keeps focus while it saves and once saved; Save and Discard give focus back to Who can join's switch, and removing a tenant moves it to the next row's remove button (each fell to the page). |
| E-mail and the Reply-To's code · 3.3.1, 3.3.8, 2.4.3, 1.3.1 | Supports (fixed 2026-11-10) | A new Reply-To is confirmed by a 6-digit code mailed to it: a labelled field with autocomplete="one-time-code" and numeric input that accepts a pasted code — nothing to remember. The address's format error now waits until the field is left or saved (it was announced from the first keystroke); a wrong, expired or locked code is the code field's own error and takes focus; focus follows Save, Confirm and Resend; the notices switch is described by its explanation. |
| Public portal's plan line and address · 1.3.1, 3.3.1, 3.3.2 | Supports (fixed 2026-11-10) | One information bar in words with Choose a plan or Change plan for an administrator; a member on a paid plan without the add-on read a second sentence asking for something else, now gone. The address field shows the resulting address as it is typed; too short, empty or a trailing hyphen is said once the field is left (it was announced at the first letter), a character never allowed or a reserved name at once. |
| Buying more — the buy dialog and Bundles and storage · 3.3.4, 2.4.3, 4.1.3, 1.3.1 | Supports (fixed 2026-11-10) | One dialog for every entry point, opened by a button whose words say what it adds and for how much (Add 10 requests — CA$49.00); the dialog is the confirmation — the bundle, the price in the organization's currency and the card it charges (We'll charge CA$49.00 plus tax to the card ending 4242.) before anything is charged, and a retry of the same click is charged once. The choices are a radio group named Bundle; the answer is a polite status in words; a refusal is an error bar; the link to Stripe's invoice page (when the bank asks to confirm or the card is declined) says it opens a new tab. Focus now stays on the confirm button while it charges, moves to Close once the units are added and to the invoice link when one is the next step, and a buy button whose line the purchase resolved hands focus to the page's main region. Settings → Subscription, its Change plan view and Bundles and storage are clean under axe in jsdom. A member reads whom to ask, by name, never an address. Since the polish pass Add a module keeps focus while it adds and, once the module is added, moves it to the next module's Add (it fell to the page). |
| Words in every language · 3.1.1, 3.1.2 | Supports (fixed 2026-11-10) | The live client's and the entry's strings in all eleven languages, checked by their tests; the shared UI's 773 hosted strings (with Subscription and the bundles) translated in all ten other languages with English's placeholders, and in the 2.6.0 localization sweep's terms since this pass — Portuguese no longer calls the trial an avaliação (this product's assessment), German says Antrag for an access request (method 22). Organization names are the organizations' own and are not marked with a language. |
| Dark theme | — | The server pages follow the system's colour scheme and were measured in both; the hosted application has one light theme. |
| Links that open a new tab · 3.2.5 (AAA, advisory), 2.4.4, 2.5.3 | Supports (fixed 2026-11-10) | Every link of the hosted surfaces that opens a new tab says so after its own words, in a visually hidden (opens in a new tab) in the reader's language — the entry's Terms of Service, the live client's Terms and the landing's footer, and in the application Talk to us, the procurement pack, Request a quote, the welcome's links, the licence banner's and the advisories' links; the visible words stay first in the name (2.5.3). Evidence: HostedPagesAccessibilityTests, EntryHandOffAndStringsTests, uxAudit.test.tsx and the shared UI's link-name tests (jsdom and server tests, not yet in a browser). |
| Users & roles — invitations and members · 2.4.3 | Supports (fixed 2026-11-10) | Revoke moves focus to the next invitation's Revoke, else the one before's, else Invite people (the last invitation's included); Resend, Revoke, Invite people's and Remove from organization's buttons stay focusable while they work and ignore a second press; after a removal focus goes to the next person's actions. Evidence: PendingInvitations.test.tsx. |
| Message bars · 4.1.3 Status Messages | Supports (fixed 2026-11-10) | On the hosted surfaces each message is announced once: a Fluent message bar is its own live region and is never placed inside another, and a status line that must be announced has a region of its own beside the bars (the buy dialog and several hosted sections wrapped bars in a second region, which some screen readers read twice). messageBarLiveRegion.test.ts allows no wrapper on the hosted surfaces; the rest of the product's 203 wrapped bars are a list that may only shrink. Not yet checked with a screen reader. |
Generated outputs (PDF, media, Excel, CSV)
Documents the product generates are consumed outside the application, so they are reported separately rather than folded into the tables above.
| Output | Status | Remarks |
|---|---|---|
| Generated PDFs (correspondence letters, attestation certificates, response packages, evidence packages, ROPA exports, converted uploads, "Other records" and delivery-note pages, accessible editions) | Partially Supports | Converted records. An administrator setting (Documents:TaggedPdf, default off) tags Word, Excel and PowerPoint conversions and HTML-sourced PDFs (converted emails, record captures, certificates, Word-sourced letters) and embeds their fonts (PDF/UA-1 7.21.4.1). On the converter used before 2.5.0, from 2026-09-25 every link in a tagged Office conversion was described — a web or mail link by the text the document shows for it, a table-of-contents entry or cross-reference by the words under it (7.18.1, 7.18.5) — and the structure that converter got wrong was corrected: Word lists became lists and Word's Title the top heading, a header cell in a table's body row headed its row, an Excel sheet's bold header row became column headers, and a one-cell table became a paragraph. A four-record corpus converted with the setting on and checked with the PDF/UA checker (PDF/UA-1, 2026-09-25): a Word memo (headings, a list, a table with a header row, a picture with alternative text, web and mail links), a Word report (a cross-reference, a header, a page-number footer) and an Excel workbook meet PDF/UA-1; a PowerPoint deck did not — that converter tagged a slide's title and subtitle placeholders as figures without a text alternative (7.3-1) and left one item per slide untagged (7.1-3), although reading order, lists, links and picture descriptions came through. The HTML / email path was not in the corpus. Since 2.5.0 every conversion runs in the deployment's own document worker — its Office converter for Office files, its HTML renderer for HTML and e-mail — and the setting still decides whether it is tagged: the Office converter tags headings and lists itself, the engine corrects table header rows (an Excel sheet's bold first row becomes column headers, a one-cell table a paragraph), gives every tagged conversion its title and PDF/UA metadata, and draws the page footer of an HTML or e-mail render as an artifact; a tagged HTML render with its footer meets PDF/UA-1 in the engine's PDF/UA checker test. The four-record corpus above was measured on the converter used before 2.5.0 and has not been re-measured on the document worker's converter, so its findings — the PowerPoint ones included — describe that converter. Turning the setting on by default waits on that re-measurement and a screen-reader pass. Image and text conversions are never tagged. Pages AccessPoint writes. Since 2026-09-24 the pages AccessPoint draws into a response package — cover letter, contents and exemption summary, "Other records", redaction index, exemption descriptions — are tagged (headings, paragraphs, tables with scoped header cells, lists; the release language on every element); PDF/UA checker samples of them passed PDF/UA-1. A merged package keeps tags only when every part is tagged; any other package is left untagged, because a screen reader skips the untagged part of a partly tagged document. Since 2.5.0 the labels, Bates numbers, watermarks and markup the engine draws on a page are marked as artifacts, so they no longer leave untagged content on a tagged page (7.1-3; until then a tagged package with Bates numbers or watermarks failed that rule). The accessible edition (since 2026-09-24). A record that cannot keep its tags — a record with a burned-in redaction is rebuilt without its structure tree when it is released, a scan has none, an upload may be untagged — is rebuilt from its REDACTED pages into a tagged edition that ships beside the faithful package: each page image drawn as an artifact; the text, read by Azure AI Document Intelligence (layout), drawn as an invisible layer tagged in reading order (headings, paragraphs, tables with header cells); every redaction announced where it sits, in the release language ("[Withheld — s.19(1) Personal information]"; a page covered by one redaction reads "Page 14 withheld in full under s.21(1)(a)"); Bates numbers and watermarks as pagination artifacts; and each figure tagged with a description a person accepted or wrote — drafted from the redacted crop by the organization's own Azure OpenAI when AI Assist is deployed, never released unreviewed (an undescribed figure says so). A rebuilt redacted record and a merged edition pass the PDF/UA checker's PDF/UA-1 profile (test fixtures, 2026-09-24 and 2026-09-25). The tagged-PDF edition is built automatically (Settings → Redaction appearance, default on); HTML, plain-text and Word editions follow the request's accessible-format field. The portal delivers the edition beside the package and the reading room publishes it beside the package, attaching one that finishes later. Without Document Intelligence a record that needs layout gets no edition. The text is machine-read and its reading order and headings are the model's inference, which is why the check asks a person to confirm them. The accessibility check (since 2026-09-24). Every response package — or its edition, once built — is checked when it is built: untagged records, redactions drawn without a label, figures without a text alternative, and, where the organization deployed the optional checker, the PDF/UA checker against PDF/UA-1 in its own subscription; a person confirms the reading order and text alternatives, which no machine can judge. A package is shown as Passed only when the PDF/UA checker found nothing, the in-house checks found nothing and a person confirmed; only such a package or edition may be described as meeting PDF/UA-1, without the checker none can pass, and nothing is claimed for a third-party record on its own. The verdict is stated to the requester on the portal's delivery page and to the public in the reading room, with a way to ask for another format; an organization can require a pass, or a recorded acknowledgement, before publication or release. Other. A request records the accessible format a requester asked for (never a disability), with the day it was provided and the statute's conversion extension reason. Redacted response PDFs intentionally remove withheld content (essential by function), and a redacted record leaves without its source file's document properties, XMP metadata and bookmarks (since 2026-09-24). The faithful release of a scan stays page images (its OCR text feeds search); its text reaches the requester through the accessible edition. Complaint evidence packages remain untagged. The program is docs/designs-implementation-plans/AccessPoint_Accessible_Releases_Design.md; the corpus measurement is docs/test-runs/benchmarks/2026-09-25-d8-tagged-conversion-corpus.md. |
| Released recordings (burned MP4 / MP3 in response packages) | Partially Supports (since 2026-09-23) | Every released recording with a transcript now travels with redacted captions — a WebVTT file (.vtt, named like the recording so players load it) and, in the MP4, the same captions as a soft caption track (mov_text, language set) — and a redacted plain-text transcript (.txt), inside the ZIP, beside a merged PDF in Export History and in a portal delivery; the delivery note and the "Other records" page say which recordings have them and how they were made, and the portal's delivery page says under About these files (since 2026-09-23, in all eleven languages, only for the kinds that delivery holds) that recordings are MP4 (H.264/AAC) or MP3 files that play in common players such as VLC, Windows Media Player and QuickTime, and that a captions file (.vtt) and a plain-text transcript (.txt) with a recording's name belong to it and most players load the captions automatically. They are built from the transcript with the release's own marks: every word inside a muted or bleeped span is replaced by what withheld it, in the release language — [Withheld — s.19(1) Personal information], or [Withheld] when the mark cites nothing (since 2026-09-25; before, [redacted]), the same words the accessible edition speaks — (a line without word timing is replaced whole), a disguised-voice (Distort) passage is captioned in its own line opening [voice disguised] — the words are audible, so a deaf requester gets what a hearing one hears — a line with a withheld or disguised passage names no speaker, speakers are numbered rather than named, and a withheld recording has none; the workspace captions and any captions embedded in the original are never released. EN 301 549 7.1.1 – 7.1.3 are met for the product's own captions; 7.1.4 (characteristics) is the player's. Since later on 2026-09-23 a recording with an imported description track also travels with a redacted description track (.descriptions.vtt, WebVTT kind="descriptions": a description under a muted or bleeped span becomes the same [Withheld — …] note, a withheld recording has none), and an MP4 release carries every audio track of the original through the same audio redaction, the described one flagged for the requester's player (EN 301 549 7.2.1 – 7.2.3); an MP3 holds the first track only. A tenant can switch all three text files off (Settings → Feature toggles), in which case no caption track is embedded either. Remaining: the product does not write descriptions — a recording without an imported track has none; captions are speech-recognition output, not checked word by word (the files say so); the MP4 track is best-effort — a render that fails with it is retried without it, the sidecars still ship. The Redaction Index and "Other records" page list every span, effect and citation as text, and the delivery note lists formats, durations and hashes. |
| Excel exports (report builder, statistical returns, data-transfer workbook with 17 tabs, discovery-survey responses) | Partially Supports | Named, localized worksheets (including the statistical-return sheet name in all 11 languages), styled header rows, typed and localized cell data; the data-transfer workbook opens on a "Read me" instructions tab and uses in-cell dropdowns. Since 2.5.0 a Report Builder export with money in more than one currency keeps a currency column beside the amounts, so each total is one currency's and no figure has to be guessed at; the discovery-survey workbook has one sheet for responses, one for program areas and one per table question, bold header rows frozen in place, and each of the organization's own questions headed in the language of the person exporting, with the original wording in a cell comment (a comment is not read by every screen reader; the original is also in the survey set-up). Remaining: no defined tables / named ranges, and a few fixed in-sheet labels ("Total", period captions) are English-only. |
| CSV exports (redaction log) | Supports | Plain UTF-8 CSV with a header row; one row per mark (page or span, effect, exemptions, status, origin, reviewer, timestamps); never detected text. |
| Requester e-mails from the public portal (verification code, receipt, receipt confirmation, payment link and receipt) | Supports | Reviewed from the renderer, MIME builder and send-request source with unit tests (2026-09-15), not yet in mail clients. In the requester's language (11 locales) with lang and dir on the document and on the content wrapper; the subject is the one heading; short, single-column, text 17.2:1 and secondary text 6.95:1; descriptive links (http(s) only); no images or tracking. The code is grouped for reading and pasting (1234 5678) and spelled digit by digit on a visible line, because screen readers read a run of digits as a number and mail clients strip ARIA and hidden text. Sent as multipart/alternative with a plain-text part. To verify: Outlook, Gmail and Apple Mail with NVDA and VoiceOver. |
Organizations with PDF/UA obligations should turn on Documents:TaggedPdf, deploy the accessibility check (deployAccessibilityCheck) and Document Intelligence (deployDocumentIntelligence, which the accessible edition needs), and treat each package's check verdict as the evidence for what they release: this report makes no conformance claim for any particular release.
Known limitations of this assessment
- Screen-reader evidence is NVDA only, driven from the keyboard by the assessor (methods 7, 10 and 13) and, for the 2.6.0 surfaces and the hosted edition, by the owner (method 26) — no JAWS, VoiceOver, or daily screen-reader user. Live NVDA covered the media viewer (method 7), the shell surfaces listed in method 10, and the native viewer, Word editor and spreadsheet (method 13); the viewer used before 2.5.0 was checked in page (method 11). None has been run on the surfaces new in 2.5.0 other than the native viewer and editors — DPIA validation, training (playbook TRN-A11Y), case archiving, the discovery survey, the spreadsheet-layout dialogs and the grid review, the activity tray, System health and the privacy program hub; the diagram / table / working-document editors, upload queue, and the repository-connector surfaces added after 2.1.0 (the connector browser and collect dialog inside the Add-from picker, the connector-job rows in the upload queue, the Source details callout, and the Settings → Connectors panel with its Test connection step list — all built from the same Fluent primitives and live-region patterns as the surfaces assessed here) have been verified by code review only. The 2026-09-23 media re-audit's fixes were then checked by NVDA (method 7); the manual tests it still needs are listed in the media section. The public intake portal received a runtime pass in a headless browser with axe-core on 2026-09-15 (see its section), but no live screen-reader session. No generated PDF, accessible edition, caption or transcript file has been read with a screen reader either; an accessible edition's reading order and headings are inferred by Document Intelligence and confirmed per package by a person, not by this assessment. The items most worth a live AT pass: the timeline slider, the marks area and its grip sliders, the descriptions live region, caption and transcript reading under NVDA / JAWS, the ARIA 1.1 combobox shape across screen readers, chart data-point tab order, and focus restoration after server-reloading lists.
- The automated runtime pass (axe, reflow) has a defined scope. The release candidate's surfaces were scanned with axe, measured at 320 and 640 CSS px and walked from the keyboard on 2026-10-13 (method 15), with the browser window mostly in the background (animation frames and short timers were stood in for in the page); the dark theme was not measured. The 320 px pass ran on 2026-09-25 over the surfaces listed in method 6. The axe pass was re-run the same evening over every Settings panel and every tab of each case panel (method 9). The PDF page frame of the viewer used before 2.5.0 was checked on its own origin with in-page rules rather than axe (method 11); the native viewer and editors are scanned with axe in real-browser tests (method 12) and were measured on the dev tenant (method 13). An upload in progress was not scanned. Of the surfaces new in 2.5.0, the spreadsheet-layout dialogs were scanned with axe (method 14); training, the privacy program hub with its Discovery tab, System health on My Day, the Storage report, Settings → Storage and archiving and the diagram editor's shape fields on 2026-10-13 (method 15); the DPIA Validation tab (no assessment on the dev tenant validates), the activity tray and the documents' storage chips have had no runtime scan.
- Third-party internals not re-audited. The viewer's page-rendering internals (page rendering and its text layer) and Fluent UI internals are assessed only as used.
- Point in time. This report describes version 2.6.0 as of 2026-11-12: the surfaces built for 2.6.0 were reviewed between 2026-11-01 and 2026-11-10 (methods 17 – 24) and checked on hosted stage and the dev tenant on 2026-11-10 – 12 (methods 25 – 27); the rest is carried forward from 2.5.0 as of 2026-10-13 — its release candidate reviewed on 2026-10-07 and checked at runtime on 2026-10-13 (method 15) — first issued for 2.1.0 on 2026-09-03 against WCAG 2.1, with the media records section re-assessed on 2026-09-23, the generated outputs on 2026-09-25, the whole application against the WCAG 2.2 additions on 2026-09-25 (method 8), the native viewer and editors on 2026-09-30 (methods 12 and 13) and the other surfaces new in 2.5.0 between 2026-10-01 and 2026-10-05 (method 14). It should be revised when the product changes materially.
- The WCAG 2.2 fixes of 2026-09-25 were re-scanned at runtime in part. The split buttons, the reorderable rows and their Move buttons, the settings panels, the case panels and the grid's column button were re-scanned with axe on the dev tenant the same evening (methods 8 and 9). The PDF viewer's marks and grips were checked in the frame (method 11) and again in the native viewer (method 13). The diagram editor's fields were scanned with axe and at 320 px on 2026-10-13 (method 15); its focus ring and the upload tray's placement rest on code review, type-checking and unit tests.
Roadmap (open items)
| # | Item | Criteria | Target |
|---|---|---|---|
| 1 | (Done: 2026-09-23, and the last part on 2026-09-25.) Media viewer keyboard fixes: shortcuts scoped to the player and off button-like targets; left / top / width / height fields for the region (create and edit — since the redesign, in the mark bar that replaced the mark editor dialog); arrow-key adjust for a selected region; Edit mark… (formerly Edit span…); grip sliders in the marks area; focus moves to the bar on [ / ] | 2.1.1, 2.4.3 | 2.4.0 |
| 2 | (Done 2026-09-23.) Timeline semantics and contrast: role="slider" on the scrub lane and the marks lane as a labelled group; Proposed #986F0B; :focus-visible ring on bars; no invisible workspace tab stop | 4.1.2, 1.4.11, 2.4.7 | 2.2.1 |
| 3 | (Done: 2026-09-23, and the editor dialogs on 2026-09-25.) Transcript segments tagged with the recording's language; upload-queue button names carry the file and progress is announced in steps; the working-document editor dialogs are named | 3.1.2, 4.1.2, 4.1.3 | next release |
| 4 | (Done 2026-09-25.) Diagram editor: visible focus indicator on focused shapes and swimlanes (independent of selection) | 2.4.7 | 2.4.0 |
| 5 | (Done 2026-09-23.) Captions policy: captions and transcript served under the same gate as the audio, speaker names masked without the requestor-PII permission | 1.2.1, 1.2.2 | 2.2.1 |
| 6 | (Done: code 2026-09-23, 320 px runtime pass 2026-09-25.) Media viewer reflow (header, rail, control bar, dialogs) | 1.4.10 | next release |
| 7 | Live screen-reader sessions (NVDA / JAWS / VoiceOver) on the media viewer (the list in the media section, including the descriptions live region and forced colours), the PDF viewer and the shell. The native PDF viewer and the Working Files editors had an NVDA pass at 200 % on 2026-09-30 (method 13); JAWS, VoiceOver and the spreadsheet's edit announcements and sheet tabs are open | Assessment | after 2.5.0 |
| 8 | (Withdrawn 2026-09-23.) Raise the on-frame caption pill opacity — the pill measures ≥ 7.0:1, not ≈2.6:1 | 1.4.3 | — |
| 9 | (Done 2026-09-25.) Non-colour series differentiation for multi-series charts on small dashboard tiles | 1.4.1 | 2.4.0 |
| 10 | (Done 2026-09-25.) Surface silently-swallowed errors: every empty catch reviewed, about 240 now say what failed | 3.3.1 | 2.4.0 |
| 11 | (Built 2026-09-23 – 25 except the open parts.) Tagged-PDF program: tagged conversions with embedded fonts and described links; the tag-preserving merge and tagged package pages (Tier B); the accessibility check with its gate and portal statement (Tier D); the accessible edition for redacted, scanned and untagged records with person-reviewed figure descriptions, delivered and published beside the package (Tier C); caption, transcript and description files beside released recordings that say what withheld a passage — docs/designs-implementation-plans/AccessPoint_Accessible_Releases_Design.md. (Bates numbers and watermarks drawn as artifacts: done in 2.5.0.) Open: re-measure the conversion corpus on the 2.5.0 converter (the document worker), with the HTML / e-mail path in it, and a screen-reader pass over converted records, package pages and editions, then tagging on by default (design decision D-8); tagged complaint evidence packages | Outputs | after 2.5.0 |
| 12 | (Visible labels done 2026-09-25.) Minor polish: persistent visible labels for placeholder-only fields; localized strings for the Fluent ColorPicker's internal inputs; localize the remaining fixed Excel labels. (Format hint on the In / Out fields, now in the mark bar: done 2026-09-23.) | 3.3.2 | after 2.5.0 |
| 13 | Public portal (closed on 2026-09-15: the checkbox-group labelling, the session warning and extension, the minutes in the page strings, status labels shown in a fallback language, the localized error page, Escape inside the pop-up, the visible h1 on every step, the language change after sending, required file fields — each checked on its own by the server, every file recording its field — the forced dark theme, the language of composed letter subjects and staff delivery titles, and a localized title for a delivery created without one): record the language of a delivery title written in another language than the tenant's base language, including the export name the Deliver dialog pre-fills in the staff member's display language (letters composed before letters recorded their language stay untagged); run live NVDA / JAWS / VoiceOver passes over the intake, code, delivery and pay flows, standalone and embedded, plus Firefox, Safari, mobile and forced-colours checks, and read the requester e-mails (now lang-tagged, multipart with a plain-text part, the code spelled digit by digit — closed 2026-09-15) in Outlook, Gmail and Apple Mail. From the 2026-09-23 audit (all 27 findings fixed that day, PA-17, PA-24 and PA-26's server half last, with the delivery page's About these files note from the media audit): run the live pass listed under Portal accessibility audit (2026-09-23), items 1–7. (Keeping unsent answers across a language change on the form: done 2026-09-22.) | 3.1.2, 3.3.1, 3.3.7, Outputs, Assessment | after 2.5.0 |
| 14 | (Done 2026-09-23 except the last two parts; code-reviewed, live screen-reader pass pending.) Audio description for media records: import and play a WebVTT kind="descriptions" track (a polite live region with a visible Descriptions switch and D, for everyone who may play), release it redacted as .descriptions.vtt (a tenant switch turns the released text files off), and carry an original's secondary audio tracks into the MP4 release with the same audio redaction applied to each (the described one flagged). Open: choose and play a described audio track in the viewer (the preview plays the first track; the browser has no audio-track selection), and the live pass in item 7 | 1.2.3, 1.2.5; EN 7.2, 7.3 | after 2.5.0 |
| 15 | Live screen-reader pass of the training surfaces — Guide me, tips, Get started, the guide, the progress table, the exercise console and the inactivity warning (playbook TRN-A11Y; the owner's). Not run yet | Assessment | 2.5.0 |
| 16 | DPIA validation surfaces: NVDA on the two risk-map grids and the decision dialog, an axe scan, a 320 px pass and 200 % zoom on the Validation tab, the consultation card, the evaluation dialog and the Risks tab (the list in the DPIA section) | Assessment | after 2.5.0 |
| 17 | Case archiving and the discovery survey: an axe scan and a 320 px pass, then NVDA over a storage chip button, the Restore and hold dialogs, the policy confirmation and the survey panel's question editors | Assessment | after 2.5.0 |
| 18 | Spreadsheet layout: NVDA over the hidden-content review dialog and its acknowledgement, the viewer's Parts section, the Page layout dialog and the grid review; a 320 px pass of the dialogs | Assessment | after 2.5.0 |
| 19 | (Done 2026-10-05.) Name a translated survey question's long-label picker, date, table, diagram and file answers by the wording on screen when the original is shown | 2.5.3 | 2.5.0 |
| 20 | (Done 2026-10-13.) The open items of the release candidate's static review (2.5.0 release-candidate changes): focus after the listed actions; date-picker error text and format hint; the received-date correction preview and the other unannounced statuses; 2.4.3, 3.3.1 and 4.1.3 back to Supports | 2.4.3, 3.3.1, 4.1.3 | 2.5.0 |
| 21 | (Done 2026-10-13, except the dark-theme measurements.) The release candidate's runtime pass on dev (method 15): axe, keyboard, 320 px and 200 % over the inventory, and the decisions it was to take (card titles as headings, the Lab library rows, modifier clicks under 2.5.7). Open: measure the 2026-10-07 dark-theme colour fixes at runtime | Assessment | 2.5.0 |
| 22 | Say the search failed, not No results, in the remaining people pickers (about seventeen) | 3.3.1, 4.1.3 | after 2.5.0 |
| 23 | AccessPoint Learning (built for 2.6.0): the owner-run NVDA pass over the coach, the player, the Studio, the page editor in the Studio and the Translations tab, and an axe scan and a 320 px pass over the player, My learning and the Studio (methods 17 and 18) — and over the L3 screens: checks, decisions, certificates, Team progress, the coverage report, the Quality, Glossary and Obligations tabs and Training done elsewhere (method 19) . (axe-core in jsdom over every test of these surfaces: done 2026-11-10, method 21. NVDA over *How we decide, My learning, the player, a Check, a Decide step, the certificate and Verify a certificate, the Studio's findings and a Glossary refusal: done 2026-11-12, method 26. Open: the browser scan, the 320 px pass, and NVDA over the coach notes editor, the page editor, the Translations tab, Team progress, the coverage report, the Quality and Obligations tabs and Training done elsewhere.)* | Assessment | 2.6.0, then after 2.6.0 |
| 24 | (Done 2026-11-10: method 21, then the polish pass for the parts it left open.) AccessPoint Learning's code-review gaps: focus after every action methods 18 and 19 listed; one announcement for a failed step write; lang on the player's own words and on text written in another language in the Studio and the Translations tab; the step outline's move-button names and a word for a badge's severity; a Studio text field's findings as its description; a confirmation before a decision or a last limited attempt is submitted (3.3.4); the term picker's label and its results announced; errors on their fields for the order question, Verify a certificate, Training done elsewhere and the Revoke and More attempts dialogs. The polish pass: aria-invalid for findings to fix, and findings tied to document fields, dropdowns and the module's texts; the Glossary and Obligations editors' refusals on their fields; the interface's words inside a step in the reader's language, and the L3 editors' labels in the interface's; a File step's viewer titled with the file's name | 3.1.2, 3.3.1, 2.4.6 | 2.6.0 |
| 25 | (NVDA over the welcome dialog, the session warning, *Here's your task and the unavailable New: done 2026-11-12, method 26.)* Onboarding, read-only, the demo and the Training Lab (built for 2.6.0, method 20): NVDA over the welcome dialog, the session warning, the read-only banners on a case page, the Lab's join form and the Live grid; an axe scan and a 320 px pass over the welcome, the read-only states and every Lab screen | As listed in Onboarding, read-only states, the marketing demo and the Training Lab | 2.6.0 |
| 26 | (The card: done 2026-11-10, method 21 — focus after Got it, and its unit test.) The method 20 code-review gaps that remain are the Training Lab client's: the New class wizard moving focus to (or announcing) each new step; the Live grid's chips read with the words they show | 2.4.3, 2.5.3 (advisory) | 2.6.0 |
| 27 | Method 21's recommendations on the 2.6.0 surfaces the demo cannot show: an axe scan in the page, a 320 px pass and the dark theme on the dev tenant for AccessPoint Learning, redaction discussion, the read-only states, dated settings and Your own AI deployments (its small item — a Bates range kept whole at 320 px — done by the polish pass, 2026-11-10) | Assessment | 2.6.0 |
| 28 | (The owner's NVDA pass: done 2026-11-12, method 26. On stage, the in-page checks of 2026-11-10 and the 320 px pass of 2026-11-12: done, method 25 — axe-core cannot run there, the stage app's security policy keeps it out.) The hosted edition (method 22): the owner's NVDA pass over sign-up, Create organization, the picker, the invitation and the session dialogs, and an axe scan and a 320 px pass of the banners and Settings' hosted sections on stage; and a landing at app.realizer.io/ (a product decision). Its other recommendations — focus on the invitation surfaces, a word for links that open a new tab, a heading for the colleague offers, the extended trial's last week, the shared-workspace kind focusable, running low's wording, focus after Add a module, one announcement per message bar on the hosted surfaces — were done by the polish pass on 2026-11-10 | Assessment, 4.1.3 | 2.6.0 |
| 29 | Repeat the 320 CSS px pass on hosted stage once method 25's three fixes are released there (the organization switcher, a panel's action buttons, the AI usage meter), and decide whether an incident's Documents sub-tabs fold into a More menu like the panel's own tabs instead of a strip that scrolls on its own | 1.4.10 | 2.6.x |
Legal disclaimer
This document is a good-faith self-assessment provided for information purposes; it is not a certification, guarantee, or legally binding commitment of conformance. Realizer Services Inc. will update this report as the product evolves. "VPAT" is a registered trademark of the Information Technology Industry Council (ITI); this report follows the structure of the VPAT WCAG edition but was not prepared or reviewed by ITI.