-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 hi No problem. I can file a bug. Which component? maybe ... gnome shell, core component? I don't mind filing bugs. My main reason for the ... I don't know if it was a rant, was that I'm the *only*, or it feels that way anyway, person filing these bugs. This isn't really gnome's fault, but accessibility is very fragile. It breaks easily, and the reason why can be very tricky. On a positive note, I've been doing a lot of testing with gnome on wayland, and it's just as accessible as x11. The desktop isn't drawn, but that's a known bug already. What about the duplicate controlls? I have no idea what's causing that. It happens primarily in gnome's control center, in almost every module, but also in gnome tweak tool. I don't think there are actually duplicate controlls, just that orca is reading duplicates, for some very odd reason. Can you point me to some a11y guidelines? It looks like I'll have to start nagging extension authors to read them. Thanks Kendell clark Sent from Fedora GNU/Linux Bastien Nocera wrote: > > > ----- Original Message ----- >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >> >> hi I'll add my voice into the debate again. The status icons >> thing needs fixing. I don't particularly care what the final >> decision is, but it *needs fixing, and very soon. Here's why. >> When the message tray was removed, the status icons were shunted >> off into a sort of hidden area of the bottom panel, accessible by >> pressing control+alt+tab until "status icons" is heard, and >> released. You land on the first icon in the list. However, >> accessibility of this area is extremely weird. The icons are >> usually, though not always, announced as the application name. EG >> pidgin. However, when you attempt to right click to bring up a >> context menu, you end up clicking on the applet to the right of >> the one orca's focus has landed on. Gnome developers cannot >> simply blow this off as, sorry, status icons is deprecated, blame >> your app provider. > > This is a bug. A plain bug. There's nothing to discuss. File a > bug. > >> An alternative is for the gnome developers to add accessibility >> guidelines > > There are already a11y guides, which the extension authors don't > read. > >> Long story short, this is gnome's, and not the extension >> author's, problem to solve. > > I really don't see how. The APIs are there, the guidelines are > there. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVUyE4AAoJEGYgJ5/kqBTdqvIP/j4RUpYimHv4MCwByvHLxN/2 Ibd6zQJhboa7F/odFMqiIUs86zcejEs/IcWE8b7srHApZwmbimK7YGLmsIk/fFFt U9RK4gh28+S42Pb7GIqFrvYQhkG7eqBseFE+T+FwOznUFk34gBOhSw+dCyy0PPTk wRFlsSr/DCuXF3ztqMBAZVBvmy709lQ9zYQ+cjxb34YJ/zq6Dhzb66Zhmxmq6oGO zt40/TTXuDiRpeygXN9jw7xFBzoRpmW84PBYGHFo77LyS9Wm3p5IuB/cWJmi/dqA g8er0JPDC98TOgjjkndk0siWzWjfQfETJupd436fhrTwpI/MHea0ID1OSzQTRdWx /sbe6QlJJY+QfDrp5VdogISCul2aLojsXgM29X43OXyljbHZQMI3rkCLCKKnG8cw DX0X+XiUbTml9+2wIyBJfCfY1miMdXldLmJwH4SECFtpa7DBOjyfJUqf+QZXR5s2 YgRnEEYvWA53seL5abpE4tK+Qpg7f7o+Ukdmx0LlRvoZVnrc8v7nIVzJB7jbrIo+ ozybeVBy7wVJEm+rDOl7RhWS7FRcgN+ZhwS0X530jY5ur0Pq9BO5AHngDgpK1drL yhnGKa+RJH3ZK73TJVDnQ7oz7TBccBhRE2m4Nc/RR1MKM4wHV9znc466ekFhoj2u n8n6pjkx2SWt9QntggSN =YQR3 -----END PGP SIGNATURE----- -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
