[00:00] <TheMuso> Well if he is working on the UI, then yes it is.
[00:00] <TheMuso> But its not Ted's problem.
[00:00] <AlanBell> ok
[00:00] <AlanBell> I will continue to pester gord :)
[00:03] <AlanBell> I don't understand how it all fell apart at the beta. I am sure alpha2 was quite good
[00:06]  * AlanBell downloads alpha2 again to see what it was really like
[00:07] <TheMuso> AlanBell: Yeah Unity 3D still feels flaky to me, in that it doesn't take much for it to fall appart.
[00:07] <TheMuso> WHich is why I am focusing on 2D now.
[00:07] <TheMuso> A11y is easier to fix there, requires much less work.
[00:33] <TheMuso> AlanBell: Ok, found the code that is supposed to set the result buttons in the unity-2D hud. An attempt was made to make this accessible from the get go, however the variable they used for the text always seems to be empty.
[00:33] <TheMuso> I found another variable that can be used, but its got characters in it that Orca speaks, which we don't want to hear.
[00:34] <TheMuso> I actually think this needs articulating a bit better anyway, as I think the user should hear what menu the item is from in a way that makes it understandable.
[00:35] <jalcine> TheMuso: The "What's This" or tool-tip could be useful there.
[00:35] <jalcine> If provided.
[00:35] <TheMuso> jalcine: What tooltip?
[00:36] <TheMuso> jalcine: There are no tooltips for the HUD.
[00:36] <jalcine> For a specific menu entry.
[00:36] <jalcine> o.O
[00:36]  * jalcine headdesks.
[00:36] <TheMuso> Or more to the point, the hud doesn't receive those.
[00:36] <jalcine> It could, since it's merely importing menus.
[00:36] <TheMuso> Not exactly.
[00:36] <TheMuso> The hud sends the search to the appenu service, which does the searching, and sends back results, and how to activate them, no more.
[00:37] <TheMuso> Actually no, it doesn't send how to activate, the appmenu side does that as usual.
[00:37] <jalcine> Hm. 
[00:37] <TheMuso> In this case, I think what is required is more code for the hud to present a nicer a11y string.
[00:38] <TheMuso> But thats too late for this cycle, since that requires more translation work to do properly, so if we can just present the results in a way that they are somewhat understood, thats ok.
[00:42] <jalcine> It would.
[00:42] <jalcine> It'd be a good idea to propose this asap, though.
[00:42] <TheMuso> I know that, I am just trying to come to grips with enough of the code to do the work myself.
[00:43] <jalcine> Scratching the itch :)
[00:43] <TheMuso> yep
[00:47] <TheMuso> Hrm. It seems that this requires a 2-pronged approach. *sigh*
[00:47] <TheMuso> I think the text formatting is done by the hud service, and sent via dbus to the hud UI.
[00:48] <TheMuso> So in order to get what I want, I need to extend the hud service to format a string for a11y use, then extend the hud API to present this string.
[00:48] <TheMuso> Then extend unity-2d to actually use this newly added struct member with the text I want.
[00:49] <jalcine> Hmm. So it's a bit messy at the moment, but the way you're describing it, it might stay similar to that setup for now..
[00:50] <TheMuso> Its messy in that I have to touch multiple projects to fix this properly.
[00:50] <TheMuso> Yeah, the problem with this is that it requires everything that uses the HUD API to be rebuilt.
[00:50] <TheMuso> Ayway, I'll plug at it and see what can be done.
[00:51] <TheMuso> anyway
[01:41] <jalcine> Experimental dictation support achieved with SpeechControl! :)
[01:49] <TheMuso> Nice.
[01:53] <jalcine> It's using libxdo, though.
[01:53] <jalcine> I'm a bit skeptical of Unicode support in it. If anything, I might include a modified version of it in the team's PPA until we can get upstream to cooperate.
[05:46] <dreamwb> Hello !
[05:46] <dreamwb> Is that anyone here ?
[17:15] <popey> yo!
[17:16] <davmor2> popey: you following me
[17:19] <popey> yes
[17:19] <davmor2> Hello everybody,  mvo and tremolux from the software center client team would like to get some help making Software Center more accessible is there anyone on this team that would like to get involved with this effort
[17:19] <davmor2> popey: don't you won't like where it leads
[17:26] <Pendulum> davmor2: are you looking for developers or testing or information?
[17:27] <davmor2> Pendulum: I think it's a mix of dev time and info then once the fixes are in place testing
[17:30] <davmor2> Pendulum: although I can utilise LDTP to do the bulk of the testing,  I think the key is knowing what to do, how to do it, and help doing it at this stage though.  They'd like to get it as accessible as possible for the release if they can now all the key items are in place
[17:35] <Pendulum> Okay, the best people to talk to about knowing the code is TheMuso or API
[17:35] <Pendulum> Just about anyone here can test
[17:38] <Pendulum> I'm not sure about developing (because I suspect TheMuso and API are over worked as it is), but AlanBell or TheMuso would probably know if there's anyone who has expressed interest in doing a11y developing.
[17:38] <Pendulum> maco might as well
[17:40] <Pendulum> Otherwise, would they care if we used this to try to recruit someone to doing a11y devel? (I can get a blog post out today looking for someone if that's the case)
[17:42] <Pendulum> We tend to end up in this issue where there's such a high barrier of entry to get into most accessibility stuff on the distro level that it's hard to recruit.
[17:42] <Pendulum> Unless there's a specific case (like this) it's not exactly easy to recruit without bitesized bugs
[17:42] <Pendulum> (which we don't have)
[18:09] <davmor2> Pendulum: indeed, we can possibly make some bitesized ones once we know what we need in place, I'll ask TheMuso when I can