Meeting Summary

  • Meeting started by Piñeiro at 16:00 CET.
  • Meeting ended at 17:16 CET.
  • Participants (Lines Said):
    • Piñeiro - API (183)
    • Magdalen - magpie (78)
    • Joseph - clown (49)
    • Juanjo - jjmarin (22)
  • Log

3.12 Updates

  • Wayland is still the main item.
  • Threads have been somewhat quiet.
  • ACTION: Piñeiro will ping the different threads open.
  • Last week Piñeiro has been talking with mousetweak developers, on a thread started with Magdalen.
  • They are also having some problems using wayland directly as wayland doesn't allow access to some features.
  • In the same way, they are removing some of the code that used X in order to use at-spi2.
  • So that means that right now, some mousetweaks features will work if at-spi2 gets the proper porting.
  • We will also keep mousetweak developers on the loop.
  • There have been discussions about whether to implement mousetweaks in gnome-shell.
  • There was a concern that other desktops would not be able to use it if that happens.
  • The rest of the 3.12 items are more or less in the same status
  • Still waiting for a formal proposal from mike gorse about async API for at-spi2.

W3C Updates

Marketing

  • Juanjo is working in improved content for ATK entry in the wikipedia.
  • He has some holes in his understanding of ATK and AT-SPI.

Miscellaneous Time

Action Items

  • Joseph:
    • Email the a11y interest list when the UIAG document is published as a last call draft.
  • Piñeiro:
    • Ping the different Wayland-related mailing list threads.

Ongoing / Rolled-Over

  • 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:
    • 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/20131031 (last edited 2013-11-07 15:52:29 by AlejandroPiñeiro)