[Previous] Modernising Danish eGov setup...

 [Next] Report Highlights 3rd Anniversary of the E-Government Act...

Some related posts from Technorati and Google.

[Naked Law] Government websites: accessibility denied: Whilst compliance with the W3C guidelines is not, of itself, mandatory, they are a useful indication of the steps which web developers can take to ensure maximum accessibility for their sites. The e-government unit have also published their own checklist which provides a useful additional reference.

 [Juicy Studio: No artificial additives] Access Key Companion: User Agent Accessibility Guidelines (UAAG), aimed at browser and assistive technology manufacturers to ensure their products are accessible to people with disabilities; and Authoring Tool Accessibility Guidelines (ATAG), aimed at developers of tools that produce markup, ranging from simple WYSIWYG editors to full-blown content management systems, to ensure the output generated is accessible to people with disabilities, as well as ensuring the tool itself is accessible.

[Ti Kouka Too] Accessibility rules!: It’s not just a matter of allowing disabled people to access government services more easily, says Bruce. Websites built to proper standards work better over the slower connections a large section of the population still has to work with.

 [TiKouka --- Miraz on Macs, web design and other matters.] Accessibility rules!: Some [New Zealand] government agencies are reluctant to adopt the new website accessibility guidelines due to take effect early next year, says the State Services Commission.

[Andy Carvin's Waste of Bandwidth] MyPyramid.gov: Achieving E-Health for All?: People with disabilities, such as the visually impaired, continue to struggle with government websites that don’t address their accessibility needs....Millions of people are effectively cut off from these increasingly essential resources as long as government information and services are not offered appropriately to accommodate their needs....

 [Rnib.org.uk] Resources - Web Access Centre: Their Web Content Accessibility Guidelines (WCAG) are generally accepted as the definitive guidelines on web accessibility and accessible design techniques, and many other apparent sets of standards and guidelines actually refer back to the WAI guidelines.

 [Isolani.co.uk] isolani - Weblogs: A 2004 survey by the American Foundation for the Blind lists the top two mobile phone accessibility needs as "keys that are easily identifiable by touch" and "voice output" - that is, the phone speaks menus options and settings, like the current time. Randy's last phone had both features, but his current phone, a Sanyo SCP-200, lacks voice output - his phone no longer talks (back) to him - but it does have voice input features, such as voice-enabled dialing.

 [Mdaccess.blogspot.com] Manchester Digital Accessibility Working Group: This is very easy with an accessible website, because all the style is in the DocumentCSS - the Cascading Style Sheet drawn in by the HTML file. With a few simple clicks in their browser they can replace the DocumentCSS with their own UserCSS to view accessible websites in the style that they choose - be that with large blue text on a yellow background, or any other combination suited to their particular dyslexia, colour blindness, or visual impairment.

Reflected tags on Technorati: Blog, E-Government, E-Business Library