Scope GardenUnity Editor tools

Version 1.0.0 documentation

UI Access Audit for Unity

Use a read-only editor scan to identify legacy uGUI review targets, then combine its evidence with the included manual checklist and testing with disabled players.

Run your first auditTroubleshooting

Before import

Requirements

  • Unity 2022.3 LTS or later.
  • Unity UI com.unity.ugui 1.0.0 or compatible.
  • An open scene containing legacy uGUI components.
Editor-only and local

The scanner never changes an audited scene, adds no player-build component and sends no project or player data anywhere.

First audit

Quick start

  1. Import the package into a backed-up Unity project.
  2. Open the scene or scenes you want to review.
  3. Choose Tools > Scope Garden > UI Access Audit.
  4. Set the target-size and contrast review thresholds.
  5. Select Scan open scenes, review findings in context, then export JSON, CSV or Markdown evidence.

Every finding includes rule ID, severity, confidence, a scene-qualified object path, an explicit limitation and a practical next step.

Fourteen rule families

Automated review targets

  • Interactive target dimensions and invisible raycast blockers.
  • Navigation exclusions and missing initial focus.
  • Absence of an active, enabled, non-empty legacy Text descendant with nonzero own alpha.
  • Empty, small, low-opacity and vertically clipped legacy Text.
  • Solid-colour contrast estimates.
  • Anchors outside the parent and non-unit transform scale.
  • Disabled interactive states that require review.

Use severity filtering to prioritise the visible evidence list. Export ordering remains deterministic.

Required human checks

Complete the manual checklist

Static scene data cannot prove accessibility. Review colour-only meaning, subtitles and audio alternatives, motion and flashing, timing, input remapping, runtime-generated UI, representative devices and the experience of disabled players.

Use findings as prompts

A finding is neither a certification failure nor proof of an inaccessible experience. Verify every result in the final rendered game and its real input flows.

Support boundary

Scope and limitations

Version 1 scans legacy uGUI Canvas, Text, Image and Selectable components in open scenes. TextMesh Pro, UI Toolkit, runtime-generated UI, textures, gradients, shaders, camera content, custom event systems and safe-area behaviour are outside automated scope.

UI Access Audit is an accessibility-minded engineering aid—not WCAG, legal, console, platform or accessibility certification.

Common fixes

Troubleshooting

No findings appear

Confirm the intended scene is open and contains legacy uGUI. TextMesh Pro and UI Toolkit are outside version 1.

Contrast differs from a design tool

The audit compares serialized solid colours and does not reproduce textures, gradients, shaders, parent alpha, camera imagery or post-processing.

A custom-navigation control is flagged

The scanner reports serialized uGUI navigation. Document the custom system and verify focus order, escape paths, wrap behaviour and device reconnection in play mode.

Export buttons are disabled

Run a scan first. The report remains in memory until the window closes or scripts reload.

More support checksEmail support