{"id":1174,"date":"2019-02-10T09:52:42","date_gmt":"2019-02-10T14:52:42","guid":{"rendered":"https:\/\/new.umaine.edu\/userguide\/?p=1174"},"modified":"2019-03-26T13:53:55","modified_gmt":"2019-03-26T17:53:55","slug":"prioritizing-accessibility","status":"publish","type":"post","link":"https:\/\/umaine.edu\/userguide\/2019\/02\/10\/prioritizing-accessibility\/","title":{"rendered":"Prioritizing Accessibility"},"content":{"rendered":"
Web accessibility has always been a requirement for\u00a091±¬ΑΟ<\/span>\u00a0websites, and Digital Communications has been increasing efforts to improve the accessibility of web content on\u00a0umaine<\/span>.edu<\/a>. The term “accessibility” refers to our efforts to remove barriers that prevent access to websites by people who have a disability. This month, we acknowledge this can be an intimidating topic to address, and provide some guidance on how to prioritize your efforts.<\/p>\n If you have looked at web accessibility reports for your\u00a0website<\/span>\u00a0(using Monsido or other tools), you may wonder where to start\u2014 every page likely has items that should be reviewed, and these tools rarely differentiate between the easy fixes and systemic content issues.<\/p>\n When you work to fix a page for accessibility, there are three items you can review that will address the majority of potential problems:<\/p>\n Web accessibility has always been a requirement for\u00a091±¬ΑΟ\u00a0websites, and Digital Communications has been increasing efforts to improve the accessibility of web content on\u00a0umaine.edu. The term “accessibility” refers to our efforts to remove barriers that prevent access to websites by people who have a disability. This month, we acknowledge this can be an intimidating topic to […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"30","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":"","spc_primary_category":0},"categories":[30,6],"tags":[],"class_list":["post-1174","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-advice"],"taxonomy_info":{"category":[{"value":30,"label":"Accessibility"},{"value":6,"label":"Advice"}]},"featured_image_src_large":false,"author_info":{"display_name":"kirby","author_link":"https:\/\/umaine.edu\/userguide\/author\/kirby\/"},"comment_info":"","category_info":[{"term_id":30,"name":"Accessibility","slug":"accessibility","term_group":0,"term_taxonomy_id":30,"taxonomy":"category","description":"","parent":0,"count":60,"filter":"raw","cat_ID":30,"category_count":60,"category_description":"","cat_name":"Accessibility","category_nicename":"accessibility","category_parent":0},{"term_id":6,"name":"Advice","slug":"advice","term_group":0,"term_taxonomy_id":6,"taxonomy":"category","description":"","parent":0,"count":69,"filter":"raw","cat_ID":6,"category_count":69,"category_description":"","cat_name":"Advice","category_nicename":"advice","category_parent":0}],"tag_info":false,"_links":{"self":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts\/1174","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/comments?post=1174"}],"version-history":[{"count":1,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts\/1174\/revisions"}],"predecessor-version":[{"id":1175,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts\/1174\/revisions\/1175"}],"wp:attachment":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/media?parent=1174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/categories?post=1174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/tags?post=1174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Where to begin?<\/h3>\n
\n
\nIf you have access to your web analytics, single out the top 10 pages of your site by web traffic. If you do not have any idea how much traffic your web pages get, just look at your home page and pages directly linked from your site navigation.<\/li>\n
\nMake your life easier by getting\u00a0accessible content for your\u00a0website<\/span>\u00a0when it is created. If you have someone new who is\u00a0taking photos or providing a news update, make sure they understand that web accessibility is a requirement. The best time to create the “alt text” for a photo on your\u00a0website<\/span>\u00a0is when it is fresh content\u2014 it is far easier to remember who is in a picture taken last week than one you stumble upon years later.<\/li>\n
\nSoftware that evaluates your\u00a0website<\/span>\u00a0for accessibility cannot distinguish between the content that you have created and the content that is part of the\u00a091±¬ΑΟ<\/span>\u00a0website<\/span>\u00a0design. Because of this, there are many items an accessibility checker will ask you to review that have already been reviewed by our office. As one example, there are over 100 links contained in the global header and footer of\u00a0umaine<\/span>.edu<\/a>\u00a0websites, and all of these have appropriately descriptive link text. Accessibility checkers do not know that, and will list these links as potential issues for review.<\/li>\n<\/ol>\nWhat to fix first?<\/h3>\n
\n
\nWe discussed the importance of “alt text” in our September 2018 newsletter<\/a>. This is always a good place to start with a web page, and will have real positive impact for anyone who relies on a screen reader to hear your content read aloud.<\/li>\n
\nIf you have links on your\u00a0website<\/span>\u00a0that are simply clickable web addresses (example:\u00a0https:\/\/umaine<\/span>.edu\/
\nA screen reader will read links to a user in a list form for their convenience, but that convenience is lost if those links have the same descriptive text. If your link text does not make sense when read aloud by itself, you should add text to that link to better describe it. Examples of problematic link text:<\/p>\n\n