Accessibility
Nevisel targets WCAG 2.1 Level AA, applied to desktop software as described in the W3C's WCAG2ICT guidance, plus the WCAG 2.2 AA criteria that are cheap to meet. This is a self-assessment by the people who make Nevisel, not a legal opinion or a third-party audit. Organizations that need a formal Accessibility Conformance Report (VPAT) should commission an independent review.
Version assessed: 1.0.0 · Platforms: Windows 10 and 11, macOS 13 or later · Last reviewed: October 3, 2026
Report an accessibility problem
Email info@causalyticsimpact.com with "Accessibility" in the subject, or ask your IT administrator to forward it. Include your operating system, any assistive technology you use (for example NVDA, JAWS, Narrator or VoiceOver) and the steps that fail. Accessibility problems are treated as bugs and prioritised for the next release.
Keyboard
Every control can be reached and used without a mouse.
| Keys | Action |
|---|---|
| Tab, Shift+Tab | Move between controls, sidebar items, categories and snippets |
| Enter or Space | Press a button, choose a sidebar item or category, open a snippet |
| F2 | Rename the focused category |
| Delete or Backspace | Ask to delete the focused category (focus moves to Keep) |
| Esc | Cancel adding, renaming or deleting a category |
| Ctrl +, Ctrl −, Ctrl 0 | Larger, smaller, or default text size |
A blue focus ring marks the focused control when you use the keyboard. Tab visits every control once, in reading order (sidebar, snippet list, editor), and wraps from the last control back to the first; Shift+Tab goes the other way. When a control disappears because of what you did, focus moves to the next sensible place instead of the top of the window. An automated test drives the real window with the keyboard and checks this on every build.
Conformance by criterion
Supports means the criterion is met. Partially supports means some content does not meet it (see Known limitations). Not applicable means the content type does not occur in Nevisel.
| WCAG 2.1 AA criterion | Status | Notes |
|---|---|---|
| 1.1.1 Non-text content | Supports | The Nevisel mark is labelled ("Nevisel, expansion on/off"); icon buttons are labelled ("Rename Clinical", "New category"); the status dots repeat information that is also given as text. |
| 1.3.1 Info and relationships | Partially supports | Landmarks (banner, navigation, region, main), list items with selection state, and field labels are exposed. Section headings are visual only. |
| 1.3.2 Meaningful sequence | Supports | Reading and focus order follow the layout: header, sidebar, snippet list, editor. |
| 1.3.3 Sensory characteristics | Supports | Instructions do not rely on shape, colour or position alone. |
| 1.3.4 Orientation | Not applicable | Desktop windows. |
| 1.3.5 Identify input purpose | Not applicable | No fields collect personal data about the user. |
| 1.4.1 Use of colour | Supports | Selection uses a bar, tint and bold text; status uses text as well as coloured dots; delete confirmation is worded. |
| 1.4.2 Audio control | Not applicable | No audio. |
| 1.4.3 Contrast (minimum) | Supports | Lowest measured text ratios: 4.7:1 in light mode and 4.7:1 in dark mode. See Contrast. |
| 1.4.4 Resize text | Supports | Text and layout scale together to 250%; the window scrolls past what fits. On Windows the starting size follows the system Text size setting. |
| 1.4.5 Images of text | Supports | All text is live text. |
| 1.4.10 Reflow | Supports | At 200% the content scrolls in one window without loss of function. |
| 1.4.11 Non-text contrast | Supports | Focus ring, selection bar, status dots and input borders are at least 3:1 against their background. |
| 1.4.12 Text spacing | Not applicable | WCAG2ICT notes this applies to content in markup languages; Nevisel's interface is not authored in one. |
| 1.4.13 Content on hover or focus | Supports | Category actions appear on hover or focus, stay while hovered or focused, and do not hide other content. |
| 2.1.1 Keyboard | Supports | See Keyboard. |
| 2.1.2 No keyboard trap | Supports | Tab and Shift+Tab leave every control, including the multi-line Phrase field; Esc closes inline editing. Covered by an automated test. |
| 2.1.4 Character key shortcuts | Supports | Single-key shortcuts (F2, Delete) act only on the focused category. Text bindings are defined by the user and can be paused. |
| 2.2.1 Timing adjustable | Supports | Nothing in Nevisel is timed. |
| 2.2.2 Pause, stop, hide | Supports | The only animations (key press, binding typing out, hover fades) last under a second. |
| 2.3.1 Three flashes | Supports | Nothing flashes. |
| 2.4.1 Bypass blocks | Supports | Landmarks let screen reader users jump between regions. |
| 2.4.2 Page titled | Supports | The window is titled "Nevisel". |
| 2.4.3 Focus order | Supports | Focus follows the visual order and wraps in both directions; when a control disappears, focus moves to the next sensible control. Covered by an automated test. |
| 2.4.6 Headings and labels | Supports | Fields carry their visible labels ("Title", "Phrase") rather than their example placeholders. |
| 2.4.7 Focus visible | Supports | A 2 px focus ring, 5:1 or better against its background. |
| 2.5.1 to 2.5.4 Pointer | Supports | Single clicks only; actions fire on release; accessible names contain the visible label; no motion input. |
| 3.1.1 Language | Supports | English user interface. |
| 3.2.1 and 3.2.2 On focus, on input | Supports | Focusing or typing never changes context; filters change only on activation. |
| 3.3.1 Error identification | Supports | Errors ("Binding ;sig is already in use", "Give the category a name") are shown in the status area and announced. |
| 3.3.2 Labels or instructions | Supports | Every field is labelled; the binding and phrase fields describe their syntax. |
| 4.1.2 Name, role, value | Supports | Custom buttons, list items, the mark and fields expose role, name and state. |
| 4.1.3 Status messages | Supports | Status and permission messages are live regions, announced without moving focus. |
From WCAG 2.2, 2.5.8 Target size (minimum) is met: every control is at least 24 × 24 px at 100% zoom. 2.4.11 Focus not obscured is not yet verified; nothing overlays focused controls, but whether the category and snippet lists scroll a focused item into view still needs checking.
Contrast
Ratios of text and indicators against the surfaces they sit on, measured from Nevisel's design tokens. "Worst surface" includes every window surface and the hover and selected fills of sidebar rows. AA requires 4.5:1 for text and 3:1 for non-text indicators.
| Element | Light | Dark |
|---|---|---|
| Primary text (worst surface) | 8.2:1 | 7.9:1 |
| Secondary text, including sidebar counts (worst surface) | 5.0:1 | 5.1:1 |
| Tertiary text: hints, row details (worst plain surface) | 4.7:1 | 5.5:1 |
| Grey button labels (rest, hover, pressed) | 9.0:1 or better | 4.7:1 or better |
| Primary button label on signal red (rest, hover, pressed) | 4.7, 5.3, 6.4:1 | 4.7, 5.3, 6.4:1 |
| White text on a selected list row, including its dimmed second line | 9.7:1 or better | 6.7:1 or better |
| Signal red as text (links in note previews) | 4.7:1 | 5.6:1 |
| Warning text ("Enterprise · read-only", "Shared library") | 5.1:1 | 7.3:1 |
| Small text on tinted rows (delete confirmation, permission and license bars) | 5.3:1 or better | 5.4:1 or better |
| Focus ring | 3.4:1 | 4.4:1 |
| Status dots in the toolbar | 4.7:1 or better | 5.2:1 or better |
| Cedar sidebar icons (worst surface) | 3.4:1 | 4.9:1 |
The large "Untitled" placeholder in an empty snippet title is lighter than AA on purpose: it marks an empty field and repeats no information, and the field is announced as "Title". Disabled controls are exempt and are not included.
Known limitations
- Headings are not exposed as headings. The interface toolkit has no heading role, so section labels (LIBRARY, CATEGORIES, TITLE) read as plain text. Landmarks and field labels carry the structure.
- Long status messages are cut off on screen, for example a long export path. Screen readers receive the full text.
- Standard text fields, drop-downs and check boxes take their placeholder and border colours from the platform style; these were not measured.
- High-contrast and reduced-motion settings are not followed. Windows High Contrast themes and macOS Increase contrast and Reduce motion do not change Nevisel's colours or animations. Nevisel's own contrast meets AA without them, and its animations are brief.
- Focus inside scrolling lists has not been checked to scroll into view when a long category or snippet list is tabbed through (WCAG 2.2 criterion 2.4.11).
- Screen reader testing is manual and not yet complete for this release with NVDA and Narrator on Windows and VoiceOver on macOS.