Meeting Summary

• Meeting started by Piñeiro at 16:15:31 CET.
• Meeting ended at 17:23:38 CET.
• Participants (Lines Said):
  • Piñeiro - API (148)
  • Joanie - joanie (64)
  • Joseph - clown (54)
  • Javi - jhernandez (29)
  • Mike - mgorse (2)
  • Daniel - danigm (2)

• Log

Boston Summit Recap

• 6-7-8 of October was last Boston Summit, this time in Boston.
• Some good summaries from Matthias Clasen and Colin Walters

• http://blogs.gnome.org/mclasen/2012/10/08/boston-gnome-summit-monday/

• Specifically about a11y, Piñeiro gave a short presentation about a11y the first day.
• But, in Piñeiro's opinion, the most important news related with a11y was during the gtk session on Saturday, when we agreed to made public some headers of the gtk implementation of ATK, so third-party apps, like evince or evolution, could extend them.

Grace Hopper Conference Open Source Day Recap

• After the Grace Hopper Conference, there was a Grace Hopper Open Source Day, the goal of which was to get women involved in Open Source through projects with "humanitarian" aspects.
• Joanie presented a full day on GNOME Accessibility. She didn't get a head count, but she is guessing that more than 15, but less than 20 joined her group.
• The task was to triage a bunch of open bugs filed against Orca.

• Joanie started with a presentation (basically the same one she gave to Andre Klapper at the GUADEC A11yCamp).

• But unlike A11yCamp, the women then spent the rest of the day (9:30- 2:30ish) actually applying what they learned during the preso.

• They got approximately 10 bugs fully triaged using Orca, Accerciser, and self-created Python event listeners, identifying where the bug really is.
• Some have indicated interest in starting/joining an a11y division of the GNOME Bugsquad.
• Joanie's conclusion is that it went (surprisingly) well. And she'll probably go next year if invited.

FoG Fund Use Update

• Joanie and Piñeiro wrote up a priority list of document-related project tasks for Bastien, including the history of and need for each area.
• They asked Bastien and the Board (implied not counting Joanie) to provide feedback on which of the areas they would like addressed.
• They also mentioned that Joseph was working on a description of the caret and focus tracking work and would be submitting that soon.

• Joseph has updated the old focus tracking proposal to represent the current state of affairs. The latest proposal is still a "draft", but it is close. It can be found here: https://live.gnome.org/GnomeShell/Magnification/DraftFocusTrackingProposal.

Miscellaneous time

• Joseph added another feature for 3.8 -- tinting enchancement: https://live.gnome.org/ThreePointSeven/Features/TintEnhancement

• At the Boston Summit Piñeiro also briefly talked with Allan Day (designer) about Bryen's mail, he suggested to created bugs about that.
• ACTION: Piñeiro will create some usability-configurability related bugs, using Bryen's mail as a starting point

• https://bugzilla.gnome.org/show_bug.cgi?id=685827

• At the Boston Summit we also talked about one feature that affects a11y: fallback mode.

• https://live.gnome.org/ThreePointSeven/Features/DropOrFixFallbackMode

• Most of the people in the room during the two or three sesssions about that were more in favour to drop it, but they were worried about the backlash if that happened.
• So the conclusion at the boston summit was that "there isn't any conclusion"

Action Items

New

• Piñeiro:
  • Create some usability-configurability related bugs, using Bryen's mail as a starting point

Ongoing / Rolled-Over

• Team members:

  • Look over Juanjo's draft about how to improve accessibility by promoting a11y to developers and designers.

• Joanie
  • (with Piñeiro) touch base to see if that evince a11y could be moved forward
  • Draft the final Q2 report for the team and get Piñeiro's review.
  • 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:
  • (with Joanie) touch base to see if that evince a11y could be moved forward
  • List some of "touch-friendly" accessibility features (ie: possibility to define a gesture to control a11y features like zoom), and send it to design team(?)
  • Investigate that "Enable by Keyboard" thing.
  • Send a mail to bastien to know 1. if he has specific features for the bridge 2. if he plans to work on that.

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