From a related bug report's comments [1] I gather the solution would be to code a new application indicator. There are tutorials on how to code an indicator using Python. Since I speak Python that's something I would be capable of doing. Could someone from Canonical confirm this is the right way to solve this issue? I don't want to code something just to have it labeled "doesn't fit our concept/doesn't apply anymore". There is also work in integration such an indicator; the accessibility preferences should have a checkbox 'show key stats' or something like that. The latter would have to be done by someone else; porting a panel to an indicator is one thing, but starting an indicator and setting it to launch with Unity and such would require knowledge of Unity workings and related technologies I don't have.
From a related bug report's comments [1] I gather the solution would be to code a new application indicator. There are tutorials on how to code an indicator using Python. Since I speak Python that's something I would be capable of doing. Could someone from Canonical confirm this is the right way to solve this issue? I don't want to code something just to have it labeled "doesn't fit our concept/doesn't apply anymore". There is also work in integration such an indicator; the accessibility preferences should have a checkbox 'show key stats' or something like that. The latter would have to be done by someone else; porting a panel to an indicator is one thing, but starting an indicator and setting it to launch with Unity and such would require knowledge of Unity workings and related technologies I don't have.
[1] https:/ /bugs.launchpad .net/ubuntu/ +source/ unity/+ bug/751207