{"id":127,"date":"2011-04-02T17:28:00","date_gmt":"2011-04-02T17:28:00","guid":{"rendered":"https:\/\/codeblam.com\/blog\/?p=127"},"modified":"2024-12-28T19:45:53","modified_gmt":"2024-12-28T19:45:53","slug":"web-accessibility-essentials","status":"publish","type":"post","link":"https:\/\/codeblam.com\/blog\/seo\/web-accessibility-essentials\/","title":{"rendered":"Web Accessibility Essentials"},"content":{"rendered":"\n<p><strong>Web Accessibility<\/strong>&nbsp;refers to the development practice of creating websites that&nbsp;accommodate&nbsp;for people with disabilities. When websites are created properly, all users have equal access to the navigation, content and functionality of the page.<\/p>\n\n\n\n<p><strong>Web Accessibility&nbsp;<\/strong>covers all disabilities that could restrict access to the web, including auditory, visual, speech and neurological disabilities.<\/p>\n\n\n\n<p>However,&nbsp;<strong>Web Accessibility<\/strong>&nbsp;does not only cover people with disabilities, but all limitations a user might face when browsing the web. For example, slow internet connection, javascript disabled, older versions of browsers\u2026<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a target=\"_blank\" href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/http:\/\/www.w3.org\/WAI\/gettingstarted\/Overview.html\" rel=\"noreferrer noopener\">Web Accessibility Initiative (WAI)<\/a><\/h2>\n\n\n\n<p>The&nbsp;<strong>WAI&nbsp;<\/strong>seeks to improve the accessibility of the web, as well as develop strategies, guidelines and resources. Below are some guidelines that can be taken into consideration when developing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Web&nbsp;Accessibility&nbsp;Quick-tips<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li>Provide text alternatives for non-text content (eg.&nbsp;<em>alt<\/em>&nbsp;attribute for images)<\/li><li>Provide captions or alternatives for audio and video<\/li><li>Make content available to assistive technologies (eg. Screen readers &amp; magnifiers, voice recognition software, touch screens)<\/li><li>Use sufficient colors and contrast, to make the web page easier to read.<\/li><li>Make all functionality keyboard accessible (eg. tab indexes)<\/li><li>Make text easily readable and understandable<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Making your website accessible<\/h2>\n\n\n\n<p>Making your website accessible can be simple or it can be complex, depending on factors such as the type of&nbsp;content, size and complexity of the site, and the development tools and environment used.<\/p>\n\n\n\n<p>Many accessibility features are easily implemented if they are planned from the beginning of Web site development or redesign. Fixing inaccessible Web sites can require significant effort, especially sites that were not originally \u201ccoded\u201d properly with standard&nbsp;XHTML&nbsp;markup, and sites with certain types of content such as multimedia.<\/p>\n\n\n\n<p>The document \u201c<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/impl\/Overview\">Implementation Plan for Web Accessibility<\/a>\u201d&nbsp;lists basic steps for addressing accessibility in Web projects. The&nbsp;<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/intro\/wcag.php\">Web Content Accessibility Guidelines<\/a>&nbsp;and techniques documents provide detailed information for developers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Evaluating web accessibility<\/h2>\n\n\n\n<p>When developing or redesigning a site, evaluating accessibility early and throughout the development process can identify accessibility problems early when it is easier to address them. Simple techniques such as changing settings in a browser can determine if a Web page meets some accessibility guidelines. A comprehensive evaluation to determine if a site meets all accessibility guidelines is much more complex.<\/p>\n\n\n\n<p>There are&nbsp;<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/ER\/existingtools.html\">evaluation tools<\/a>&nbsp;that help with evaluation. However, no tool alone can determine if a site meets accessibility guidelines. Knowledgeable&nbsp;<strong>human evaluation is required<\/strong>&nbsp;to determine if a site is accessible.<\/p>\n\n\n\n<p>The document \u201c<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/eval\/Overview.html\">Evaluating Web Sites for Accessibility<\/a>\u201d provides guidance on&nbsp;<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/eval\/preliminary\">preliminary reviews<\/a>&nbsp;using techniques to quickly assess some of the accessibility problems on a site. It also provides general procedures and tips for evaluating&nbsp;<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/eval\/conformance\">conformance to accessibility guidelines<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">References<\/h2>\n\n\n\n<p>For more detailed information on Web Accessibility I recommend&nbsp;<a target=\"_blank\" href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/accessites.org\" rel=\"noreferrer noopener\">accessites.org<\/a>&nbsp;where you can see screenshots and discuss Web Accessibility with experts in the field. To see an excellant example comparing an accessible site with a non accessible site, visit&nbsp;<a href=\"https:\/\/web.archive.org\/web\/20160629164211mp_\/http:\/\/www.w3.org\/WAI\/EO\/2005\/Demo\/\">http:\/\/www.w3.org\/WAI\/EO\/2005\/Demo\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Web Accessibility&nbsp;refers to the development practice of creating websites that&nbsp;accommodate&nbsp;for people with disabilities. When websites are created properly, all users have equal access to the navigation, content and functionality of&#46;&#46;&#46;<\/p>\n","protected":false},"author":1,"featured_media":329,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,15,16],"tags":[],"class_list":["post-127","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo","category-w3c","category-web-accessibility"],"_links":{"self":[{"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/posts\/127","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/comments?post=127"}],"version-history":[{"count":1,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/posts\/127\/revisions"}],"predecessor-version":[{"id":320,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/posts\/127\/revisions\/320"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/media\/329"}],"wp:attachment":[{"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/media?parent=127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/categories?post=127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codeblam.com\/blog\/wp-json\/wp\/v2\/tags?post=127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}