SlideShare a Scribd company logo
Accessibility Guidelines 01/03/2007
Provide equivalent alternatives to auditory and visual content Although some people cannot use images, movies, sounds, applets, etc. directly, they may still be able to use pages that include equivalent information to the visual or auditory content.  The equivalent information must serve the same purpose as the visual or auditory content.
Don’t rely on colour alone If colour alone is used to convey information, people who cannot differentiate between certain colours will not receive the information. For example, links should not be indicated by changing colour alone, as users may not identify them.  When foreground and background colors are too similar, they may not provide sufficient contrast when viewed by people with different types of color deficits.
Use markup and style sheets  and do so properly You may be tempted to use (or misuse) code to achieve a desired formatting effect. Be aware that these practices cause accessibility problems and you must consider whether the formatting effect is so critical as to warrant making the document inaccessible to some users.  Using markup improperly – not according to specification – hinders accessibility.
Clarify natural language usage   When content developers mark up language changes in a document, speech synthesisers and Braille devices can automatically switch to the new language, making the document more accessible to multilingual users.  In addition to helping assistive technologies, natural language markup allows search engines to find key words and identify documents in a desired language.
Create tables that transform gracefully Some browsers allow users to navigate among table cells and access header and other table cell information to give them a better understanding of the table’s content by describing each cell in turn. Unless marked-up properly, the tables will not provide users with the appropriate information.  Tables should be used to mark up truly tabular information ("data tables"). You must avoid using them to lay out pages ("layout tables").
Ensure that pages featuring  new technology transform gracefully Users often prefer to use their own style sheet to specify their own text size, colours, fonts, etc.  Pages that transform gracefully remain accessible despite any of the constraints including physical, sensory, and cognitive disabilities, work constraints, and technological barriers.  It’s a myth that disabled users do not use new technologies such as AJAX, Flash or streaming audio/video.
Ensure user control of time-sensitive content changes Some people with cognitive or visual disabilities are unable to read moving text quickly enough or at all. Movement can also cause such a distraction that the rest of the page becomes unreadable for people with cognitive disabilities (dyslexia). Screen readers are unable to read moving text. People with physical disabilities might not be able to move quickly or accurately enough to interact with moving objects.  Applies to AJAX, Flash, DHTML and animated gifs.
Ensure direct accessibility of  embedded user interfaces When an embedded object has its "own interface", the interface – like the interface to the browser itself – must be accessible. If the interface of the embedded object cannot be made accessible, an alternative accessible solution must be provided. Again, this applies to AJAX, Flash and DHTML. It is a myth that these technologies aren’t used by disabled users, so you must make them accessible.
Design for device independence Ensure that any page can be operated in a device-independent manner. For example, for scripts, specify logical event handlers rather than device-dependant event handlers (onMouseup requires the user to be using a mouse). Generally, pages that allow keyboard interaction are also accessible by users with assistive devices.
Use interim solutions For example, older screen readers read lists of consecutive links as one link – for now separate those links.  Also, changing the current window or popping up new windows can be very disorienting to users who cannot see that this has happened. If a link opens in a new window, or changes the current window the user should be forewarned.
Use W3C technologies and guidelines These guidelines are version 1.0 of the W3C Web Content Authoring Guidelines. XMTHL and CSS are W3C technologies and user agents like IE, Firefox or JAWS are developed according to the W3C User Agent Accessibility Guidelines. It all fits together. By using these guidelines we (as part of the wider Internet community) can make the Internet more accessible to users with disabilities.
Provide context and orientation information Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret.  Providing information about the relationships between parts of a page can be useful for all users.
Provide clear navigation mechanisms Clear and consistent navigation mechanisms are important to people with cognitive disabilities or with visual disabilities and benefit all users. Orientation information, navigation bars, a site map, etc. will increase the likelihood that a person can find what they are looking for on a site.
Ensure that documents are clear and simple Consistent page layout, recognizable graphics, and easy to understand language benefit all users. In particular, they help people with cognitive disabilities or those who have difficulty reading. Using clear and simple language promotes effective communication and also benefits people whose first language differs from your own, including those people who communicate primarily in sign language.

More Related Content

PPTX
User interface design for people with special needs
PPTX
User interface design
PDF
Design for accessibility
PDF
User Interface Design- Module 2 Uid Process
PPTX
A Web for Everyone: Accessibility as a design challenge
PDF
Accessible Design Presentation
PPTX
User interfaces presentation
ODP
Web Accessibility: A Shared Responsibility
User interface design for people with special needs
User interface design
Design for accessibility
User Interface Design- Module 2 Uid Process
A Web for Everyone: Accessibility as a design challenge
Accessible Design Presentation
User interfaces presentation
Web Accessibility: A Shared Responsibility

What's hot (20)

PPTX
Usability meets accessibility
PDF
Website Accessibility
PPT
User cognitive aspects for HCI
PPTX
Universal usability
PPT
Multimedia user interface principles
PPT
Guidelines for JEN-ii Website
PPTX
Digital Accessibility - The Quick Wins
PPTX
Introduction To Web Accessibility
PPTX
Accessibility and ucd
PDF
User Interface Design - Module 1 Introduction
PPT
Accessibility and Information Systems
PDF
Web a11y beyond guidelines
PPT
Graphical user interface of web form
PPTX
Web accessibility: it’s everyone’s responsibility
PPTX
Design for Accessibility
PDF
User Interface Design-Module 4 Windows
PPT
Universal design for e learning final
PDF
Accessibility & Universal Design
PPT
Interaction design and cognitive aspects
PPTX
Accessibility for content designers
Usability meets accessibility
Website Accessibility
User cognitive aspects for HCI
Universal usability
Multimedia user interface principles
Guidelines for JEN-ii Website
Digital Accessibility - The Quick Wins
Introduction To Web Accessibility
Accessibility and ucd
User Interface Design - Module 1 Introduction
Accessibility and Information Systems
Web a11y beyond guidelines
Graphical user interface of web form
Web accessibility: it’s everyone’s responsibility
Design for Accessibility
User Interface Design-Module 4 Windows
Universal design for e learning final
Accessibility & Universal Design
Interaction design and cognitive aspects
Accessibility for content designers
Ad

Viewers also liked (20)

PDF
Christchurch BAPN Presentation 2015-11-19 v1_4
PDF
8-2016 BEGIS - UAV UAS DRONE INS BROCHURE
PDF
Beleggingsadvies
PPTX
Front Cover Analysis
PPT
Dekoh Press Meet, Bangalore, India
PPTX
Medee
PPTX
Radio trailer
PDF
ABN Flyer CPR
PDF
My circular economy journal
PDF
Snapchat ve 4 Başarılı Kampanya
PPTX
οι άρχοντεσ των σκουπιδιών τηλιακος β4
DOCX
Game Theory Examples
DOCX
Brandon Resume 2015
PDF
Φωνηεντόληκτα επίθετα τρίτης κλίσης, 4η ενότητα Αρχαίων Β΄ Γυμνασίου
PDF
Το τέχνασμα του Θεμιστοκλή, εν. 2, Αρχαία Β΄ Γυμνασίου
PDF
Αρχαία Α΄ Γυμνασίου, ενότητα 10
DOCX
Eνότητα 5
Christchurch BAPN Presentation 2015-11-19 v1_4
8-2016 BEGIS - UAV UAS DRONE INS BROCHURE
Beleggingsadvies
Front Cover Analysis
Dekoh Press Meet, Bangalore, India
Medee
Radio trailer
ABN Flyer CPR
My circular economy journal
Snapchat ve 4 Başarılı Kampanya
οι άρχοντεσ των σκουπιδιών τηλιακος β4
Game Theory Examples
Brandon Resume 2015
Φωνηεντόληκτα επίθετα τρίτης κλίσης, 4η ενότητα Αρχαίων Β΄ Γυμνασίου
Το τέχνασμα του Θεμιστοκλή, εν. 2, Αρχαία Β΄ Γυμνασίου
Αρχαία Α΄ Γυμνασίου, ενότητα 10
Eνότητα 5
Ad

Similar to Summary Guidelines (20)

KEY
Build Accessibly - Community Day 2012
PDF
Getting Down and Dirty with Accessibility and Usability workshop at TCUK12
PPTX
Accessibility Update: Section 508 and WCAG in a Library 2.0 World
PPT
Web Accessibility
PPT
Accessibility Workshop
PPT
corePHP Usability Accessibility by Steven Pignataro
PPT
Week 5 - Accessibility
PPT
Corporate Web Accessibility Implementation Strategies
PDF
Making Learning Products Accessible
PPTX
Introduction to Web Accessibility and WCAG
PPTX
Introduction to Web Accessibility and WCAG
PDF
Icaweb402 a jenninecarlin
PPT
Understanding Web Accessibility
PPTX
HCID2014: Accessibility primer. Joe Chidzik, Abilitynet
PPT
Plan For Accessibility - TODCon 2008
PPT
Hands On (& Eyes & Ears) Accessibility Workshop
PPTX
apidays LIVE Paris - Accessibility matters by Ilona Koren-Deutsch
PPT
Seth Duffy Accessibility97035
PDF
Four Principles of Accessibility UK Version
Build Accessibly - Community Day 2012
Getting Down and Dirty with Accessibility and Usability workshop at TCUK12
Accessibility Update: Section 508 and WCAG in a Library 2.0 World
Web Accessibility
Accessibility Workshop
corePHP Usability Accessibility by Steven Pignataro
Week 5 - Accessibility
Corporate Web Accessibility Implementation Strategies
Making Learning Products Accessible
Introduction to Web Accessibility and WCAG
Introduction to Web Accessibility and WCAG
Icaweb402 a jenninecarlin
Understanding Web Accessibility
HCID2014: Accessibility primer. Joe Chidzik, Abilitynet
Plan For Accessibility - TODCon 2008
Hands On (& Eyes & Ears) Accessibility Workshop
apidays LIVE Paris - Accessibility matters by Ilona Koren-Deutsch
Seth Duffy Accessibility97035
Four Principles of Accessibility UK Version

Recently uploaded (20)

PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
PDF
Encapsulation theory and applications.pdf
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
PDF
Machine learning based COVID-19 study performance prediction
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PDF
KodekX | Application Modernization Development
PDF
Electronic commerce courselecture one. Pdf
PDF
Empathic Computing: Creating Shared Understanding
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PPTX
MYSQL Presentation for SQL database connectivity
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
PPTX
20250228 LYD VKU AI Blended-Learning.pptx
PPTX
Cloud computing and distributed systems.
PDF
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
PPT
Teaching material agriculture food technology
PDF
Encapsulation_ Review paper, used for researhc scholars
“AI and Expert System Decision Support & Business Intelligence Systems”
Encapsulation theory and applications.pdf
Reach Out and Touch Someone: Haptics and Empathic Computing
Machine learning based COVID-19 study performance prediction
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Building Integrated photovoltaic BIPV_UPV.pdf
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
The Rise and Fall of 3GPP – Time for a Sabbatical?
KodekX | Application Modernization Development
Electronic commerce courselecture one. Pdf
Empathic Computing: Creating Shared Understanding
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
MYSQL Presentation for SQL database connectivity
Mobile App Security Testing_ A Comprehensive Guide.pdf
Diabetes mellitus diagnosis method based random forest with bat algorithm
20250228 LYD VKU AI Blended-Learning.pptx
Cloud computing and distributed systems.
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
Teaching material agriculture food technology
Encapsulation_ Review paper, used for researhc scholars

Summary Guidelines

  • 2. Provide equivalent alternatives to auditory and visual content Although some people cannot use images, movies, sounds, applets, etc. directly, they may still be able to use pages that include equivalent information to the visual or auditory content. The equivalent information must serve the same purpose as the visual or auditory content.
  • 3. Don’t rely on colour alone If colour alone is used to convey information, people who cannot differentiate between certain colours will not receive the information. For example, links should not be indicated by changing colour alone, as users may not identify them. When foreground and background colors are too similar, they may not provide sufficient contrast when viewed by people with different types of color deficits.
  • 4. Use markup and style sheets and do so properly You may be tempted to use (or misuse) code to achieve a desired formatting effect. Be aware that these practices cause accessibility problems and you must consider whether the formatting effect is so critical as to warrant making the document inaccessible to some users. Using markup improperly – not according to specification – hinders accessibility.
  • 5. Clarify natural language usage When content developers mark up language changes in a document, speech synthesisers and Braille devices can automatically switch to the new language, making the document more accessible to multilingual users. In addition to helping assistive technologies, natural language markup allows search engines to find key words and identify documents in a desired language.
  • 6. Create tables that transform gracefully Some browsers allow users to navigate among table cells and access header and other table cell information to give them a better understanding of the table’s content by describing each cell in turn. Unless marked-up properly, the tables will not provide users with the appropriate information. Tables should be used to mark up truly tabular information ("data tables"). You must avoid using them to lay out pages ("layout tables").
  • 7. Ensure that pages featuring new technology transform gracefully Users often prefer to use their own style sheet to specify their own text size, colours, fonts, etc. Pages that transform gracefully remain accessible despite any of the constraints including physical, sensory, and cognitive disabilities, work constraints, and technological barriers. It’s a myth that disabled users do not use new technologies such as AJAX, Flash or streaming audio/video.
  • 8. Ensure user control of time-sensitive content changes Some people with cognitive or visual disabilities are unable to read moving text quickly enough or at all. Movement can also cause such a distraction that the rest of the page becomes unreadable for people with cognitive disabilities (dyslexia). Screen readers are unable to read moving text. People with physical disabilities might not be able to move quickly or accurately enough to interact with moving objects. Applies to AJAX, Flash, DHTML and animated gifs.
  • 9. Ensure direct accessibility of embedded user interfaces When an embedded object has its "own interface", the interface – like the interface to the browser itself – must be accessible. If the interface of the embedded object cannot be made accessible, an alternative accessible solution must be provided. Again, this applies to AJAX, Flash and DHTML. It is a myth that these technologies aren’t used by disabled users, so you must make them accessible.
  • 10. Design for device independence Ensure that any page can be operated in a device-independent manner. For example, for scripts, specify logical event handlers rather than device-dependant event handlers (onMouseup requires the user to be using a mouse). Generally, pages that allow keyboard interaction are also accessible by users with assistive devices.
  • 11. Use interim solutions For example, older screen readers read lists of consecutive links as one link – for now separate those links. Also, changing the current window or popping up new windows can be very disorienting to users who cannot see that this has happened. If a link opens in a new window, or changes the current window the user should be forewarned.
  • 12. Use W3C technologies and guidelines These guidelines are version 1.0 of the W3C Web Content Authoring Guidelines. XMTHL and CSS are W3C technologies and user agents like IE, Firefox or JAWS are developed according to the W3C User Agent Accessibility Guidelines. It all fits together. By using these guidelines we (as part of the wider Internet community) can make the Internet more accessible to users with disabilities.
  • 13. Provide context and orientation information Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret. Providing information about the relationships between parts of a page can be useful for all users.
  • 14. Provide clear navigation mechanisms Clear and consistent navigation mechanisms are important to people with cognitive disabilities or with visual disabilities and benefit all users. Orientation information, navigation bars, a site map, etc. will increase the likelihood that a person can find what they are looking for on a site.
  • 15. Ensure that documents are clear and simple Consistent page layout, recognizable graphics, and easy to understand language benefit all users. In particular, they help people with cognitive disabilities or those who have difficulty reading. Using clear and simple language promotes effective communication and also benefits people whose first language differs from your own, including those people who communicate primarily in sign language.