Pre-enabled Orca vs On-Demand Install: Default Kali Live Accessibility Trade-off

The Kali Linux live USB aims to serve both penetration testers requiring maximum tool performance and visually impaired users needing immediate screen-reader feedback. Enabling Orca at boot through the accessibility menu provides out-of-the-box spoken navigation but adds memory overhead and boot latency that can degrade resource-intensive security tools on constrained hardware. Keeping the session minimal and installing Orca only when needed preserves the baseline for testing workflows, yet assumes network connectivity and sighted assistance to run apt install orca—conditions that fail in air-gapped or isolated deployments.

Open questions

1. Should the default live image prioritize immediate accessibility by starting Orca automatically, accepting the resource cost on low-end systems?
2. Is an on-demand installation path viable for environments without network access or where no sighted operator is present to trigger the install?
3. Could a hybrid approach—such as a boot parameter to toggle Orca—resolve the conflict without fragmenting the image?