- From: James Craig <jcraig@apple.com>
- Date: Tue, 08 Apr 2014 11:40:22 -0700
- To: "Foliot, John" <john.foliot@chase.com>
- Cc: Birkir Gunnarsson <birkir.gunnarsson@deque.com>, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>, Cynthia Shelly <cyns@microsoft.com>, "public-pfwg@w3.org" <public-pfwg@w3.org>
On Apr 8, 2014, at 11:25 AM, Foliot, John <john.foliot@chase.com> wrote: > I think we are talking past each other. There won't be "a list" - there will be a data-store of test results of ARIA attributes (and combinations when required) tested against [Operating system + versions] + [Browser + versions] + [Assistive Technology + versions]. It will all be captured in a single database - the end. It sounds a lot like the ARIA test harness. Why are you duplicating this effort instead of contributing to the existing one? We've got 700+ test cases already. > No, asking the crowd to be that granular is a recipe for low participation. At a minimum then, the tool should not prevent them from entering this critical information. > Once the data store starts growing, it would be relatively easy for an engineer at any company to run a query to ferret out bugs in their current builds Browser and AT manufacturers deal in bug numbers of thousands or tens of thousands with every release and have work flows revolving around the official bug databases for those products. It's naïve to assume an engineer would manually compare and resolve the results of one database query against another. If your database included a place for a bug number, plus other useful information such as "last tested version", this would not have to be manual.
Received on Tuesday, 8 April 2014 18:41:52 UTC