KDE Neon first-run workflow: Plasma accessibility options not surfaced before System Settings

KDE Neon ships the Plasma accessibility stack (screen reader, magnifier, high contrast) through System Settings, but the user-facing install and first-boot path appears to require manual navigation to System Settings > Accessibility before any of these features are discoverable. I am evaluating whether this is a gap that should be addressed in the onboarding flow.

The specific uncertainty is where accessibility quick toggles or prompts belong: the login manager (SDDM), the Plasma Welcome first-run app, or both. There is also a design question about default enablement, since turning on a screen reader or magnifier by default would affect all users, while hiding the options entirely hurts discoverability for those who need them.

A complicating constraint is Neon's composition: the User Edition rolls the Plasma stack on top of an Ubuntu LTS base, so the accessibility components and underlying libraries can move at different speeds. Any onboarding change would need to account for that version skew.

Is there a documented or recommended way to surface Plasma accessibility toggles during first run or at the login screen on Neon? How should default enablement be handled given the rolling Plasma/LTS base split? Which Plasma versions change this behavior?