W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2008

Re: Alternative Formats

From: Mag Leahy <magleahy@gmail.com>
Date: Thu, 28 Aug 2008 17:03:31 +0100
Message-ID: <a25bda170808280903r14cd24c7xa10d391a7fbf02a1@mail.gmail.com>
To: "Ryan Jean" <ryanj@disnetwork.org>
Cc: "Phill Jenkins" <pjenkins@us.ibm.com>, w3c-wai-ig@w3.org
That's an awesome goal. Right behind you!

On Thu, Aug 28, 2008 at 4:56 PM, Ryan Jean <ryanj@disnetwork.org> wrote:

>  Thank you for your reply. It's my goal to have EVERYTHING accessible to
> EVERYONE.
>
>
>
> Sincerely,
>
> Ryan Jean
>
> Assistant IT Specialist
>
> The Disability Network
>
> Flint, MI
>
>
>  ------------------------------
>
> *From:* w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] *On
> Behalf Of *Phill Jenkins
> *Sent:* Thursday, August 28, 2008 10:04 AM
> *To:* w3c-wai-ig@w3.org
> *Subject:* RE: Alternative Formats
>
>
>
>
> >  . . . I was referring to all formats, such as visual, audio, and
> written. I do see where all 3
> > of these would fall into web accessibility. Visual for graphics, audio
> for sound, and
>  > written for downloading files as PDF or TXT. Do you agree?
>
> Well, I would expand your simple list to also include the following, quoted
> from Understand WCAG:
>
>    - *Controls, Input: *If non-text content is a control or accepts user
>    input, then it has a name<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#namedef>that describes its purpose. (Refer to
>    *Guideline 4.1*<http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat.html>for additional requirements for controls and content that accepts user
>    input.)
>    - *Time-Based Media: *If non-text content is time-based media, then
>    text alternatives at least provide descriptive identification of the
>    non-text content. (Refer to *Guideline 1.2*<http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv.html>for additional requirements for media.)
>    - *Test: *If non-text content is a test or exercise that must be
>    presented in non-text format<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#must-nontextdef>,
>    then text alternatives at least provide descriptive identification of the
>    non-text content.
>    - *Sensory: *If non-text content is primarily intended to create a specific
>    sensory experience<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#sensoryexpdef>,
>    then text alternatives at least provide descriptive identification of the
>    non-text content.
>    - *CAPTCHA*<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#CAPTCHAdef>
>    *: *If the purpose non-text content is to confirm that content is being
>    accessed by a person rather than a computer, then text alternatives that
>    identify and describe the purpose of the non-text content are provided, and
>    alternative forms of CAPTCHA using output modes for different types of
>    sensory perception are provided to accommodate different disabilities.
>    - *Decoration, Formatting, Invisible: *If non-text content is pure
>    decoration<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#puredecdef>,
>    is used only for visual formatting, or is not presented to users, then it is
>    implemented in a way that it can be ignored by assistive technology<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#atdef>
>    .
>
>
> Regards,
> Phill Jenkins
> IBM Research - Human Ability & Accessibility Center
> http://www.ibm.com/able
>



-- 
Mag
Received on Thursday, 28 August 2008 16:04:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:28 GMT