Meeting Summary

  • Meeting started by Piñeiro at 16:01 CET.
  • Meeting ended at 17:05 CET.
  • Participants (Lines Said):
    • Piñeiro - API (152)
    • Joanie - joanie (68)
    • Joseph - clown (62)
  • Log

"Boston" Summit Recap and Wayland Situation

  • Last weekend (+Monday) some members of the a11y team were present at the "Boston" Summit, this year in Montreal.
  • The main topic was Wayland, and we were testing, debugging and triagging GNOME during the summit (and joanie even before).
  • We also talked with several developers there about the Wayland situation. Specifically Matthias Clasen and Jasper.
  • Wou can find a summary of current status and findings here: Accessibility/Hackfests/Montreal2013

  • Joanie has started looking into the OSK too, which is not on that page yet.
  • We plan to use that page as a base of a more general and permanent "Current situaion of wayland" page.
  • FWIW, we also fixed non-wayland bugs there.
  • As an outcome of those conversations, some mailing list threads were started.
  • One on gnome-accessibility-devel about getting the information of the current window.
  • https://mail.gnome.org/archives/gnome-accessibility-devel/2013-October/msg00006.html

  • And another on wayland list, sent by mclasen, that lists several of the things we discussed at the summit.
  • https://mail.gnome.org/archives/gnome-accessibility-devel/2013-October/msg00008.html

  • ACTION: gnome-shell is not accessible on wayland, though a hacky solution is available. Piñeiro will look into a proper solution.
  • ACTION: Piñeiro will look at tooltip related code to see the possibility of adding mouse-in, mouse-out event at the a11y toolkit.
  • ACTION: Joanie will keep testing the OSK and write up her findings, file bugs, etc.
  • ACTION: everybody: being active on the threads opened.
  • ACTION: Joanie will create a non-hackfest/summit a11y in wayland page.
  • Tentatively: Mike will keep his focus on the at-spi2 async API.

Other 3.12 Work

  • Plans for 3.12 are similar to the list we made last week.
  • Main topics: wayland + at-spi2 async API.
  • Medium topics:
    • already existing features (tinting+focus tracking UI).
    • that to-be-proposed feature about homogeneous keyboard navigation.
    • several focus related methods were deprecated. Some work started on toolkits: test it.
    • atk_text_get_string_at_offset defined at ATK. Need to start to implement and test it on the toolkits. Probably that would lead to having just one implementation on gtk/clutter, probably on pango. Follow up on this, test it.
    • About the previous item: webkitgtk already has a implementation of that method.
  • ACTION: Joanie will test Benjamin's work-in-progress focus-related deprecation patch.
  • ACTION: Piñeiro will check with gtk and clutter developers to see what the plans are with respect to pango.
  • We are at the beginning of the cycle, so listing all the remaining tasks. Eventually we would need to do a fine-grained prioritization and see if there is something that can wait to 3.14.

W3C Updates

Miscellaneous Time

  • (Nothing infoed)

Action Items

  • Joanie:
    • Create a non-hackfest/summit a11y in wayland page.
    • Test Benjamin's work-in-progress focus-related deprecation patch.
  • Piñeiro:
    • 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.

Ongoing / Rolled-Over

  • 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.
    • 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 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.
    • 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.

Accessibility/Minutes/20131017 (last edited 2013-11-07 12:48:51 by JoanmarieDiggs)