Hi Happy with talking about this at the next debconf. I have two points: a) BRLTTY cannot be shipped in a specific tasksel, as it covers the accessibility of all the distro (DE, tty, d-i, etc). So we should maybe see how it was shipped in the d-i to apply to livecd. b) Including enabling of accessibility in the tasksel seems a problem. First because it implies changing several ones, while the stuff is transversal. Next because I guess if it is not in desktops such as MATE, it is likely to avoid some issues. that is why BRLTTY, as well as the speakup scripts, include accessibility enabling it, if the installer uses brltty and speakup, as the last step of the process. So here, it should be the 1st step of the process, and an additional script to add to the livecd when running the live session on the desktop.
regards Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://www.hypra.fr ----- Samuel Thibault <sthiba...@debian.org> a écrit : > Daniel Baumann, le Thu 13 Aug 2015 13:49:34 +0200, a écrit : > > a) can someone who is accessibility-aware please work on getting > > accessibility related packages integrated into tasksel (for example > > via an task-gnome-accessibiltiy or whatever the tasksel maintainers > > would prefer)? > > This is already done (notably gnome-orca), except for the brltty > package. I guess we should discuss about it at debconf: we don't > include brltty by default because it would then start by default, thus > potentially spuriously grabbing some usb-to-serial devices. > > > b) file bugs on the desktop environment for accessibility integration > > (for the out-of-the-box experience of "press s and $something > > happnes"-things) > > This is indeed a common desktop thing which matters for installed > systems too. Again we can perhaps discuss about it at debconf. > > Samuel >
