W3C home > Mailing lists > Public > public-aria@w3.org > February 2017

Minutes for Thursday, 23 February 2017 WAI-ARIA Working Group

From: Michiel Bijl (list) <michiel.list@moiety.me>
Date: Thu, 23 Feb 2017 18:32:05 +0000
To: ARIA Working Group <public-aria@w3.org>
Message-Id: <79897F3A-6549-4A78-8777-8FB3F5085B13@moiety.me>
Minutes for today’s call can be found as text in this e-mail or at this URL: https://www.w3.org/2017/02/23-aria-minutes.html

— Michiel


      [1] http://www.w3.org/

                               - DRAFT -

   Accessible Rich Internet Applications Working Group Teleconference

23 Feb 2017

   See also: [2]IRC log

      [2] http://www.w3.org/2017/02/23-aria-irc


          Joanmarie_Diggs, Stefan, MichielBijl, janina,
          Joseph_Scheuhammer, jongund

          Léonie_Watson, James_Nurthen, Bryan_Garaventa


          MichielBijl, joanie


     * [3]Topics
         1. [4]Testable statements - Progress update
         2. [5]ATTA progress updates
         3. [6]Testable statements - Progress update
         4. [7]ATTA progress updates
         5. [8]Getting started on manual testing
     * [9]Summary of Action Items
     * [10]Summary of Resolutions

   <joanie> agenda: this

   <joanie> agenda: be done

Testable statements - Progress update

   <MichielBijl> scribe: MichielBijl


     [11] https://www.w3.org/wiki/ARIA_1.1_Testable_Statements

   <joanie> "volunteer name here": 131

   <joanie> "stefan": 37

   ^ list of people and their assigned objects

   JD: We need to get volunteers for those 131 items

   <joanie> Updated Milestones:

     [12] https://www.w3.org/WAI/ARIA/project

   We’ll hit PR Feb 2017

   That’s like, now…

   MC: That’s the latest milestone that we discussed and agreed to

   If it raises concerns if we don’t meet them

   Should tell Philippe if we’re not going to meet them

   JD: If you can volunteer for part of these testable statements
   that be great

   We could work together on the same issue

   If someone wrote like the markup for issues

   SS: I see that the “has tests” is still in the document

   JD: Joseph went through it

   JS: I’m working my way through them when I can

   JD: Reason we keep flags in there, it’s kind of a hack for lack
   of a better word for it

   Anything with parenthesis basically says “Don’t generate actual

   MB: Is it just writing mark-up?


     [13] https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#combobox_haspopup_unspecified


     [14] https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#aria-haspopup

   SS: The code part is for humans?

   They read and do a manual test based on that?

   The next part is for machines?

   JD: Partly correct

   The first part gets pulled into Shane’s tool

   The part that surrounds the code is not processed

ATTA progress updates

   JG: We installed WPT on Windows

   Build a simple adapter

   We can now get the information from WPT

   <joanie> scribe: joanie

   JD: Regarding the Mac, I now have the core accessibility API
   stuff down. I have local code which can print accessibility
   trees, listen for accessibility events, locate specific
   elements, get the desired properties of a specified element,
   etc. In other words, I am able to do the core functionality
   needed in an ATTA. And this works both with Safari and Chrome
   Canary. The one blocking bit is that Chrome Canary

   doesn't expose the HTML id attribute, and we're counting on
   that attribute being present to locate the element specified in
   the testable statements. I've emailed Dominic Mazzoni (Google
   accessibility developer) and told him how Safari exposes it. He
   said he'd see about doing the same in Chrome so we can do
   automated testing there. My next step is to turn what I've got
   into an actual ATTA which works with

   WPT. I think that will be pretty easy as the Mac code I've done
   is in Python 3 and the Linux ATTA I've written which is fully
   functional is also written in Python 3.

   <scribe> scribe: MichielBijl

   JD: **Correction**: text that prefixed code is processed by
   Shane’s tool.

Testable statements - Progress update


     [15] https://github.com/Spec-Ops/web-platform-tests/blob/aria-atta-support/wai-aria/tools/make_tests.pl#L225

ATTA progress updates

Getting started on manual testing

   JD: Any questions on this?

   Thank you all, that’s a wrap

Summary of Action Items

Summary of Resolutions

   [End of minutes]

    Minutes formatted by David Booth's [16]scribe.perl version
    1.148 ([17]CVS log)
    $Date: 2017/02/23 18:25:31 $

     [16] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [17] http://dev.w3.org/cvsweb/2002/scribe/

Scribe.perl diagnostic output

   [Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14
Check for newer version at [18]http://dev.w3.org/cvsweb/~checkout~/2002/

     [18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Philipe/Philippe/
Succeeded: s/Regarding the Mac/JD: Regarding the Mac/
Found Scribe: MichielBijl
Inferring ScribeNick: MichielBijl
Found Scribe: joanie
Inferring ScribeNick: joanie
Found Scribe: MichielBijl
Inferring ScribeNick: MichielBijl
Scribes: MichielBijl, joanie
ScribeNicks: MichielBijl, joanie
Present: Joanmarie_Diggs Stefan MichielBijl janina Joseph_Scheuhammer jo
Regrets: Léonie_Watson James_Nurthen Bryan_Garaventa
Found Date: 23 Feb 2017
Guessing minutes URL: [19]http://www.w3.org/2017/02/23-aria-minutes.html
People with action items:

     [19] http://www.w3.org/2017/02/23-aria-minutes.html

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

   [End of [20]scribe.perl diagnostic output]

     [20] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm

— Michiel
Received on Thursday, 23 February 2017 18:32:59 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 February 2017 18:32:59 UTC