1 <<TableOfContents(2)>>
   2 
   3 = Meeting Summary =
   4  * Meeting started by Piñeiro at 16:04 CET.
   5  * Meeting ended at 17:15 CET.
   6  * Participants (Lines Said):
   7    * Piñeiro - API (85)
   8    * Joanie - joanie (70)
   9    * Joseph - clown (62)
  10    * Magdalen - magpie (28)
  11    * Juanjo - jjmarin (19)
  12  * [[attachment:20130502_log.txt|Log]]
  13 
  14 == Our GSoC/OPW candidate ==
  15   * After evaluating her first proposal, the click lock feature, it was decided with Marina to ask her to look for another project.
  16   * Magpie was interested in a11y, so she decided to go for the caret and focus tracking.
  17   * Joanie wrote a draft for the caret and focus tracking and magpie started to work on her application with the help of Joanie and Juanjo.
  18     https://docs.google.com/document/d/1fZ2_3GT_Z5qBSnY1aMnfcHsp_c8sgLlffGBztP6nIgA/edit
  19     https://docs.google.com/document/d/15Qin-ohJ4M8GWRIsNLob87kvGL9ul2OmcQErPlq0Ioo/edit?usp=sharing
  20   * Juanjo will help magpie to send her application to OPW and GSoC.
  21   * ACTION: Juanjo will help magpie to send her application to OPW and GSoC.
  22 
  23 == W3C Update ==
  24   * Results page for ARIA  testing is now public: http://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=1.
  25   * The report shows the results for different browsers, and for different accessbility APIs.
  26   * The rows are the different test cases. Clicking the link of a test case will take you to a more detailed view of who ran the test, and what they declared about it.
  27   * Example: test case 163: http://www.w3.org/WAI/PF/testharness/testresults?testsuite_id=1&testcase_id=163
  28   * A test case where the role="button" and aria-pressed="mixed".  The expected result, alas, is not shown.
  29   * Each tester is assigned a specific platform. Joseph has been focusing on FF/ATK/AT-SPI.
  30   * Everywhere there is a "Pass" in the right most column of the overall results indicates that the specific aria markup is successfully implemented by two platforms.  Meaning, meets success wrt to W3C's CR criteria.
  31   * Although it seems a really interesting and complete test suite GNOME developers are concerned about the involvement of execute the tests with at-spi2 as any bug could be a bug in at-spi2, and not in the implementation of the spec itself.
  32   * We are also worried about the lack of automatic execution and the fact that they are not integrated with the already existing browsers test suites (ff and webkit).
  33   * In our opinion, it would be good to have all those tests integrated.
  34   * As Joanie put it, "I seriously think the thing to do is get these tests added to the implementor's test suites, then you get automation and also buy-in, and less work."
  35 
  36 == Marketing ==
  37   * Nothing to see here, please move on.
  38 
  39 == Miscellaneous Time ==
  40   * Nothing logged.
  41 
  42 = Action Items =
  43 ## ai-start
  44   * Juanjo:
  45     * Help magpie to send her application to OPW and GSoC.
  46 
  47 === Ongoing / Rolled-Over ===
  48   * Joanie:
  49     * Email Mark Sadecki about our team meetings and invite him to join us to provide W3C updates.
  50     * Do a full evaluation of the accessibility breakage in Evolution 3.6 and file bugs accordingly.
  51   * Juanjo:
  52     * Take a look at the current a11y material in order to make an action plan.
  53   * Piñeiro:
  54     * Send a email to accessibility-dev, just in case the Wayland Accessibility section needs to be filled.
  55     * Compose a "what accessibility needs from Wayland, how to use it" email, ask for review, send to the Wayland Developer's list.
  56     * Ping GNOME designers, so hopefully some default keybinding will be available for 3.8.
  57     * Create some usability-configurability related bugs, using Bryen's mail as a starting point.
  58     * Update the AtkObject:children-changed documentation, as this could be also used on ATK implementors.
  59 ## ai-end