Introduction to the Capstone Project
The final capstone project is an opportunity to apply everything you’ve learned about accessibility, including the POUR principles (Perceivable, Operable, Understandable, Robust) and WCAG 2.1 guidelines, to design a fully accessible web page. This project will challenge you to create a web page that is usable by all people, including those with disabilities, and incorporates best practices for accessibility.
The project will be evaluated based on how well your design meets the WCAG 2.1 standards and the overall accessibility and usability of the page. You will receive feedback on your design, which you can use to make further improvements.
Capstone Project Requirements
Objective:
Design a fully accessible web page that meets WCAG 2.1 Level AA guidelines and incorporates the POUR principles of accessibility.
What You Need to Include:
- Text Content: Make sure all text is accessible, clear, and easy to read.
- Images and Media: Provide alt text for images, captions, or transcripts for multimedia.
- Navigation: Ensure that the page is fully navigable by keyboard and that focus indicators are visible.
- Forms: Include at least one form element, such as a contact form, that is accessible.
- Interactive Elements: Buttons, links, and other interactive elements should be operable by various input methods.
- Color Contrast and Text Scaling: Test the contrast ratio of text against the background and allow text scaling without breaking the layout.
- Semantic HTML: Use appropriate HTML tags (e.g., headings, lists, landmarks) to structure your content logically.
Steps for Designing an Accessible Web Page
1. Planning Your Web Page
Before jumping into the design, outline the structure of your web page. Consider:
- What content will you include? (e.g., headings, paragraphs, forms, media)
- How will users navigate the page? (e.g., navigation menus, internal links)
- Who is your target audience? Make sure your content and layout are accessible to people with diverse needs, including users with visual, auditory, cognitive, or motor disabilities.
2. Ensuring Perceivability
Users should be able to perceive all content on your page, regardless of their abilities. This means making sure that:
- Alt text is provided for all images so that users with visual impairments can understand the content.
- Captions and transcripts are available for any audio or video content.
- Text is readable, with proper font size, line spacing, and high contrast between text and background.
3. Making Your Page Operable
Your page should be fully operable by keyboard and assistive technologies. This includes:
- Keyboard Navigation: Ensure that all elements are accessible using the keyboard. Users should be able to navigate using the “Tab” key, with logical focus order.
- Interactive Elements: Make sure buttons, links, and forms are accessible via keyboard and screen readers.
- Visible Focus Indicators: Highlight which element is currently in focus when navigating via keyboard.
4. Designing for Understandability
Ensure that users can easily understand how to navigate and interact with your page. Best practices include:
- Consistent Navigation: Provide consistent navigation throughout the page and use clear, descriptive labels for menus and links.
- Plain Language: Write in clear, simple language and avoid technical jargon. Break up long paragraphs into smaller sections.
- Form Instructions: Make sure forms have clear labels and instructions. Error messages should provide guidance on how to correct mistakes.
5. Making the Design Robust
Your page should be robust enough to work across different browsers, devices, and assistive technologies. This includes:
- Using Semantic HTML: Ensure proper use of HTML tags like
<header>
,<nav>
,<article>
, and<footer>
to create a logical structure that is easily interpreted by screen readers. - ARIA Roles: Where necessary, use ARIA (Accessible Rich Internet Applications) roles to enhance accessibility (e.g.,
role="button"
for clickable elements). - Compatibility with Assistive Technologies: Test your page with screen readers and other assistive technologies to ensure it works across a range of devices.
Key Accessibility Features to Include
-
Text Alternatives:
Provide descriptive alt text for all non-text content, including images, icons, and charts. Alt text should clearly explain the function or meaning of the image. -
Keyboard Accessibility:
Ensure that users can navigate through the web page and activate all buttons, links, and form elements using only the keyboard. The “Tab” key should move through interactive elements in a logical order, and focus indicators should be clearly visible. -
Form Accessibility:
Include at least one form on your web page, such as a contact form or a subscription form. Forms must:- Have properly labeled input fields (e.g., using
<label>
for each input). - Provide clear error messages when incorrect information is entered.
- Be fully operable using a keyboard or screen reader.
- Have properly labeled input fields (e.g., using
-
Accessible Media:
If you include any videos or audio clips, provide transcripts and closed captions. Ensure that users with visual or auditory impairments can still access the information in the media. -
Color Contrast and Text Size:
Check the contrast between text and background colors using tools like the Color Contrast Analyzer to ensure it meets WCAG 2.1 standards (minimum contrast ratio of 4.5:1 for normal text, 3:1 for large text). Allow users to resize text up to 200% without losing content or functionality. -
Semantic HTML Structure:
Use proper HTML tags to create a well-structured page that screen readers can easily interpret. This includes using heading levels (<h1>
,<h2>
, etc.) in a logical order and ensuring that navigation menus, lists, and forms are properly coded.
Tools and Resources for Designing Your Accessible Web Page
-
WAVE (Web Accessibility Evaluation Tool):
Use this tool to check your page for accessibility issues. It provides feedback on problems such as missing alt text, low contrast, and keyboard inaccessibility.
https://wave.webaim.org/ -
Axe Accessibility Checker:
A browser extension that helps identify WCAG violations and offers suggestions for improving accessibility.
https://www.deque.com/axe/ -
Color Contrast Analyzer:
Test the contrast ratio between text and background colors to ensure readability for users with visual impairments.
https://developer.paciellogroup.com/resources/contrastanalyser/ -
Screen Readers (NVDA, VoiceOver):
Use a screen reader to test how your web page is interpreted and navigated by users with visual impairments.- NVDA (Windows): https://www.nvaccess.org/
- VoiceOver (macOS): Built-in screen reader for macOS devices.
Project Submission and Feedback
Once your web page design is complete:
- Submit your web page: Submit your HTML, CSS, and any other relevant files.
- Accessibility Evaluation: Your web page will be evaluated based on how well it meets WCAG 2.1 Level AA standards, incorporates POUR principles, and addresses accessibility issues.
- Receive Feedback: You will receive personalized feedback on your design, highlighting areas where you excelled and suggestions for further improvements.
End of Lecture Quiz
1. What does the “O” in POUR stand for?
- a) Operable
- b) Optional
- c) Optimized
Answer: a) Operable
Rationale: “O” stands for Operable, which means that users should be able to interact with all the features on a web page, including navigation, forms, and interactive elements.
2. Which of the following tools would you use to check the contrast ratio on your web page?
- a) WAVE
- b) Color Contrast Analyzer
- c) NVDA
Answer: b) Color Contrast Analyzer
Rationale: The Color Contrast Analyzer is specifically designed to check the contrast ratio between text and background colors to ensure readability.
3. What should you do to ensure your web page is fully navigable using only the keyboard?
- a) Make sure all links and buttons are clickable.
- b) Ensure all interactive elements can be accessed and used by the “Tab” key, and provide visible focus indicators.
- c) Provide additional images and animations.
Answer: b) Ensure all interactive elements can be accessed and used by the “Tab” key, and provide visible focus indicators.
Rationale: Keyboard navigation ensures that users who cannot use a mouse can still access all the interactive elements on your page.
Conclusion
The capstone project is a culmination of everything you’ve learned about accessible design. By designing a fully accessible web page that adheres to WCAG 2.1 guidelines and integrates the POUR principles, you’ll gain practical experience in creating inclusive digital content. Remember to focus on key aspects such as text alternatives, keyboard accessibility, clear navigation, and robust design to ensure your page works for all users.