Cheap Cialis - Discount Online Pharmacy http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/ Accessibility news: WCAG, WAI, PAS 78 ... and all manner of other weird acronyms and stuff Sun, 24 Jan 2010 22:14:20 +0000 hourly 1 http://wordpress.org/?v=3.0 Cheap Cialis - Discount Online Pharmacy http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/comment-page-1/#comment-6013 Justin Thorp Wed, 21 Mar 2007 13:37:55 +0000 http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/#comment-6013 Patrick's article is great! It is conceptually similar to the W3C WAI's "Essential Components of Web Accessibility"[1] article, which is a great read. [1] http://www.w3.org/WAI/intro/components.php Patrick’s article is great! It is conceptually similar to the W3C WAI’s “Essential Components of Web Accessibility”[1] article, which is a great read.

[1] http://www.w3.org/WAI/intro/components.php

]]> Cheap Cialis - Discount Online Pharmacy http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/comment-page-1/#comment-5978 Ian Lloyd Wed, 21 Mar 2007 10:35:47 +0000 http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/#comment-5978 Damn those WYSIWYG editors. Rogue space is now gone. Damn those WYSIWYG editors. Rogue space is now gone.

]]> Cheap Cialis - Discount Online Pharmacy http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/comment-page-1/#comment-5971 Grzesiek Wolański Wed, 21 Mar 2007 10:01:59 +0000 http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/#comment-5971 Delete space from the link. :-) Delete space from the link. :-)

]]> Cheap Cialis - Discount Online Pharmacy http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/comment-page-1/#comment-5970 JackP Wed, 21 Mar 2007 10:00:20 +0000 http://accessify.com/news/2007/03/whos-responsible-for-web-accessibility/#comment-5970 Ian - you've got a "%20" at the end of the link you need rid of. It's a nice little article, too. There's two threads, really. Thread 1 is the user: i) The user agent (browser etc) the user is using to access the site should support accessibility features and make them easy to use ii) The user themselves should know how to 'work' their user agent. And thread 2 is the site: i) The site owner/commissioner needs to understand why accessibility is important, using PAS78 etc ii) The site developer then needs to ensure that their site doesn't place barriers in the way of people using it. In practice however Thread 2 point ii) has been the most important because regardless of how well a user agent CAN perform, you'll find some proportion of users won't be using it properly, and clients often expect developers to look after the accessibility/usability aspects. I'm not saying that is RIGHT - because I agree with Patrick - just acknowledging the reasons behind it and saying that as DEVELOPERS there is only a certain amount we can do as regards the other strands, and that's why maybe some of us go further than we should at times in offering features that are already available for people who know how their browsers work... ...after all, there's no minimum standard or driving licence required in order to drive on the information superhighway :-) Ian – you’ve got a “%20″ at the end of the link you need rid of. It’s a nice little article, too.

There’s two threads, really. Thread 1 is the user:
i) The user agent (browser etc) the user is using to access the site should support accessibility features and make them easy to use
ii) The user themselves should know how to ‘work’ their user agent.

And thread 2 is the site:
i) The site owner/commissioner needs to understand why accessibility is important, using PAS78 etc
ii) The site developer then needs to ensure that their site doesn’t place barriers in the way of people using it.

In practice however Thread 2 point ii) has been the most important because regardless of how well a user agent CAN perform, you’ll find some proportion of users won’t be using it properly, and clients often expect developers to look after the accessibility/usability aspects.

I’m not saying that is RIGHT – because I agree with Patrick – just acknowledging the reasons behind it and saying that as DEVELOPERS there is only a certain amount we can do as regards the other strands, and that’s why maybe some of us go further than we should at times in offering features that are already available for people who know how their browsers work…

…after all, there’s no minimum standard or driving licence required in order to drive on the information superhighway :-)

]]>