a11y:installer
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| a11y:installer [2026/06/27 11:19] – created alexandrospr | a11y:installer [2026/06/27 11:59] (current) – alexandrospr | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | proposition / a11y from the start . | ||
| + | |||
| + | prerequisites: | ||
| + | |||
| + | Installer should probe the user in a dialogue to agree on the preferable UI-display-input typed to use. Installer would probe first the hardware to see available UI devices . | ||
| + | |||
| + | So eg: | ||
| + | - (Installer) Hi User. Look, | ||
| + | |||
| + | Aligning with stated preferences the Distro should prioritize software tagged approprietely. For example : If a user states Display: | ||
| + | |||
| + | One user-init-system would tie all these processes. If visual-impaired user , or a tty oriented user decides to execute a pixel-oriented-visual process (mpv playing a video) (assuming there is that output device) on the display screen that could happen with a process with the same RUID. | ||
| + | |||
| + | A user could change the preferable user init IO type. So system could in next login ask password through a sound device and land you to a sound enabled shell. | ||
| + | |||
| + | So a user session would be comprised of processes with different IO types . Each output device type would need it's server since many process could need access to them. | ||
| - | proposition / a11y from the start . Installer should probe the user in a dialogue to agree on the preferable UI-display-input typed to use. Installer would probe first the hardware to see available UI devices . So eg: - (Installer) Hi User. Look, | ||
a11y/installer.1782559174.txt.gz · Last modified: by alexandrospr
