Meeting Summary

• Meeting started by Piñeiro at 16:01 CET.
• Meeting ended at 17:15 CET.
• Participants (Lines Said):
  • Piñeiro - API (214)
  • Joseph - clown (50)
  • Joanie - joanie (40)
  • Juanjo - jjmarin (12)
  • Mike - mgorse (4)

• Log

Boston Summit

• Who's coming?
  • Alejandro Piñeiro bought his flight tickets, foundation confirmed that will support him, so he will be in Montreal.
  • Mike bought a ticket and will be there too.
  • Joanie will drive up.
  • Juanjo won't attend.

  • Joseph won't attend since he will be returning from the jQuery a11y summit.

• The main topic will likely be wayland.
• For that it would be good to do some pre-summit homework: basic stuff, like compiling everything using current documentation, and trying at-spi2, orca etc.

• Joanie created a wiki page with all that stuff: Accessibility/Hackfests/Montreal2013

• So as an outcome of that homework, some of the stuff to discuss there could be:
  1. Comment about the tests outcome
  2. Identify features needed for X and Wayland
  3. Determine how open we (and others) are to an API change especially with respect to device events (current API is not really good)
• The second main topic would be discuss about making at-spi2 API more async
  1. Can we start looking now at what API changes (if any) are needed?
  2. Think about how such a change would affect the idea of merging atspi/ATK
• ACTION: API will send a email to the -devel ml in relation with the informal agenda for the "Boston" Summit

GNOME 3.12 Planning

• Obviously two of main topic for 3.12 are the already-mentioned Wayland + asynchrony on at-spi2, but there are others
• We are right now in feature proposal period.
• After thinking a little, and talking with joanie we came with an idea: "Make keyboard navigation consistent across our entire platform"
• Rationale: gtk and gnome-shell focus when using keyboard navigation is slightly different. For example, in gnome-shell, in most cases TAB is the same as Left-Arrow, except that adds also cycle, but in gtk, TAB is used to "jump" across containers.
• Using TAB in gnome-shell to move from one container to another was already mentioned in the past, but it would be good to try to have a plan.
• In the same way, during the last weeks of this cycle, we found some key navigation issues/inconsistencies in gtk.
• This was mostly in new widgets, so it would be good to review the platform.
• ARIA authoring practices recommends using TAB/SHIFT-TAB to move between containers, and arrows to move within a container. The main reason is to avoid seemingly endless TABing to acquire a widget. So TAB is for navigating larger parts of the interface.
• ACTION: API will send a feature proposal email to d-d-l, ideally before feature proposal period ends
• Magnifier plans for 3.12
  1. Tinting
     • Joseph already mentioned that he is busy, so if he is not against, Piñeiro volunteers to take over the task to move tinting forward.
     • As in the case of the tracking, as far as he knows, this is also about providing a configuration GUI.
     • Taking into account Joseph's comments, Piñeiro will also check that the code is still there.

     • ThreePointEleven/Features/TintEnhancement

  2. Tracking preferences GUI
     • In the past, we proposed this kind of thing as a new feature.
     • Now, Piñeiro thinks that this is too much hassle because, after all, the functionality is there. What remains is providing a GUI. We should just provide the GUI, and then in the release notes mention that now users have an easy way to do the same that they were able to do using terminal.
     • People seem to agree, so the tracking preference GUI would be tracked as bugfixing, and ideally it would be solved for 3.12.
     • ACTION: Piñeiro will contact Magdalen, as she is not at the meeting right now.
• API additions, deprecations, and changes.

  • During the end of the previous cycle there were several API deprecations, like several AtkText methods and especially focus methods.

  • Benjamin already asked about how to proceed with gtk3
  • Joanie made recently a good point in relation with gtk2.

  • It would be good to also add new API. Example: collection at ATK, improvements on AtkDocument (related to FoG) etc.

  • ACTION: API will ping Benjamin in order to know how much can be done on gtk+2.
  • ACTION: Joanie already volunteered to review current bugs about API additions and create new ones, with 3.12 target in mind.

W3C Updates

• First public draft of ARIA 1.1 was published.

• Announcment here: http://lists.w3.org/Archives/Public/public-pfwg/2013Sep/0073.html

• Differences from 1.0 here: http://www.w3.org/WAI/PF/aria-1.1/appendices#changelog

• ACTION: Joanie will review the first public draft of ARIA 1.1 with specific attention to our current API.

Marketing

• Juanjo helped on the release notes. The notes about the focus and caret tracking feature were finally included

Action Items

• Joanie:
  • 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.
• Piñeiro:
  • Send a email to the -devel ml in relation with the informal agenda for the "Boston" Summit.
  • Send a feature proposal email to d-d-l, ideally before feature proposal period ends.
  • Contact Magdalen, as she is not at the meeting right now.
  • Ping Benjamin in order to know how much can be done on gtk+2

Ongoing / Rolled-Over

• Joanie:
  • 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:
  • Compose a "what accessibility needs from Wayland, how to use it" email, ask for review, send to the Wayland Developer's list.