The aim of the W3C Web Accessability Initiative (WAI) is to provide and develop strategies, guidelines and resources to make the Web accessible to people with disabilities.

Disabilities: a first glance
Everyone uses the internet, blind people, deaf people, elderly people, people with visual disabilities, learning disabilities, cognitive disabilities, with limited fine motor control, with attention deficit hyperactivity disorder (ADHD) and dyslexia, with low vision, hand tremor, and mild short-term memory loss, with Down syndrome, ...

Pictures: Braille Keyboards for blind

A little bit of History
1996/97: W3C launched the Web Accessibility Initiative (WAI)
2000: Authoring Tool Accessibility Guidelines
2002: User Agent Accessibility Guidelines: access to information and communications technologies, including the Web, is a basic human right.
2006: UN: Convention on the Rights of Persons with Disabilities
2008: Web Content Accessibility Guidelines
2012: Government Digital Service Design Principles

W3C Web Accessibility Initiative (WAI), start page
W3C Introduction to Web Accessibility: What is Web Accessability?
todays standards:
W3C WAI: Web Content Accessibility Guidelines (WCAG) 2.0
Your own computer: W3C Better Web Browsing: Tips for Customizing Your Computer
W3C: Web Design and Applications
W3C: Web Accessibility Evaluation Tool List
W3C: A guide to understanding and implementing Web Content Accessibility Guidelines 2.0
W3C: Accessibility Evaluation Resources
W3C: Web Accessibility Evaluation Tools List

Situation in UK: Web Accessibility UK: Legal and Policy Factors (Links dead!)
Here they are: Government Service Design Manual, start page
Disability Discrimination Act 1995
Government Digital Service Design Principles


Joomla: Accessibility Statement
Joomla 3.x provides full accessibility. To create a full accessable website with Joomla CMS one has to ensure that all third party extentions and the templaste fulfill the criteria of accessibility. Additionally, there are extentions to improve accessibility, Especially to mention the Screen Reader.
The template is central for accessibility: if the template doesn't fulfill the criteria of accessibility, the whole website doesn't. One should use only templates matching these criteria.
- Alternative Text for Images
- provide all Keyboard Functionality 9
- Transcripts for Podcasts and Audio-Files
- use CSS for all formating, design, layout, positioning, ... wherever possible
- do not use HTML-tables
Example: beez3 and beez5 templates

free Web Accessibility Tester