Digital accessibility means a website or computer program is designed to be used by a wide range of users, including those that may have visual, auditory, motor, or cognitive disabilities. Users with special needs may not be able to easily read text on a screen, hear a video narration, type on a keyboard, or use a mouse.
The Web Content Accessibility Guidelines or WCAG 2.0 are widely used by websites to help ensure pages are usable by most users. The WCAG 2.0 guidelines are based on 4 principles:
Principle 1: Perceivable - Users must be able to obtain (perceive) information
Principle 2: Operable - Users must be able to use (operate) navigation and other user interface components
Principle 3: Understandable - Users must be able to understand the information presented
Principle 4: Robust - Content must be compatible with assistive technologies (e.g. screen readers)
Read through the WCAG guidelines for each principle by clicking on the link below.
Notice that each principle has many guidelines to deal with different situations. For example, under Principle 1, point "1.1.1 Non-text Content" says, essentially, that non-text content should have alternative text descriptions. Can you envision how this would work on a web page? If you have an image, for example, that image might be accompanied by a text description of the image. That way, someone who has vision difficulty can use a screen reader to hear the text description and understand (or perceive) what is in the image.
For each of the 4 WCAG principles, select one specific point underneath a guideline (e.g. "1.1.1 Non-text Content") and briefly describe the problem in your own words. Also, try to guess how the recommended solution might assist readers. List the point you selected and your description in the text areas below.
This is a teacher-graded exercise.
1. Principle 1 (Perceivable) - Which specific guideline did you select? Explain the problem and solution in your own words. Can you guess how this solution will help users?
2. Principle 2 (Operable) - Which specific guideline did you select? Explain the problem and solution in your own words. Can you guess how this solution will help users?
3. Principle 3 (Understandable) - Which specific guideline did you select? Explain the problem and solution in your own words. Can you guess how this solution will help users?
4. Principle 4 (Robust) - Which specific guideline did you select? Explain the problem and solution in your own words. Can you guess how this solution will help users?
1 answer
2. Principle 2 (Operable) - I selected guideline 2.1.1 Keyboard. This guideline requires that all functionality on a website should be operable through a keyboard interface without requiring specific timings for individual keystrokes. The problem is that users with motor disabilities may have difficulty using a mouse and may rely on a keyboard for navigation. The recommended solution is to ensure that all interactive elements on a website are operable using only the keyboard, allowing users with motor disabilities to easily navigate the site.
3. Principle 3 (Understandable) - I selected guideline 3.1.1 Language of Page. This guideline states that the default human language of web pages should be identified in the markup. The problem is that users with cognitive disabilities may struggle to understand the content of a webpage if the language is not identified. The recommended solution is to specify the language of the webpage in the HTML code, allowing assistive technologies to provide accurate language support to users with cognitive disabilities.
4. Principle 4 (Robust) - I selected guideline 4.1.2 Name, Role, Value. This guideline requires that all user interface components must have a programmatically determinable name, role, and value. The problem is that users using assistive technologies, such as screen readers, may struggle to interact with components that do not have these attributes defined. The recommended solution is to provide the necessary information for each user interface component, allowing assistive technologies to accurately represent and interact with these components for users with disabilities.