SPB Git

Repository Public License

accessibility.md 5.5 KB

# Accessibility report

State on 2026-11-21, ORIX Monitor 1.0.0 (build 1). This report separates what was built, what was checked by machine, and what nobody has checked.

# What is built

Area Implementation
VoiceOver labels Rows combine label and value; page headers carry the header trait with the subtitle as value; icon-only buttons have labels
Charts LiveChart and HistoryChart replace the drawing by a text summary: latest value, minimum and maximum per series, number of gaps
Per-core displays Each core is an element with "Core n" and its percentage; the heatmap reads the busiest core
Colour independence Severity, memory pressure, thermal state and data quality always carry a word and a symbol; decorative meters and swatches are hidden from assistive technology
Contrast Text colour tokens reach at least 4.5:1 against canvas, surface and raised surface in both appearances (computed, table below)
Colour-vision deficiency Optional Okabe–Ito based metric palette
Reduce Motion Readout and dashboard animations are disabled when the system setting is on; live charts never animate
Keyboard Standard focus navigation; shortcuts for pause, bookmark, refresh insights, new dashboard window
Density Compact, regular, comfortable (padding and spacing only)

# Text contrast (computed, WCAG 2 relative luminance)

Minimum ratio of each text colour over the three backgrounds it is used on.

Token Light Dark
textPrimary 16.3 14.3
textSecondary 5.5 6.8
textTertiary 5.1 5.0
success 5.1 8.2
warning 5.5 9.4
danger 5.1 5.7
accent 5.1 8.7

Before this review the light values of textTertiary, success, warning and accent were between 3.2 and 4.1; they were darkened and the app rebuilt and re-notarized. Metric palette colours are used for chart marks and icons, where the applicable threshold is 3:1; the lowest of them is 3.2 (network, light, on the raised surface).

# What a machine checked

Apple's performAccessibilityAudit was run by testAccessibilityAuditOfEveryPage on twelve pages of the Debug build, in Dark Mode, one fresh instance per page. Audit types: contrast, element detection, hit region, sufficient element description, parent/child. The raw output is accessibility-audit.tsv.

Page Contrast failed Contrast nearly passed Parent/Child mismatch Unknown role Element has no description Total
overview 12 0 5 6 5 28
cpu 12 0 13 24 6 55
gpu 14 0 15 15 6 50
memory 11 0 23 15 5 54
disk 12 0 4 3 5 24
network 11 0 13 11 5 40
power 11 0 18 16 5 50
thermal 10 1 34 5 6 56
history 11 0 1 2 5 19
insights 11 0 1 1 5 18
alerts 11 2 8 1 5 27
reports 12 0 1 1 5 19
All 138 3 136 100 63 440

The audit reported no hit-region issue on any page.

# Reading of the results

These are notes from an automated tool, not confirmed defects, and they have not been resolved. What can be said about each group:

  • Contrast failed (138). The audit gives no element for any of these notes, so they could not be traced. The run was in Dark Mode, where every text token computes to 5.0:1 or better, so the notes are probably about something else: text drawn over chart areas and gradients, axis labels, system-drawn sidebar and toolbar text on the translucent window material, or disabled controls. That is a guess. The count did not fall after the light-mode colour fix, which is consistent with the run being in Dark Mode and says nothing about Light Mode, which was not audited.
  • Parent/Child mismatch (136). Typical of SwiftUI containers whose accessibility children are re-parented (grids, cards, chart overlays). Not investigated individually.
  • Unknown role (100). Mostly the combined label-and-value rows (KeyValueRow) and chart summaries: they have a label and a value but no control role, which is intended for static read-outs. Some have an empty label and were not identified.
  • Element has no description (63). No element is named by the audit. Candidates are Canvas drawings and layout containers that should be hidden from assistive technology and are not.

# What nobody has checked

  • No person has used the app with VoiceOver. Reading order, verbosity and whether the chart summaries are actually useful are unverified.
  • Light Mode was not audited by the tool.
  • Full Keyboard Access and Switch Control were not tried.
  • Increase Contrast and Reduce Transparency system settings were not tried; the app has no specific handling for them.
  • Text size: macOS has no Dynamic Type; text does not scale beyond what the density setting does to spacing.
  • The colour-blind-safe palette was chosen from published values and not verified with a simulator or by an affected user.
  • The French interface was not audited.

# Next steps

  1. A VoiceOver pass by a person, page by page.
  2. Hide Canvas drawings and pure layout containers from assistive technology, then rerun the audit to see which notes remain.
  3. Audit Light Mode.
  4. Decide whether static rows should expose the static-text role explicitly.
Files main
Menu

Theme