plan: fix all remaining accessibility issues for gnome 3.18

[kendell clark]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

hi
Thanks for this link. This is, to put it bluntly, discouraging. I
would expect the gnome accessibility team, if there is one, to have
gotten further than this. Guess it's bug filing time. This is a
critical area for me and other linux blind people. Whether wayland or
x is used, orca should be able to access apps running the same way it
does running under xorg. If it can't, it needs to be fixed. I'll ping
the orca people to see what they know about this, but I think the
brunt of the work lies in wayland and/or gnome. I'm always on #a11y on
irc.gnome.org. Should I find a wayland channel and idle in there? Are
the wayland people interested or able to fix accessibility issues? To
be honest, accessibility baked into the display server with an API
orca talks to would be ideal. Possibly at-spi2, but whatever is used
it would reduce the complexity and the multiple layors needed for orca
to speak.
Thanks
Kendell clark
Sent from Fedora GNU/Linux


drago01 wrote:
> On Mon, Mar 23, 2015 at 2:39 AM, Pete Travis <lists at petetravis.com>
> wrote:
>> 
>> On Mar 22, 2015 6:53 PM, "kendell clark" <coffeekingms at gmail.com>
>> wrote:
>>> 
> hi all. I'm writing in to let everyone on the desktop list know
> that I'm intending to work with anyone here and with the gnome
> people to fix all remaining accessibility issues for gnome 3.18.
> This currently includes, unlabeled controlls, buttons and links, in
> various gnome control center modules. Duplicate controlls in the
> power settings module, duplicate buttons in gnome tweak tool. Gdm
> is inaccessible to orca. Orca is unable to see the login screen so
> cannot navigate it's controlls. This last one is exclusive to gnome
> 3.16, gnome 3.14 works just fine. I plan to have all these issues
> ironed out in time for gnome 3.18 and f23. I will file bugs,
> provide logs, anything that is necessary. My plan is that by f23,
> there will be 0 (zero) accessibility issues with orca and gnome
> shell. I would like to make one possible request, not sure where
> this is applicable. Would it be possible, as a temporary measure,
> to cause gdm to fall back to using x for it's login screen when
> accessibility is enabled? I have no idea how this can be done, but
> this would allow orca to again see the screen and navigate it,
> until whatever is wrong in wayland can be fixed up stream? If there
> are any people who work on gnome itself, would you mind logging on
> to #fedora-accessibility, or I can log on to #a11y on gnome's
> server to discuss issues? I don't want to flood the list with
> accessibility traphic. Thanks Kendell clark Sent from Fedora
> GNU/Linux
>>> --
>> 
>> I'll throw out my vague understanding, in the hope that someone
>> will validate or knock it down:
>> 
>> A big driver for moving to Wayland is the additional security
>> context provided; one application, by design, cannot access
>> another application through the interface to the display server.
>> I *think* that orca works *because* it is able to access other
>> applications through Xorg.  So, based on this very basic
>> understanding, I would expect that Orca would not work as-is on
>> Wayland, and maybe would need a fundamental redesign to follow
>> the migration away from X.
>> 
>> GDM on F22 is a Wayland session by default, so it is isolated
>> from other processes ie Orca.
> 
> https://wiki.gnome.org/Accessibility/Wayland
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVD8TAAAoJEGYgJ5/kqBTdwbYP/RhgU7aLdPm0ggcPMJNRpSoM
hJJw9hVnCqJIgP9VU3uArnuprCfgwJG7ymMZT/y0jiL3PZH2v6XxKvI70Fcp+RyL
14lSDaFr9hYDo5P70xASBCMpw6slDp+V5Y+X+9fUpS3SmJsVXae++pN5rBZJni2H
V7aCboJEX6EC8/QnQ52end8FIWVyqd11/oVJS3nxjtD6AX8gXGU0YLmUd5k0ufvx
opjboeJq0H9FX5JPvPBXfsR2+QAoxFDwXuNWC6UQUoyzkNEY/8L68Dyffsg3AGcO
p+8X/9Au/+hPN1HUccLJbnpOR/Z97ZIebmsI+sYOybYTDlnIBn1/AERCTHldeUZP
7YRyHlcBHW5IMebSIGmCzy4kFRMdU+JWvDDlgtbN2Wx7j3fHyccKjwRgOlBGZ31g
moXOKWrxnMrz6mXWx6vNJo5drGTgLOZRKu5NBZtVcRFTCpjLUAxyjrXBY19UlD5h
6IRuR9jqur0YMuXIIK5bRpy6EL1bKGT115jJcsRAcPIpu6mOpEAUVRvldqoFNTBH
/+LkU41Q0gMWnTqHVu42X0WnScBCalnZOnHY0ox9aU43uu7DnVZcaZUhFnyfcRJy
MuEd+nRXY+Xm1SoJZ8cor30wYuZ42qMyehgGIavJtHa02z5eXz2d0RU3miB3GZTQ
UnZWUoD9b78R779OnnlI
=nwyi
-----END PGP SIGNATURE-----