Thread Subject: Re: Clarification on accessible contentregardlessof medium

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: Gregg Vanderheiden
Date: Wed, Feb 13 2008 2:45 PM

Good note Allen,

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



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Hoffman, Allen
> Sent: Wednesday, February 13, 2008 3:20 PM
> To: TEITAC Committee
> Subject: Re: [teitac-committee] Clarification on accessible
> contentregardlessof medium
>
> This provision is intended, I believe, to answer the question
> of is content not transported, or delivered just from a web
> server, required to be accessible. My memory is that almost
> all thought that the content does need to be accessible.
> What in this language beyond the archiving issue, is problematic?
>
> "In complying with this subpart, each agency must operate
> software in a manner such that output from the software that
> is distributed or archived by the agency, regardless of the
> medium of storage or transmission, is made accessible to
> people with disabilities."
>
> I can live with removal of archiving.
>
> I could also suggest additional notes go with it such as:
>
> Note:
> The committee recognizes that interim versions of documents
> may not meet this requirement as work groups develop language
> or content in stages.
> However, when content is distributed to an audience that is
> not sufficiently small enough so that the authors know the
> accessibility needs for each member, then the content must be
> made accessible.
> Basically, when in doubt, make accessible. Additionally,
> when content is intended to store a specific visual capture
> of images for various purposes, such content is considered
> accessible as long as it is accompanied by an alternate text
> description--which can be accomplished in several ways, which
> don't all involve incorporating that description in to a
> single file, or file format.
>
>
>
>
>
> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Jim Tobias
> Sent: Wednesday, February 13, 2008 3:39 PM
> To: 'TEITAC Committee'
> Subject: [teitac-committee] Clarification on accessible
> content regardlessof medium
>
> Hi All,
>
> In our discussion this past Monday with the Access Board, an
> item came up that they would like the Committee to clarify.
> Many people seem to think that as long as content is not on
> the web, such as stored on on a CD or DVD, or transmitted via
> email or FTP (instead of HTTP), it is somehow exempt from 508.
>
> Although our recommendations seem to clearly cover other
> media, the staff would like to see some more explicit
> language. I think the best place is in Subpart D, provision
> 2-D - Accessible Content. It currently
> reads:
>
> "In complying with this subpart, each agency must operate
> software in a manner such that output from the software that
> is distributed or archived by the agency is made accessible
> to people with disabilities."
>
> Mike and I propose amending it to read:
>
> "In complying with this subpart, each agency must operate
> software in a manner such that output from the software that
> is distributed or archived by the agency, regardless of the
> medium of storage or transmission, is made accessible to
> people with disabilities."
>
> This provision is on next Tuesday's agenda.
>
> Thanks.
>
> ***
> Jim Tobias
> Inclusive Technologies
> +1.732.441.0831 v/tty
> +1.908.907.2387 mobile
> skype jimtobias
>
>

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