Provide clear and concise instructions
Design for keyboard accessibility
Provide alternatives for non-text content
Use semantic HTML
Accessibility is an ongoing process
About the author
Summary
Provide clear instructions for using form fields or navigating through the website.
Why it's important: Clear and concise instructions help all users understand how to interact with the website. This is especially important for users who may have difficulty with language or cognitive processing.
How to implement it: Use clear and concise language for all instructions, labels, and error messages. Use plain language whenever possible and avoid using jargon or technical terms.
Allow users to navigate through the website using only the keyboard, without requiring a mouse.
Why it's important: Some users with disabilities may not be able to use a mouse, so ensuring keyboard accessibility is crucial. In addition, keyboard accessibility also benefits users who prefer using keyboard shortcuts or who have slow internet connections.
How to implement it: Make sure all interactive elements (links, buttons, form fields, etc.) can be accessed using the keyboard alone. Test the website's keyboard accessibility using a keyboard-only navigation tool.
Provide alt text for images that describe the content of the image for users who cannot see it.
Why it's important: Users who are visually impaired rely on assistive technology such as screen readers to access content. Providing alt text for images allows these users to understand the content of the image and its relevance to the overall content.
How to implement it: Use the alt attribute in the image tag to provide a concise, accurate description of the image. Avoid using generic phrases like "image" or "photo".
Use heading tags (h1, h2, h3, etc.) to structure content and provide a hierarchy of information.
Why it's important: Semantic HTML provides context and structure for users, especially those who use assistive technology such as screen readers. It helps users understand the purpose of each section of the website and how the content is organized.
How to implement it: Use appropriate HTML tags to structure content. For example, use h1 tags for main headings, h2 tags for subheadings, and so on. Avoid using tags simply for styling purposes.
A website might be accessible today, but as new content and features are added, it might become inaccessible. Regular audits and updates are necessary to maintain accessibility.
Why it's important: Ensuring accessibility is an ongoing process because it's not just about meeting a set of standards, but about making sure that all users can access and use the content of the website. By continuously auditing and updating the website, developers can ensure that it remains accessible to everyone.
How to implement it: Create a plan for regular accessibility audits and updates. This plan should include timelines, testing procedures, and a process for addressing any issues that are found.
Use semantic HTML
Use semantic HTML
Accessibility is an ongoing process
Provide alternatives for non-text content
Web developers, designers, and content creators who want to ensure their websites comply with Section 508 accessibility standards.
Who is it for?
.png)
Accessibility is an ongoing process
The Accessibility Handbook is a comprehensive guide to creating websites that meet Section 508 accessibility standards. The author, Katie Cunningham, provides practical advice and guidance on how to design and develop websites that are accessible to people with disabilities, including those who are blind, visually impaired, deaf, hard of hearing, or have mobility impairments.
The book covers a range of topics related to web accessibility, including the basics of accessibility, how to write accessible HTML and CSS, how to make multimedia content accessible, and how to test websites for accessibility compliance. The book also includes real-world examples of accessible websites and case studies of organizations that have successfully implemented accessibility strategies.
Katie Cunningham is a passionate Python developer at Cox Media Group, who strongly advocates for Python, Open Source Software, and programming education for all. She is a frequent speaker at open source conferences, including PyCon and DjangoCon, where she often talks about beginner-level topics, such as creating a first website in the cloud and making it accessible to everyone.
In addition, Katie actively supports PyLadies, a program dedicated to promoting diversity in the Python community, by organizing events and teaching classes that take novices from installation to developing their first app within just 48 hours.
When she's not coding, Katie enjoys sharing her experiences and insights on her website (http://therealkatie.net), covering a variety of topics such as Python, accessibility, and working from home.
Provide alternatives for non-text content
Provide clear and concise instructions
Design for keyboard accessibility
Provide clear and concise instructions
Design for keyboard accessibility
Katie Cunningham
Accessibility Handbook
Making 508 Compliant Websites
Product design, Accessibility