- From: Andrew Arch <andrew.arch@nils.org.au>
- Date: Thu, 24 Feb 2005 13:56:53 +1100
- To: <public-wai-eo-site@w3.org>
ML & I had a side chat because I didn't reply to all. Sorry, Andrew > > -----Original Message----- > From: Michael Lenz [mailto:mlenz@cisco.com] > Sent: Wednesday, 23 February 2005 1:01 PM > To: Andrew Arch > Subject: Re: font size toggle issues > > > I thought so too, but don't recall specifically. I think we said yes on > the toggle, then at a later date decided that, and didn't update the > comp to reflect the change. > > > On Feb 22, 2005, at 4:35 PM, Andrew Arch wrote: > >> Didn't we have this discussion previously - and decide to provide >> education/instructions, not built in techniques? (Sorry, can't find >> the >> reference.) >> >> Andrew >> >> -----Original Message----- >> From: public-wai-eo-site-request@w3.org >> [mailto:public-wai-eo-site-request@w3.org]On Behalf Of Michael Lenz >> Sent: Tuesday, 22 February 2005 6:33 PM >> To: Wayne Dick >> Cc: Justin Thorp; public-wai-eo-site@w3.org >> Subject: Re: font size toggle issues >> >> >> >> The value I see here is if we were to used fixed (px) based CSS as >> default, then the toggle has pretty good value. But it looks like that >> isn't going to happen, hence it really isn't needed, and as Wayne >> pointed out, could cause a bit of confusion on the developers side of >> the house. >> >> -ml >> >> >> On Feb 21, 2005, at 12:10 PM, Wayne Dick wrote: >> >>> >>> To the Website Team, >>> >>> I really appreciate the work Justin and the rest of you have on the >>> enlargement of text, but I'm not sure it is the right approach. To >>> me >>> adding large print buttons is like providing a text only option. It >>> leads to the comfortable assumption that a developer is done with a >>> given population. >>> >>> This worries me because developers will look to the WAI as a model to >>> emulate. This may give developers the false impression that they >>> need >>> to build local assistive technologies into their pages. Few web >>> developers have the skills or time to do that well. So they may be >>> tempted to skip accessibility. >>> >>> We need to communicate that the way to achieve accessibility is to >>> follow the guidelines -accessibility and technical. Web developers >>> just need to facilitate assistive technology by producing good web >>> content. I think that is the example we need to project. >>> >>> Don't worry. Lazy users with low vision won't find our site. You >>> have >>> to enlarge Google first. >>> >>> You all are doing great work on this site. It is nice to look at; >>> the >>> navigation is getting better and better. It behaves much better than >>> other sites even when I apply my magic enlargement potions. Keep it >>> up. >>> >>> Wayne >>> >> >
Received on Thursday, 24 February 2005 19:16:55 UTC