Meeting Summary

• Meeting started by Piñeiro at 16:05 CET.
• Meeting ended at 17:00 CET.
• Participants (Lines Said):
  • Piñeiro - API (110)
  • Joseph - clown (56)
  • Juanjo - jjmarin (20)
  • Joanie - joanie (11)
  • Javi - jhernandez (11)

• Log

GSoC Update

• After the Magdalen's success last week, Joseph noticed the tracker was too public.
• That was useful for debugging.
• He suggested a way to hide most of the Atspi registry code from the outside world.
• Clients just deal with standard signal handling now: connect(), disconnect().
• Joseph will read the logs and see if all is okay.
• Magdalen did send email about not receiving focus events for tabs.
• Joseph forwarded that email to Joanie, Piñeiro, and Juanjo for their input.
• "We" need to investigate that issue and see what is going on.

W3C Update

• No important news on W3C accessibility activity.

• LINK: https://bugs.webkit.org/show_bug.cgi?id=117367

• LINK: http://trac.webkit.org/changeset/151827

• Piñeiro checked that WebKit is already implementing some of the stuff proposed by the IndieUI W3C group

Marketing

• The GNOME Accessibility bid winner was announced: http://www.gnome.org/news/2013/06/gnome-accessibility-bid-selected/

• Karen Sandler asked Juanjo to add a quote for the announcement
• ACTION: Juanjo will write to the anaconda team to inform them about the plans for an a11y BoF at GUADEC 6th august

Miscellaneous Time

• LINK: https://wiki.gnome.org/ThreePointFive/Features/InitialSetup

Action Items

• Juanjo:
  • Write to the anaconda team to inform them about the plans for an a11y BoF at GUADEC 6th august

Ongoing / Rolled-Over

• Joanie:
  • Email Mark Sadecki about our team meetings and invite him to join us to provide W3C updates.
  • Do a full evaluation of the accessibility breakage in Evolution 3.6 and file bugs accordingly.
• Juanjo:
  • Take a look at the current a11y material in order to make an action plan.
• Piñeiro:
  • Ping mousetweaks maintainers in relation with their plans towards Wayland.
  • Send a email to accessibility-dev, just in case the Wayland Accessibility section needs to be filled.
  • Compose a "what accessibility needs from Wayland, how to use it" email, ask for review, send to the Wayland Developer's list.
  • Ping GNOME designers, so hopefully some default keybinding will be available for 3.8.
  • Create some usability-configurability related bugs, using Bryen's mail as a starting point.

  • Update the AtkObject:children-changed documentation, as this could be also used on ATK implementors.