-----BEGIN PGP SIGNED MESSAGE-----
Unfortunately, gnome control center 3.16.2 did not fix the duplicate
controlls issue. Orca still sees two dim screen brightness controlls,
two blank screen controlls, etc. I'll file a bug
Sent from Sonar GNU/Linux
kendell clark wrote:
hi There's a new gnome control center? Great. I don't think I
it yet, I'm still on 3.16.1 here, so I'll wait for an update and
write back in with results. Thanks Kendell clark Sent from Fedora
Bastien Nocera wrote:
> ----- Original Message -----
>> -----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.
> You're certainly an early adopter amongst our orca users.
>> This isn't really gnome's fault, but accessibility is very
>> fragile. It breaks easily, and the reason why can be very
> Yes, certainly. Which is one of the reasons why we made a11y
> switchable at run-time. In the olden days, you had to log out
> and log in again when enabling an a11y feature.
> Which is why testing is invaluable.
>> On a positive note, I've been doing a lot of testing with
>> gnome on wayland, and it's just as accessible as x11.
> Yay :)
>> The desktop isn't drawn, but that's a known bug already. What
>> about the duplicate controlls?
> That's usually missing metadata on the widgets, and easily
> fixable through a couple of GtkBuilder lines.
>> I have no idea what's causing that. It happens primarily in
>> gnome's control center, in almost every module,
> Aren't most of those fixed? Rui released a new 3.16
> gnome-control-center yesterday, and we're backporting those
> fixes for GNOME 3.14 and Fedora 21 as well.
>> 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.
> This is the main entry point:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----