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

VOLUNTEERS NEEDED: Writing ARIA 1.1 Testable Statements

From: Joanmarie Diggs <jdiggs@igalia.com>
Date: Fri, 17 Feb 2017 08:09:02 -0500
To: ARIA Working Group <public-aria@w3.org>
Cc: "public-aria-test@w3.org" <public-aria-test@w3.org>
Message-ID: <69dc858b-2a86-df01-4e30-d91d45eeacce@igalia.com>
Hey all.

If you were at yesterday's ARIA meeting, feel free to stop reading --
unless you like the sound of broken records, in which case I'd encourage
you to break a record and play it in the background while you write some
testable statements. ;)

For everyone else.... As discussed at length during yesterday's meeting,
it turns out we have about 170 testable statements left to write for
ARIA 1.1 CR testing. This finding is the result of Michael's review, my
confirmation of his findings, and subsequently adding placeholders for
missing tests. Details of that assessment can be found here:

During the meeting, I asked (arguably begged) for people to tell me my
assumptions and conclusions described in the aforementioned assessment
details were incorrect so that we could reduce the number of testable
statements left to write. No one did. Seems we really do have an
unexpectedly large amount of work to do before testing can begin. :(

If you are able to write testable statements, please take a look at
https://www.w3.org/wiki/ARIA_1.1_Testable_Statements where you will find
a list of items, many of which have a "NEEDS TEST" flag. If that flag is
followed by "volunteer name here" and you feel it's a test you can
write, please replace "volunteer name here" with your name like Stefan
did for quite a few tests. (Thanks Stefan!!)

In an attempt to make things easier, tests are now grouped by property,
and each property has text which describes the change to be tested,
links to the places in the spec where mappings can be found, and in many
cases at least one test that is already written. As an example, see what
was done for aria-checked:

I believe that in many cases, the tests for a given section can be
written via copy and paste, tweaking just one or two things. Again, see
the aria-checked section for an example of where that should be the case.

Lastly, if one particular test seems hard to write, just don't
volunteer. Using aria-checked as an example, if you're not sure how to
write a test for "switch checked value changes" but feel comfortable
writing tests for "switch checked {true,mixed,undefined}" please do the
three you're comfortable with. If we all chip away at this problem, it
should eventually go away. :)

Thank you very, very, very, very much for helping out with this.
Received on Friday, 17 February 2017 13:09:45 UTC

This archive was generated by hypermail 2.3.1 : Friday, 17 February 2017 13:09:46 UTC