Thread Subject: Re: Additional issues with closed,self-contained products

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.

From: Rex Lint
Date: Tue, Nov 14 2006 2:25 PM

Indeed, the very first provision for the closed products says,
1194.25 (a) "Self contained products shall be usable by people with
disabilities without requiring an end-user to attach assistive technology to
the product. Personal headsets for private listening are not assistive
technology."

So by "closing" a PC based product with a policy, there is then a different
set of provisions to satisfy than if it were not closed by a policy. I
daresay that the provisions on a closed system are significantly different
than those for the other product classes. And if your suggestion that, " To
meet closed system access they would need to (with their installed AT) be
accessible" (from the provision above), I submit, is open to interpretation:
"be usable by people with disabilities" is not defined in the standard, so
far as I can tell. And all the specific technical requirements for s/w and
o/s and web pages don't apply, only the "closed product" provisions do.

I suspect you have a different interpretation...?

Rex

Rex Lint, Consultant
Chair, Section 508 Working Group
Information Technology Association of America
PH: 603-860-7651, FAX: 603-882-6612


-----Original Message-----
From: Gregg Vanderheiden [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, November 14, 2006 1:32 PM
To: 'Rex Lint'; = EMAIL ADDRESS REMOVED = ; 'TEITAC self contained/closed products
subcommittee'
Subject: RE: [teitac-closed] Additional issues with closed,self-contained
products

Not sure I understand Rex. To meet closed system access they would need to
(with their installed AT) be accessible.

I can understand the "not meeting OS" because they are closed and the AT
part of OS access wouldn't be needed (since it couldn't be accessed anyway).
But the other OS parts would be met because of their closed system
counterparts. And if it browsed web content - wouldn't it need to render
it accessibly to be called accessible?

Or were you saying something else?


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: Rex Lint [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Tuesday, November 14, 2006 12:21 PM
> To: 'Gregg Vanderheiden'; = EMAIL ADDRESS REMOVED = ; 'TEITAC self
> contained/closed products subcommittee'
> Subject: RE: [teitac-closed] Additional issues with
> closed,self-contained products
>
> "Or rather, in their "closed state" they meet all the closed
> product guidelines." {Gregg Vanderheiden]
>
> ...And they might NOT meet the provisions for computer
> operating system/applications nor allow conformant web pages
> to be accessible.
>
> Perhaps we draft an observation that policy can affect
> accessibility as much as technical provisions do, and that
> policy should be adjusted to allow for addition of AT. Where
> to put it? Probably in the standard somewhere...
>
> Rex
>
> Rex Lint, Consultant
> Chair, Section 508 Working Group
> Information Technology Association of America
> PH: 603-860-7651, FAX: 603-882-6612
>
>
> -----Original Message-----
> From: Gregg Vanderheiden [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Tuesday, November 14, 2006 1:14 PM
> To: = EMAIL ADDRESS REMOVED = ; 'Rex Lint'; 'TEITAC self
> contained/closed products subcommittee'
> Subject: RE: [teitac-closed] Additional issues with
> closed,self-contained products
>
> This is a good discussion.
>
> In Diane's example, the computers are closed by policy. So
> some of them
> have AT installed on them (built into them before they are
> closed). Thus they would meet 'closed system' access
> requirements because they met the built in accessibility (by
> added AT) before they were closed. Or rather, in their
> "closed state" they meet all the closed product guidelines.
>
>
> Gregg
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
>
>
>
>

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University