Comments on: Government Web Site Failure – Is It So Shocking? http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/ Working together for standards Wed, 27 Mar 2013 12:19:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Britney’s Blog » Government Web Site Failure - Is It So Shocking? http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-601 Britney’s Blog » Government Web Site Failure - Is It So Shocking? Fri, 05 May 2006 11:06:43 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-601 [...] Government Web Site Failure - Is It So Shocking? [...] [...] Government Web Site Failure – Is It So Shocking? [...]

]]>
By: Matt Williams http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-444 Matt Williams Tue, 25 Apr 2006 12:03:54 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-444 While I firmly believe in the use of validators, I wonder how many of these failing websites actually receive complaints from real life disabled website visitors? How many of them present real life obstacles? While I firmly believe in the use of validators, I wonder how many of these failing websites actually receive complaints from real life disabled website visitors? How many of them present real life obstacles?

]]>
By: Steve Ferguson http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-233 Steve Ferguson Mon, 03 Apr 2006 15:50:11 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-233 Considering the content development tools that most people struggle with, I'd say that 40% is quite high too. The <a href="http://www.w3.org/QA/2006/01/failed_commitments.html" rel="nofollow">Failed Commitments</a> posting at the W3 points out that maintaining quality is even harder than developing it. If you want to maintain the quality of sites you have to find a development/publishing/testing process to verify your work without crippling you ability to add and modify content. Considering the content development tools that most people struggle with, I’d say that 40% is quite high too.

The Failed Commitments posting at the W3 points out that maintaining quality is even harder than developing it.

If you want to maintain the quality of sites you have to find a development/publishing/testing process to verify your work without crippling you ability to add and modify content.

]]>
By: Andy http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-223 Andy Sun, 02 Apr 2006 23:30:21 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-223 Most sites I look at are not valid, especially those generated with wysiwyg editors like Frontpage or Dreamweaver. 7 out of 10 sites I've looked at have no 'DTD' and most so called web-designers/developers don't even know what it is let alone what it is for! If you cannot open notepad, write sematically correct and accessible html to the latest standards as set out by W3C, which is by the way xhtml/css, then go learn your trade correctly. The fault here is with the 'Goverment' run training courses heavily influenced by the likes of microsoft, one of the major culprits in problems created in web-development. Box Model anyone? (and thats just for starters - what a nightmare). People though it seems are learning and companies like the above mentioned are having to really sort themselves out. Microsoft has just seen a major in house reshuffle over Vista. Not going to help them with macs now Operating on pc based intel hardware. Major drives in open source browsers such as Firefox have gone a long way to improving standards and microsofts I.E. has been forced to follow suit. They had no choice, people were switching to stand alone browsers that worked and they could help develop. I'm waiting for some disabled groups to take class actions against these non-compliant/non-accessible sites, it will be most fun to see what happens... Most sites I look at are not valid, especially those generated with wysiwyg editors like Frontpage or Dreamweaver.
7 out of 10 sites I’ve looked at have no ‘DTD’ and most so called web-designers/developers don’t even know what it is let alone what it is for!

If you cannot open notepad, write sematically correct and accessible html to the latest standards as set out by W3C, which is by the way xhtml/css, then go learn your trade correctly.

The fault here is with the ‘Goverment’ run training courses heavily influenced by the likes of microsoft, one of the major culprits in problems created in web-development. Box Model anyone? (and thats just for starters – what a nightmare).

People though it seems are learning and companies like the above mentioned are having to really sort themselves out. Microsoft has just seen a major in house reshuffle over Vista. Not going to help them with macs now Operating on pc based intel hardware.

Major drives in open source browsers such as Firefox have gone a long way to improving standards and microsofts I.E. has been forced to follow suit. They had no choice, people were switching to stand alone browsers that worked and they could help develop.

I’m waiting for some disabled groups to take class actions against these non-compliant/non-accessible sites, it will be most fun to see what happens…

]]>
By: Keri Henare http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-214 Keri Henare Sat, 01 Apr 2006 22:29:33 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-214 I love the <a href="http://www.e.govt.nz/standards/web-guidelines/compliance-checklist.html" rel="nofollow">New Zealand Government</a> sometimes. I love the New Zealand Government sometimes.

]]>
By: Digital Media Technologies » Blog Archive » Accessibility matters http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-209 Digital Media Technologies » Blog Archive » Accessibility matters Fri, 31 Mar 2006 21:16:36 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-209 [...] Accessibility matters Just for a little fun so I try to use the google to search what will come up by enter keywords “css april 1″ and I’ve found this Buzz Archives - The Web Standards Project web site which contains sort of a news area as well as place for people to discuss about things such as accessibility, CSS, DOM, HTML/XHTML, usability, web standards, etc. The latest news that draws my attention is Government Web Site Failure - Is It So Shocking? which a study has found a 60% failure rate in UK government websites in which they have not made the content well enough to cater for people with disabilities. What if this problem is also happening in Australia? That will be a signifiant matter as I have this impression that the Australian Government is so concerned about accessibility for everyone. [...] [...] Accessibility matters Just for a little fun so I try to use the google to search what will come up by enter keywords “css april 1″ and I’ve found this Buzz Archives – The Web Standards Project web site which contains sort of a news area as well as place for people to discuss about things such as accessibility, CSS, DOM, HTML/XHTML, usability, web standards, etc. The latest news that draws my attention is Government Web Site Failure – Is It So Shocking? which a study has found a 60% failure rate in UK government websites in which they have not made the content well enough to cater for people with disabilities. What if this problem is also happening in Australia? That will be a signifiant matter as I have this impression that the Australian Government is so concerned about accessibility for everyone. [...]

]]>
By: Steve M http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-208 Steve M Fri, 31 Mar 2006 21:01:25 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-208 Although 61% of government websites in the UK are inaccessible, it could be far worse. In the Netherlands, a <a href="http://www.accessibility.nl/files/documenten/AM2005.pdf" title="http://www.accessibility.nl/files/documenten/AM2005.pdf" rel="nofollow">2005 report</a> showed that 96%(!) of government websites were inaccessible and 98% of the website did not validate. And this is a government that just put legislation like the US Section 508 in working and even has <a href="http://webrichtlijnen.overheid.nl/" title="http://webrichtlijnen.overheid.nl/" rel="nofollow">guidelines</a><a> for building accessibile websites.</a> Although 61% of government websites in the UK are inaccessible, it could be far worse. In the Netherlands, a 2005 report showed that 96%(!) of government websites were inaccessible and 98% of the website did not validate. And this is a government that just put legislation like the US Section 508 in working and even has guidelines for building accessibile websites.

]]>
By: Tom Simcox http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-207 Tom Simcox Fri, 31 Mar 2006 16:28:37 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-207 Working for a Government Department in the UK (heavily involved in the Direct Gov site) I too am unsurprised by these figures. From personal experience I know that a lot of time and effort has gone into raising awareness of Accessibility, Web Standards et all from a grassroots level but the problems come with gaining buy-in at a Senior Management level. There is simply a lack of knowledge and awareness at this level, particularly of the fundamentals of the web as an information delivery platform. My suggestion would be for Government Senior Management to work with groups such as Wasp to gain the awareness that is needed from an authoritive source, rather than the renegade junior web developer (i.e. Me :-)). Working for a Government Department in the UK (heavily involved in the Direct Gov site) I too am unsurprised by these figures.

From personal experience I know that a lot of time and effort has gone into raising awareness of Accessibility, Web Standards et all from a grassroots level but the problems come with gaining buy-in at a Senior Management level.

There is simply a lack of knowledge and awareness at this level, particularly of the fundamentals of the web as an information delivery platform. My suggestion would be for Government Senior Management to work with groups such as Wasp to gain the awareness that is needed from an authoritive source, rather than the renegade junior web developer (i.e. Me :-)).

]]>
By: Mike Cherim http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-205 Mike Cherim Fri, 31 Mar 2006 15:19:00 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-205 Though my experience with the [US] gov pertains to accessibility, this is no surprise to me. About a year ago I contacted the EFTPS, or Electronic Funds Transfer Somethin'-Somethin' (the Internal Revenue Service's electronic business tax payments interface) about an important but simple-to-fix accessibility/usability issue. I called them as contacting the webmaster from the site is no easy feat (strike one right there). I waited on hold for 45 minutes or so and ended up after all that having to leave a voice mail message. This was all on my dime, by the way. As it turned out, they never responded to me or fixed the problem. And what was this big problem? Well, they have some checkboxes and I asked them if they could put the accompanying text inside the label so I could click on the text instead of having to target the little checkbox with my mouse. I asked for too much perhaps. For a site that is supposed to comply with Section 508 guidelines, the fact they didn't act on my rather simple request is a real travesty. The point: Governments [al of them probably] can sure talk-the-talk, but they don't seem very capable of walking-the-walk. Though my experience with the [US] gov pertains to accessibility, this is no surprise to me. About a year ago I contacted the EFTPS, or Electronic Funds Transfer Somethin’-Somethin’ (the Internal Revenue Service’s electronic business tax payments interface) about an important but simple-to-fix accessibility/usability issue.

I called them as contacting the webmaster from the site is no easy feat (strike one right there). I waited on hold for 45 minutes or so and ended up after all that having to leave a voice mail message. This was all on my dime, by the way.

As it turned out, they never responded to me or fixed the problem. And what was this big problem? Well, they have some checkboxes and I asked them if they could put the accompanying text inside the label so I could click on the text instead of having to target the little checkbox with my mouse. I asked for too much perhaps.

For a site that is supposed to comply with Section 508 guidelines, the fact they didn’t act on my rather simple request is a real travesty.

The point: Governments [al of them probably] can sure talk-the-talk, but they don’t seem very capable of walking-the-walk.

]]>
By: Lee http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/comment-page-1/#comment-204 Lee Fri, 31 Mar 2006 15:18:26 +0000 http://www.webstandards.org/2006/03/31/government-web-site-failure-is-it-so-shocking-2/#comment-204 Although that a lot of government sites aren't completely standards complaint, I do know that they are working towards it. If this report is carried out in say 6 months time I'm sure the percentage would be different. Although that a lot of government sites aren’t completely standards complaint, I do know that they are working towards it. If this report is carried out in say 6 months time I’m sure the percentage would be different.

]]>