Thread Subject: Re: intro for 8.1?

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: Andrew Kirkpatrick
Date: Thu, Sep 20 2007 11:05 AM

Allen,

You state "When determining the most accessible product from a set of
more than one, the format information is provided in can determine if
other requirements can be met or not" but just because a format includes
support for a particular standard it doesn't mean that the product that
uses that format takes advantage of that support.

How do you envision the support for the content formats being defined?
Does each content format have a VPAT? If so, who writes it?

Part of my concern with the implementation of this section is that the
product is already reporting on how they support standards that overlap
with the content format items - I'm not sure that it will actually help
in procurement decisions since the product needs to meet the section 3
standards, and the section 8 standards not only don't bring anything new
to the picture but they are not necessarily representative of the
accessibility in the specific product.

AWK





> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Hoffman, Allen
> Sent: Thursday, September 20, 2007 11:43 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] intro for 8.1?
>
> All:
>
> Several people have raised questions related to how
> provisions in 8.1 relate to other sections. I think I'd like
> to propose an update to the draft for 09/14 to include some
> intro materials to alleviate this concern, as it is obvious
> some connection is needed to make this self-evident.
>
> So:
>
> Sections 3 and 6 above require that information delivered
> must be presented meeting accessibility requirements. To
> accomplish this, information storage formats must allow for
> inclusion of certain accessibility related attributes and/or
> functionalities. This section describes the functional
> accessibility requirements for such formats.
> When determining the most accessible product from a set of
> more than one, the format information is provided in can
> determine if other requirements can be met or not, and can be
> an important factor in the final determination. Note:
> Formats which do not include some functionalities such as the
> ability to represent synchronized media, would not be subject
> to that provision.
>
>
>

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