On 28 March 2011 12:08, Bobby Jack <[email protected]> wrote: > Reminds me very much of work I've had to do in the past to support text-size > changing via a front-end 'widget'. Of course, as we all know, browsers > support (to varying degrees) this feature themselves, but many users are not > aware of this, so we made the decision to reinvent the wheel to cater for > user ignorance.
Websites that want to be able to shout "I'm accessible" tend to have certain pre-navigation features in common: http://www.london2012.com/ > It sometimes feels like, as website builders, we're doomed to reinvent the > browser feature-set in client-side scripts, in many different and > inconsistent ways. Even for relatively straightforward features such as > changing text size, let alone dealing with alternative stylesheets, user > stylesheets, cookie management, etc. Uhuh. A full time information architect recently told me that back and forward buttons had to be available on every page (distinct from esoteric site structure navigation), because you couldn't rely on the user having any understanding or access to the browser chrome. Can be taken to far. Way too far. Regards, Barney ______________________________________________________________________ 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/
