Thread Subject: Multiple testable criteria
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
Return to this mailing list's archives
From: Andi Snow-Weaver
Date: Tue, Oct 24 2006 8:20 PM
Subject: Multiple testable criteria
<Allen's comment>
Just an aside, one thing to make the standards when final less confusing
is to *not* put two testable conditions into one standard. It makes
making straightforward test plans with condition, expected outcome, and
result a lot more complicated, when, for example, a standard actually
has two tests, and several outcomes.
<end of Allen's comment>
Allen,
Can you provide an example of Section 508 criteria where this is a problem?
Andi
From: Hoffman, Allen
Date: Wed, Oct 25 2006 6:10 AM
Subject: Re: Multiple testable criteria
<Andi's comment:
>Allen,
>
>Can you provide an example of Section 508 criteria where this is a
problem?
1194.21(d) Sufficient information about a user interface element
including the identity, operation and state of the element shall be
available to assistive technology. When an image represents a program
element, the information conveyed by the image must also be available in
text.
This has (a), use of appropriate attributes/assistive technology API(s)
to expose information about interface elements, and (b) the item related
to text for images. these are separate items, so when the test fails,
it can fail for (a) or (b).
1194.21(b) also has two testable conditions, OS related, and application
related.
Allen Hoffman
Department of Homeland Security
Office on Accessible Systems & Technology
From: Andrew Kirkpatrick
Date: Wed, Oct 25 2006 8:55 AM
Subject: Re: Multiple testable criteria
> 1194.21(d) Sufficient information about a user interface
> element including the identity, operation and state of the
> element shall be available to assistive technology. When an
> image represents a program element, the information conveyed
> by the image must also be available in text.
>
> This has (a), use of appropriate attributes/assistive
> technology API(s) to expose information about interface
> elements, and (b) the item related to text for images. these
> are separate items, so when the test fails, it can fail for
> (a) or (b).
I view b as a subset of a in 21d. The identity of the image is
established via the text. In a application, if there is no image
equivalent then it fails based on both portions.
I agree that there are multiple testable criteria in 21b, but I'm not
sure that this is a problem.
AWK
WebAIM is an initiative of:
