{"id":15840,"date":"2021-03-08T09:06:02","date_gmt":"2021-03-08T14:06:02","guid":{"rendered":"https:\/\/carleton.ca\/webservices\/?p=15840"},"modified":"2026-03-18T05:41:53","modified_gmt":"2026-03-18T09:41:53","slug":"what-are-the-top-five-accessibility-issues","status":"publish","type":"post","link":"https:\/\/carleton.ca\/webservices\/2021\/what-are-the-top-five-accessibility-issues\/","title":{"rendered":"What are the top five accessibility issues?"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n What are the top five accessibility issues?\n <\/h1>\n \n \n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n\n\n

The new year has brought all kinds of excitement about accessibility. January marked the latest standard in AODA coming into operation. Because of this, and because the web community at Carleton is committed to making their websites as accessible as possible, many people are asking Web Services to run accessibility assessments of their websites.<\/p>\n\n\n\n

We have a couple of ways we look at sites to determine if there are any accessibility issues. We use a technical application based on Accessibility In Mind<\/a>‘s WAVE tool to spot any clear breaches of WCAG 2.0 web accessibility standards<\/a>. These are the standards upon which AODAs<\/p>\n\n\n\n

In the next few weeks, we are going to take a look at the main issues that come up when assessing websites. These are<\/p>\n\n\n\n

    \n
  1. Linked image missing alternative text<\/li>\n\n\n\n
  2. Empty heading<\/li>\n\n\n\n
  3. Empty Link<\/span><\/span><\/span><\/span><\/li>\n\n\n\n
  4. Missing or uninformative page title<\/span><\/span><\/span><\/span><\/li>\n\n\n\n
  5. Missing form label<\/span><\/span> <\/span>
    <\/span><\/li>\n<\/ol>\n\n\n\n

    These are the top 5 items listed by the application we use. But not all accessibility blockers are spotted by assessment tools – even the best ones we employ. Therefore, we look through websites page by page when we create a report.  Here are the top five items we have noticed looking at the front end of a site or the code forming the content:<\/p>\n\n\n\n

      \n
    1. Images being used to convey messaging with lack of <\/span>transcription<\/span>, e.g., diagram or <\/span>infographic<\/span><\/span><\/li>\n\n\n\n
    2. Lack of page hierarchy (H3s are not nested within H2s, etc.)<\/span><\/span><\/li>\n\n\n\n
    3. Images with no alt text attribute<\/li>\n\n\n\n
    4. Decorative images with unnecessary alt text<\/span><\/span><\/li>\n\n\n\n
    5. Tables being used for display, not data<\/span> <\/span><\/li>\n<\/ol>\n\n\n\n

      If you would like a report on your website please let us know<\/a>. We have many hundreds of sites to scan but we can always prioritize the keeners among you!<\/p>\n\n\n\n

      The last thing to say is that these are assessments made by software applications and by people who are not living with disabilities and accessibility challenges. Nothing is a replacement for the lived experience of a person with disabilities. It is worth taking the time to view videos on the web of people talking about their experiences, both of how bad web content impacts their access to information and also how skillfully they deal with these. I highly recommend watching this video<\/a> if you are a user who does not access websites with a screenreader. I promise the first minute will astound you as to what the human brain can do.<\/p>\n\n\n\n

      For more information about accessibility, visit our accessibility training:<\/p>\n\n\n\n

      \n
      Accessibility Training<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      The new year has brought all kinds of excitement about accessibility. January marked the latest standard in AODA coming into operation. Because of this, and because the web community at Carleton is committed to making their websites as accessible as possible, many people are asking Web Services to run accessibility assessments of their websites. We […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[197,390,391],"tags":[],"class_list":["post-15840","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-keep","category-rewrite"],"acf":{"cu_post_thumbnail":""},"_links":{"self":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/15840","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/comments?post=15840"}],"version-history":[{"count":1,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/15840\/revisions"}],"predecessor-version":[{"id":21369,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/15840\/revisions\/21369"}],"wp:attachment":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media?parent=15840"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/categories?post=15840"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/tags?post=15840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}