- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Mon, 23 Jul 2018 07:46:46 +0100
- To: Joanmarie Diggs <jdiggs@igalia.com>
- Cc: Léonie Watson <tink@tink.uk>, "group-aria-chairs@w3.org" <group-aria-chairs@w3.org>, "public-html@w3.org" <public-html@w3.org>, sohara@paciellogroup.com
- Message-ID: <CA+ri+Vkkqr91Oh7DfWEmcyUGXT7gD+k6u0Ut6uXOvanjYKnwXQ@mail.gmail.com>
thanks Joanie, looping in Scott O'hara as he will be co-editing HTML-AAM -- Regards SteveF Current Standards Work @W3C <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/> On 22 July 2018 at 20:46, Joanmarie Diggs <jdiggs@igalia.com> wrote: > Hey Steve. > > No worries. In terms of what needs to be done on your end: The tests > need to be created. In my original message I included links to what > we've done for Core-AAM in WPT as those seem closest to what you'll need > to write/generate for HTML-AAM testing. > > I think for all the element to platform-role tests, you'll have slight > variations of > https://github.com/web-platform-tests/wpt/blob/master/core-aam/paragraph- > manual.html. > In fact, the paragraph-manual.html test probably only needs one change > to be used for the 'p' element: Where we have: > > <div role="paragraph" id="test">content</div> > > You'd want something like: > > <p id="test">content</p> > > Of course, the line above that says: > > <p>This test examines the ARIA properties for paragraph.</p> > > You presumably want the description of the test to be about HTML rather > than ARIA. Thus two changes rather than one. But you get the idea. > > What you'll see in the json included in the test file should remind you > of a typical AAM table entry. > > Regarding the "wai-aria" tools, for now you want to keep those as-is. > That's where Shane's code lives. Once we refine the ATTAs and try to get > them upstreamed into WPT, that might change. > > If you have some tests for me to try locally, I'm happy to do so. > Similarly, if you have questions about how to write a test to accomplish > something, let me know. There are ARIA and/or Core-AAM tests for roles, > states, properties, events, etc. The AccName tests have name and > description calculation examples. There are also so docs-in-progress > here: https://spec-ops.github.io/atta-api/ > > Once we have working HTML-AAM tests, we can add them to WPT and then > start generating the test results using the local ATTAs and wptreport. > > Hope this helps. And please let me know if you have any questions. Thanks! > > --joanie > > On 07/19/2018 05:32 AM, Steve Faulkner wrote: > > Hi Joanie, > > really sorry for not responding earlier, i missed the email. > > > > Thanks and YES PLEASE, let me know what needs doing from our end. > > > > Note I will be on vacation august 2nd-30th. > > > > -- > > > > Regards > > > > SteveF > > Current Standards Work @W3C > > <http://www.paciellogroup.com/blog/2015/03/current- > standards-work-at-w3c/> > > > > On 10 July 2018 at 18:21, Léonie Watson <tink@tink.uk > > <mailto:tink@tink.uk>> wrote: > > > > + public-html@w3.org <mailto:public-html@w3.org> > > > > Thanks Joanie, and sorry for this late reply. It's my understanding > > that this testing would be very helpful, but I'll defer to the > > editors. Steve, Alexander, Bogdan, and Scott, can you confirm? > > > > Thanks. > > Léonie. > > > > > > On 05/07/2018 22:02, Joanmarie Diggs wrote: > > > > (Fixing Steve's address. Sorry for the noise.) > > > > Hey all. > > > > As you may recall, I volunteered to get you test results for > > HTML-AAM > > using the ARIA Working Group's in-progress (but working well > enough) > > automated testing tools. That offer still stands. Are you > > interested? > > > > If so, you can find examples of what the tests need to look like > in > > https://github.com/web-platform-tests/wpt/tree/master/core-aam > > <https://github.com/web-platform-tests/wpt/tree/master/core-aam>. > As > > you'll see there, if the test name starts with "aria-" it's a > > state or > > property test. If it starts with a role name, it's a role test. > > My guess > > is that you should be able to generate the tests you need > > automatically > > by creating a javascript tool to parse your spec and spew out > > one test > > file per element or attribute in the table. > > > > If you have other plans for testing, let us know and I'll stop > > with the > > pinging. :) Otherwise, this approach should help the ARIA WG > further > > sanity check and improve its tools while at the same time quickly > > getting you a thorough set of results. > > > > Take care. > > --joanie > > > > > > -- > > @LeonieWatson @tink@toot.cafe Carpe diem > > > > > >
Received on Monday, 23 July 2018 06:47:55 UTC