Web Accessibility | Accessibility
Standards Based Development
Five Layers of Accessibility
- html
- css
- JavaScript
- css for JavaScript
- wai aria
Web Accessibility
four main types of disabilities that can be used to explain how we should be thinking about accessibility:
Web Accessibility
Web Accessibility is the inclusive practice of making websites usable by people of all abilities and disabilities. Correctly designed, developed and edited web documents allow all users to have equal access to information and functionality. Web Accessibility addresses these needs:
- Visual: visual impairments including blindness, various common types of low vision and poor eyesight, as well as various types of color blindness.
- Motor/Mobility: difficulty or inability to use the hands, including tremors, muscle slowness, loss of fine muscle control, etc., due to conditions like Parkinson's Disease, stroke, and others.
- Auditory: deafness or hearing impairments, including those who are hard of hearing.
- Seizures: photoepileptic seizures caused by visual strobe or flashing effects.
- Cognitive/Intellectual: developmental disabilities, learning disabilities, cognitive disabilities of various origins, affecting memory, attention, developmental "maturity", problem-solving, logic skills, and others.
html Accessibility
JavaScript Accessibility
Essential Components of Web Accessibility
Website accessibility relies on eight components:
- the website itself - natural information (text, images and sound) and the markup code that defines its structure and presentation
- user agents, such as web browsers and media players
- assistive technologies, such as screen readers and input devices used in place of the conventional keyboard and mouse
- users' knowledge and experience using the web
- developers
- authoring tools
- evaluation tools
- a defined web accessibility standard, or a policy for your organization (against which to evaluate the accessibility)
These components interact with each other to create an environment that is accessible to people with disabilities.
Web developers usually use authoring tools and evaluation tools to create Web content.
People ("users") use Web browsers, media players, assistive technologies or other "user agents" to get and interact with the content."
Guidelines for different components
Authoring Tool Accessibility Guidelines
atag contains 28 checkpoints that provide guidance on:
- producing accessible output that meets standards and guidelines
- promoting the content author for accessibility-related information
- providing ways of checking and correcting inaccessible content
- integrating accessibility in the overall look and feel
- making the authoring tool itself accessible to people with disabilities
Web Content Accessibility Guidelines (WCAG)
- WCAG 1.0: Web Content Accessibility Guidelines: 14 guidelines that are general principles of accessible design
- WCAG 2.0: 12 principal guidelines
User Agent Accessibility Guidelines (UAAG)
- UAAG contains a comprehensive set of checkpoints that cover:
- access to all content
- user control over how content is rendered
- user control over the user interface
- standard programming interfaces
References and Resources
References and Resources
- Web Accessiblity Mindmap
- eAccess+ Hub
- A11y Buzz
- How to Build an Accessible Web Application
- Accessibility for All
- A user agent developer's guide to understanding and implementing accessibility support in HTML
- Just Ask: Integrating Accessibility Throughout Design (ebook)

- uiAccess.com is a resource for universal interface design and usable accessibility information.
- Demystifying Accessibility
- Accessibility Assistant is an information resource that supports the design and procurement of accessible products and services.
- Web Accessibility
- Accessible Web Typography - An Introduction for Web Designers
- Design Accessible Sites Now
Web Accessibility Techniques
Accessibility and Screen Readers
Some screen readers (such as Apple's VoiceOver), read the content inside pseudo elements. When you assign single characters to your icons, you wouldn't want the screen reader to read these characters. By using the PUA or the symbols options for the encoding of your glyphs, you can prevent this problem.
You can make screen readers read any text you wish. This is usually useful when you want to use an icon without any visual text near it. Here's an example:
<a href="#" data-icon="">
<span class="visuallyhidden">Home</span></a>
.visuallyhidden {
border: 0;
clip: rect(0 0 0 0);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
width: 1px;
}
References
- WordPress Accessibility
- Android Accessibility
- Display Size And Resolution Accessibility
- Derek Featherstone: Accessibility Is More Than Compliance
- Open & Closed - Uniting Global Knowledge Of Accessibile Media
-

- WebAnywhere
- Skip Navigation Links
- Accessibility Tips
- Working with Active Accessibility in the 2007 Office Fluent User Interface
- Seven Accessibility Mistakes You Don't Want To Make
- Understanding Accessibility
- IBM Web Accessibility Checklist
- Making Ajax Work With Screen Readers
- http://www.digital-web.com/articles/seven_accessibility_mistakes_part_1/
- http://www.digital-web.com/articles/seven_accessibility_mistakes_part_2/
- How to Build Accessible iOS Apps
a11y Web Development References & Resources
- Implementing wai Authoring Tool Accessibility Guidelines in Developing Adaptive Elearning (pdf)
- Computer Accessibility
- Web Accessibility
- Accessibility
- Skip Navigation Links
- Accessibility Tips
- Seven Accessibility Mistakes You Don't Want To Make
- Understanding Accessibility
- IBM Web Accessibility Checklist
- Making Ajax Work With Screen Readers
- Seven Accessibility Mistakes Part 1/
- Seven Accessibility Mistakes Part 2
- Don't Leave Money On The Table: Marketing To People With Disabilities
- Accessibility Heuristics
- Accessibility In Print
- Accessibility Tips For Audio And Video
- iPhone - Accessibility
- Web Accessibility Initiative (WAI)
- http://ryankeiser.net/blog/accessible-color/
- http://www.etre.com/tools/colourblindsimulator/
- http://www.logocritiques.com/resources/color_psychology_in_logo_design/
- Scripting Enabled - How To Make The Web More Accessible With JavaScript And Flash
- Flash And Keyboard Accessibility Access Accross Browsers
- Designing For Accessibility
- Accessibility: Can't We All Just Get Along?
- Designing Accessible Websites
- Configuring Your Machine For Testing With A Screen Reader
- Section 508: Uncle Sam's Guide To Web Accessibility
- Display Size And Resolution Accessibility
- Derek Featherstone: Accessibility Is More Than Compliance
- Open & Closed - Uniting Global Knowledge Of Accessibile Media
- Accessibility Heuristics
- Accessibility In Print
- Accessibility Tips For Audio And Video
- iPhone - Accessibility
- Web Accessibility Initiative (WAI)
- http://ryankeiser.net/blog/accessible-color/
- http://www.etre.com/tools/colourblindsimulator/
- http://www.logocritiques.com/resources/color_psychology_in_logo_design/
- Scripting Enabled - How To Make The Web More Accessible With JavaScript And Flash
- Flash And Keyboard Accessibility Access Accross Browsers
- Designing For Accessibility
- Accessibility: Can't We All Just Get Along?
- Designing Accessible Websites
- Configuring Your Machine For Testing With A Screen Reader