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: Smith, Jamie
Date: Wed, Sep 12 2007 12:30 PM

I definitely feel we must have this as a provision. In Florida, public
information is often in Spanish and Creole as well as English. Some
documents are the "Florida Comprehensive Assessment Test" test materials
and while the document is in Spanish or Creole the test examples are
always in English. The lack of coding for the language did cause speech
to select a language and attempt to read the Creole with that language.
>From the point of the first change to Creole on (even when text was back
to English), speech messed up. Adding the language code in the doctype
and then to the specific sections which had a different language fixed
the problem. The reason the language code wasn't done, simply because
it wasn't required.

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: Thursday, September 06, 2007 9:32 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] 3d/3e for content format

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