** Tags added: a11y
** Tags removed: accessibility
--
[Lucid or Maverick] When Ubuntu installation is happening with accessibility
mode, need default enabled the accessibility support with future created users
in installed system
https://bugs.launchpad.net/bugs/563717
You received this bug
I have to disagree with this. While a user installing Ubuntu with
accessibility enabled will want accessible login, I don't think it is
correct to assume every new user that is set up on the system will want
accessibility enabled.
Also, this would need to be done with all accessibility profiles,
** Tags added: patch
--
[Lucid or Maverick] When Ubuntu installation is happening with accessibility
mode, need default enabled the accessibility support with future created users
in installed system
https://bugs.launchpad.net/bugs/563717
You received this bug notification because you are a
Luke, if you have a little time, possible you look my attached patches,
and write my choosed way is acceptable with Ubuntu Core Developers?
If my any patch is good, possible apply this with Lucid Casper source
package, or this patch applying only after Ubuntu 10.10 development
cicle is
This patch modify in the ubiquity-hooks/30accessibility script the gct function.
Now, accessibility settings is enabled with user based settings method. This
patch change this way with system wide setting.
I tested this patch with following criterias, all my doed tests is passed:
1. Have
I sending an optional completed revision, with containing only following
modification with prewious patch:
I copyed during installation the modifyed .orca folder in target
system/etc/skel folder, similar with happening gdm.
Of course, this is only an optional feature.
Attila
** Attachment
