W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2013

How to extend Easy Checks.

From: Wayne Dick <wayneedick@gmail.com>
Date: Thu, 9 May 2013 11:18:35 -0700
Message-ID: <CAJeQ8SBOJVcM-0bVU3sb6CDVAZUVOnGuzUEvG-gYz1UetJ2JSg@mail.gmail.com>
To: Shawn Henry <shawn@w3.org>
Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Hi,

I need to work here starting at 5AM PDT, so I won't be there tomorrow.
So, here are my ideas.

Easy Check Extensions to Ongoing Testing:

I think the Easy Check is sufficient for ongoing development.  That is
if the developer thinks of each project phase(and fragment of a phase)
as an end product then Easy Check is good and efficient.

I think we should NOT focus on a new check list.  We need to instead
teach developers how to customize Easy Check their project and
institutional culture.  Namely, how do we translate the easy check
generic and vender neutral operations to specific procedures and
vendor assignment.  We can do this all in a vendor neutral neutral
context.

Example Contrast:  We already give table of generic contrast
measurement tools.  So we could say pick an eye-drop tool.  Also, pick
a tabular tool.  Then we could describe a protocol for using both.
Like, hot do deal with recurring false positives in tables.  How to
sample using an eye dropper test. We make no recommendations, but we
describe a protocol for advanced use.  All the development needs to do
is choose venders and go.


Wayne
Received on Thursday, 9 May 2013 18:19:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:56:01 UTC