WCAG 2.0 Principles: Perceivable

Share on facebook
Share on twitter
Share on linkedin
Perceivable

Perceivable – The scope of the challenge

When creating content for websites, accessibility experts recommend following four principles known as P.O.U.R.: Perceivable, Operable, Understandable and Robust

Perceivable – what does it mean and how does it work?

Achieving “perceivable” content in this instance includes using special coding techniques, allowing access to 3rd party code and re-coding legacy code. This inevitably leads to questions within organizations that must be answered to meet the needs of disabled users: Who in the organization is responsible for the 3rd party software code to make a website ‘perceivable?’ Who is responsible for the alternate version of the text that meets the needs of the disabled community? How do the content managers manage images, links, and files? These are both logistical and stylistic questions that must be addressed to better serve a targeted audience.

Even though styling tends to enhance user experience, the main message and information of a site should not depend on the mode of presentation. This is crucial because not all users will be able to perceive the “look and feel” (i.e. how a site looks to the user and how it feels when the user is interacting with it, which directly conveys an attitude to clients) aspects of web content. If a website is not coded with proper labeling (such as an image that writes “Click Here”) it will be of little use to someone using a screen reader if the image meta data does not specify the text, which is what screen readers work off of, and in some cases can even lead to legal ramifications.

Other questions developers must consider: Can the object on the screen be seen? Is the color contrast set to the recommended/necessary ratio for certain individuals? Can the font size easily be adjusted larger or smaller – without using a mouse (a possible concern for individuals with motor disabilities)? Are there alternative descriptions to each link and image? Does the video have closed captioning? These are only a small subset of questions that arise in attempting to achieve “Perceivable” web content.

Why are sites slow to adopt measures to reach Perceivable standards?

Today, Web 2.0 emphasizes user-generated content, where website owners can publish content instantly, automatically, and most importantly without the need for a dedicated web developer. The rise of Web 2.0 allows individuals and companies to focus on site traffic and analytics of content use, drawing focus away from accessibility standardization.

Accessible content hinges on three basic foundations:

  • Who is managing the content?
  • How to monitor new changes in the content?
  • How to fix the content if it is found to not meet the recommended standard?

For companies focusing on web accessibility, making their content “Perceivable” means engaging an estimated population of 285 millions people who have some form of visual impairment. To do that, other modes of communication are necessary. The audio format is a good example of this—assistive technologies can perform this conversion, but only if the written content is designed with accessibility in mind.

Another complication that arises for content producers is that making their content accessible typically requires multiple professionals to collaborate. It is quite common that these various professionals are not located at the main headquarters or even in the same country, which adds another element of complexity to the process.

Thus, it can be seen that the nature of Web 2.0 makes it difficult to achieve and maintain Perceivable standards, and even the process of reaching compliance is complex, and on-going.

Privacy Policy

User1st is committed to protecting the privacy of your personal information when you access and use this website. Therefore, User1st does not collect your personal information without your express permission during your experience on this website.

The following are the only circumstances in which your personal information may be provided to User1st through your use of this website:

  • When you contact User1st (via the numbers and addresses listed on the Contact page of this website or when requesting a product demonstration)
  • When you link to, like, or comment upon User1st social media pages (i.e., LinkedIn, Facebook, Twitter) (via the social media icons set forth throughout this website)
  • When you comment on an article or blog post

In the event that you disclose your name, title, business name, address, phone, fax, personal handle or alias, or email to User1st through one of the mechanisms set forth above, please know that any non-public information goes directly to User1st personnel and is not provided to any third party. Such information is used solely for the purpose of furthering any potential business relationships between you and User1st.

Please note that User1st uses third party tools to monitor website traffic usage and patterns. These tools do NOT collect your personal private information and only collect clickstream or navigation information.

If you have any questions regarding this Privacy Policy, please feel free to contact us at the numbers and addresses listed on the Contact page of this website.