W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > December 2007

Re: reply to the review of Issue ID: 2034

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Tue, 11 Dec 2007 15:29:46 -0800
Message-ID: <824e742c0712111529t6b4e96advaa0868ebf0175b95@mail.gmail.com>
To: "aurélien levy" <aurelien.levy@free.fr>
Cc: public-comments-wcag20@w3.org

We do not believe it is appropriate to add "in an closed environment".
Technologies relied upon must be accessibility supported, that is,
they must be supported by user agents and assistive technology
available to users. If the user agents for a technology in an open
environment support zoom, then this technique could be used in that
environment.

We do not think it is necessary to repeat all the conditions of the
success criterion in the title of the techniques. It makes them more
difficult to read and understand. The test procedure for this
technique (which has not yet been written) would make clear that there
must not be loss of content or functionality.

Regards,

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group

On Nov 4, 2007 2:47 AM, aurélien levy <aurelien.levy@free.fr> wrote:
>
> Hi,
>
> here is my comment in regard of the current review for bug 2034 :
> http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=2034
>
> the G142 technique need some rewriting because the commonly available
> term is not usable I think it must be something like :
> G142: Using a technology in an closed environment where the used user
> agents support zoom
>
> Technique number 3 : "Providing controls on the Web page that
> incrementally change the size of the text"
> need a rewriting too because providing controls is not a guarantee that
> there is no lost loss of content or functionality."
> I think it must be something like :
> 3. Providing controls on the Web page that incrementally change the size
> of the text and do not cause loss of content or functionality when the
> text is resized up to 200% or down to 50%
>
> Furthermore, You must specify if it's for all the text present in the
> page or just for a part of it (for example the controls resize the
> content but not the navigation bar).
> So it become something like :
> 3. Providing controls on the Web page that incrementally change the size
> of all the text and do not cause loss of content or functionality when
> the text is resized up to 200% or down to 50%
>
> Finally, I think there is a need for another technique like :
> "Using measurements that are relative to other measurements for the text
> sizing AND ensuring that there is no loss of content or functionality
> when the text is resized up to 200% or down to 50%"
> to cover the case of text sizing with relative unit and block sizing
> with absolute unit and because in that case I don't need controls on the
> web page the resize text
>
> By the way, you don't say if the text resizing functionality must be
> usable with keyboard only. For example, there is a native zoom feature
> in the flash player but it's accessible only with the right click on a
> mouse. Did that mean that every flash animation must have text resizing
> controls in the animation by itself ?
>
> Best regards
> A.Levy
>
Received on Tuesday, 11 December 2007 23:30:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:09 UTC