On Mon, Mar 23, 2015 at 2:39 AM, Pete Travis <lists@xxxxxxxxxxxxxx> wrote: > > On Mar 22, 2015 6:53 PM, "kendell clark" <coffeekingms@xxxxxxxxx> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> 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 >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2 >> >> iQIcBAEBCgAGBQJVD2P9AAoJEGYgJ5/kqBTdoCkP/29oOPh23a2K4R/PfOoOZTan >> pc194D7gvzU2wEQsXp240AtLSd/62/p5btddEtyR59QkhQHXoyYCQQ36dMqc6rYW >> A+Lq9tE8P/H9IuZASf3JS86TCq2k0PKh4HufA2E/3x5NjRJ0nguiYp4HPzmux/kv >> ql6KVgvbrBoHz4kj7CV+Qg+Jq1lgDhXZlo7aidNaL/DELzQeYNWnkrSN0XhX1Uqq >> 6Qenvp47Hg2CvFfAhzb302YxMBXfHhtJkvjXZ8wkgWmAJEppisI2/3McUXHXjRdt >> EG8J77zHgsEqdgC7MZFPmhOUE/RI/5FkBix9bQKA5OgxxeDkHGINyuhwj5AlHLq1 >> Cx4cuFzgNVI/kv8n8eRQuYl1sLe4I/eoM59v1ETsihz1O+PYOHgompYOVWUEqmgn >> KFce/Db2gxJKXRghHra7ZVaQnz8+EYvLs8xu+nF+NFVYD+gGqGbwJcIrrLBBu5JT >> ylcQ8zf0TYjm+M1NeLJrhmeQav5SUj+Hq9D9T6uZMj5NmZQXx+wKXNUjFsC0CXWh >> xEH9ywHAWiwrcqKmpCAnXaQKQViI4uLRXh2HHfwEBGkU0PTvNcReVGiRfQbGNkp4 >> 12W8UskCfucmx14wIChPVd5/qSme/sRTC6yK2YpcJieAoXyaNU6fu4aQ1Fweg2Ob >> lgAv4RnTDn0fmmFs0f6C >> =955T >> -----END PGP SIGNATURE----- >> -- > > 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 -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
