W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2005

RE: Applicability Conditions For Techniques

From: Alistair Garrison <alistair.garrison@accessinmind.com>
Date: Mon, 10 Jan 2005 21:15:10 +0100
To: "'Chris Ridpath'" <chris.ridpath@utoronto.ca>, <w3c-wai-gl@w3.org>
Message-Id: <20050110201514.CA7F438005@smtp1-1-sn3.vrr.skanova.net>
Hi Chris, 


With a little tweaking these might work well as a support for an HTML
Techniques Checklist, however, the issues arise when you start trying to
incorporate the general techniques, or start to think about potential future
technologies.  To my mind, the safest solution would be to provide
'applicability conditions' for each technique (no matter what the
technology) - the reason being that possibly the best approach (and
simplest) to the checklist problem would be to ask which Technologies a user
is looking to implement to what level of accessibility, then formulate a
list of all relevant techniques, and by using the 'applicability conditions'
on each technique simply ask the user which are appropriate to them.


They then would end up with a list of all applicable techniques (for all
conceivable techniques), which they could test using your test suites :-).


Let me know your thoughts.  





From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Chris Ridpath
Sent: 10 January 2005 20:40
To: Alistair Garrison; w3c-wai-gl@w3.org
Subject: Re: Applicability Conditions For Techniques


Hi Alistair,


The techniques are already organized by HTML element, like the HTML spec. If
you want to find out about authoring data tables then you go to the data
tables section. Example:



The test suite is organized by HTML element as well. Is this the
"applicability condition" you need?





----- Original Message ----- 

From: Alistair Garrison <mailto:alistair.garrison@accessinmind.com>  

To: w3c-wai-gl@w3.org 

Sent: Monday, January 10, 2005 1:37 PM

Subject: Applicability Conditions For Techniques


Dear All, 


I believe there is a need for each technique to contain one or more simple
statements which define the conditions under which the technique is deemed
applicable - an example of such a statement might be simply 'This technique
is applicable if one or more data-tables have been used'.


The benefit of doing this is that it allows a user to determine without
doubt whether or not a technique is relevant to their situation - if it is
applicable they can proceed to test whether it is 'passed' or 'failed', and
if it isn't they can mark it as 'non-applicable'. 


By providing 'applicability conditions' I believe it further strengthens the
'testability' of the guidelines.  This extra step ensures that decisions as
to 'applicability' can be made with certainty, providing an almost
prescriptive framework (taking into account 'testable statements') by which
a technique can being declared as 'passed', 'failed' or 'non-applicable'.  


Please let me know your thoughts.


Alistair Garrison 

Managing Director 

Accessinmind Limited UK Filial


Tel.: 0046 8 44 65 287
Website: http://www.accessinmind.com
IMPORTANT: This e-mail, including any attachments, is for the addressee   
only.  It may contain privileged and/or confidential information.  If it   
has come to you in error, please notify the sender immediately.  If you   
are not the intended recipient you must not use, disclose, copy, print,   
distribute or rely on its contents.  All e-mails and any attachments are
believed, but not warranted, to be virus free.  However, all e-mails   
should be virus checked before being downloaded and we accept no  
responsibility therefore. 

Received on Monday, 10 January 2005 20:15:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:52 UTC