RE: 1.4.4 Text Resize question

I would say there needs to be less functionality/information when scaled in order for there to be a 'loss' - so it doesn't necessarily fail, however I agree with Gregg, fix the page for everyone and then see if there is a loss when scaled.

Sean Hayes
Incubation Lab
Accessibility Business Unit
Microsoft

Office:  +44 118 909 5867,
Mobile: +44 7875 091385


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Gregg Vanderheiden
Sent: 16 February 2008 01:42
To: Cynthia Shelly; 'WCAG'
Subject: RE: 1.4.4 Text Resize question


I would say that it technically fails -- it ALSO fails for others so it
theoretically should fail.  But WCAG doesn't specifically say that if it is
broken for all -----

But a broken page is not one to get all up in arms for.  Presumably it will
be fixed and should be evaluated then.


Gregg
 -- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: w3c-wai-gl-request@w3.org
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Cynthia Shelly
> Sent: Friday, February 15, 2008 3:39 PM
> To: WCAG
> Subject: 1.4.4 Text Resize question
>
>
> I'm evaluating a site against WCAG 2.0, and I've run into an
> edge case for 1.4.4.
>
> The page contains a table that is clipped so that there is a
> loss of content.  Seems like it would fail 1.4.4, except...
> It's clipped with the default text size too.  There's a loss
> of content for all users.  Clearly this is a bug, but is it a
> failure of 1.4.4?  I'm inclined to say No, because there the
> content is missing for everyone.  Thoughts?  Something we
> need to clarify in the understanding?
>
>
>

Received on Saturday, 16 February 2008 11:00:14 UTC