{"id":19719,"date":"2023-08-18T15:23:00","date_gmt":"2023-08-18T19:23:00","guid":{"rendered":"https:\/\/carleton.ca\/webservices\/?p=19719"},"modified":"2026-03-19T06:20:03","modified_gmt":"2026-03-19T10:20:03","slug":"5-common-web-accessibility-issues-part-2","status":"publish","type":"post","link":"https:\/\/carleton.ca\/webservices\/2023\/5-common-web-accessibility-issues-part-2\/","title":{"rendered":"5 Common Web Accessibility Issues: Part 2"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n 5 Common Web Accessibility Issues: Part 2\n <\/h1>\n \n \n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n

Earlier this summer, we blogged about 5 common accessibility issues<\/a> found on websites. If your site is free of these issues, then congratulations! Your site would perform well on the accessibility test from our third-party accessibility scanning system, Pope Tech<\/a>. This software is not perfect and does not detect all accessibility errors. That means it\u2019s up to our clients and the help of Web Services to also do a manual visual scan to ensure all accessibility errors are found and fixed when an accessibility scan<\/a> is requested. Have a look at this list and see if your site is free of these issues.<\/p>\n\n\n\n

1. Contextual Text on Images<\/h2>\n\n\n\n

Images cannot have contextual text. This is mainly because a screen reader cannot read the text on an image, therefore resulting in the user missing out on vital information and creating an unmatched universal user experience. All contextual text should be placed above, below, or beside the image.<\/p>\n\n\n\n

On the other hand, decorative text can be a part of the image if it does not enhance the user\u2019s experience. For example, the right-hand  image below of the person in front of a bookshelf, the titles of the books are decorative text.<\/p>\n\n\n\n

\"A
The text on the book titles is for decorative purposes.<\/figcaption><\/figure>\n\n\n\n
\"Landscape
A screenreader cannot read the text “Carleton University!”<\/figcaption><\/figure>\n\n\n\n

2. Inadequate Video Features<\/h2>\n\n\n\n

For videos to be accessible, they must have all the stipulated video controls such as pause, play forward and rewind. Additionally, closed captions must be made available as well as video transcripts. As these features are built into YouTube<\/a>, we host all our videos there. <\/span>These video features are vital to users with hearing disabilities. It also helps users with learning disabilities, or those who are not native to the language the video is in. Accessibility is for everyone and having these video features can further enhance any user’s experience.<\/p>\n\n\n\n

3. Non-Web Friendly Text<\/h2>\n\n\n\n

A general guideline for text is that it should be less than 50 words per paragraph and sentences should be between 20 and 50 words. Breaking up long paragraphs of text makes web content easier to comprehend for a reader and overall improves the legibility. Another web writing tip is to break up the text with bullet points or lists and avoid using italics and all caps when possible.<\/p>\n\n\n\n

In terms of headings, they must be descriptive, and relevant to the content they contain. A good heading contains keywords and is short and to the point (about 8 words is ideal). They also must be used appropriately, using proper heading hierarchy. For more information on web-friendly text, visit our Paragraphs and Headings<\/a> page from our Accessibility Training Workshop<\/a>.<\/p>\n\n\n\n

4. Banner Images Lacking Contrast<\/h2>\n\n\n\n

Banner images should be darkened to create enough contrast for the banner text to be legible. Here at Carleton, all banner images should be darkened to at least 50%. This can be done by editing the page on the backend of your site by scrolling down to Page Options<\/strong>, selecting a Banner Image Type<\/strong> (either Hosted or Upload), then selecting Dark (50%)<\/strong> for Banner Opacity<\/strong>.<\/p>\n\n\n\n

5. Improper Use of Hyperlinks<\/h2>\n\n\n\n

As for hyperlinks, the URL (the full link address) must be renamed to describe the link destination. There are two key things to note here. The first is the URL must be renamed, as a screen reader may read out the URL which is unnecessary and inconvenient for users. The second part to note is a hyperlink must be renamed to a phrase that describes the URL\u2019s destination. For example, \u201cclick here\u201d does not describe a hyperlink, however, \u201cfor more information, visit our accessibility training on hyperlinks<\/a>\u201d does.<\/p>\n\n\n\n

If you have reviewed this list, and you are still unsure if your website displays accessibility errors, you can request an accessibility scan<\/a>. You can also explore our Web Accessibility Checklist<\/a>, as well as more accessibility resources<\/a> on our site. Lastly, in preparation for the cuTheme migration, we recommend our clients review our Accessibility Training<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Earlier this summer, we blogged about 5 common accessibility issues found on websites. If your site is free of these issues, then congratulations! Your site would perform well on the accessibility test from our third-party accessibility scanning system, Pope Tech. This software is not perfect and does not detect all accessibility errors. That means it\u2019s […]<\/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-19719","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-keep","category-rewrite"],"acf":{"cu_post_thumbnail":"video-2"},"_links":{"self":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/19719","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=19719"}],"version-history":[{"count":1,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/19719\/revisions"}],"predecessor-version":[{"id":21414,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/19719\/revisions\/21414"}],"wp:attachment":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media?parent=19719"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/categories?post=19719"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/tags?post=19719"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}