Thread Subject: Re: 3d/3e for content format

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 06 2007 7:40 AM

In the spirit of trying to reduce the extra weight of the new standards,
I'll raise my question again -- why is language support in 508? We do
have other WCAG standards that we have not included, and this seems like
it is not needed in the U.S. standard.

What is our rationale for requiring the language support in content
formats and web and software provisions?

AWK

> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Peter Korn
> Sent: Tuesday, September 04, 2007 3:56 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] 3d/3e for content format
>
> Hi Allen,
>
> We need to be careful with this one. Simple text editors (think
> Notepad) won't be able to do this.
>
>
> Regards,
>
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.
>
> > Action item from Tuesday, 09/04.
> >
> > Content formats which support multiple languages MUST provide a
> > programmatically determinable mechanism to identify the primary
> > language, and the language of any sections which are in
> another language
> > from the primary language.
> >
> >
> >
> > Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
> >

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