{"id":481,"date":"2014-10-14T19:16:33","date_gmt":"2014-10-14T23:16:33","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/dpsi\/?p=481"},"modified":"2014-10-24T10:01:14","modified_gmt":"2014-10-24T14:01:14","slug":"update-from-accessed","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/dpsi\/2014\/10\/14\/update-from-accessed\/","title":{"rendered":"Update from AccessEd"},"content":{"rendered":"<p><strong>What we worked on:<\/strong><\/p>\n<p><span style=\"line-height: 1.5\">We met this week to discuss to reflect on what we&#8217;ve learned so far as well as next steps going forward.\u00a0<\/span><\/p>\n<p><span style=\"line-height: 1.5\"> I also got to see a demo of <a href=\"http:\/\/www.hisoftware.com\/products\/hisoftware-compliance-sheriff-overview\/hisoftware-compliance-sheriff\/accessibility-compliance.aspx\">HiSoftware&#8217;s Compliance Sheriff<\/a>, which is a software tool that scans\u00a0a webpage&#8217;s html code to see if it is compliant with web accessibility standards such as\u00a0<a href=\"http:\/\/www.section508.gov\/\">\u00a0Section 508<\/a> or <a href=\"http:\/\/www.w3.org\/TR\/WCAG20\/\">WCAG 2.0<\/a>. The tool is pretty easy to use and can spider through each link to check compliance. It can provide a high level view (e.g., what departments&#8217;\/percentage of your website is compliant with web accessibility standards) as well as an in-depth view into non-compliant code. For example, Compliance Sheriff can highlight the exact portion of the code that is non-compliant and explain how it is non-compliant. One thing Compliance Sheriff does not do is go ahead and fix the code for a developer.<\/span><\/p>\n<p><span style=\"line-height: 1.5\"><strong>What went well:<\/strong><\/span><\/p>\n<p>It is heartening to know and understand that a variety of tools and technologies already exist to help make digital content accessible for persons with disabilities.<\/p>\n<p><strong>What&#8217;s been challenging:<\/strong><\/p>\n<p>The real difficulty is\u00a0<em>lack of consensus<\/em>\u00a0on specifics of accessibility. Based on our research so far, we haven&#8217;t found a best practices for captioning technology, for example. \u00a0We hope our research this week will shed light on that particular problem. We also hope to set up a meeting with some of the <a href=\"https:\/\/www.edx.org\/\">edX<\/a> team to get an overview of how courses are put online as well as how edX deals with accessibility issues.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What we worked on: We met this week to discuss to reflect on what we&#8217;ve learned so far as well as next steps going forward.\u00a0 I also got to see a demo of HiSoftware&#8217;s Compliance Sheriff, which is a software tool that scans\u00a0a webpage&#8217;s html code to see if it is compliant with web accessibility &hellip; <a href=\"https:\/\/archive.blogs.harvard.edu\/dpsi\/2014\/10\/14\/update-from-accessed\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Update from AccessEd<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":5215,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[127506,127571],"tags":[63976,64031,8884,111234,127579],"class_list":["post-481","post","type-post","status-publish","format-standard","hentry","category-2014-teams","category-accessed","tag-edx","tag-moocs","tag-online-education","tag-wcag","tag-web-accessibility"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/posts\/481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/users\/5215"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/comments?post=481"}],"version-history":[{"count":1,"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/posts\/481\/revisions"}],"predecessor-version":[{"id":482,"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/posts\/481\/revisions\/482"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/media?parent=481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/categories?post=481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/dpsi\/wp-json\/wp\/v2\/tags?post=481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}