The old expression \u201ca picture is worth a thousand words\u201d can be applied to modern digital content just as readily as it is to books or holiday Kodak photos to bore the neighbors. <\/p>\n\n\n\n
Content, whether in print or digital form, is more than just paragraph text: content creators employ images, tables, graphs, maps, and other representations to supplement text. <\/p>\n\n\n\n
They can be decorative or informative and appear in technical, educational, and literary documents.<\/p>\n\n\n\n
However, as with text content, all such non-text content must be accessible to users with disabilities. Users with visual, mobility, or cognitive disabilities need to be able to identify, navigate, and benefit from this content, just as with text. <\/p>\n\n\n\n
Let\u2019s consider some measures that can be applied to non-text content.<\/p>\n\n\n\n
(Note that we will not discuss video content in this article. That is a separate topic that we will address in a separate blog post.)<\/p>\n\n\n\n
Photos, artwork, diagrams, illustrations, pictures of bar graphs, and chart graphs are all examples of images that may need to have alternative representation for people with disabilities. <\/p>\n\n\n\n
While it may seem that this content would be detrimental to people with visual disabilities, images are an excellent way to communicate a variety of information, and this information can usually be represented in alternative text for users with visual disabilities.<\/p>\n\n\n\n
HTML and PDF documents utilize images with embedded alternative text, abbreviated \u201calt text,\u201d that encapsulates the meaning of these images. <\/p>\n\n\n\n
There are limits to alt text: it should not be particularly long (hence \u201cencapsulate the meaning\u201d), as screen readers have difficulties parsing it and may bypass part of it. <\/p>\n\n\n\n
Therefore, complex images (for example, of a bar chart or an anatomical diagram) may require some additional representative text. <\/p>\n\n\n\n
This could be screen reader-only text that is invisible to sighted users or visibly represented.<\/p>\n\n\n\n
Text within images<\/strong>\u2014whether labeling in a diagram or prominent banner text\u2014should be readily perceivable by users with low vision or color vision disabilities. This includes a few considerations. <\/p>\n\n\n\n The graphic text needs to have sufficient color contrast against the background. <\/p>\n\n\n\n The mathematical contrast ratios for different kinds of text and against different backgrounds are detailed in the Web Content Accessibility Guidelines (WCAG)<\/a>.<\/p>\n\n\n\n In addition, text within images needs to be scalable, such that when magnified, it will maintain as much detail and clarity as possible.<\/p>\n\n\n\n Another consideration is where the image is strictly decorative. Examples include visual flourishes and decorative artwork. <\/p>\n\n\n\n Due to the difficulty in defining accurate representative alternative text, you may decide that the less confusing course of action is to hide these images from being read by screen readers. <\/p>\n\n\n\n In HTML, this is done by providing an empty \u201calt\u201d attribute; in PDF documents, this is done by \u201cartifacting\u201d the content. <\/p>\n\n\n\n Deciding to do so is often a subjective decision as to which image is decorative rather than informative.<\/p>\n\n\n\n Tables are grid-like representations of information, where the information can be represented in categories. <\/p>\n\n\n\n These categories take the form of \u201cheaders,\u201d which can be either present as one or more rows of column headers or as columns of headers at the start of each row.<\/p>\n\n\n\n An example of a common data table is a calendar: the days of the week are typically in a row at the top of each month, with each day, its number within the month, and any event details present below.<\/p>\n\n\n\n In digital documents such as HTML or PDF, there are ways to present either visible or invisible information about the table and its data. <\/p>\n\n\n\n For example, adding captions to summarize the table contents and mark up the row and column header cells is possible. This helps screen reader users identify the extent of the table and how information within it is categorized.<\/p>\n\n\n\n This helps represent the relationships about the information that is otherwise available visually, such as the scope or range data that any header applies to. <\/p>\n\n\n\n Another important consideration for digital documents is ensuring their width is controlled proportionally to the document. <\/p>\n\n\n\n This matters for users with low vision or cognitive disabilities, as it minimizes the amount of horizontal scrolling required, which can lead to difficulty navigating or orienting within the document.<\/p>\n\n\n\n For print documents that cannot rely on the same invisible information, it is important to provide clear, high-contrast table elements so that users with low vision or color vision deficits can readily interpret the content. <\/p>\n\n\n\n This includes visually distinguishing all headers, providing readily discernable cell borders, and visible table captions where appropriate. <\/p>\n\n\n\n Ensure the table does not rely solely on color to communicate information (such as status).<\/p>\n\n\n\n Maps can present significant challenges to people with disabilities, as they include multiple visual information types. <\/p>\n\n\n\n These can include community names, political boundaries, geographic features, and topographic information, to name a few. <\/p>\n\n\n\n These types are represented in maps by text (horizontally, vertically, or along diagonals), color, and illustrative elements, including lines and curves.<\/p>\n\n\n\n Rendering maps that are fully accessible can be very difficult. Making alternative versions of maps can include steps such as:<\/p>\n\n\n\n If the map is part of an online application, ensure that:<\/p>\n\n\n\n Whenever possible, make a larger version of the map available in both digital and print documents. This could be via a link to a larger version or on request by the user.<\/p>\n\n\n\n We have touched on some, but not all possible, instances of non-text content. Thankfully, this is not the extent of our familiarity with this topic. <\/p>\n\n\n\n Allyant has a well-deserved reputation as a \u201cone-stop-shop\u201d for accessible communications. As such, we have extensive experience in defining, remediating, and consulting on non-text content. <\/p>\n\n\n\n This includes instances within print documents and digital applications, with clients ranging from governments to educational institutions to banking.<\/p>\n\n\n\n We understand the importance of non-text content, how it can supplement surrounding text, and how to best address the accessibility needs of the public or customer base. <\/p>\n\n\n\n If you have any questions or requirements regarding the accessibility of images, tables, diagrams, charts, maps, or similar content, please reach out to our team today<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" The old expression \u201ca picture is worth a thousand words\u201d can be applied to modern digital content just as readily as it is to books or holiday Kodak photos to […]<\/p>\n","protected":false},"author":32,"featured_media":92979,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14],"tags":[66,53,107,97,80],"class_list":["post-92975","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-accessibility","tag-accessibility-software","tag-alt-format","tag-alternative-format","tag-web-accessibility"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tTables<\/h2>\n\n\n\n
Maps<\/h2>\n\n\n\n
\n
\n