Understanding Accessibility
This book combines both a comprehensive guide to understanding the
concepts behind creating Accessible Web Content as well as a complete
accessibility remediation guide that allows you to quickly make your
site accessible.
Understanding Accessibility - Printed Copy
Product Details
Register
the book to receive updates
Table of Contents
1. GETTING ACQUAINTED WITH THE ACCESSIBILITY
PROBLEM AND ITS CHALLENGES
PEOPLE WITH DISABILITIES AND ACCESS TO WEB-BASED
INFORMATION
DISABILITIES ADDRESSED BY THE ACCESSIBILITY STANDARDS
IMPROVING THE WEB FOR EVERYONE
INDUSTRY AND THE FUTURE OF ACCESSIBLE TECHNOLOGY
FEDERAL REGULATIONS FOR ACCESSIBLE WEB CONTENT
Overview of Subpart B
Requesting a copy of Section 508
W3C guidelines for accessible Web content
When accessibility laws take effect
WHERE TO START
Know the accessibility laws
Find trusted resources
Stay informed
Who can help
CREATING ACCESSIBLE WEB CONTENT
Differences between Section 508 and W3C
Why you should build accessible
Be an advocate
One set of Content
2. THE CHECKPOINTS AND THEIR MEANING
UNDERSTANDING PARAGRAPH (A) / W3C P1 (1.1)
UNDERSTANDING PARAGRAPH (B) / W3C P1 (1.4)
UNDERSTANDING PARAGRAPH (C) / W3C P1 (2.1)
UNDERSTANDING PARAGRAPH (D) / W3C P1 (6.1)
UNDERSTANDING PARAGRAPH (E) & (F) / W3C P1 (1.2) & (9.1)
UNDERSTANDING PARAGRAPH (G) & (H) / W3C P1 (5.1) & (5.2)
UNDERSTANDING PARAGRAPH (I) / W3C P1 (12.1)
UNDERSTANDING PARAGRAPH (J) / W3C P1 (7.1)
UNDERSTANDING PARAGRAPH (K) / W3C P1 (11.4)
UNDERSTANDING PARAGRAPH (L) / W3C P1 (PARTIAL 6.3)
UNDERSTANDING PARAGRAPH (M)
UNDERSTANDING PARAGRAPH (N)
UNDERSTANDING PARAGRAPH (O)
UNDERSTANDING PARAGRAPH (P)
3. INTRODUCTION TO ACCESSIBILITY TESTING
COMMON ACCESSIBILITY ERRORS
AN INTRODUCTION TO QUALITY ASSURANCE
Beta Testing
INTRODUCTION TO ACCESSIBILITY TESTING
Page versus Site
Advanced Content Delivery
USING TOOLS
Verification tools
Remediation (Repair) tools
Monitoring tools
What automated tools cannot do
Evaluating Accessibility Testing and Repair Tools
EXISTING CONTENT MANAGEMENT SYSTEMS
EXISTING TESTING ARCHITECTURE
What is an API?
4. DEVELOPING A STRATEGY FOR ACCESSIBILITY
COMPLIANCE
LOOKING FORWARD
THE RIGHT LEADERSHIP
A PHASED APPROACH
The Site Assessment
Setting Goals
Setting Design Guidelines
IMPLEMENTING ORGANIZATIONAL GUIDELINES
Training Developers
Retrofit current content and develop all new
content according to guidelines
ACCESSIBILITY TESTING
Unit Testing
Conformance Testing
Compatibility Testing
Assistive Technology Testing
ACCESSIBILITY MAINTENANCE
INTRODUCTION TO INTRANETS
Internet Sites vs. Intranet Sites
Creating an accessible Intranet
Intranet Priorities
TAKE SMALL STEPS FOR LARGE GAINS IN
ACCESSIBILITY
5. ACCESSIBILITY & DYNAMIC CONTENT
INTRODUCING DYNAMIC CONTENT
COMMON FORMS OF DYNAMIC CONTENT
HTML Templates
Server Side Includes
Web pages generated from a database
WEB SITE STRUCTURE
Add Structure to your Web site
WHO SHOULD BE TESTING DYNAMIC CONTENT
WEB BASED APPLICATIONS
BROWSER EMULATION
CASE STUDY I - COMMON ISSUES WITH DYNAMIC CONTENT AS SEEN IN A MAJOR
E-COMMERCE SITE
CASE STUDY II – SUBMITTING YOUR WEB SITE TO A POPULAR SEARCH ENGINE
6. THE UNSEEN MEANING
METADATA FOR ACCESSIBILITY
An introduction to metadata
Metadata for Accessibility
The structure of the Meta tag
Choosing Meta tags
Adding Meta tags to documents
WRITING TEXT EQUIVALENTS
Tips for writing text equivalents
Branding and Accessibility Guidelines
Prevent Meaningless Link Text
ACCESSIBILITY AND IMAGES
Common but FLAWED practices
Common Error to Avoid – Text as Image
Good Practices
7. TUTORIAL: CORRECTING ACCESSIBILITY ERRORS
comes with complete set of workshop HTML files
SECTION 1 – SECTION 508 (A) W3C GUIDELINES 1.1
1. Simple Image Requiring Alternative Text
2. Same image: also serves as a navigation link
3. An image requiring a long description
4. Object MS Office Spreadsheet
5. Applet
6. Input Elements (also 508 (n))
7. Inline Frame (IFRAME)
9. Images As Bullets Example
SECTION 2 – SECTION 508 (B) W3C GUIDELINES 1.1
Audio Files
SECTION 3 – SECTION 508 (C) W3C GUIDELINES 2.1
1. Colored Text as the only way to determine a
required step
2. Required form fields
SECTION 4 – SECTION 508 (E) W3C GUIDELINES 1.2
1. Provide Redundant Text Links for server
Side Image Maps
SECTION 5 – SECTION 508 (G&H) W3C GUIDELINES 5.1
&5.2
1. Row and Column Headers shall be identified
for Data Tables
2. All data tables should have a caption
3. All column & row header cells are required to contain the scope
attribute
4. All DATA cells are required to contain the header attribute
5. All DATA cells are required to contain the AXIS attribute
6. When row grouping elements are used, all rows are required to
be grouped
SECTION 6 – SECTION 508 (I) W3C GUIDELINES 1.1
&12.1
1. All Frame Elements are required to contain
the title attribute
2. All Frameset Elements are required to contain the noframes
element
SECTION 7 – SECTION 508 (J) W3C GUIDELINES 7.1
1. Do not use the BLINK Element
2. Do not use the MARQUEE element
SECTION 8 – SECTION 508 (L)&(M) W3C GUIDELINES
6.3
1. If you use the SCRIPT element use the
NOSCRIPT element
2. Do not use script in ANCHOR elements
3. Do not use script in AREA elements
SECTION 9 – SECTION 508 (0)
1. Skip Navigation Links
8. USE ACCESSIBLE SOLUTIONS
THE VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE
Software Output
Supporting Features
Remarks and Explanations
9. ACCESSIBILITY RESOURCES FOR FURTHER READING
APPENDIX A
SECTION 508 STANDARDS AND W3CŪ PRIORITY 1
CHECKPOINTS
APPENDIX B
SUMMARY OF SECTION 508 STANDARDS FOR SOFTWARE
APPLICATIONS AND OPERATING SYSTEMS
GLOSSARY
INDEX
REGISTER YOUR BOOK
