Gunlaug Sørtun wrote: > All browsers have user-options, and some users may intentionally or > unintentionally set/use a few of those, like font-resizing etc. It is > always good to figure out and optimize what your creations can handle, > before end-users run into serious problems because your creations break > when they apply such options. > See/visit: <http://www.w3.org/WAI/>, <http://www.webaim.org/> and > <http://www.accessifyforum.com/> for a bit more.
Strongly agreed. Also useful for this is the BBC's My Web My Way (written as a guide for end-users): http://www.bbc.co.uk/accessibility/ Where I work we try to follow the Yahoo! Grade Browser Strategy ( http://developer.yahoo.com/yui/articles/gbs/ ), test two text sizes up and down (matching the main IE6 text sizing interface), test with and without JS, and (when complex functionality is involved) test with assistive technologies like screen readers. For my part, I also try to test with user styles partly or wholly overriding publisher CSS (e.g. using the Opera User Accessibility styles, by changing color preferences in Internet Explorer, or by turning off CSS in Firefox) but JS enabled. -- Benjamin Hawkes-Lewis ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
