Comment 12 for bug 1546317

Revision history for this message
Luke Yelavich (themuso) wrote :

The accessibility indicator is no longer showing because I have been revamping the accessibility profile system this cycle, and unfortunately ran out of time to properly implement support for flavours other than Ubuntu Unity.

It is worth noting however that the accessibility indicator only provided real use in Ubuntu proper anyway, as the profile settings were entirely geared around Ubuntu only. They likely would have mostly worked in the GNOME flavour, but not very likely to work in mate at all, since mate has different GSettings schemas to GNOME and Unity. So for example, if you were to try and enable a profile in Ubuntu Mate 15.10, you wouldn't see any real change, other than maybe Orca loading, because all the settings are GNOME and unity related. In addition, if you were to dig into the installer logs, you would notice errors when attempting to select a profile, because GSettings schemas required for profile functionality in GNOME/Unity are not likely present in the mate flavour.

This doesn't excuse my lack of providing support for Mate. As I said, it was planned, and due to some other work that was required for this to go ahead taking longer than I hoped, I did not get around to adding non-Unity support in time.

If enough people want this, and enough of us could put a case forward to get an FFE approved, I could add support for Non-Unity flavours, and we could add some Mate specific settings to the profiles, and if you want, add extra profiles specific to Mate, since the advantage of the new profile system is adding custom profiles, whereas the previous sytem was all hard-coded in a script that lived in the casper package.