Meeting Summary

Debian's Switch to XFCE as the Default Desktop Environment

Recently Debian made an internal commit in order to switch default desktops, from GNOME to XFCE
One of the reasons given was Accessibility.
Piñeiro sent an email clarifying the situation of current accessibility status of both GNOME and XFCE.
Summarizing it in one line "Accessibility shouldn't be one of the reasons used to switch to XFCE."
ACTION: Juanjo will keep an eye out for any subsequent accessibility-specific issues/questions/concerns that we should address.

Joseph was contaced by Sriram Ramkrshna and Gayathri Subrmanian to mentor Gayathri on the ARIA automated testing proposal from the dark ages.
I said I did not have time to mentor anyone at the moment.
But I committed to bringing the issue to this group in case someone here wants to be a mentor.
Joanie wishes she had time, but she does not.
The project is described at this url: https://wiki.gnome.org/Accessibility/AriaAutomatedTesting
Piñeiro also doesn't have time this cycle for mentoring.
Last week, OPW was raised, and the conclusion is that no one from the a11y team seems to have time this cycle for a full mentoring.
The only seemingly suitable project are adding configuration UI to some of the magnifier features. But for that, someone from the design team seems a more suitable mentor.
ACTION: Juanjo will remove the ARIA testing project from the list of available projects.
ACTION: Joseph will formally reply to Sriram Ramkrshna stating that no mentors are available, and that the project has been withdrawn.
ACTION: Piñeiro will ping jasper.

Given that the focus tracker stuff from atk and focus: method are being deprecated, Joanie had a chat with Alex Surkov.
He filed a bug and provided a patch.
Trev Saunders, who is one of the Mozilla a11y developers asked a question to which Piñeiro provided a detailed reply.
As questions like Trev's come up, and possibly as we file the bugs against other toolkits and apps, that comment 5 might serve as a good guide.
i.e. Perhaps we should include some of that content in the opening report and/or point to it as questions are asked of us.
With respect to Orca, joanie is slowly but surely doing the switch over to no longer listen for focus: events.
It's taking forever, and users are finding occasional bugs, but mostly it's progressing nicely.
With only one (so far) gtk+ bug needing to be fixed.

Focus deprecations are also part of 3.12 work, see previous section for more info.
Piñeiro sent a email just today to gnome-shell list about keyboard navigation.
Although the plan was proposing that as a feature, he concluded that it would be strange to propose a feature related with gnome-shell, without talking with them first.
Mike has been working on being able to cache properties in a way that's more flexible. He will send an email to the list this week with a proposed API.
Matthias filed a bug about implementing the scaling from wayland into mutter and I think this will be a good idea for the magnifier.
Mousetweaks is still undecided.
Piñeiro has an action item about sending emails to resume conversations.
He sent some (like the mentioned keynav) but he still needs to send some more (like mousetweaks one).

Joseph posted to the a11y list about the last call publication of the User Agent Implementation Guide for ARIA 1.0.
Last week, we discovered that the test results page was private.
Joseph asked if it could be made public, and was given a postive response.
https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=2
ACTION: Joseph will report that the switch to public did not work, and will request that it be made public.

Juanjo has draft for the ATK entry in the wikipedia and has receive some feedback from Piñeiro.
As suggested, it makes sense to do as well the entry for AT-SPI, to complement the ATK entry.
ACTION: Juanjo will start to write about AT-SPI and will menace Mike to ask him for comments about AT-SPI when he has an early draft about it.

Joseph:
- Formally reply to Sriram Ramkrshna stating that no mentors are available, and that the project has been withdrawn.
- Report that the switch to public did not work, and will request that it be made public.
Juanjo:
- Keep an eye out for any subsequent accessibility-specific issues/questions/concerns that we should address with respect to the Debian switch discussion.
- Start to write about AT-SPI and will menace Mike to ask him for comments about AT-SPI when he has an early draft about it.
- Remove the ARIA testing project from the list of available projects.
Piñeiro:
- Ping Jasper about OPW and mentoring.

Mike:
- Propose more specific API for being asynchronous and email the list.
Joanie:
- Test Benjamin's work-in-progress focus-related deprecation patch.
- Review current bugs about API additions and create new ones, with 3.12 target in mind.
- Review the first public draft of ARIA 1.1 with specific attention to our current API.
- Do some testing and update the Evolution a11y bugs.
Juanjo:
- Take a look at the current a11y material in order to make an action plan.
Piñeiro:
- Ping the different Wayland-related mailing list threads.
- Send a email explaining his proposal about gnome-shell under wayland, and asking for suggestions.
- gnome-shell not accessible on wayland. Hacky solution available. Proper solution needed.
- Look at tooltip related code to see the possibility of adding mouse-in, mouse-out event at the a11y toolkit.
- Check with gtk and clutter developers to see what the plans are with respect to pango.
- Ping Benjamin in order to know how much can be done on gtk+2
- Compose a "what accessibility needs from Wayland, how to use it" email, ask for review, send to the Wayland Developer's list.
  - I think that mclasen already sent this: ask joanie if this ai can be closed

Accessibility/Minutes/20131107 (last edited 2013-11-14 14:45:18 by JoanmarieDiggs)