Enable KDE Accessibility Framework by Default vs. Leave Disabled Until User Activation

Goal: Improve accessibility for KDE Neon users while balancing system performance and user experience.

Constraint: The KDE Accessibility Framework (KDE AF) adds AT‑SPI2 support, screen‑reader hooks, and high‑contrast themes. Enabling it at boot increases startup time and memory usage, but keeping it disabled may delay discovery for visually impaired users, who often do not explore accessibility settings during initial setup.

Unresolved Decision: Should KDE Neon pre‑enable KDE AF during installation, or should it remain disabled until the user manually activates it in System Settings?

Questions:

• What measurable impact does pre‑activating KDE AF have on average system startup time and memory consumption across typical hardware configurations?
• Does pre‑activation improve discoverability and early adoption of accessibility features for users with visual impairments, compared to the current manual activation workflow?
• Are there documented compatibility issues with legacy applications when KDE AF is enabled by default, and how can they be mitigated?