# Accessibility

# Table of Contents

• Overview
• Screen Reader Support
• Colour and Non-Colour Cues
• Keyboard Navigation
• Contact
• TODO's and items to check
  • CLI Module Menu Flow Standard

# Overview

• Menu titles use blue (cyan) for visibility.
• Documentation/resource sections use purple (magenta).
• All user-facing output is clear, concise, and accessible.
• No technical log details are shown to the user in the terminal.

# Screen Reader Support

• All menus and documentation are screen reader and keyboard navigation friendly
• Inline comments and menu documentation use accessible, annotated ASCII-art

# Colour and Non-Colour Cues

• All menu cues have non-colour fallbacks (e.g., asterisk for changed state, not just red text)

# Keyboard Navigation

• All error and status messages are actionable and accessible

# Contact

• For any accessibility feedback, please contact the project maintainer

# TODO's and items to check

• All scripts and documentation follow accessibility and EN-AU standards
• Review output and documentation for screen reader compatibility
• Use inclusive language throughout

---

# CLI Module Menu Flow Standard

For all CLI modules and menu-driven scripts:

• CLI modules must never redirect to menus themselves.
  All CLI modules and functions should return control to their caller after completing their task, including after errors or user exits.

• Menu navigation and flow must be managed by the calling (wrapper) function or script.
  This ensures consistent, predictable menu behaviour and prevents accidental returns to the wrong menu or main menu.

• CLI modules must not call other menus, main menus, or perform navigation logic.
  They should only perform their core function and return.

• Document this pattern in all new CLI modules and review existing modules for compliance.

This standard ensures robust, maintainable, and accessible menu navigation throughout the project.