Meeting Summary

  • Meeting started by Piñeiro at 16:05 CET.
  • Meeting ended at 17:27 CET.
  • Participants (Lines Said):
    • Piñeiro - API (206)
    • Joanie - joanie (99)
    • Joseph - clown (95)
    • Magdalen - magpie_ (48)
    • Heidie - heidie (32)
    • Juanjo - jjmarin (14)
    • Mike - mgorse (9)
  • Log

MouseTrap Update

  • LINK: https://wiki.gnome.org/MouseTrap

  • Working to get it up to gnome 3 (including python 3)
  • Head, finger, and use eyes to click.
  • It isn't working yet, and we're focusing on the forehead.
  • This is the second class meeting for our Software Engineering class.
  • We've got six students who are going to push on MouseTrap for the semester.

  • And we're just getting up to speed on IRC channels and stuff.
  • Hopefully soon we'll have an upstream branch where the current work will be placed.

Bug 707010

  • API detected a bug that prevents using atspi listener on javascript code, specifically, in a program using gjs context (so c+javascript)
  • The problems seems to be that the methods are loaded -- all of them, doesn't matter if they are used or not.
  • Jasper recognizes that it seems to be a gjs bug, but does not plan to fix that soon.
  • Piñeiro's proposal is to skip that method at the gobject-introspection phase.
  • Taking into account that that method doesn't conform gobject-introspection format, Piñeiro thinks that makes sense. But to do that we need to ensure that is not used. Looking at pyatspi2 he didn't find anything.
  • General consensus (included maintainer) is skip that method.
  • ACTION: Piñeiro will request an API freeze break request
  • LINK: https://live.gnome.org/Schedule

Orca preferences/configuration GUI abstraction/separation

  • Topic postponed due to Luke being absent

AT-SPI and desktop environment compositors using Wayland/Mir

  • Topic postponed due to Luke being absent

Extending at-spi to support touch gestures

  • Topic postponed due to Luke being absent

GSoC Update

  • End of last week, Joseph worked with Magdalen in IRC preparing the latest patch for the tracker + magnifier.
  • Mostly were working on the tracker code at that time. More specifically Joseph was asking about that.
  • Magdalen posted a patch to bugzilla on Monday.
  • Jasper reivewed and Joseph reviewed.
  • Magdalen has had a lot of problems testing the files and hopes that the problem Piñeiro found will make testing easier from here.
  • Magdalen intends to get the next patch out as soon as possible and for it to be fully working.
  • Magdalen is not sure where the current work sits in the timeline.
  • https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/magpie/1

  • Regarding when/how to attach patches:
    • Bugzilla is a tool to report bugs, and provide patches that solve the bug.
    • Usually, those patches are finished (so working) and tested
    • If that is not the case, but the developer things that it is worth to upload it, the usual is adding a disclaimer.
  • ACTION: Magdalen is going to apply Mike Gorse's patch and start testing the work and then make the last changes that need to be done to get the patch ready.
  • There are a couple of warnings in the magnifier that also need to be looked at.
  • Magdalen is not sure whether to fix them separately from the magnifier work.
  • Steps recommended by Joseph:
    1.  Get a app that supports focus navigation via the TAB key.
    2. Start the magnifier.
    3.  Use the TAB key presses to move focus around that app.
    4.  Does the focused object scroll into view?  If not, it isn't working.
    5.  Drop into a terminal and change the tracking gsettings  — switch between centered, push, proprotional.
    6.  Does the mode of focus tracking appropriately change?
    7. Find an app that exposes caret motion through the a11y API.
    8.  Repeat steps 3, 4, and 5. with the text caret insertion point.

Marketing

  • Recently Allan Day sent an email about Release Notes Time
  • https://mail.gnome.org/archives/desktop-devel-list/2013-August/msg00210.html

  • Team members can inform Juanjo by irc or email or fill info in on the wiki.

  • ACTION: Joanie will go through and make the list of features included in the minutes as they were not infoed.
  • Features from the log:
    • implemented magnifier caret and focus tracking (if it gets included in time for the release)
    • implemented accessibility support for gnome-shell sliders
    • made gnome-shell calendar keyboard navigable (with bugs, but now is navigable)
    • implemented caret navigation for evince so that documents can be read by Orca users
    • Super + Alt + S now is the official keyboard shortcut to toggle orca

Action Items

  • Joanie:
    • Make the list of features included in the minutes since they were not infoed.
  • Magdalen:
    • Apply Mike Gorse's patch and start testing the work and then make the last changes that need to be done to get the patch ready.
  • Piñeiro:
    • Request API freeze break request for bug 707010.

Ongoing / Rolled-Over

  • Joanie:
    • Do some testing and update the Evolution a11y bugs.
    • Email Mark Sadecki about our team meetings and invite him to join us to provide W3C updates.
  • 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.

Accessibility/Minutes/20130829 (last edited 2013-09-12 13:31:14 by JoanmarieDiggs)