{"id":30,"date":"2019-08-17T14:45:57","date_gmt":"2019-08-17T13:45:57","guid":{"rendered":"https:\/\/cerovac.com\/a11y\/?p=30"},"modified":"2019-08-19T14:11:36","modified_gmt":"2019-08-19T13:11:36","slug":"lets-pour-us-a-big-bottle-of-accessibility","status":"publish","type":"post","link":"https:\/\/cerovac.com\/a11y\/2019\/08\/lets-pour-us-a-big-bottle-of-accessibility\/","title":{"rendered":"Let&#8217;s POUR us a big bottle of accessibility &#8211; intro"},"content":{"rendered":"\n<p>I&#8217;ve intentionally wanted to use the verb <strong>POUR <\/strong>in my first blog post title and use it as an metaphor and now please allow me to explain why;<\/p>\n\n\n\n<p>The <strong>four main guiding principles<\/strong> of accessibility (in  Web Content Accessibility Guidelines (WCAG)) are:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Perceivable<\/li><li>Operable<\/li><li>Understandable<\/li><li>Robust<\/li><\/ul>\n\n\n\n<p>So this is what POUR stands for &#8211; <strong>P<\/strong>(erceivable), <strong>O<\/strong>(perable), <strong>U<\/strong>(nderstandable), <strong>R<\/strong>(obust). Worth memorizing it as it is probably the shortest possible description of accessibility.<\/p>\n\n\n\n<p>These letters are the four corner stones and the foundation for the (web) accessibility &#8211; and they do a good job explaining what accessibility really is about and what we must make sure of &#8211; if we want our products to be accessible.<\/p>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<p>To me personally it seems very logical &#8211; I like to lean myself on the basics of communication theory: <br><br>we have a <strong>message <\/strong>that we want to distribute through a <strong>channel <\/strong>and there are quite a lot of possible interruptions on the way (channel) from the <strong>sender <\/strong>of the message to the <strong>receiver <\/strong>of the message. At the same time the interruptions or problems may also occur on the sender or receiver sides.<\/p>\n\n\n\n<p>So &#8211; to get the message through &#8211; all three key points must ensure that message will not be transformed or even lost. Message should therefore be <strong>perceivable <\/strong>(the receiver must be able to get it), <strong>operable <\/strong>(the receiver must be able to detect it is really a message), <strong>understandable <\/strong>(the receiver must get the point of the message) and <strong>robust <\/strong>(the message should not be transformed, malformed or even lost on it&#8217;s way).<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Sender <\/strong>is us &#8211; or our customer that we are building a website or web application for,<\/li><li><strong>Channel <\/strong>is the website or web application (and of course the web \/ internet itself),<\/li><li><strong>Receiver <\/strong>is the audience &#8211; the end-user (and the web crawler and the robot if we are totally honest about it \ud83d\ude42 ).<\/li><\/ul>\n\n\n\n<p>Therefore we can come to the following conclusion:<br><br>To make messages Perceivable, Operable, Understandable and Robust (POUR) &#8211; <strong>we need to respect basic rules<\/strong> that makes sure we can distribute the message to the majority of the receivers.<br><br>or applied to web;<br><br>To make our content POUR we have to<strong> respect and implement Web Content Accessibility Guidelines<\/strong> (WCAG) &#8211; that is the only reliable method to <strong>get our message out to the widest possible audience<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<p>This post is meant as a introductory post for the POUR principles. Please revisit my blog and get more info on the POUR &#8211; I will go through all four letters and dissect them all.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve intentionally wanted to use the verb POUR in my first blog post title and use it as an metaphor and now please allow me to explain why; The four main guiding principles of accessibility (in Web Content Accessibility Guidelines (WCAG)) are: Perceivable Operable Understandable Robust So this is what POUR stands for &#8211; P(erceivable), &hellip; <a href=\"https:\/\/cerovac.com\/a11y\/2019\/08\/lets-pour-us-a-big-bottle-of-accessibility\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Let&#8217;s POUR us a big bottle of accessibility &#8211; intro&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,3],"tags":[23,6,7],"class_list":["post-30","post","type-post","status-publish","format-standard","hentry","category-general","category-principles","tag-pour","tag-wcag2-0","tag-wcag2-1"],"_links":{"self":[{"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/posts\/30","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/comments?post=30"}],"version-history":[{"count":0,"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/posts\/30\/revisions"}],"wp:attachment":[{"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/media?parent=30"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/categories?post=30"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cerovac.com\/a11y\/wp-json\/wp\/v2\/tags?post=30"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}