WCAG 2.0: Constructing a POUR Website - Tips to Increase Accessibility…
WCAG 2.0: Constructing a POUR Website - Tips to Increase Accessibility
Use language that is comprehensible to users of diverse backgrounds. Provide background information to fill in potential gaps in user knowledge. Include abstracts, graphics, and summaries to make lengthy content more accessible.
The functions of a website should be easily understood and used, especially when a website is complex and has many pages. Navigation features and points of interaction should be consistent and clearly labeled.
Perceivable :eye: :ear: :raised_hand_with_fingers_splayed:
Make sure visual content can be converted to other modes of communication, for example, it should be possible to convert text to audio for users with limited vision.
Make sure to provide captions for all audio and video content for users with limited hearing.
For users without sight and hearing, touch is very important. It should be possible to convert content into Braille using an assistive device.
The key idea is that content must be perceivable in a variety of ways depending on the needs of the user. Content should be able to transform from one medium to another.
Content vs. Style and Presentation
The content of a website should be independent from the style. If the style transforms for accessibility reasons, the content should not be altered.
Allow users to input information using a variety of devices, not just the standard keyboard and mouse.
Uses search features, site maps, indexes, and other tools that allow easy navigation across the website. Include organizational structures that make the content structure clear.
User Control Over Timing
To provide accessibility to users who move more slowly, allow customizable time controls. For multimedia, allow users to pause, rewind, and fast-forward.
Provide functionality to prevent and recover from errors. For example, confirm user intent before deleting a file. Allow recovery of accidentally deleted files.
Functionality Across Current and Future Technologies
Consider the variety of devices and platforms that might be used to access your content (e.g., different browsers, plug-ins, operating systems, etc.). Anticipate changes to these platforms that will occur in the near future.
Use of Technologies According to Specification
Follow the specifications of the technologies being used to create and deliver content. For example, use correct HTML code to avoid bugs or lapses in accessibility.
For more info, see
WCAG 2.0 Guidelines