-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 hi This makes sense. I agree with wayland's approach. Unfortunately, this has the side effect of rendering orca useless until this can be fixed, which imo needs to be done yesterday. I'm not trying to be demanding, but this does need fixing, else blind users won't have access to linux's graphical sessions. Thanks Kendell clark Sent from Fedora GNU/Linux Pete Travis wrote: > On Mar 22, 2015 6:53 PM, "kendell clark" <coffeekingms@xxxxxxxxx> > 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. > > --Pete --Pete > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVD3FgAAoJEGYgJ5/kqBTdlQMP/j671ALd4aukZNX8ae9W5cyX RO7DnMfp3EyXZlDxnFp3WrFwJUbSPr4kzcOGCSH3904OidTEfWxR9zPenWFKOH8x P+4H9kgkI2WWQo0E/s3BLZb5uPs47h6pzondZgyugIDWPqUFEyHttsxiPKffYYtH 508u6WZQ2pa/CssozJ5tUQb12ZPdgfycwRd068gVuWdFvsPtQj0lrfYrDaP5MeXw nUlQWLzr+z6eeCXLzh5S5KbwWqUqxBM2g2r2uzhmZ77iPtxyS+WtjL0uyXQ1h4q0 1TG+07vMtnmA/DjdnRLMk/b3By6Iv5DVH84jcLoqYQFgPWMPF/w39OUOx2Xcg4Xj TaB++xWr48waPPunI6MbytFR6+iAo4bMDTvroKahDkBWFuduv4g32tDAIvUJsEar vnL7S6OwdqEA9/YuP1iQ+KyAkP/QzpsE9ZRPnO+mdKwO4h7wuv62lP3aiQs5q0Lk JIdhmB5e3g5+7oIE6Ie2RdjKF7hu1t5G33qyEyDpmjZaKJ77O6ZLUVoYbiseWYy8 fi82OPwyNiuUfTNzHA14yB9/POxuxTFzj6WCzCyT2G/R7byxOR/iyJS2VTypqJ1G T+3TFvAXaNgZ/5jgxmaGDh3AFHkGzzd4l9w3DM+RfHRJDAwehXtQv87xYi07cwmw F1d+cQ9xnVJvMvTL/Xxz =g8OA -----END PGP SIGNATURE----- -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
