Re: 30 Jan 2007 Team B Meeting

Late regrets.  I couldn't make it this morning.....

I agree with Sorcha that the readers still might ask a question why
200%, not 175% or 190%. It'll be much better that we could explain the
rationale in more detail.

- Makoto

2007/1/31, Sorcha Moore <sorcha@segala.com>:
>
> The text scaling How To Meet pages look great, except that I think it lacks a
> rational behind the 200% measurement - I do think this will be commented and
> queried.  Forgive me if this has already been explained and I am not "getting"
> it but why not 175% or 190%?  On what information did we base 200% - if
> designers are having problems maintaining their design with font resized to
> 200% but not 180% they should have some basis/motivation for going for 200% not
> just because the WCAG picked 200%.
> Also, does 200% mean double? So, is that double the height and width of the
> font? I hate to be the devils advocate but someone is going to ask in the next
> round of comments, what if someone starts off with a really small font and
> scales it up 200% - it still may not be accessible...
>
>
>
> Quoting Loretta Guarino Reid <lorettaguarino@google.com>:
>
> >
> > 18:00 UTC
> > 10:00 AM Palo Alto
> > 1:00 PM Boston
> > 6:00 PM England, Ireland
> > 3:00 AM (Jan 31) Japan
> > Bridge: +1.617.761.6200 Passcode 92248#
> >
> > irc.w3.org port 6665 #wcag-teamb
> >
> > Agenda:
> > 1. Review text scaling How To Meet pages for survey
> >
> >
> http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_1.4.5
> >
> >
> http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criterion_1.4.6
> > (Has anyone been able to find any relevant resources?)
> >
> > 2. Review Team B proposals for survey
> >
> http://www.w3.org/WAI/GL/WCAG20/issue-tracking/search_results.php?terms=[TEAMB]&status=proposal
> >
> > 3. Review some conformance proposals
> >
> >
> http://www.w3.org/WAI/GL/WCAG20/issue-tracking/search_results.php?terms=[confAAA]
> >
> >
> http://www.w3.org/WAI/GL/WCAG20/issue-tracking/search_results.php?terms=[confAggr]
> >
> >
> http://www.w3.org/WAI/GL/WCAG20/issue-tracking/search_results.php?terms=[confLevels]
> >
> >
>
>
> --
> Sorcha Moore
> Lead Accessibility Developer and Senior Auditor, Segala
> Member Web Content Accessibility Guidelines Working Group
> Mobile Web Best Practices Working Group
>
> HQ: 19 The Mall / Beacon Court / Sandyford /Dublin 18 / Ireland
> UK:   2 Coltsfoot Drive / Burpham / Guildford / GU1 1YH / Surrey / UK
> Office:   +353 (0)1 2931 966
> Mobile:  +353 (0)87 6462726
>
> Do you design, build or test Web sites?
> Join the Segala-Certified Partner Programme for Accessibility
> Segala Partner Programme Membership now open http://partner.segala.com
>
>

Received on Wednesday, 31 January 2007 03:18:56 UTC