{"id":639,"date":"2018-05-02T13:54:52","date_gmt":"2018-05-02T13:54:52","guid":{"rendered":"http:\/\/pressbooks.library.ryerson.ca\/dabp\/?post_type=chapter&#038;p=639"},"modified":"2019-09-10T21:15:17","modified_gmt":"2019-09-10T21:15:17","slug":"the-business-case-for-accessibility","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/chapter\/the-business-case-for-accessibility\/","title":{"raw":"The Business Case for Accessibility","rendered":"The Business Case for Accessibility"},"content":{"raw":"In 2011 and 2012, Karl Groves wrote an interesting series of articles that looked at the reality of business arguments for web accessibility. He points out that any argument needs to answer affirmatively to at least one of the following questions:\r\n<ol>\r\n \t<li style=\"list-style-type: none\">\r\n<ol>\r\n \t<li>Will it make us money?<\/li>\r\n \t<li>Will it save us money?<\/li>\r\n \t<li>Will it reduce risk?<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ol>\r\nHe outlines a range of potential arguments for accessibility:\r\n<ul>\r\n \t<li><strong>Improved search engine optimization:<\/strong> Customers will be able to find your site more easily because search engines can index it more effectively.<\/li>\r\n \t<li><strong>Improved usability:<\/strong> Customers will have a more satisfying experience, thus spend more or return to your site more often.<\/li>\r\n \t<li><strong>Reduced website costs:<\/strong> Developing to standard reduces bugs and interoperability issues, reducing development costs and problems integrating with other systems.<\/li>\r\n \t<li><strong>People with disabilities have buying power:<\/strong> They won\u2019t spend if they have difficulty accessing your site; they will go to the competition that <em>does<\/em> place importance on accessibility.<\/li>\r\n \t<li><strong>Reduced resource utilization:<\/strong> Building to standard reduces use of resources.<\/li>\r\n \t<li><strong>Support for low bandwidth:<\/strong> If your site takes too long to load, people will go elsewhere.<\/li>\r\n \t<li><strong>Social responsibility:<\/strong> Customers will come if they see you doing good for the world, and you are thinking of people with disabilities as full citizens.<\/li>\r\n \t<li><strong>Support for aging populations:<\/strong> Aging populations also have money to spend and will come to your site over the less accessible, less usable competition.<\/li>\r\n \t<li><strong>Reduced legal risk:<\/strong> You may be sued if you prevent equal access for citizens\/customers or discriminate against people with disabilities.<\/li>\r\n<\/ul>\r\nWhat accessibility really boils down to is \u201cquality of work,\u201d as Groves states. So, in approaching web accessibility, you may be better off not thinking so much in terms of reducing the risk of being sued, or losing customers because your site takes too long to load. Rather, the work you do is quality work, and the website you present to your potential customers is a quality website.\r\n\r\n<strong>Video: <a href=\"https:\/\/www.youtube.com\/watch?v=jZySw1HSR0Y\" target=\"_blank\" rel=\"noopener noreferrer\">The Business Case for Accessibility<\/a><\/strong>\r\n\r\n[embed]https:\/\/www.youtube.com\/watch?v=jZySw1HSR0Y[\/embed]\r\n<div class=\"colorBox sugReading\">\r\n\r\n<strong>Readings &amp; References:\u00a0<\/strong>If you\u2019d like to learn more about business cases, here are a few references:\r\n<ul>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\/\/www.w3.org\/WAI\/business-case\/\">Developing a Web Accessibility Business Case for Your Organization (W3C)<\/a><\/li>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/www.karlgroves.com\/2011\/04\/13\/chasing-the-accessibility-business-case-part-1\/\">Chasing the Web Accessibility Business Case (Karl Groves, 2012) part 1<\/a><\/li>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/www.karlgroves.com\/2011\/09\/22\/chasing-the-accessibility-business-case-part-2\/\">Chasing the Web Accessibility Business Case (Karl Groves, 2012) part 2<\/a><\/li>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/www.karlgroves.com\/2012\/01\/27\/chasing-the-accessibility-business-case-conclusion\/\">Chasing the Web Accessibility Business Case (Karl Groves, 2012) conclusion<\/a><\/li>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\/\/www.akamai.com\/us\/en\/about\/news\/press\/2009-press\/akamai-reveals-2-seconds-as-the-new-threshold-of-acceptability-for-ecommerce-web-page-response-times.jsp\">2 Seconds as the New Threshold of Acceptability for eCommerce Web Page Response Times (Akamai, 2009)<\/a><\/li>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/martinprosperity.org\/releasing-constraints-the-impacts-of-increased-accessibility-on-ontarios-economy\/\">Releasing Constraints: the impacts of increased accessibility on Ontario's economy (Summary)<\/a><\/li>\r\n \t<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/martinprosperity.org\/media\/ReleasingConstraints_June22.pdf\">Releasing Constraints: Projecting the Economic Impacts of Increased Accessibility in Ontario (Full Report) [PDF]<\/a><\/li>\r\n<\/ul>\r\n<\/div>","rendered":"<p>In 2011 and 2012, Karl Groves wrote an interesting series of articles that looked at the reality of business arguments for web accessibility. He points out that any argument needs to answer affirmatively to at least one of the following questions:<\/p>\n<ol>\n<li style=\"list-style-type: none\">\n<ol>\n<li>Will it make us money?<\/li>\n<li>Will it save us money?<\/li>\n<li>Will it reduce risk?<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<p>He outlines a range of potential arguments for accessibility:<\/p>\n<ul>\n<li><strong>Improved search engine optimization:<\/strong> Customers will be able to find your site more easily because search engines can index it more effectively.<\/li>\n<li><strong>Improved usability:<\/strong> Customers will have a more satisfying experience, thus spend more or return to your site more often.<\/li>\n<li><strong>Reduced website costs:<\/strong> Developing to standard reduces bugs and interoperability issues, reducing development costs and problems integrating with other systems.<\/li>\n<li><strong>People with disabilities have buying power:<\/strong> They won\u2019t spend if they have difficulty accessing your site; they will go to the competition that <em>does<\/em> place importance on accessibility.<\/li>\n<li><strong>Reduced resource utilization:<\/strong> Building to standard reduces use of resources.<\/li>\n<li><strong>Support for low bandwidth:<\/strong> If your site takes too long to load, people will go elsewhere.<\/li>\n<li><strong>Social responsibility:<\/strong> Customers will come if they see you doing good for the world, and you are thinking of people with disabilities as full citizens.<\/li>\n<li><strong>Support for aging populations:<\/strong> Aging populations also have money to spend and will come to your site over the less accessible, less usable competition.<\/li>\n<li><strong>Reduced legal risk:<\/strong> You may be sued if you prevent equal access for citizens\/customers or discriminate against people with disabilities.<\/li>\n<\/ul>\n<p>What accessibility really boils down to is \u201cquality of work,\u201d as Groves states. So, in approaching web accessibility, you may be better off not thinking so much in terms of reducing the risk of being sued, or losing customers because your site takes too long to load. Rather, the work you do is quality work, and the website you present to your potential customers is a quality website.<\/p>\n<p><strong>Video: <a href=\"https:\/\/www.youtube.com\/watch?v=jZySw1HSR0Y\" target=\"_blank\" rel=\"noopener noreferrer\">The Business Case for Accessibility<\/a><\/strong><\/p>\n<p><iframe loading=\"lazy\" id=\"oembed-1\" title=\"The Business Case for Accessibility\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/jZySw1HSR0Y?feature=oembed&#38;rel=0\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<div class=\"colorBox sugReading\">\n<p><strong>Readings &amp; References:\u00a0<\/strong>If you\u2019d like to learn more about business cases, here are a few references:<\/p>\n<ul>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\/\/www.w3.org\/WAI\/business-case\/\">Developing a Web Accessibility Business Case for Your Organization (W3C)<\/a><\/li>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/www.karlgroves.com\/2011\/04\/13\/chasing-the-accessibility-business-case-part-1\/\">Chasing the Web Accessibility Business Case (Karl Groves, 2012) part 1<\/a><\/li>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/www.karlgroves.com\/2011\/09\/22\/chasing-the-accessibility-business-case-part-2\/\">Chasing the Web Accessibility Business Case (Karl Groves, 2012) part 2<\/a><\/li>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/www.karlgroves.com\/2012\/01\/27\/chasing-the-accessibility-business-case-conclusion\/\">Chasing the Web Accessibility Business Case (Karl Groves, 2012) conclusion<\/a><\/li>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\/\/www.akamai.com\/us\/en\/about\/news\/press\/2009-press\/akamai-reveals-2-seconds-as-the-new-threshold-of-acceptability-for-ecommerce-web-page-response-times.jsp\">2 Seconds as the New Threshold of Acceptability for eCommerce Web Page Response Times (Akamai, 2009)<\/a><\/li>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/martinprosperity.org\/releasing-constraints-the-impacts-of-increased-accessibility-on-ontarios-economy\/\">Releasing Constraints: the impacts of increased accessibility on Ontario&#8217;s economy (Summary)<\/a><\/li>\n<li><a rel=\"noopener noreferrer\" target=\"_blank\" href=\"http:\/\/martinprosperity.org\/media\/ReleasingConstraints_June22.pdf\">Releasing Constraints: Projecting the Economic Impacts of Increased Accessibility in Ontario (Full Report) [PDF]<\/a><\/li>\n<\/ul>\n<\/div>\n","protected":false},"author":56,"menu_order":4,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-639","chapter","type-chapter","status-publish","hentry"],"part":604,"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/639","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/users\/56"}],"version-history":[{"count":10,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/639\/revisions"}],"predecessor-version":[{"id":1155,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/639\/revisions\/1155"}],"part":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/parts\/604"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapters\/639\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/media?parent=639"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/pressbooks\/v2\/chapter-type?post=639"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/contributor?post=639"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/dabp\/wp-json\/wp\/v2\/license?post=639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}