- From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
- Date: Thu, 22 Feb 2018 16:20:13 +0000
- To: Joanmarie Diggs <jdiggs@igalia.com>
- CC: 'ARIA Working Group' <public-aria@w3.org>
No problem, :) I'm aware also of many of these and am still working the finer details out. E.G Nested widgets like comboboxes I have working properly now which impacts other nested widget types, plus I'm in the process of adding aria-owns mappings which were previously missing, so as I work on the adding of these processes and making these work in accordance with the spec then everything will shift slightly from a testing perspective. I hope to have these recursion.js changes done by sometime next week, so the name computation testing at present is still a bit premature until this is done. As I go through this as well, I'm saving out more advanced test cases that are missing from the archive, so I'll have a separate folder for these when all of these things are done. Bryan Garaventa Accessibility Fellow Level Access, Inc. Bryan.Garaventa@LevelAccess.com 415.624.2709 (o) www.LevelAccess.com -----Original Message----- From: Joanmarie Diggs [mailto:jdiggs@igalia.com] Sent: Thursday, February 22, 2018 6:21 AM To: Bryan Garaventa <bryan.garaventa@levelaccess.com> Cc: 'ARIA Working Group' <public-aria@w3.org> Subject: Re: HTML Executables for Testing Statements Now Complete Bryan, have I mentioned you rock? <smiles> Thank you so much for doing this work! I've compared what your tool says the name should be with what the ARIA 1.0 expectations were/are. There are some discrepancies. In some cases I think our expectations are right. In some cases, I'd have to look at the algorithm. Since I need to investigate mappings on macOS and likely update the platform expectations accordingly, it would be great if you could investigate the discrepancies. I've detailed them here: https://github.com/WhatSock/w3c-alternative-text-computation/issues/6 Thanks again *very* much!! --joanie On 02/20/2018 02:32 AM, Bryan Garaventa wrote: > Hi, > As requested I added all of the testable statements as executable HTML > files in the archive at > https://github.com/whatsock/w3c-alternative-text-computation > > I started doing this individually, and found that it was brain numbingly boring and tedious, so I wrote a JScript application that will do this automatically, which I've added to the repo in case it's useful for anybody else. I think this only works on Windows; I'm not sure if WScript is executable elsewhere. > > This also automatically generates an index.html file in the same folder for easy testing on webservers: > https://whatsock.github.io/w3c-alternative-text-computation/Autogenera > ted%20AccName%201.1%20Testable%20Statements%20-%20W3C/index.html > > When the Testable Statements wiki page is updated, running this script will refresh the list and add the new tests automatically. > > As requested, I'll continue going through them to identify those that are missing, but this takes care of the lionshare of what I was tasked to do at present. > > All the best, > Bryan > > > > Bryan Garaventa > Accessibility Fellow > Level Access, Inc. > Bryan.Garaventa@LevelAccess.com > 415.624.2709 (o) > www.LevelAccess.com > >
Received on Thursday, 22 February 2018 16:20:45 UTC