- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Wed, 21 Jun 2006 12:13:03 -0500
- To: <public-wcag-teama@w3.org>
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
The Player for my DSS sound file is at http://tinyurl.com/dho6b
-----Original Message-----
From: Lisa Seeman [mailto:lisa@ubaccess.com]
Sent: Wednesday, June 21, 2006 11:37 AM
To: Gregg Vanderheiden
Subject: Re: CLARIFICATION
thanks
also please piont out to the group that there are many more people with LD
then who are blind
All the best and thanks again
Lisa
----- Original Message -----
From: "Gregg Vanderheiden" <gv@trace.wisc.edu>
To: "'Lisa Seeman'" <lisa@ubaccess.com>
Sent: Wednesday, June 21, 2006 5:30 PM
Subject: RE: CLARIFICATION
> Done
>
>
>
> Gregg
>
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
> Professor - Ind. Engr. & BioMed Engr.
> Director - Trace R & D Center
> University of Wisconsin-Madison
> The Player for my DSS sound file is at http://tinyurl.com/dho6b
>
>
>> -----Original Message-----
>> From: Lisa Seeman [mailto:lisa@ubaccess.com]
>> Sent: Tuesday, June 20, 2006 2:40 PM
>> To: Gregg Vanderheiden
>> Subject: Fw: CLARIFICATION
>>
>> please forward my comments on to team A
>> thanks
>> ----- Original Message -----
>> From: <public-wcag-teama-request@w3.org>
>> To: <lisa@ubaccess.com>
>> Sent: Tuesday, June 20, 2006 8:25 PM
>> Subject: Re: CLARIFICATION
>>
>>
>> > *** NOTE: ***
>> >
>> > Your message was sent from an address which is not on the list
>> > of people who are authorized to post to this mailing list.
>> > Therefore, your message has been forwarded to the list maintainer
>> > for manual processing.
>> >
>> > If you do not see your message appear on the list or in the
>> > mailing list archives within a few business days, you may wish
>> > to contact the mailing list maintainer to investigate the delay.
>> >
>> > -- W3C Postmaster
>> > http://www.w3.org/Mail/
>> >
>> > your message follows:
>> >
>> --------------------------------------------------------------
>> --------------
>> >
>> >
>> > This is a multi-part message in MIME format.
>> >
>> > --Boundary_(ID_2YRzpl/p5kcmzOp6E9jAVg)
>> > Content-type: text/plain; charset=iso-8859-1
>> > Content-transfer-encoding: 7BIT
>> >
>> > Sometimes the text may say something that most people find
>> easy and "
>> > obvious"
>> >
>> > such as: "fill in your social security number"
>> >
>> > A video clip may show you how to find your social security
>> number, what
>> > it might be written on etc.
>> >
>> > this clip is for extra information for people with non
>> localized LD. It
>> > can be really easy to make using a simple web cam. A large
>> website could
>> > have a library of small clips that take you through
>> important tasks or
>> > information.
>> > These clips make the tasks and information accessible.
>> >
>> > Making them require synchronized captions mean that they
>> are suddenly
>> > burdensome to make. Hence people will make less of them, hence
>> > accessibility will be defeated.
>> >
>> > All the best
>> > Lisa
>> >
>> >
>> >
>> > ----- Original Message -----
>> > From: Gregg Vanderheiden
>> > To: 'Lisa Seeman'
>> > Cc: public-wcag-teama@w3.org
>> > Sent: Monday, June 19, 2006 7:28 AM
>> > Subject: CLARIFICATION
>> >
>> >
>> > In your comment below you ask for an exception for video
>> that is added to
>> > make things clearer for those with cognitive disabilities.
>> >
>> >
>> >
>> > Usually, you do not have to caption a video if the
>> information is already
>> > presented on the same page in text.
>> >
>> > So if you are talking about video only - you are ok.
>> >
>> > If it is audio only you are ok.
>> >
>> > The only problem would be if you adding audio-visual
>> multimedia and the
>> > visual is not redundant with the audio.
>> >
>> > What do you have in mind when you say 'add an animation clip'.
>> >
>> > If you really mean just video - and it is an alternate to
>> the text on the
>> > page - then you are all set. Not caption or description is
>> required and
>> > thus you need no exception.
>> >
>> >
>> >
>> > Can you give us a more specific example of what you mean?
>> >
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> >
>> > Gregg
>> >
>> >
>> >
>> >
>> >
>> > Document: WCAG 2.0 Guidelines
>> > Submitter: Lisa Seeman <lisa@ubaccess.com>
>> Affiliation: Invited
>> > expert at W3C, UB access
>> > Comment Type: substantive
>> > Location: media-equiv
>> >
>> > Comment:
>> > Comment (including rationale for any proposed change):
>> >
>> > I am concerned that the requirement for real time
>> synrcrization put a lot
>> > of extra work on authors who would like to provide short
>> animations or
>> > clips that help people with learning disabilities fulfill a
>> task. On the
>> > whole, a lot of multi media, especially in education, is
>> good for many
>> > learning disabilities, and these requirements may act as a
>> step backwards
>> > for learning disabilities.
>> >
>> > Proposed Change:
>> >
>> > Make an exception in 1.2 for any content provides extra
>> help visual for
>> > tasks and information that has been described in text else wear.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --Boundary_(ID_2YRzpl/p5kcmzOp6E9jAVg)
>> > Content-type: text/html; charset=iso-8859-1
>> > Content-transfer-encoding: quoted-printable
>> >
>> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>> > <HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
>> > "urn:schemas-microsoft-com:vml" xmlns:o =3D=20
>> > "urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
>> > "urn:schemas-microsoft-com:office:word" xmlns:ns0 =3D=20
>> > "urn:schemas-microsoft-com:office:smarttags"><HEAD>
>> > <META http-equiv=3DContent-Type content=3D"text/html; =
>> > charset=3Diso-8859-1">
>> > <META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
>> > <STYLE>@font-face {
>> > font-family: Tahoma;
>> > }
>> > @font-face {
>> > font-family: Coronet;
>> > }
>> > @font-face {
>> > font-family: Monotype Corsiva;
>> > }
>> > @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in
>> 1.0in 1.25in; }
>> > P.MsoNormal {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
>> > }
>> > LI.MsoNormal {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
>> > }
>> > DIV.MsoNormal {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
>> > }
>> > H1 {
>> > FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 12pt 0in 3pt;
>> FONT-FAMILY: =
>> > Arial
>> > }
>> > H2 {
>> > FONT-WEIGHT: bold; FONT-SIZE: 14pt; MARGIN: 12pt 0in 3pt;
>> FONT-STYLE: =
>> > italic; FONT-FAMILY: Arial
>> > }
>> > H3 {
>> > FONT-WEIGHT: bold; FONT-SIZE: 13pt; MARGIN: 12pt 0in 3pt;
>> FONT-FAMILY: =
>> > Arial
>> > }
>> > H4 {
>> > FONT-WEIGHT: bold; FONT-SIZE: 14pt; MARGIN: 12pt 0in 3pt;
>> FONT-FAMILY: =
>> > "Times New Roman"
>> > }
>> > P.MsoFooter {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
>> > }
>> > LI.MsoFooter {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
>> > }
>> > DIV.MsoFooter {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
>> > }
>> > P.MsoListBullet3 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l1 level1 lfo3
>> > }
>> > LI.MsoListBullet3 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l1 level1 lfo3
>> > }
>> > DIV.MsoListBullet3 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l1 level1 lfo3
>> > }
>> > P.MsoListNumber2 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; TEXT-INDENT: 0in;
>> FONT-FAMILY: =
>> > "Times New Roman"; mso-list: l0 level1 lfo4
>> > }
>> > LI.MsoListNumber2 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; TEXT-INDENT: 0in;
>> FONT-FAMILY: =
>> > "Times New Roman"; mso-list: l0 level1 lfo4
>> > }
>> > DIV.MsoListNumber2 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 6pt; TEXT-INDENT: 0in;
>> FONT-FAMILY: =
>> > "Times New Roman"; mso-list: l0 level1 lfo4
>> > }
>> > P.MsoTitle {
>> > FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 0in 0in 0pt;
>> FONT-FAMILY: =
>> > "Times New Roman"; TEXT-ALIGN: center
>> > }
>> > LI.MsoTitle {
>> > FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 0in 0in 0pt;
>> FONT-FAMILY: =
>> > "Times New Roman"; TEXT-ALIGN: center
>> > }
>> > DIV.MsoTitle {
>> > FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 0in 0in 0pt;
>> FONT-FAMILY: =
>> > "Times New Roman"; TEXT-ALIGN: center
>> > }
>> > A:link {
>> > COLOR: blue; TEXT-DECORATION: underline
>> > }
>> > SPAN.MsoHyperlink {
>> > COLOR: blue; TEXT-DECORATION: underline
>> > }
>> > A:visited {
>> > COLOR: purple; TEXT-DECORATION: underline
>> > }
>> > SPAN.MsoHyperlinkFollowed {
>> > COLOR: purple; TEXT-DECORATION: underline
>> > }
>> > P.MsoDocumentMap {
>> > FONT-SIZE: 10pt; BACKGROUND: navy; MARGIN: 0in 0in 0pt;
>> FONT-FAMILY: =
>> > Tahoma
>> > }
>> > LI.MsoDocumentMap {
>> > FONT-SIZE: 10pt; BACKGROUND: navy; MARGIN: 0in 0in 0pt;
>> FONT-FAMILY: =
>> > Tahoma
>> > }
>> > DIV.MsoDocumentMap {
>> > FONT-SIZE: 10pt; BACKGROUND: navy; MARGIN: 0in 0in 0pt;
>> FONT-FAMILY: =
>> > Tahoma
>> > }
>> > P {
>> > FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
>> > "Times New Roman"; mso-margin-top-alt: auto;
>> mso-margin-bottom-alt: auto
>> > }
>> > P.AbstractBullets {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l3 level1 lfo1
>> > }
>> > LI.AbstractBullets {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l3 level1 lfo1
>> > }
>> > DIV.AbstractBullets {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l3 level1 lfo1
>> > }
>> > P.SingleSpaceListing {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 3pt 1in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l2 level2 lfo2
>> > }
>> > LI.SingleSpaceListing {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 3pt 1in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l2 level2 lfo2
>> > }
>> > DIV.SingleSpaceListing {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 3pt 1in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l2 level2 lfo2
>> > }
>> > P.abstractbullets0 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l3 level1 lfo5
>> > }
>> > LI.abstractbullets0 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l3 level1 lfo5
>> > }
>> > DIV.abstractbullets0 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l3 level1 lfo5
>> > }
>> > P.singlespacelisting0 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 3pt 1in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l2 level2 lfo6
>> > }
>> > LI.singlespacelisting0 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 3pt 1in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l2 level2 lfo6
>> > }
>> > DIV.singlespacelisting0 {
>> > FONT-SIZE: 12pt; MARGIN: 0in 0in 3pt 1in; TEXT-INDENT: -0.25in; =
>> > FONT-FAMILY: "Times New Roman"; mso-list: l2 level2 lfo6
>> > }
>> > SPAN.EmailStyle28 {
>> > COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type:
>> personal-compose
>> > }
>> > DIV.Section1 {
>> > page: Section1
>> > }
>> > OL {
>> > MARGIN-BOTTOM: 0in
>> > }
>> > UL {
>> > MARGIN-BOTTOM: 0in
>> > }
>> > </STYLE>
>> > <!--[if gte mso 9]><xml>
>> > <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
>> > </xml><![endif]--><!--[if gte mso 9]><xml>
>> > <o:shapelayout v:ext=3D"edit">
>> > <o:idmap v:ext=3D"edit" data=3D"1" />
>> > </o:shapelayout></xml><![endif]--></HEAD>
>> > <BODY lang=3DEN-US vLink=3Dpurple link=3Dblue bgColor=3D#ffffff>
>> > <DIV><FONT face=3DArial size=3D2>Sometimes the text may say
>> something =
>> > that most=20
>> > people find easy and " obvious"</FONT></DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2>such as: </FONT><FONT
>> face=3DArial =
>> > size=3D2>"fill=20
>> > in your social security number"</FONT></DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2>A video clip may show
>> you how to =
>> > find=20
>> > your social security number, what it might be
>> written on=20
>> > etc.</FONT></DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2>this clip is for extra
>> information =
>> > for people=20
>> > with non localized LD. It can be really easy to make using
>> a simple web =
>> > cam. A=20
>> > large website could have a library of small clips that take
>> you through=20
>> > important tasks or information.</FONT></DIV>
>> > <DIV><FONT face=3DArial size=3D2>These clips make the tasks and =
>> > information=20
>> > accessible.</FONT></DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2>Making them require synchronized =
>> > captions mean that=20
>> > they are suddenly burdensome to make. Hence people will
>> make less of =
>> > them, hence=20
>> > accessibility will be defeated.</FONT></DIV>
>> > <DIV> </DIV>
>> > <DIV><FONT face=3DArial size=3D2>All the best</FONT></DIV>
>> > <DIV><FONT face=3DArial size=3D2>Lisa</FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> > <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
>> > size=3D2></FONT> </DIV>
>> > <DIV>----- Original Message ----- </DIV>
>> > <BLOCKQUOTE dir=3Dltr=20
>> > style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>> > BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
>> > <DIV=20
>> > style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
>> > black"><B>From:</B>=20
>> > <A title=3Dgv@trace.wisc.edu
>> href=3D"mailto:gv@trace.wisc.edu">Gregg=20
>> > Vanderheiden</A> </DIV>
>> > <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
>> > title=3Dlisa@ubaccess.com=20
>> > href=3D"mailto:lisa@ubaccess.com">'Lisa Seeman'</A> </DIV>
>> > <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
>> > title=3Dpublic-wcag-teama@w3.org=20
>> >
>> href=3D"mailto:public-wcag-teama@w3.org">public-wcag-teama@w3.
>> org</A> =
>> > </DIV>
>> > <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, June
>> 19, 2006 =
>> > 7:28 AM</DIV>
>> > <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> CLARIFICATION</DIV>
>> > <DIV><BR></DIV>
>> > <DIV class=3DSection1>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In your
>> comment below =
>> > you ask for=20
>> > an exception for video that is added to make things
>> clearer for those =
>> > with=20
>> > cognitive disabilities. <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
>> > Arial"><o:p> </o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Usually, you
>> do not have =
>> > to=20
>> > caption a video if the information is already presented on
>> the same =
>> > page in=20
>> > text. <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">So if you
>> are talking =
>> > about video=20
>> > only =96 you are ok. <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If it is
>> audio only you =
>> > are ok.=20
>> > <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The only
>> problem would =
>> > be if you=20
>> > adding audio-visual multimedia and the visual is not
>> redundant with =
>> > the audio.=20
>> > <BR><BR>What do you have in mind when you say 'add an
>> animation clip'. =
>> >
>> > <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If you
>> really mean just =
>> > video =96=20
>> > and it is an alternate to the text on the page =96 then
>> you are all =
>> > set. =20
>> > Not caption or description is required and thus you need no=20
>> > exception. <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
>> > Arial"><o:p> </o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Can you give
>> us a more =
>> > specific=20
>> > example of what you mean? <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
>> > Arial"><o:p> </o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks=20
>> > <o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
>> > style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
>> > Arial"><o:p> </o:p></SPAN></FONT></P>
>> > <P><FONT face=3D"Times New Roman" size=3D3><SPAN=20
>> > style=3D"FONT-SIZE: 12pt"><BR></SPAN></FONT><FONT
>> face=3D"Monotype =
>> > Corsiva"=20
>> > size=3D4><SPAN=20
>> > style=3D"FONT-SIZE: 13.5pt; FONT-FAMILY: 'Monotype =
>> > Corsiva'">Gregg<o:p></o:p></SPAN></FONT></P>
>> > <P><FONT face=3D"Monotype Corsiva" size=3D4><SPAN=20
>> > style=3D"FONT-SIZE: 13.5pt; FONT-FAMILY: 'Monotype =
>> > Corsiva'"><o:p> </o:p></SPAN></FONT></P>
>> > <P><FONT face=3DCoronet size=3D4><SPAN=20
>> > style=3D"FONT-SIZE: 13.5pt; FONT-FAMILY: =
>> > Coronet"><BR></SPAN></FONT><BR><STRONG><B><FONT=20
>> > face=3D"Times New Roman">Document:</FONT></B></STRONG> WCAG 2.0=20
>> > Guidelines<BR><STRONG><B><FONT=20
>> > face=3D"Times New Roman">Submitter:</FONT></B></STRONG>
>> Lisa Seeman=20
>> > =
>> >
>> <lisa@ubaccess.com> <STRONG
>> ><B><FONT=20
>> > face=3D"Times New Roman">Affiliation:</FONT></B></STRONG> Invited =
>> > expert at W3C,=20
>> > UB access<BR><STRONG><B><FONT face=3D"Times New Roman">Comment=20
>> > Type:</FONT></B></STRONG> substantive<BR><STRONG><B><FONT=20
>> > face=3D"Times New Roman">Location:</FONT></B></STRONG> <A=20
>> > =
>> >
>> href=3D"http://www.w3.org/TR/WCAG20/complete.html#media-equiv"
>> >media-equi=
>> > v</A> <o:p></o:p></P>
>> > <P><STRONG><B><FONT face=3D"Times New Roman" size=3D3><SPAN=20
>> > style=3D"FONT-SIZE: =
>> > 12pt">Comment:</SPAN></FONT></B></STRONG><BR>Comment=20
>> > (including rationale for any proposed change): <BR><BR>I
>> am concerned =
>> > that the=20
>> > requirement for real time synrcrization put a lot of extra
>> work on =
>> > authors who=20
>> > would like to provide short animations or clips that help
>> people with =
>> > learning=20
>> > disabilities fulfill a task. On the whole, a lot of multi media, =
>> > especially in=20
>> > education, is good for many learning disabilities, and these =
>> > requirements may=20
>> > act as a step backwards for learning disabilities.
>> <BR><BR>Proposed =
>> > Change:=20
>> > <BR><BR>Make an exception in 1.2 for any content provides
>> extra help =
>> > visual=20
>> > for tasks and information that has been described in text else=20
>> > wear.<o:p></o:p></P>
>> > <P style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3D"Times New Roman" =
>> > size=3D3><SPAN=20
>> > style=3D"FONT-SIZE: 12pt"><BR><BR><o:p></o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3D"Times New Roman"
>> size=3D3><SPAN=20
>> > style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
>> > <P class=3DMsoNormal><FONT face=3D"Times New Roman"
>> size=3D3><SPAN=20
>> > style=3D"FONT-SIZE: =
>> >
>> 12pt"><o:p> </o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></
>> BODY></HTML=
>> >>
>> >
>> > --Boundary_(ID_2YRzpl/p5kcmzOp6E9jAVg)--
>> >
>>
>>
>>
>
Received on Wednesday, 21 June 2006 17:13:08 UTC