This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:nnels:etext:images:complex_images [2022/11/22 18:53] rachel.osolen |
public:nnels:etext:images:complex_images [2024/09/04 20:09] (current) rachel.osolen [Common Image Types] |
||
---|---|---|---|
Line 13: | Line 13: | ||
<note tip>If you have any questions, post your question on the [[public: | <note tip>If you have any questions, post your question on the [[public: | ||
- | ======How to Write Long Descriptions====== | + | < |
- | + | ||
- | The complex descriptions must also follow the standard Alt-text guidelines (though it will be longer than 2-3 sentences). | + | |
- | * Use as few words as possible. Be clear and precise. | + | |
- | * Be consistent and balanced in your descriptions. Most long descriptions are not narrative and are more repetitive than general Alt-Text. This helps the reader keep track of the data and information without getting lost. | + | |
- | < | + | |
- | * Know your audience. If it is a fantasy novel map, a more narrative style would work for the description. But if it is a map in a textbook, then a be less narrative focusing on the data and facts. | + | |
- | * Focus on the data and not on extraneous visual elements. Don’t describe every detail. | + | |
- | < | + | |
- | * The reader should be able to understand the description in one reading. | + | |
- | * Start with a brief description, | + | |
- | * Use multiple modalities when necessary. Some content is better converted to tables or lists than being provided in a narrative description. | + | |
- | + | ||
- | A strategy we use is to break the image up into its component parts, and then organize them so that the description makes logical sense. | + | |
- | + | ||
- | There are a couple of techniques you can use to breakdown a complex description: | + | |
- | * '' | + | |
- | * '' | + | |
- | * '' | + | |
- | + | ||
- | The type of breakdown | + | |
- | + | ||
- | < | + | |
- | + | ||
- | + | ||
- | A good rule to follow is that all tables need a header row and are used for tabular data. If that fits the image you are describing then use a table. Go to [[public: | + | |
- | + | ||
- | + | ||
- | If you are using lists, you can also use a more narrative style with the list by adding relational information to the data in the lists.</ | + | |
- | + | ||
- | <note tip>We recommend you check out the DAISY webinars on Complex Descriptions. You can find the links in the [[public: | + | |
- | + | ||
- | <note tip>If you have any questions, post your question on the [[public: | + | |
- | ======Getting Started===== | + | ======Getting Started====== |
For images that require more complex or extended descriptions we create two descriptions: | For images that require more complex or extended descriptions we create two descriptions: | ||
Line 69: | Line 37: | ||
<note tip>If you have any questions, post your question on the [[public: | <note tip>If you have any questions, post your question on the [[public: | ||
- | =====Maps===== | ||
- | This is the most common complex image you will come across in your work. Again, context will also help you out a lot in your description. Below are the general guidelines for how to describe a map. | + | ======How |
- | * Include the Name/Title of the Map and a Description of the Legend | ||
- | * It is not necessary to describe types of lines/ | ||
- | * Aim for clarity, even if detail is sacrificed. Focus on the information that is relevant in the greater context of the book. | ||
- | * Ask yourself: What is this Map telling the reader? Only describe what is necessary to convey the intended meaning of the map. This will vary. | ||
- | Spatial relationships are very important in maps. The reader needs to know where they are and where they are going within the description. The most common way to break down a map is with the compass technique, but this also is dependent | + | <note tip> |
- | < | + | The complex descriptions must also follow the standard Alt-text guidelines (though it will be longer than 2-3 sentences). |
+ | * Breakdown the image into smaller parts and organize it in a logical order (you may have to experiment with which technique works best: Quadrant, Compass, or Clock. See below for more details about breaking down an image.) | ||
+ | * Start with a brief description, | ||
+ | * Be consistent and balanced in your descriptions. Most long descriptions are not narrative and are more repetitive than general Alt-Text. This helps the reader keep track of the data and information without getting lost. | ||
+ | < | ||
+ | * Know your audience. If it is a fantasy novel map, a more narrative style would work for the description. But if it is a map in a textbook, then a be less narrative focusing on the data and facts. | ||
+ | * Details are important and so is consistency in terminology across all images in a book or chapter (you can pull terminology from the surrounding text). | ||
+ | * Focus on the data and not on extraneous visual elements. Don’t describe every detail.If the visual elements are important | ||
+ | * If a graph, chart, or other type of visualization has an intentional visual impact, you should include that in your description, | ||
+ | * Use multiple modalities when necessary. Some content is better converted to tables or lists than being provided in a narrative description. | ||
+ | * The reader | ||
- | See examples on [[public: | + | =====Breaking Down Image into Smaller Parts===== |
- | More tips on [[http:// | + | A strategy we use is to break the image up into its component parts, and then organize them so that the description makes logical sense. |
- | We also recommend checking out the DAISY webinars on the [[public:nnels:etext:images:resources|Resources page]]. | + | There are a couple of techniques you can use to breakdown a complex description: |
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
- | <note tip> | + | The type of breakdown will depend on the context, audience, and type of image. Sometimes |
- | =====Graphs | + | < |
- | Not all graphs require a long description. More simple graphs and charts can be easily described in 3-4 sentences and can go directly into the Alt-text. When they do need a long description it is important to focus on the facts and data more than any visual elements. | ||
- | As with maps, ask what is this chart saying? Are there any striking visual trends in this chart? Remember | + | A good rule to follow |
- | See examples on [[public: | ||
- | Again, multiple modalities | + | If you are using lists, you can also use a more narrative style with the list by adding relational information to the data in the lists.</ |
- | ====Bar Charts==== | + | <note tip>We recommend you check out the DAISY webinars on Complex Descriptions. You can find the links in the [[public: |
- | Below are the guidelines for describing a Bar Chart. | + | <note tip>If you have any questions, post your question on the [[public: |
- | * Describe only the visual features that convey meaning. | + | =====Using Multiple Modalities===== |
- | * Focus on the meaning of symbols and not their appearance. | + | |
- | * Describe the layout of the graph before describing specific data (i.e. "A Bar Chart of ..." | + | |
- | * State what the graph is telling you before you describe its details (i.e. The chart shows murder rates in Chicago from 1990 to 2020.) | + | |
- | * Include implied visual impact. | + | |
- | * Provide the most relevant information first, like what is being measured on the X and Y axes. | + | |
- | * Make sure what you are describing is relevant to the image. Do not simply repeat the titles and labels without providing information about what the graph portrays. | + | |
- | * For units, use the full word instead of short forms (ex. Use “seconds” instead of “s”) and ensure the unit is described consistently throughout the description. | + | |
- | See examples on [[public: | + | Organization |
- | < | + | Common usage of multiple modalities: |
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
- | ====Pie chart==== | + | Multiple modalities can really help with organizing the informational structure of the image in a way that will avoid cognitive overload. |
- | The description for a pie chart needs to reference the following data elements: | + | Multiple Modalities can include: |
- | * The title of the pie chart. | + | * Tables |
- | * The structure and design of the chart. | + | * Lists |
- | * The number of variables. | + | * Paragraph breaks |
- | * The data point(s) for each variable. This may be a value, a percentage or both. | + | * Even subheadings |
- | * When describing the data, organize the data into size order to help the user with visualizing and understanding the chart. | + | |
- | * Unless colour is integral to understanding the chart, it does not need to be referenced. | + | |
- | See examples on [[public: | + | < |
- | ====Flowcharts and Trees==== | + | In your list can include the following: |
+ | * The name of the item/ | ||
+ | * The shape (not needed for maps) | ||
+ | * The location | ||
+ | * Proximity (i.e. spatial relationship to other items/ | ||
+ | * Colour (for science images) | ||
+ | </ | ||
- | Flowcharts | + | =====Word Choice |
- | The description of a flowchart needs to reference | + | It is very important that the describer understand |
- | * The title of the flowchart. | + | |
- | * The structure of the chart and a summary of what it is saying (i.e. The Smiths Family Tree). | + | |
- | * Number of Tiers or Layers. Describe all the levels first, then start at the beginning and work your way through the flowchart | + | |
- | * When describing | + | |
- | * Describe pathways through the flowchart to guide the user | + | |
- | <note tip> | + | Word choice is paramount. Be consistent. |
- | <note tip>If there is jumping back and forth between different points in the flowchart, then you should mix headings with your list as opposed | + | Using the surrounding text the describer will be able to pull terminology for their descriptions. You can also use the dictionary |
- | For examples, go to [[public: | + | Track terminology used, any progression in the image types, and be consistent with terminology. For example, when a simple image is introduced earlier in the book, and then reintroduced later with more details. |
- | ====Venn Diagrams==== | ||
- | A Venn Diagram consists of a list of elements interacting with each other to form sets. Your description should trace the diagram in a clockwise direction and list each interaction and the sets created by those interactions. | + | ======Common Image Types====== |
- | The description of a Venn Diagram needs to reference the following elements | + | The following sections go do a deeper dive for particular image types that we commonly come across in our work. |
- | * State the number of variables and the labels. | + | |
- | * Identify the focus or gateway point. | + | |
- | * Identify the pathway (left to right or clockwise depending on the style of Venn diagram). | + | |
- | * Reference the labels as you move through the pathway identifying the interactions | + | |
- | For examples, go to [[public: | + | * [[public: |
+ | * [[public:nnels: | ||
+ | * [[public: | ||
+ | * [[public: | ||
+ | * [[public: | ||
+ | * [[public: | ||
<note tip>If you have any questions, post your question on the [[public: | <note tip>If you have any questions, post your question on the [[public: | ||
- | =====Paintings===== | + | <note tip>If you want more support on writing long descriptions beyond this written documentation. We recommend you check out the following webinars: |
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | These are all very helpful with learning about writing complex long descriptions.</ | ||
- | Depending on the context, | + | < |
+ | </ | ||
- | The description of a Painting needs to reference | + | <note tip> |
- | * An overview of the artwork piece including | + | |
- | * the title | + | |
- | * a brief description | + | |
- | < | ||
- | The [[https:// | + | <note tip>Go to [[public: |
- | + | ||
- | For a complex description it is important to consider the context for which you need the description. This may include: | + | |
- | + | ||
- | * The painting style | + | |
- | * The color and composition | + | |
- | * The style and location of the figures/ | + | |
- | * Allegorical Meaning | + | |
- | * Historical Context | + | |
- | + | ||
- | For examples, go to [[public: | + | |
- | + | ||
- | <note tip>If you have any questions, post your question on the [[public: | + | |
- | + | ||
- | =====Anatomy and Diagrams with Labels===== | + | |
- | + | ||
- | Unlike other long descriptions described above, shapes are important to Anatomy and Diagrams with Labels. Spatial relationships are also essential. You do not want to simply list all the labels without context or relations. Remember, you want to walk the reader through the diagram, and you should be able to recreate the image from your description. | + | |
- | + | ||
- | The description of an Anatomy Image or Diagram with Labels needs to reference the following elements: | + | |
- | + | ||
- | * Include the shapes of the parts and where they are located in relation to each other. | + | |
- | * Spatial relationships, | + | |
- | + | ||
- | < | + | |
- | + | ||
- | For examples, go to [[public: | + | |
- | + | ||
- | <note tip>If you have any questions, post your question on the [[public: | + | |
- | + | ||
- | < | + | |
- | </ | + | |
- | <note tip> | + | |
[[public: | [[public: | ||