{"id":120,"date":"2019-07-23T17:04:48","date_gmt":"2019-07-23T17:04:48","guid":{"rendered":"https:\/\/pressbooks.library.ryerson.ca\/docs\/?post_type=chapter&#038;p=120"},"modified":"2021-05-19T17:41:35","modified_gmt":"2021-05-19T17:41:35","slug":"keynote","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/docs\/chapter\/keynote\/","title":{"raw":"Keynote for Mac","rendered":"Keynote for Mac"},"content":{"raw":"[rl_collapsible_section title=\"Usage Notes\" title-tag=\"h2\" collapsed=\"no\"]\r\n\r\nAt the time of testing (September 30, 2010), Keynote '09 lacks several features that enable accessible office document authoring, most notably: the ability to add alternative text to images and objects, indicating natural language, quick styles or named styles, and change tracking. As a result, some of the other features that might otherwise support accessibility, such as its extensive templates are not as effective. In addition, Keynote \u201809 does not include an accessibility checking feature, which is a more advanced accessibility feature.\r\n<div class=\"textbox textbox--learning-objectives\">\r\n<div class=\"textbox__content\">\r\n\r\n<strong>Editor's note:<\/strong> In later versions of Keynote, users can add alt text to images and objects. Apple has added significant accessibility improvements to its iWork applications, but an accessibility checker is not a feature yet.\r\n\r\n<\/div>\r\n<\/div>\r\n<h3>What\u2019s an \u201cOffice Document\u201d?<\/h3>\r\nYou should use these techniques when you are using Keynote '09 to create documents that are:\r\n<ul>\r\n \t<li><strong>Intended to be used by people <\/strong>(i.e., not computer code),<\/li>\r\n \t<li><strong>Text-based<\/strong> (i.e., not simply images, although they may contain images),<\/li>\r\n \t<li><strong>Fully printable <\/strong>(i.e., where dynamic features are limited to automatic page numbering, table of contents, etc. and do not include audio, video, or embedded interactivity)<strong>,<\/strong><\/li>\r\n \t<li><strong>Self-contained<\/strong> (i.e., without hyperlinks to other documents, unlike web content), and<\/li>\r\n \t<li><strong>Typical of office-style workflows <\/strong>(Reports, letters, memos, budgets, presentations, etc.).<\/li>\r\n<\/ul>\r\n<strong>If you are creating forms, web pages, applications, or other dynamic and\/or interactive content, these techniques will still be useful to you, but you should also consult the <\/strong><a href=\"http:\/\/www.w3.org\/WAI\/intro\/wcag.php\" target=\"_blank\" rel=\"noopener noreferrer\"><strong>W3C-WAI Web Content Accessibility Guidelines (WCAG 2.0)<\/strong><\/a><strong> because these are specifically designed to provide guidance for highly dynamic and\/or interactive content. <\/strong>\r\n<h3>File Formats<\/h3>\r\nThe default file format for Keynote \u201809 is the native <strong>iWork format<\/strong>. In addition, Keynote \u201809 offers many other presentation processor and web format saving options. Most of these have not been checked for accessibility, but some information and\/or instructions are available for the following formats in <a href=\"#key12\">Technique 12<\/a>:\r\n<ul>\r\n \t<li>MS PowerPoint (PPT)<\/li>\r\n \t<li>PDF<\/li>\r\n \t<li>HTML<\/li>\r\n<\/ul>\r\n<h3>Document Conventions<\/h3>\r\nWe have tried to formulate these techniques so that they are useful to all authors, regardless of whether they use a mouse. However, for clarity there are several instances where mouse-only language is used. Below are the mouse-only terms and their keyboard alternatives:\r\n<ul>\r\n \t<li><strong>*Right-click:<\/strong> To right-click with the keyboard, select the object using the Shift+Arrow keys and then press either (1) the \u201cRight-Click\u201d key (some keyboard have this to the right of the spacebar) or Shift+F10.<\/li>\r\n<\/ul>\r\n<h3>Disclaimer and Testing Details:<\/h3>\r\n<strong>Following these techniques will increase the accessibility of your documents, but it does not guarantee accessibility to any specific disability groups<\/strong>. In cases where more certainty is required, it is recommended that you test the office documents with end users with disabilities, including screen reader users. The application-specific steps and screenshots in this document were created using iWork Keynote \u201809 (ver.5.0.3(791), Mac OS X, Sept. 2010) and Keynote, version 9.1 (December 2019) while producing a document in the proprietary file format. Files are also easily saved as other file formats (see <a href=\"#key12\">Technique 12<\/a>).\r\n\r\n[\/rl_collapsible_section]\r\n\r\n<a id=\"key1\"><\/a>[rl_collapsible_section title=\"Technique 1. Use Accessible Templates\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nAll office documents start with a template, which can be as simple as a blank standard-sized page or as complex as a nearly complete document with text, graphics and other content. For example, a \u201cMeeting Minutes\u201d template might include headings for information relevant to a business meeting, such as \u201cActions\u201d above a table with rows to denote time and columns for actions of the meeting. Because templates provide the starting-point for so many documents, accessibility is critical. If you are unsure whether a template is accessible, you should check a sample document produced when the template is used (see <a href=\"#key11\">Technique 11<\/a>). The default template for new documents in Keynote \u201809 is a blank presentation. If you are connected to the internet, you can access a variety of blank business presentation templates. These are all accessible by virtue of being blank. As well, you may create your own templates.\r\n<h4>To create an accessible template<\/h4>\r\n<ol>\r\n \t<li>Go to menu item: <strong>File &gt; New<\/strong> or <strong>File &gt; New from Theme Chooser\u2026 <\/strong><\/li>\r\n \t<li>In the <strong>Theme Chooser<\/strong> dialog, select the <strong>White <\/strong>theme or select one of the other existing template designs<\/li>\r\n \t<li>A new document in your selected template style will open<\/li>\r\n \t<li>Ensure that you follow the techniques in this document<\/li>\r\n \t<li>When you are finished you should also check the accessibility of the document (see <a href=\"#key11\">Technique 11<\/a>)<\/li>\r\n \t<li>Go to menu item: <strong>File &gt; Save Theme\u2026<\/strong><\/li>\r\n \t<li>In the <strong>Save As<\/strong> box, type a name for the template. Using a descriptive template name (e.g. \u201cAccessible Memo Template\u201d) will increase the prominence of the accessibility status.<\/li>\r\n \t<li>Specify a folder in which to save your template. <em>Note:<\/em> By default, it will be saved in your home folder in Library\/Application Support\/iWork\/Keynote\/Templates\/My Templates pane of the <strong>Template Chooser<\/strong>. To save the template in a different location than the default, create a new folder in the <strong>Templates <\/strong>folder. The folder name is then used as a template category in the <strong>Template Chooser.<\/strong>\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_1.png\" alt=\"Image demonstrates location of Save As box and Where option.\" width=\"335\" height=\"104\" \/><\/li>\r\n \t<li>Click <strong>Save <\/strong><\/li>\r\n<\/ol>\r\n<h4>To select an accessible template<\/h4>\r\n<em>Note:<\/em> Only use these steps if you have an accessible template available (e.g. that you previously saved). Otherwise, simply open a new (blank) document.\r\n<ol>\r\n \t<li>Go to menu item: <strong>File &gt; New from Theme Chooser\u2026<\/strong><\/li>\r\n \t<li>In the <strong>Template Chooser<\/strong> dialog, select <strong>My Templates<\/strong> from the left pane<\/li>\r\n \t<li>Select your accessible template and click <strong><strong>Choose\r\n<\/strong><\/strong><img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_2.png\" alt=\"Image demonstrates location of My template option and template icons in Template Chooser dialog.\" width=\"223\" height=\"221\" \/><\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 2. Set Document Language\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nAt this time, it is not possible to manually indicate the natural language for specific slides or sections of text in Keynote \u201809. As well, it is not possible to change the natural language of the document itself from the default language. <strong>[Tested: September 30th, 2010]<\/strong>\r\n<div class=\"textbox textbox--learning-objectives\">\r\n<div class=\"textbox__content\">\r\n\r\n<strong>Editor's note:<\/strong> In later versions of Keynote, users are able to set a presentation's language.\r\n<ol>\r\n \t<li>Choose File &gt; Advanced &gt; Language &amp; Region (from the File menu at the top of your screen).<\/li>\r\n \t<li>In the dialog that appears, click the pop-up menus and choose a language and a region.\r\n<em style=\"text-align: initial;font-size: 1em\">Note:<\/em><span style=\"text-align: initial;font-size: 1em\"> You can\u2019t change this setting for a shared presentation.<\/span><\/li>\r\n \t<li><span style=\"text-align: initial;font-size: 1em\">Click OK.<\/span><\/li>\r\n<\/ol>\r\nFor more details, see <a href=\"https:\/\/support.apple.com\/kb\/PH28043\" target=\"_blank\" rel=\"noopener noreferrer\">how to change a presentation\u2019s language and formatting<\/a>.\r\n\r\n<\/div>\r\n<\/div>\r\n&nbsp;\r\n\r\nIn order for assistive technologies (e.g., screen readers) to be able to present your document accurately, it is important to indicate the natural language of the document. If a different natural language is used for a paragraph or selected text, this also needs to be clearly indicated.\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 3. Use Built-In Layout and Styling Features\" title-tag=\"h2\" collapsed=\"yes\"]\r\n<h3>3.1 Use Built-In Slide Layouts<\/h3>\r\nInstead of creating each slide in your presentation by starting from a blank slide, check whether there is a suitable built-in layout. <em>Note:<\/em> The built-in layouts can be more accessible to users of assistive technologies because they technologies sometimes read the floating items on the slide in the order that they were placed on the slide. The built-in layouts have usually taken this into account (e.g., \u201cTitle\u201d first followed by other items, left to right and from top to bottom). If you create slide layouts from scratch, it is sometimes difficult to keep track of the order elements were placed. <em>Note:<\/em> Each slide in Keynote \u201909 is derived from a Master Slide (<a href=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/chapter\/openoffice-impress#tech3.1\">Technique 3.2<\/a>) applying \u201ctrue layouts\u201d requires that you use Master Slides that are accessible and appropriately designed for your purposes.\r\n<h3><a id=\"key3.2\"><\/a>3.2 Customize Using Master Slides<\/h3>\r\nIf a layout must be customized, it is recommended that Master Slides be used. Every slide layout in a presentation is defined by its master slide. A master slide determines the formatting style for various elements of the slide layout. This includes font styles, character formatting, and the positioning of elements. Essentially, each master slide acts as a design template for the slide layout. If you edit any aspect of the slide layout in the master slide, the change will affect all slides that were created based on it. For this reason, it is good practice to edit the master slide and use the slide layouts before building individual slides. It is essential that you create and use master slides that meet the accessibility requirements outlined in this document.\r\n<h4>To create or customize a master slide<\/h4>\r\n<ol>\r\n \t<li>Select the slide Note: To design a master slide from scratch, select a blank slide to start with. Otherwise, select a slide that resembles how you would like your slide to look and be sure to modify the slide characteristics to align with accessibility guidelines in this document.<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Master Slides<\/strong><\/li>\r\n \t<li>In the <strong>Master Slide Navigator<\/strong> in the left pane, select the <strong>Master Slide Layout<\/strong> you would like to modify<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_3.png\" alt=\"Image demonstrates location of Master Slide Layouts in Master Slides view.\" width=\"216\" height=\"298\" \/><\/li>\r\n \t<li>Customize the master slide to suit your needs (e.g., define placeholders for text, change background elements, add alignment guides, and more) ensuring that your changes meet accessibility requirements<\/li>\r\n<\/ol>\r\n<h4>To define default attributes of text and objects<\/h4>\r\n<ol>\r\n \t<li>Select the slide Note: To design a master slide from scratch, select a blank slide to start with. Otherwise, select a slide that resembles how you would like your slide to look and be sure to modify the slide characteristics to align with accessibility guidelines in this document.<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Master Slides<\/strong><\/li>\r\n \t<li>In the <strong>Master Slide Navigator<\/strong> in the left pane, select the <strong>Master Slide Layout<\/strong> you would like to define default attributes for\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_4.png\" alt=\"Image demonstrates location of Master Slide Layouts in Master Slides view.\" width=\"216\" height=\"298\" \/><\/li>\r\n \t<li>In the <strong>Toolbar<\/strong>, click the element type (e.g., text box, shapes, table, charts)\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_5.png\" alt=\"Image demonstrates elements type options in the Toolbar.\" width=\"247\" height=\"48\" \/><\/li>\r\n \t<li>In the <strong>Formatting<\/strong> bar, format the element ensuring that it meets accessibility guidelines outlined in this document<\/li>\r\n \t<li>To make the element a default for your current master slide, go to menu item: <strong>Format &gt; Advanced &gt; Define (element type) for Current Master <\/strong>Note: To make the element a default for all master slides, go to menu item: <strong>Format &gt; Advanced &gt; Define (element type) for All Masters<\/strong><\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n<a id=\"key4\"><\/a>[rl_collapsible_section title=\"Technique 4. Set a Logical Tab Order\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nMany presentation applications create content composed almost exclusively of \"floating\" objects. This means that they avoid the transitions between in-line content and secondary \"floating\" objects (text boxes, images, etc.) that can cause accessibility issues in word processors. However, when you are working with \"floating\" objects, it is important to remember that the way objects are positioned in two dimensions on the screen may be completely different from how the objects will be read by a screen reader or navigated using a keyboard. The order that content is navigated sequentially is called the \"Tab Order\" because often the \"Tab\" key is used to navigate from one \"floating\" object to the next.\r\n<div class=\"textbox shaded\">\r\n<h4>Tips for setting a logical \u201ctab order\u201d for \"floating\" objects<\/h4>\r\n<ul>\r\n \t<li>The tab order of floating objects is usually from the \u201clowest\u201d object on the slide to the \u201chighest\u201d.<\/li>\r\n \t<li>Because objects automatically appear \u201con top\u201d when they are inserted, the default tab order is from the first object inserted to the last. However, this will change if you use features such as \u201cbring to front\u201d and \u201csend to back\u201d.<\/li>\r\n \t<li>The slide\u2019s main heading should be first in the tab order.<\/li>\r\n \t<li>Headings should be placed in the tab order immediately before the items (text, diagrams, etc.) for which they are acting as a heading.<\/li>\r\n \t<li>Labels should be in the reading order placed immediately before the objects that they label.<\/li>\r\n \t<li>For simple slide layouts, it may be possible to simply insert objects in a logical tab order.<\/li>\r\n \t<li>For more complex layouts, it may be easier to simply to create the slide as usual and then set the tab order (see below).<\/li>\r\n<\/ul>\r\n<\/div>\r\n<h4>To set the tab order<\/h4>\r\n<ol>\r\n \t<li>Select the object<\/li>\r\n \t<li>Go to menu item: <strong>Arrange &gt; Bring Forward<\/strong>, <strong>Bring to Front<\/strong>, <strong>Send Backward<\/strong> or <strong>Send to Back<\/strong><\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 5. Use Slide Notes\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nA useful aspect of presentation applications is the facility to add notes to slides, which can then be read by assistive technologies. You can use these slide notes to explain and expand on the contents of your slides in text format. Slide notes can be created as you build your presentation.\r\n<h4>To add notes to your slides<\/h4>\r\n<ol>\r\n \t<li>Go to menu item: <strong>View &gt; Show Presenter Notes<\/strong><\/li>\r\n \t<li>In the pane at the bottom of the window (below the slide), enter notes to accompany each slide<\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 6. Provide Text Alternatives for Images and Graphical Objects\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nAt this time, Keynote \u201909 does not offer a mechanism which enables the user to add alternative text descriptions to images or objects. <strong>[Tested: September 28, 2010]<\/strong>\r\n<div class=\"textbox textbox--learning-objectives\">\r\n<div class=\"textbox__content\">\r\n\r\n<strong>Editor's note: <\/strong>For later versions of Keynote, users can add alternative text descriptions for images and objects.\r\n<ol>\r\n \t<li>Select the image and go to the <strong>Format<\/strong> side bar. Click on the image tab.<\/li>\r\n \t<li>Click the <strong>Description<\/strong> text box, then enter your text.<\/li>\r\n<\/ol>\r\nFor more details, see the section on <a href=\"https:\/\/support.apple.com\/en-ca\/guide\/keynote\/tan77aea6844\/mac\" target=\"_blank\" rel=\"noopener noreferrer\">how to add an image description<\/a> on the Keynote User Guide for Mac.\r\n\r\n<\/div>\r\n<\/div>\r\n&nbsp;\r\n\r\nWhen using images or other graphical objects, such as charts and graphs, it is important to ensure that the information you intend to convey by the image is also conveyed to people who cannot see the image. This can be accomplished by adding concise alternative text of each image. If an image is too complicated to concisely describe in the alternative text alone (artwork, flowcharts, etc.), provide a short text alternative and a longer description as well.\r\n<div class=\"textbox shaded\">\r\n<h4>Tips for writing alternative text<\/h4>\r\n<ul>\r\n \t<li>Try to answer the question \"what information is the image conveying?\"<\/li>\r\n \t<li>If the image does not convey any useful information, leave the alternative text blank<\/li>\r\n \t<li>If the image contains meaningful text, ensure all of the text is replicated<\/li>\r\n \t<li>Alternative text should be fairly short, usually a sentence or less and rarely more than two sentences<\/li>\r\n \t<li>If more description is required (e.g., for a chart or graph), provide a short description in the alternative text (e.g., a summary of the trend) and more detail in the long description, see below<\/li>\r\n \t<li>Test by having others review the document with the images replaced by the alternative text<\/li>\r\n<\/ul>\r\n<\/div>\r\n<div class=\"textbox shaded\">\r\n<h4>Tips for writing longer descriptions<\/h4>\r\n<ul>\r\n \t<li>Long descriptions should be used when text alternatives (see above) are insufficient to answer the question \"what information is the image conveying?\"<\/li>\r\n \t<li>In some situations, the information being conveyed will be how an image looks (e.g., an artwork, architectural detail, etc.). In these cases, try to describe the image without making too many of your own assumptions.<\/li>\r\n \t<li>One approach is to imagine you are describing the image to a person over the phone<\/li>\r\n \t<li>Ensure that you still provide concise alternative text to help readers decide if they are interested in the longer description<\/li>\r\n<\/ul>\r\nAlternatively, you can include the same information conveyed by the image within the body of the document, providing the images as an alternate to the text. In that case, you do not have to provide alternate text within the image.\r\n\r\n<\/div>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 7. Use Built-In Structuring Features\" title-tag=\"h2\" collapsed=\"yes\"]\r\n<h3>7.1 Tables<\/h3>\r\nWhen using tables, it is important to ensure that they are clear and appropriately structured. This helps all users to better understand the information in the table and allows assistive technologies (e.g., screen readers) to provide context so that the information within the table can be conveyed in a meaningful way.\r\n<div class=\"textbox shaded\">\r\n<h4>Tips for tables<\/h4>\r\n<ul>\r\n \t<li>Only use tables for tabular information, not for formatting.<\/li>\r\n \t<li>Use \u201creal tables\u201d rather than text formatted to look like tables using the TAB key or space bar. These will not be recognized by assistive technology.<\/li>\r\n \t<li>Keep tables simple by avoiding merged cells and dividing complex data sets into separate smaller tables, where possible.<\/li>\r\n \t<li>If tables split across pages, set the header to show at the top of each page. Also set the table to break between rows instead of in the middle of rows.<\/li>\r\n \t<li>Create a text summary of the essential table contents. Any abbreviations used should be explained in the summary.<\/li>\r\n \t<li>Table captions or descriptions should answer the question \"what is the table's purpose and how is it organized?\" (e.g., \"A sample order form with separate columns for the item name, price and quantity\").<\/li>\r\n \t<li>Table cells should be marked as table headers when they serve as labels to help interpret the other cells in the table.<\/li>\r\n \t<li>Table header cells labels should be concise and clear.<\/li>\r\n \t<li>Ensure the table is not \u201cfloating\u201d on the page (see <a href=\"#key4\">Technique 4<\/a>).<\/li>\r\n<\/ul>\r\n<\/div>\r\n<h4>To set default table attributes<\/h4>\r\n<ol>\r\n \t<li style=\"list-style-type: none\">\r\n<ol>\r\n \t<li>Go to menu item: <strong>View &gt; Show Master Slides<\/strong><\/li>\r\n \t<li>Select a master slide from the <strong>Master Slides Navigator<\/strong> in the left pane\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_6.png\" alt=\"Image demonstrates location of master slide layouts in Master Slides view.\" style=\"text-align: initial;font-size: 1em\" width=\"216\" height=\"298\" \/><\/li>\r\n \t<li>In the <strong>Toolbar<\/strong>, click <strong>Table\r\n<\/strong><img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_7.png\" alt=\"Image demonstrates location of table element in Toolbar.\" style=\"text-align: initial;font-size: 1em\" width=\"280\" height=\"57\" \/><\/li>\r\n \t<li>Select the table<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\r\n \t<li>In the <strong>Inspector<\/strong> dialog, select <strong>Table inspector<\/strong><\/li>\r\n \t<li>Click the <strong>Table<\/strong> tab<\/li>\r\n \t<li>In the <strong>Headers &amp; Footers<\/strong> section, select <strong>Choose the number of header columns<\/strong> or <strong>Choose the number of header rows<\/strong> drop-down menus<\/li>\r\n \t<li>Select the number of headers\r\n<em>Note:<\/em> Limiting your table to one row or column of header will ensure your table remains clear and easy to interpret by assistive technologies.\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_8.png\" alt=\"Image demonstrates Table icon, Table tab, and Headers &amp; Footer section in Inspector dialog.\" style=\"text-align: initial;font-size: 1em\" width=\"236\" height=\"169\" \/><\/li>\r\n \t<li>Customize the other characteristics of your table through the other sections of the <strong>Table inspector<\/strong> dialog<\/li>\r\n \t<li>To make the table a default for your current master slide, go to menu item: <strong>Format &gt; Advanced &gt; Define Table for Current Master\r\n<\/strong><em>Note:<\/em> To make the table a default for all master slides, go to menu item: <strong style=\"text-align: initial;font-size: 1em\">Format &gt; Advanced &gt; Define Table for All Masters<\/strong><span style=\"text-align: initial;font-size: 1em\"> Note: Defining the table as a default for all masters means that when you insert a Table element into any slide, it will display your preformatted characteristics (including appropriate headers)<\/span><\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ol>\r\n<h3>7.2 Lists<\/h3>\r\nWhen you create lists, it is important to format them as \u201creal lists\u201d. Otherwise, assistive technologies will interpret your list as a series of short separate paragraphs instead of a coherent list of related items.\r\n<h4>To create an ordered or unordered list<\/h4>\r\n<ol>\r\n \t<li>Select the text box or highlight the text<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\r\n \t<li>In the <strong>Inspector <\/strong>dialog, click <strong>Text inspector<\/strong><\/li>\r\n \t<li>Click the <strong>Bullets <\/strong>tab<\/li>\r\n \t<li>In the <strong>Bullets &amp; Numbering<\/strong> section, click the drop-down menu and choose a bullet or numbering option<\/li>\r\n \t<li>Customize the list style accordingly, ensuring your selections align with the guidelines in this document<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_9.png\" alt=\"Image demonstrates location of Text inspector button, Bullets tab, and Bullets &amp; Numbering section of Inspector dialog.\" width=\"173\" height=\"115\" \/><\/li>\r\n<\/ol>\r\n<h3>7.3 Columns<\/h3>\r\nUse Columns feature for placing text in columns. <em>Note:<\/em> Because columns can be a challenge for users of some assistive technologies, consider whether a column layout is really necessary.\r\n<h3>7.4 Document Title<\/h3>\r\nIn case the document is ever converted into HTML, it should be given a descriptive and meaningful title.\r\n<h4>To change the title of the current document<\/h4>\r\n<ol>\r\n \t<li>In the <strong>Toolbar<\/strong>, select <strong>Inspector<\/strong><\/li>\r\n \t<li>In the <strong>Inspector<\/strong> dialog, select the <strong>Document inspector<\/strong> button<\/li>\r\n \t<li>Click the <strong>Spotlight <\/strong>tab<\/li>\r\n \t<li>In the <strong>Title<\/strong> box, type a descriptive name for the document <em>Note:<\/em> The <strong>Title<\/strong> defined in the properties is different than the file name. It is also unrelated to the template name, discussed above.\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_10.png\" alt=\"Image demonstrates location of Document inspector button, Spotlight tab, and Title text box in Inspector dialog.\" width=\"167\" height=\"215\" \/><\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 8. Create Accessible Charts\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nCharts can be used to make data more understandable for some audiences. However, it is important to ensure that your chart is as accessible as possible to all members of your audience. All basic accessibility considerations that are applied to the rest of your document must also be applied to your charts and the elements within your charts. For example, use shape and color, rather than color alone, to convey information. As well, some further steps should be taken to ensure that the contents are your chart are appropriate labeled to give users reference points that will help them to correctly interpret the information.\r\n<h4>To create a chart<\/h4>\r\n<ol>\r\n \t<li>Go to menu item: <strong>Insert &gt; Chart<\/strong><\/li>\r\n \t<li>Select the type of chart you want to use<\/li>\r\n \t<li>Update the <strong>Chart Data Editor<\/strong> with the data you would like to display<\/li>\r\n \t<li>Close the <strong>Chart Data Editor<\/strong><\/li>\r\n<\/ol>\r\n<h4>To add titles and labels<\/h4>\r\n<ol>\r\n \t<li>Select the chart<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\r\n \t<li>In the <strong>Chart Inspector<\/strong>, select <strong>Chart<\/strong><\/li>\r\n \t<li>Ensure the <strong>Show Title<\/strong> and <strong>Show Legend<\/strong> check boxes are selected<\/li>\r\n \t<li>Select <strong>Axis<\/strong><\/li>\r\n \t<li>Under <strong>Value Axis (Y)<\/strong> and <strong>Category Axis (X)<\/strong>, select <strong>Show Title<\/strong> and <strong>Show Value Labels<\/strong> from their respective drop-down menus<\/li>\r\n<\/ol>\r\n<h4>To change to a different predefined Chart Type<\/h4>\r\n<ol>\r\n \t<li>Select the chart<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\r\n \t<li>Select a chart type from the <strong>Choose a chart type<\/strong> drop-down menu<\/li>\r\n<\/ol>\r\n<h3>Other Chart Considerations<\/h3>\r\n<ul>\r\n \t<li>When creating line charts, use the formatting options to create different types of dotted lines to facilitate legibility for users who are color blind<\/li>\r\n \t<li>When creating bar charts, it is helpful to apply texture instead of color to differentiate the bars<\/li>\r\n \t<li>Change the default colors to a color safe or gray-scale palette<\/li>\r\n \t<li>Use the formatting options to change predefined colors, ensuring that they align with sufficient contrast requirements (see <a href=\"#key92\">Technique 9.2<\/a>)<\/li>\r\n<\/ul>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 9. Make Content Easier to See\" title-tag=\"h2\" collapsed=\"yes\"]\r\n<h3>9.1 Format of Text<\/h3>\r\nWhen formatting text, especially when the text is likely to be printed, try to:\r\n<ul type=\"disc\">\r\n \t<li>Use font sizes between 12 and 18 points for body text.<\/li>\r\n \t<li>Use fonts of normal weight, rather than bold or light weight fonts. If you do choose to use bold fonts for emphasis, use them sparingly.<\/li>\r\n \t<li>Use standard fonts with clear spacing and easily recognized upper and lower case characters. Sans serif fonts (e.g., Arial, Verdana) may sometimes be easier to read than serif fonts (e.g., Times New Roman, Garamond).<\/li>\r\n \t<li>Avoid large amounts of text set all in caps, italic or underlined.<\/li>\r\n \t<li>Use normal or expanded character spacing, rather than condensed spacing.<\/li>\r\n \t<li>Avoid animated or scrolling text.<\/li>\r\n<\/ul>\r\n<strong>But can\u2019t users just zoom in?<\/strong> Office applications do typically include accessibility features such as the ability to magnify documents and support for high contrast modes. However, because printing is an important aspect of many workflows and changing font sizes directly will change documents details such the pagination, the layout of tables, etc., it is best practice to always format text for a reasonable degree of accessibility.\r\n<h3><a id=\"key92\"><\/a>9.2 Use Sufficient Contrast<\/h3>\r\nThe visual presentation of text and images of text should have a contrast ration of at least 4.5:1. To help you determine the contrast, here are some examples on a white background:\r\n<ul type=\"disc\">\r\n \t<li>Very good contrast (Foreground=black, Background=white, Ratio=21:1)<\/li>\r\n \t<li>Acceptable contrast (Foreground=#767676, Background=white, Ratio=4.54:1)<\/li>\r\n \t<li>Unacceptable contrast (Foreground=#AAAAAA, Background=white, Ratio=2.32:1)<\/li>\r\n<\/ul>\r\nAlso, always use a single solid color for a text background rather than a pattern. In order to determine whether the colors in your document have sufficient contrast, you can consult an online contrast checker, such as:\r\n<ul>\r\n \t<li><a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\" target=\"_blank\" rel=\"noopener noreferrer\">WebAIM: Contrast Checker<\/a><\/li>\r\n \t<li><a href=\"http:\/\/juicystudio.com\/services\/luminositycontrastratio.php\" target=\"_blank\" rel=\"noopener noreferrer\">Juicy Studio: Luminosity Color Contrast Ratio Analyzer<\/a><\/li>\r\n \t<li><a href=\"http:\/\/www.joedolson.com\/color-contrast-tester.php\" target=\"_blank\" rel=\"noopener noreferrer\">Joe Dolson Color Contrast Spectrum Tester<\/a><\/li>\r\n \t<li><a href=\"http:\/\/www.joedolson.com\/color-contrast-compare.php\" target=\"_blank\" rel=\"noopener noreferrer\">Joe Dolson Color Contrast Comparison<\/a><\/li>\r\n<\/ul>\r\n<h3>9.3 Avoid Using Color Alone<\/h3>\r\nColor should not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. In order to spot where color might be the only visual means of conveying information, you can create a screenshot of the document and then view it with online gray-scale converting tools, such as:\r\n<ul>\r\n \t<li>GrayBit v2.0: Grayscale Conversion Contrast Accessibility Tool<\/li>\r\n<\/ul>\r\n<div class=\"textbox textbox--learning-objectives\">\r\n<div class=\"textbox__content\">\r\n\r\n<strong>Editor's note: <\/strong>GrayBit v2.0 is no longer available. However, multiple tools can be found online: <a href=\"https:\/\/www.google.com\/search?q=convert+image+to+grayscale+online\" target=\"_blank\" rel=\"noopener noreferrer\">Google Search: gray-scale conversion tool<\/a>.\r\n\r\n<\/div>\r\n<\/div>\r\n<h3>9.4 Avoid Relying on Sensory Characteristics<\/h3>\r\nThe instructions provided for understanding and operating content should not rely solely on sensory characteristics such as the color or shape of content elements. Here are two examples:\r\n<ul type=\"disc\">\r\n \t<li>Do not track changes by simply changing the color of text you have edited and noting the color. Instead use PowerPoint 2010\u2019s \u201cTrack Changes\u201d feature to track changes.<\/li>\r\n \t<li>Do not distinguish between images by referring to their appearance (e.g., \u201cthe bigger one\u201d). Instead, label each image with a figure number and use that for references.<\/li>\r\n<\/ul>\r\n<h3>9.5 Avoid Using Images of Text<\/h3>\r\nBefore you use an image to control the presentation of text (e.g., to ensure a certain font or color combination), consider whether you can achieve the same result by styling \u201creal text\u201d. If this is not possible, as with logos containing stylized text, make sure to provide alternative text for the image following the techniques noted above.\r\n<h3>9.6 Avoid Transitions<\/h3>\r\nTransitions between slides and elements in each slide (e.g., bullets in a list flying onto the screen) can be distracting to users with disabilities. It can also cause assistive technologies to read the slide incorrectly. For these reasons, it is best to avoid transitions altogether.\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 10. Make Content Easier to Understand\" title-tag=\"h2\" collapsed=\"yes\"]\r\n<h3>10.1 Write Clearly<\/h3>\r\nBy taking the time to design your content in a consistent way, it will be easier to access, navigate and interpret for all users:\r\n<ul type=\"disc\">\r\n \t<li>Whenever possible, write clearly with short sentences.<\/li>\r\n \t<li>Introduce acronyms and spell out abbreviations.<\/li>\r\n \t<li>Avoid making the document too \u201cbusy\u201d by using lots of whitespace and by avoiding too many different colors, fonts and images.<\/li>\r\n \t<li>If content is repeated on multiple pages within a document or within a set of documents (e.g., headings, footings, etc.), it should occur consistently each time it is repeated.<\/li>\r\n<\/ul>\r\n<h3>10.2 Provide Context for Hyperlinks<\/h3>\r\nHyperlink text in your document should be meaningful when read out of context. To be an effective navigation aid, the link text should describe the destination of the link.\r\n\r\nConsider the experience of screen reader users: Generally, screen readers generate a list of links, and screen reader users navigate this list alphabetically. Hyperlink text such as \"click here\" or \"more\" is meaningless in this context.\r\n\r\nIn order to be useful to someone using a screen reader, ensure that hyperlink text is self-describing and meaningful on its own. To make the address of hyperlink clear when printing, you may wish to include the address in brackets following the descriptive text of the hyperlink.\r\n<h4>To edit hyperlink text<\/h4>\r\n<ol>\r\n \t<li>Enter the hyperlink<\/li>\r\n \t<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\r\n \t<li>In the <strong>Inspector<\/strong> dialog, click <strong>Hyperlink inspector<\/strong><\/li>\r\n \t<li>In the <strong>Display<\/strong> box, enter the text you would like to display\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_11.png\" alt=\"Image demonstrates location of Hyperlink inspector button and Display text box in Inspector dialog.\" width=\"187\" height=\"139\" \/><\/li>\r\n<\/ol>\r\n<h3>10.3 Accessible Presentations<\/h3>\r\nIt is important to consider accessibility before, during, and after presentations. Below is a helpful link with guidance on how to make presentations accessible to all:\r\n<ul>\r\n \t<li>\u201cHow to Make Presentations Accessible to All\u201d <a href=\"http:\/\/www.w3.org\/WAI\/training\/accessible\" target=\"_blank\" rel=\"noopener noreferrer\">(Source: W3C-WAI Draft)<\/a><\/li>\r\n<\/ul>\r\n[\/rl_collapsible_section]\r\n\r\n<a id=\"key11\"><\/a>[rl_collapsible_section title=\"Technique 11. Check Accessibility\" title-tag=\"h2\" collapsed=\"yes\"]\r\nAt this time, Keynote \u201909 does not offer a mechanism to check for potential accessibility errors in your document prior to publishing. <strong>[Tested: September 30th, 2010]<\/strong> In order to get some indication of the accessibility of your document or template (see <a href=\"#key1\">Technique 1<\/a>), then you may consider saving the file into HTML or PDF in order to perform an accessibility check in one of those formats, as described below.\r\n<h4>To evaluate HTML accessibility<\/h4>\r\nIf you wish to check the accessibility of your document or template (see <a href=\"#key1\">Technique 1<\/a>), one option is to save it into HTML format and use one of the web accessibility checkers available online. Such as:\r\n<ul>\r\n \t<li><a href=\"https:\/\/achecker.achecks.ca\/checker\/index.php\" target=\"_blank\" rel=\"noopener noreferrer\">AChecker<\/a><\/li>\r\n \t<li><a href=\"http:\/\/wave.webaim.org\/\" target=\"_blank\" rel=\"noopener noreferrer\">WebAIM Wave Web Accessibility Evaluation Tool<\/a><\/li>\r\n<\/ul>\r\n<h4>To evaluate PDF accessibility<\/h4>\r\nIf you saved your document in tagged PDF format, you can use the following tools and steps to evaluate the accessibility of the PDF document:\r\n<ul>\r\n \t<li><a href=\"https:\/\/acrobat.adobe.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">Adobe Acrobat Professional<\/a><\/li>\r\n \t<li><a href=\"https:\/\/commonlook.com\/accessibility-software\/pdf-validator\/\" target=\"_blank\" rel=\"noopener noreferrer\">CommonLook PDF Evaluator<\/a><\/li>\r\n \t<li><a href=\"https:\/\/www.access-for-all.ch\/en\/pdf-lab\/pdf-accessibility-checker-pac.html\" target=\"_blank\" rel=\"noopener noreferrer\">PDF Accessibility Checker (PAC)<\/a> \u2013 a free alternative provided by \u201cAccess for all\u201d<\/li>\r\n<\/ul>\r\n<h4>To evaluate PDF accessibility in Adobe Acrobat Professional<\/h4>\r\n<ol>\r\n \t<li>Go to menu item: <strong>Advanced &gt; Accessibility &gt; Full Check\u2026<\/strong><\/li>\r\n \t<li>In the <strong>Full Check<\/strong> dialog, select all the checking option<\/li>\r\n \t<li>Select the <strong>Start Checking<\/strong> button<\/li>\r\n<\/ol>\r\n<div class=\"textbox textbox--learning-objectives\">\r\n<div class=\"textbox__content\">\r\n\r\n<strong>Editor's note: <\/strong>For detailed instructions, see our section on <a href=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/chapter\/adobe-acrobat-11-pro-and-dc\/\" target=\"_blank\" rel=\"noopener noreferrer\">how to check accessibility using Adobe Acrobat Professional<\/a>.\r\n\r\n<\/div>\r\n<\/div>\r\n[\/rl_collapsible_section]\r\n\r\n<a id=\"key12\"><\/a>[rl_collapsible_section title=\"Technique 12. Use Accessibility Features when Saving\/Exporting to Other Formats\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nIn some cases, additional steps must be taken in order to ensure accessibility information is preserved when saving\/exporting to formats other than the default.\r\n<h4>To export to a different format<\/h4>\r\n<ol>\r\n \t<li>Go to menu item: <strong>Share &gt; Export<\/strong><\/li>\r\n \t<li>Select the file format you would like to export<\/li>\r\n \t<li>Customize the settings relevant to the selected file format<\/li>\r\n \t<li>Click <strong>Next<\/strong><\/li>\r\n \t<li>In the <strong>Save As<\/strong> box, enter a descriptive file name<\/li>\r\n \t<li>In the <strong>Where <\/strong>drop-down menu, specify the location you would like the exported file to be saved<\/li>\r\n \t<li>Click <strong>Export <\/strong><\/li>\r\n<\/ol>\r\n<h3>PDF<\/h3>\r\nPDF documents are not always accessible. Accessible PDF documents are often called \u201cTagged PDF\u201d because they include \u201ctags\u201d that encode structural information required for accessibility. To evaluate the accessibility of your PDF document, see Technique 11 (above).\r\n<h4>To clean up your HTML file<\/h4>\r\n<ul>\r\n \t<li>Remove unnecessary styles, line breaks, etc.<\/li>\r\n \t<li>Remove unnecessary id, class, and attributes<\/li>\r\n \t<li>Remove font tags<\/li>\r\n \t<li>Remove styles in the &lt;head&gt; tag<\/li>\r\n \t<li>Ensure the &lt;th&gt; tags have a scope attribute<\/li>\r\n \t<li>Remove &lt;p&gt; tags nested inside &lt;th&gt; and &lt;td&gt; tags<\/li>\r\n \t<li>Check for accessibility (see <a href=\"#key11\">Technique 11<\/a>) <em>Note:<\/em> you may wish to use HTML editors or utilities to help with this process.<\/li>\r\n<\/ul>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Technique 13. Consider Using Accessibility Support Applications\/Plugins\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\n<em>Disclaimer:<\/em> This list is provided for information purposes only. It is not exhaustive and inclusion of an application or plug-in on the list does not constitute a recommendation or guarantee of results. The following accessibility related plug-ins and support are available for Keynote \u201809:\r\n<ul>\r\n \t<li>PowerTalk \u2013 an accessibility tool that provides a good approximation of how presentations will sound with a screen reader. [<strong>Editor's note:<\/strong> Tool no longer available.]<\/li>\r\n \t<li><a href=\"http:\/\/www.apple.com\/support\/keynote\/\" target=\"_blank\" rel=\"noopener noreferrer\">Keynote Support<\/a><\/li>\r\n<\/ul>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Accessibility Help\" title-tag=\"h2\" collapsed=\"yes\"]\r\nIf you are interested in what features are provided to make using Keynote \u201809 more accessible to users, documentation is provided in the Help system:\r\n<ol>\r\n \t<li>Go to menu item: <strong>Help<\/strong><\/li>\r\n \t<li>Enter your search term in the <strong>Search<\/strong> box<\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"References and Resources\" title-tag=\"h2\" collapsed=\"yes\"]\r\n<ol>\r\n \t<li><a href=\"https:\/\/support.apple.com\/en-ca\/guide\/keynote\/welcome\/mac\" target=\"_blank\" rel=\"noopener noreferrer\">Keynote User Guide for Mac <\/a><\/li>\r\n \t<li><a href=\"https:\/\/support.apple.com\/en-ca\/HT210563\" target=\"_blank\" rel=\"noopener noreferrer\">Apple: Create accessible presentations with Keynote<\/a><\/li>\r\n \t<li><a href=\"http:\/\/www.gawds.org\/show.php?contentid=28\" target=\"_blank\" rel=\"noopener noreferrer\">GAWDS Writing Better Alt Text<\/a><\/li>\r\n<\/ol>\r\n[\/rl_collapsible_section]\r\n\r\n[rl_collapsible_section title=\"Acknowledgments\" title-tag=\"h2\" collapsed=\"yes\"]\r\n\r\nThis document was produced as part of the <a href=\"https:\/\/adod.idrc.ocadu.ca\" target=\"_blank\" rel=\"noopener noreferrer\">Accessible Digital Office Document (ADOD) Project<\/a><a href=\"http:\/\/adod.idrc.ocad.ca\/\"><\/a>.\r\n\r\nThis project has been developed by the Inclusive Design Research Centre, OCAD University as part of an EnAbling Change Partnership project with the Government of Ontario and UNESCO (United Nations Educational, Scientific and Cultural Organization).\r\n<img src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/partners.png\" alt=\"Partner logos: UNESCO-United Nations Educational, Scientific and Cultural Organization, the Government of Ontario and the Inclusive Design Research Centre (OCAD University)\" width=\"626\" height=\"166\" \/>\r\n<a href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/deed.en_US\" rel=\"license\"><img src=\"https:\/\/i.creativecommons.org\/l\/by-sa\/3.0\/88x31.png\" alt=\"Creative Commons License\" \/><\/a>\r\n[\/rl_collapsible_section]\r\n\r\n<hr \/>\r\n\r\n<strong>Source:<\/strong> <a href=\"https:\/\/adod.idrc.ocadu.ca\/keynote.html\" target=\"_blank\" rel=\"noopener noreferrer\">Authoring Techniques for Accessible Office Documents: iWork Keynote '09<\/a> by the <a href=\"https:\/\/idrc.ocadu.ca\/\" target=\"_blank\" rel=\"noopener noreferrer\">Inclusive Design Research Centre (IDRC)<\/a> used under <a href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\" target=\"_blank\" rel=\"noopener noreferrer\">CC-BY-SA 3.0<\/a>.","rendered":"<div style=\"text-align: right\"><button class=\"rl-collapsible-section-toggle-button\">Expand \/ Collapse All<\/button><\/div>\n<div class=\"rl-collapsible-section \">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"true\">Usage Notes<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>At the time of testing (September 30, 2010), Keynote &#8217;09 lacks several features that enable accessible office document authoring, most notably: the ability to add alternative text to images and objects, indicating natural language, quick styles or named styles, and change tracking. As a result, some of the other features that might otherwise support accessibility, such as its extensive templates are not as effective. In addition, Keynote \u201809 does not include an accessibility checking feature, which is a more advanced accessibility feature.<\/p>\n<div class=\"textbox textbox--learning-objectives\">\n<div class=\"textbox__content\">\n<p><strong>Editor&#8217;s note:<\/strong> In later versions of Keynote, users can add alt text to images and objects. Apple has added significant accessibility improvements to its iWork applications, but an accessibility checker is not a feature yet.<\/p>\n<\/div>\n<\/div>\n<h3>What\u2019s an \u201cOffice Document\u201d?<\/h3>\n<p>You should use these techniques when you are using Keynote &#8217;09 to create documents that are:<\/p>\n<ul>\n<li><strong>Intended to be used by people <\/strong>(i.e., not computer code),<\/li>\n<li><strong>Text-based<\/strong> (i.e., not simply images, although they may contain images),<\/li>\n<li><strong>Fully printable <\/strong>(i.e., where dynamic features are limited to automatic page numbering, table of contents, etc. and do not include audio, video, or embedded interactivity)<strong>,<\/strong><\/li>\n<li><strong>Self-contained<\/strong> (i.e., without hyperlinks to other documents, unlike web content), and<\/li>\n<li><strong>Typical of office-style workflows <\/strong>(Reports, letters, memos, budgets, presentations, etc.).<\/li>\n<\/ul>\n<p><strong>If you are creating forms, web pages, applications, or other dynamic and\/or interactive content, these techniques will still be useful to you, but you should also consult the <\/strong><a href=\"http:\/\/www.w3.org\/WAI\/intro\/wcag.php\" target=\"_blank\" rel=\"noopener noreferrer\"><strong>W3C-WAI Web Content Accessibility Guidelines (WCAG 2.0)<\/strong><\/a><strong> because these are specifically designed to provide guidance for highly dynamic and\/or interactive content. <\/strong><\/p>\n<h3>File Formats<\/h3>\n<p>The default file format for Keynote \u201809 is the native <strong>iWork format<\/strong>. In addition, Keynote \u201809 offers many other presentation processor and web format saving options. Most of these have not been checked for accessibility, but some information and\/or instructions are available for the following formats in <a href=\"#key12\">Technique 12<\/a>:<\/p>\n<ul>\n<li>MS PowerPoint (PPT)<\/li>\n<li>PDF<\/li>\n<li>HTML<\/li>\n<\/ul>\n<h3>Document Conventions<\/h3>\n<p>We have tried to formulate these techniques so that they are useful to all authors, regardless of whether they use a mouse. However, for clarity there are several instances where mouse-only language is used. Below are the mouse-only terms and their keyboard alternatives:<\/p>\n<ul>\n<li><strong>*Right-click:<\/strong> To right-click with the keyboard, select the object using the Shift+Arrow keys and then press either (1) the \u201cRight-Click\u201d key (some keyboard have this to the right of the spacebar) or Shift+F10.<\/li>\n<\/ul>\n<h3>Disclaimer and Testing Details:<\/h3>\n<p><strong>Following these techniques will increase the accessibility of your documents, but it does not guarantee accessibility to any specific disability groups<\/strong>. In cases where more certainty is required, it is recommended that you test the office documents with end users with disabilities, including screen reader users. The application-specific steps and screenshots in this document were created using iWork Keynote \u201809 (ver.5.0.3(791), Mac OS X, Sept. 2010) and Keynote, version 9.1 (December 2019) while producing a document in the proprietary file format. Files are also easily saved as other file formats (see <a href=\"#key12\">Technique 12<\/a>).<\/p>\n<\/div>\n<\/div>\n<p><a id=\"key1\"><\/a><\/p>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 1. Use Accessible Templates<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>All office documents start with a template, which can be as simple as a blank standard-sized page or as complex as a nearly complete document with text, graphics and other content. For example, a \u201cMeeting Minutes\u201d template might include headings for information relevant to a business meeting, such as \u201cActions\u201d above a table with rows to denote time and columns for actions of the meeting. Because templates provide the starting-point for so many documents, accessibility is critical. If you are unsure whether a template is accessible, you should check a sample document produced when the template is used (see <a href=\"#key11\">Technique 11<\/a>). The default template for new documents in Keynote \u201809 is a blank presentation. If you are connected to the internet, you can access a variety of blank business presentation templates. These are all accessible by virtue of being blank. As well, you may create your own templates.<\/p>\n<h4>To create an accessible template<\/h4>\n<ol>\n<li>Go to menu item: <strong>File &gt; New<\/strong> or <strong>File &gt; New from Theme Chooser\u2026 <\/strong><\/li>\n<li>In the <strong>Theme Chooser<\/strong> dialog, select the <strong>White <\/strong>theme or select one of the other existing template designs<\/li>\n<li>A new document in your selected template style will open<\/li>\n<li>Ensure that you follow the techniques in this document<\/li>\n<li>When you are finished you should also check the accessibility of the document (see <a href=\"#key11\">Technique 11<\/a>)<\/li>\n<li>Go to menu item: <strong>File &gt; Save Theme\u2026<\/strong><\/li>\n<li>In the <strong>Save As<\/strong> box, type a name for the template. Using a descriptive template name (e.g. \u201cAccessible Memo Template\u201d) will increase the prominence of the accessibility status.<\/li>\n<li>Specify a folder in which to save your template. <em>Note:<\/em> By default, it will be saved in your home folder in Library\/Application Support\/iWork\/Keynote\/Templates\/My Templates pane of the <strong>Template Chooser<\/strong>. To save the template in a different location than the default, create a new folder in the <strong>Templates <\/strong>folder. The folder name is then used as a template category in the <strong>Template Chooser.<\/strong><br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_1.png\" alt=\"Image demonstrates location of Save As box and Where option.\" width=\"335\" height=\"104\" \/><\/li>\n<li>Click <strong>Save <\/strong><\/li>\n<\/ol>\n<h4>To select an accessible template<\/h4>\n<p><em>Note:<\/em> Only use these steps if you have an accessible template available (e.g. that you previously saved). Otherwise, simply open a new (blank) document.<\/p>\n<ol>\n<li>Go to menu item: <strong>File &gt; New from Theme Chooser\u2026<\/strong><\/li>\n<li>In the <strong>Template Chooser<\/strong> dialog, select <strong>My Templates<\/strong> from the left pane<\/li>\n<li>Select your accessible template and click <strong><strong>Choose<br \/>\n<\/strong><\/strong><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_2.png\" alt=\"Image demonstrates location of My template option and template icons in Template Chooser dialog.\" width=\"223\" height=\"221\" \/><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 2. Set Document Language<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>At this time, it is not possible to manually indicate the natural language for specific slides or sections of text in Keynote \u201809. As well, it is not possible to change the natural language of the document itself from the default language. <strong>[Tested: September 30th, 2010]<\/strong><\/p>\n<div class=\"textbox textbox--learning-objectives\">\n<div class=\"textbox__content\">\n<p><strong>Editor&#8217;s note:<\/strong> In later versions of Keynote, users are able to set a presentation&#8217;s language.<\/p>\n<ol>\n<li>Choose File &gt; Advanced &gt; Language &amp; Region (from the File menu at the top of your screen).<\/li>\n<li>In the dialog that appears, click the pop-up menus and choose a language and a region.<br \/>\n<em style=\"text-align: initial;font-size: 1em\">Note:<\/em><span style=\"text-align: initial;font-size: 1em\"> You can\u2019t change this setting for a shared presentation.<\/span><\/li>\n<li><span style=\"text-align: initial;font-size: 1em\">Click OK.<\/span><\/li>\n<\/ol>\n<p>For more details, see <a href=\"https:\/\/support.apple.com\/kb\/PH28043\" target=\"_blank\" rel=\"noopener noreferrer\">how to change a presentation\u2019s language and formatting<\/a>.<\/p>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<p>In order for assistive technologies (e.g., screen readers) to be able to present your document accurately, it is important to indicate the natural language of the document. If a different natural language is used for a paragraph or selected text, this also needs to be clearly indicated.\n<\/p><\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 3. Use Built-In Layout and Styling Features<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<h3>3.1 Use Built-In Slide Layouts<\/h3>\n<p>Instead of creating each slide in your presentation by starting from a blank slide, check whether there is a suitable built-in layout. <em>Note:<\/em> The built-in layouts can be more accessible to users of assistive technologies because they technologies sometimes read the floating items on the slide in the order that they were placed on the slide. The built-in layouts have usually taken this into account (e.g., \u201cTitle\u201d first followed by other items, left to right and from top to bottom). If you create slide layouts from scratch, it is sometimes difficult to keep track of the order elements were placed. <em>Note:<\/em> Each slide in Keynote \u201909 is derived from a Master Slide (<a href=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/chapter\/openoffice-impress#tech3.1\">Technique 3.2<\/a>) applying \u201ctrue layouts\u201d requires that you use Master Slides that are accessible and appropriately designed for your purposes.<\/p>\n<h3><a id=\"key3.2\"><\/a>3.2 Customize Using Master Slides<\/h3>\n<p>If a layout must be customized, it is recommended that Master Slides be used. Every slide layout in a presentation is defined by its master slide. A master slide determines the formatting style for various elements of the slide layout. This includes font styles, character formatting, and the positioning of elements. Essentially, each master slide acts as a design template for the slide layout. If you edit any aspect of the slide layout in the master slide, the change will affect all slides that were created based on it. For this reason, it is good practice to edit the master slide and use the slide layouts before building individual slides. It is essential that you create and use master slides that meet the accessibility requirements outlined in this document.<\/p>\n<h4>To create or customize a master slide<\/h4>\n<ol>\n<li>Select the slide Note: To design a master slide from scratch, select a blank slide to start with. Otherwise, select a slide that resembles how you would like your slide to look and be sure to modify the slide characteristics to align with accessibility guidelines in this document.<\/li>\n<li>Go to menu item: <strong>View &gt; Show Master Slides<\/strong><\/li>\n<li>In the <strong>Master Slide Navigator<\/strong> in the left pane, select the <strong>Master Slide Layout<\/strong> you would like to modify<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_3.png\" alt=\"Image demonstrates location of Master Slide Layouts in Master Slides view.\" width=\"216\" height=\"298\" \/><\/li>\n<li>Customize the master slide to suit your needs (e.g., define placeholders for text, change background elements, add alignment guides, and more) ensuring that your changes meet accessibility requirements<\/li>\n<\/ol>\n<h4>To define default attributes of text and objects<\/h4>\n<ol>\n<li>Select the slide Note: To design a master slide from scratch, select a blank slide to start with. Otherwise, select a slide that resembles how you would like your slide to look and be sure to modify the slide characteristics to align with accessibility guidelines in this document.<\/li>\n<li>Go to menu item: <strong>View &gt; Show Master Slides<\/strong><\/li>\n<li>In the <strong>Master Slide Navigator<\/strong> in the left pane, select the <strong>Master Slide Layout<\/strong> you would like to define default attributes for<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_4.png\" alt=\"Image demonstrates location of Master Slide Layouts in Master Slides view.\" width=\"216\" height=\"298\" \/><\/li>\n<li>In the <strong>Toolbar<\/strong>, click the element type (e.g., text box, shapes, table, charts)<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_5.png\" alt=\"Image demonstrates elements type options in the Toolbar.\" width=\"247\" height=\"48\" \/><\/li>\n<li>In the <strong>Formatting<\/strong> bar, format the element ensuring that it meets accessibility guidelines outlined in this document<\/li>\n<li>To make the element a default for your current master slide, go to menu item: <strong>Format &gt; Advanced &gt; Define (element type) for Current Master <\/strong>Note: To make the element a default for all master slides, go to menu item: <strong>Format &gt; Advanced &gt; Define (element type) for All Masters<\/strong><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<p><a id=\"key4\"><\/a><\/p>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 4. Set a Logical Tab Order<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>Many presentation applications create content composed almost exclusively of &#8220;floating&#8221; objects. This means that they avoid the transitions between in-line content and secondary &#8220;floating&#8221; objects (text boxes, images, etc.) that can cause accessibility issues in word processors. However, when you are working with &#8220;floating&#8221; objects, it is important to remember that the way objects are positioned in two dimensions on the screen may be completely different from how the objects will be read by a screen reader or navigated using a keyboard. The order that content is navigated sequentially is called the &#8220;Tab Order&#8221; because often the &#8220;Tab&#8221; key is used to navigate from one &#8220;floating&#8221; object to the next.<\/p>\n<div class=\"textbox shaded\">\n<h4>Tips for setting a logical \u201ctab order\u201d for &#8220;floating&#8221; objects<\/h4>\n<ul>\n<li>The tab order of floating objects is usually from the \u201clowest\u201d object on the slide to the \u201chighest\u201d.<\/li>\n<li>Because objects automatically appear \u201con top\u201d when they are inserted, the default tab order is from the first object inserted to the last. However, this will change if you use features such as \u201cbring to front\u201d and \u201csend to back\u201d.<\/li>\n<li>The slide\u2019s main heading should be first in the tab order.<\/li>\n<li>Headings should be placed in the tab order immediately before the items (text, diagrams, etc.) for which they are acting as a heading.<\/li>\n<li>Labels should be in the reading order placed immediately before the objects that they label.<\/li>\n<li>For simple slide layouts, it may be possible to simply insert objects in a logical tab order.<\/li>\n<li>For more complex layouts, it may be easier to simply to create the slide as usual and then set the tab order (see below).<\/li>\n<\/ul>\n<\/div>\n<h4>To set the tab order<\/h4>\n<ol>\n<li>Select the object<\/li>\n<li>Go to menu item: <strong>Arrange &gt; Bring Forward<\/strong>, <strong>Bring to Front<\/strong>, <strong>Send Backward<\/strong> or <strong>Send to Back<\/strong><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 5. Use Slide Notes<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>A useful aspect of presentation applications is the facility to add notes to slides, which can then be read by assistive technologies. You can use these slide notes to explain and expand on the contents of your slides in text format. Slide notes can be created as you build your presentation.<\/p>\n<h4>To add notes to your slides<\/h4>\n<ol>\n<li>Go to menu item: <strong>View &gt; Show Presenter Notes<\/strong><\/li>\n<li>In the pane at the bottom of the window (below the slide), enter notes to accompany each slide<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 6. Provide Text Alternatives for Images and Graphical Objects<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>At this time, Keynote \u201909 does not offer a mechanism which enables the user to add alternative text descriptions to images or objects. <strong>[Tested: September 28, 2010]<\/strong><\/p>\n<div class=\"textbox textbox--learning-objectives\">\n<div class=\"textbox__content\">\n<p><strong>Editor&#8217;s note: <\/strong>For later versions of Keynote, users can add alternative text descriptions for images and objects.<\/p>\n<ol>\n<li>Select the image and go to the <strong>Format<\/strong> side bar. Click on the image tab.<\/li>\n<li>Click the <strong>Description<\/strong> text box, then enter your text.<\/li>\n<\/ol>\n<p>For more details, see the section on <a href=\"https:\/\/support.apple.com\/en-ca\/guide\/keynote\/tan77aea6844\/mac\" target=\"_blank\" rel=\"noopener noreferrer\">how to add an image description<\/a> on the Keynote User Guide for Mac.<\/p>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<p>When using images or other graphical objects, such as charts and graphs, it is important to ensure that the information you intend to convey by the image is also conveyed to people who cannot see the image. This can be accomplished by adding concise alternative text of each image. If an image is too complicated to concisely describe in the alternative text alone (artwork, flowcharts, etc.), provide a short text alternative and a longer description as well.<\/p>\n<div class=\"textbox shaded\">\n<h4>Tips for writing alternative text<\/h4>\n<ul>\n<li>Try to answer the question &#8220;what information is the image conveying?&#8221;<\/li>\n<li>If the image does not convey any useful information, leave the alternative text blank<\/li>\n<li>If the image contains meaningful text, ensure all of the text is replicated<\/li>\n<li>Alternative text should be fairly short, usually a sentence or less and rarely more than two sentences<\/li>\n<li>If more description is required (e.g., for a chart or graph), provide a short description in the alternative text (e.g., a summary of the trend) and more detail in the long description, see below<\/li>\n<li>Test by having others review the document with the images replaced by the alternative text<\/li>\n<\/ul>\n<\/div>\n<div class=\"textbox shaded\">\n<h4>Tips for writing longer descriptions<\/h4>\n<ul>\n<li>Long descriptions should be used when text alternatives (see above) are insufficient to answer the question &#8220;what information is the image conveying?&#8221;<\/li>\n<li>In some situations, the information being conveyed will be how an image looks (e.g., an artwork, architectural detail, etc.). In these cases, try to describe the image without making too many of your own assumptions.<\/li>\n<li>One approach is to imagine you are describing the image to a person over the phone<\/li>\n<li>Ensure that you still provide concise alternative text to help readers decide if they are interested in the longer description<\/li>\n<\/ul>\n<p>Alternatively, you can include the same information conveyed by the image within the body of the document, providing the images as an alternate to the text. In that case, you do not have to provide alternate text within the image.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 7. Use Built-In Structuring Features<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<h3>7.1 Tables<\/h3>\n<p>When using tables, it is important to ensure that they are clear and appropriately structured. This helps all users to better understand the information in the table and allows assistive technologies (e.g., screen readers) to provide context so that the information within the table can be conveyed in a meaningful way.<\/p>\n<div class=\"textbox shaded\">\n<h4>Tips for tables<\/h4>\n<ul>\n<li>Only use tables for tabular information, not for formatting.<\/li>\n<li>Use \u201creal tables\u201d rather than text formatted to look like tables using the TAB key or space bar. These will not be recognized by assistive technology.<\/li>\n<li>Keep tables simple by avoiding merged cells and dividing complex data sets into separate smaller tables, where possible.<\/li>\n<li>If tables split across pages, set the header to show at the top of each page. Also set the table to break between rows instead of in the middle of rows.<\/li>\n<li>Create a text summary of the essential table contents. Any abbreviations used should be explained in the summary.<\/li>\n<li>Table captions or descriptions should answer the question &#8220;what is the table&#8217;s purpose and how is it organized?&#8221; (e.g., &#8220;A sample order form with separate columns for the item name, price and quantity&#8221;).<\/li>\n<li>Table cells should be marked as table headers when they serve as labels to help interpret the other cells in the table.<\/li>\n<li>Table header cells labels should be concise and clear.<\/li>\n<li>Ensure the table is not \u201cfloating\u201d on the page (see <a href=\"#key4\">Technique 4<\/a>).<\/li>\n<\/ul>\n<\/div>\n<h4>To set default table attributes<\/h4>\n<ol>\n<li style=\"list-style-type: none\">\n<ol>\n<li>Go to menu item: <strong>View &gt; Show Master Slides<\/strong><\/li>\n<li>Select a master slide from the <strong>Master Slides Navigator<\/strong> in the left pane<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_6.png\" alt=\"Image demonstrates location of master slide layouts in Master Slides view.\" style=\"text-align: initial;font-size: 1em\" width=\"216\" height=\"298\" \/><\/li>\n<li>In the <strong>Toolbar<\/strong>, click <strong>Table<br \/>\n<\/strong><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_7.png\" alt=\"Image demonstrates location of table element in Toolbar.\" style=\"text-align: initial;font-size: 1em\" width=\"280\" height=\"57\" \/><\/li>\n<li>Select the table<\/li>\n<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\n<li>In the <strong>Inspector<\/strong> dialog, select <strong>Table inspector<\/strong><\/li>\n<li>Click the <strong>Table<\/strong> tab<\/li>\n<li>In the <strong>Headers &amp; Footers<\/strong> section, select <strong>Choose the number of header columns<\/strong> or <strong>Choose the number of header rows<\/strong> drop-down menus<\/li>\n<li>Select the number of headers<br \/>\n<em>Note:<\/em> Limiting your table to one row or column of header will ensure your table remains clear and easy to interpret by assistive technologies.<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_8.png\" alt=\"Image demonstrates Table icon, Table tab, and Headers &amp; Footer section in Inspector dialog.\" style=\"text-align: initial;font-size: 1em\" width=\"236\" height=\"169\" \/><\/li>\n<li>Customize the other characteristics of your table through the other sections of the <strong>Table inspector<\/strong> dialog<\/li>\n<li>To make the table a default for your current master slide, go to menu item: <strong>Format &gt; Advanced &gt; Define Table for Current Master<br \/>\n<\/strong><em>Note:<\/em> To make the table a default for all master slides, go to menu item: <strong style=\"text-align: initial;font-size: 1em\">Format &gt; Advanced &gt; Define Table for All Masters<\/strong><span style=\"text-align: initial;font-size: 1em\"> Note: Defining the table as a default for all masters means that when you insert a Table element into any slide, it will display your preformatted characteristics (including appropriate headers)<\/span><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<h3>7.2 Lists<\/h3>\n<p>When you create lists, it is important to format them as \u201creal lists\u201d. Otherwise, assistive technologies will interpret your list as a series of short separate paragraphs instead of a coherent list of related items.<\/p>\n<h4>To create an ordered or unordered list<\/h4>\n<ol>\n<li>Select the text box or highlight the text<\/li>\n<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\n<li>In the <strong>Inspector <\/strong>dialog, click <strong>Text inspector<\/strong><\/li>\n<li>Click the <strong>Bullets <\/strong>tab<\/li>\n<li>In the <strong>Bullets &amp; Numbering<\/strong> section, click the drop-down menu and choose a bullet or numbering option<\/li>\n<li>Customize the list style accordingly, ensuring your selections align with the guidelines in this document<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_9.png\" alt=\"Image demonstrates location of Text inspector button, Bullets tab, and Bullets &amp; Numbering section of Inspector dialog.\" width=\"173\" height=\"115\" \/><\/li>\n<\/ol>\n<h3>7.3 Columns<\/h3>\n<p>Use Columns feature for placing text in columns. <em>Note:<\/em> Because columns can be a challenge for users of some assistive technologies, consider whether a column layout is really necessary.<\/p>\n<h3>7.4 Document Title<\/h3>\n<p>In case the document is ever converted into HTML, it should be given a descriptive and meaningful title.<\/p>\n<h4>To change the title of the current document<\/h4>\n<ol>\n<li>In the <strong>Toolbar<\/strong>, select <strong>Inspector<\/strong><\/li>\n<li>In the <strong>Inspector<\/strong> dialog, select the <strong>Document inspector<\/strong> button<\/li>\n<li>Click the <strong>Spotlight <\/strong>tab<\/li>\n<li>In the <strong>Title<\/strong> box, type a descriptive name for the document <em>Note:<\/em> The <strong>Title<\/strong> defined in the properties is different than the file name. It is also unrelated to the template name, discussed above.<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_10.png\" alt=\"Image demonstrates location of Document inspector button, Spotlight tab, and Title text box in Inspector dialog.\" width=\"167\" height=\"215\" \/><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 8. Create Accessible Charts<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>Charts can be used to make data more understandable for some audiences. However, it is important to ensure that your chart is as accessible as possible to all members of your audience. All basic accessibility considerations that are applied to the rest of your document must also be applied to your charts and the elements within your charts. For example, use shape and color, rather than color alone, to convey information. As well, some further steps should be taken to ensure that the contents are your chart are appropriate labeled to give users reference points that will help them to correctly interpret the information.<\/p>\n<h4>To create a chart<\/h4>\n<ol>\n<li>Go to menu item: <strong>Insert &gt; Chart<\/strong><\/li>\n<li>Select the type of chart you want to use<\/li>\n<li>Update the <strong>Chart Data Editor<\/strong> with the data you would like to display<\/li>\n<li>Close the <strong>Chart Data Editor<\/strong><\/li>\n<\/ol>\n<h4>To add titles and labels<\/h4>\n<ol>\n<li>Select the chart<\/li>\n<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\n<li>In the <strong>Chart Inspector<\/strong>, select <strong>Chart<\/strong><\/li>\n<li>Ensure the <strong>Show Title<\/strong> and <strong>Show Legend<\/strong> check boxes are selected<\/li>\n<li>Select <strong>Axis<\/strong><\/li>\n<li>Under <strong>Value Axis (Y)<\/strong> and <strong>Category Axis (X)<\/strong>, select <strong>Show Title<\/strong> and <strong>Show Value Labels<\/strong> from their respective drop-down menus<\/li>\n<\/ol>\n<h4>To change to a different predefined Chart Type<\/h4>\n<ol>\n<li>Select the chart<\/li>\n<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\n<li>Select a chart type from the <strong>Choose a chart type<\/strong> drop-down menu<\/li>\n<\/ol>\n<h3>Other Chart Considerations<\/h3>\n<ul>\n<li>When creating line charts, use the formatting options to create different types of dotted lines to facilitate legibility for users who are color blind<\/li>\n<li>When creating bar charts, it is helpful to apply texture instead of color to differentiate the bars<\/li>\n<li>Change the default colors to a color safe or gray-scale palette<\/li>\n<li>Use the formatting options to change predefined colors, ensuring that they align with sufficient contrast requirements (see <a href=\"#key92\">Technique 9.2<\/a>)<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 9. Make Content Easier to See<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<h3>9.1 Format of Text<\/h3>\n<p>When formatting text, especially when the text is likely to be printed, try to:<\/p>\n<ul type=\"disc\">\n<li>Use font sizes between 12 and 18 points for body text.<\/li>\n<li>Use fonts of normal weight, rather than bold or light weight fonts. If you do choose to use bold fonts for emphasis, use them sparingly.<\/li>\n<li>Use standard fonts with clear spacing and easily recognized upper and lower case characters. Sans serif fonts (e.g., Arial, Verdana) may sometimes be easier to read than serif fonts (e.g., Times New Roman, Garamond).<\/li>\n<li>Avoid large amounts of text set all in caps, italic or underlined.<\/li>\n<li>Use normal or expanded character spacing, rather than condensed spacing.<\/li>\n<li>Avoid animated or scrolling text.<\/li>\n<\/ul>\n<p><strong>But can\u2019t users just zoom in?<\/strong> Office applications do typically include accessibility features such as the ability to magnify documents and support for high contrast modes. However, because printing is an important aspect of many workflows and changing font sizes directly will change documents details such the pagination, the layout of tables, etc., it is best practice to always format text for a reasonable degree of accessibility.<\/p>\n<h3><a id=\"key92\"><\/a>9.2 Use Sufficient Contrast<\/h3>\n<p>The visual presentation of text and images of text should have a contrast ration of at least 4.5:1. To help you determine the contrast, here are some examples on a white background:<\/p>\n<ul type=\"disc\">\n<li>Very good contrast (Foreground=black, Background=white, Ratio=21:1)<\/li>\n<li>Acceptable contrast (Foreground=#767676, Background=white, Ratio=4.54:1)<\/li>\n<li>Unacceptable contrast (Foreground=#AAAAAA, Background=white, Ratio=2.32:1)<\/li>\n<\/ul>\n<p>Also, always use a single solid color for a text background rather than a pattern. In order to determine whether the colors in your document have sufficient contrast, you can consult an online contrast checker, such as:<\/p>\n<ul>\n<li><a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\" target=\"_blank\" rel=\"noopener noreferrer\">WebAIM: Contrast Checker<\/a><\/li>\n<li><a href=\"http:\/\/juicystudio.com\/services\/luminositycontrastratio.php\" target=\"_blank\" rel=\"noopener noreferrer\">Juicy Studio: Luminosity Color Contrast Ratio Analyzer<\/a><\/li>\n<li><a href=\"http:\/\/www.joedolson.com\/color-contrast-tester.php\" target=\"_blank\" rel=\"noopener noreferrer\">Joe Dolson Color Contrast Spectrum Tester<\/a><\/li>\n<li><a href=\"http:\/\/www.joedolson.com\/color-contrast-compare.php\" target=\"_blank\" rel=\"noopener noreferrer\">Joe Dolson Color Contrast Comparison<\/a><\/li>\n<\/ul>\n<h3>9.3 Avoid Using Color Alone<\/h3>\n<p>Color should not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. In order to spot where color might be the only visual means of conveying information, you can create a screenshot of the document and then view it with online gray-scale converting tools, such as:<\/p>\n<ul>\n<li>GrayBit v2.0: Grayscale Conversion Contrast Accessibility Tool<\/li>\n<\/ul>\n<div class=\"textbox textbox--learning-objectives\">\n<div class=\"textbox__content\">\n<p><strong>Editor&#8217;s note: <\/strong>GrayBit v2.0 is no longer available. However, multiple tools can be found online: <a href=\"https:\/\/www.google.com\/search?q=convert+image+to+grayscale+online\" target=\"_blank\" rel=\"noopener noreferrer\">Google Search: gray-scale conversion tool<\/a>.<\/p>\n<\/div>\n<\/div>\n<h3>9.4 Avoid Relying on Sensory Characteristics<\/h3>\n<p>The instructions provided for understanding and operating content should not rely solely on sensory characteristics such as the color or shape of content elements. Here are two examples:<\/p>\n<ul type=\"disc\">\n<li>Do not track changes by simply changing the color of text you have edited and noting the color. Instead use PowerPoint 2010\u2019s \u201cTrack Changes\u201d feature to track changes.<\/li>\n<li>Do not distinguish between images by referring to their appearance (e.g., \u201cthe bigger one\u201d). Instead, label each image with a figure number and use that for references.<\/li>\n<\/ul>\n<h3>9.5 Avoid Using Images of Text<\/h3>\n<p>Before you use an image to control the presentation of text (e.g., to ensure a certain font or color combination), consider whether you can achieve the same result by styling \u201creal text\u201d. If this is not possible, as with logos containing stylized text, make sure to provide alternative text for the image following the techniques noted above.<\/p>\n<h3>9.6 Avoid Transitions<\/h3>\n<p>Transitions between slides and elements in each slide (e.g., bullets in a list flying onto the screen) can be distracting to users with disabilities. It can also cause assistive technologies to read the slide incorrectly. For these reasons, it is best to avoid transitions altogether.\n<\/p><\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 10. Make Content Easier to Understand<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<h3>10.1 Write Clearly<\/h3>\n<p>By taking the time to design your content in a consistent way, it will be easier to access, navigate and interpret for all users:<\/p>\n<ul type=\"disc\">\n<li>Whenever possible, write clearly with short sentences.<\/li>\n<li>Introduce acronyms and spell out abbreviations.<\/li>\n<li>Avoid making the document too \u201cbusy\u201d by using lots of whitespace and by avoiding too many different colors, fonts and images.<\/li>\n<li>If content is repeated on multiple pages within a document or within a set of documents (e.g., headings, footings, etc.), it should occur consistently each time it is repeated.<\/li>\n<\/ul>\n<h3>10.2 Provide Context for Hyperlinks<\/h3>\n<p>Hyperlink text in your document should be meaningful when read out of context. To be an effective navigation aid, the link text should describe the destination of the link.<\/p>\n<p>Consider the experience of screen reader users: Generally, screen readers generate a list of links, and screen reader users navigate this list alphabetically. Hyperlink text such as &#8220;click here&#8221; or &#8220;more&#8221; is meaningless in this context.<\/p>\n<p>In order to be useful to someone using a screen reader, ensure that hyperlink text is self-describing and meaningful on its own. To make the address of hyperlink clear when printing, you may wish to include the address in brackets following the descriptive text of the hyperlink.<\/p>\n<h4>To edit hyperlink text<\/h4>\n<ol>\n<li>Enter the hyperlink<\/li>\n<li>Go to menu item: <strong>View &gt; Show Inspector<\/strong><\/li>\n<li>In the <strong>Inspector<\/strong> dialog, click <strong>Hyperlink inspector<\/strong><\/li>\n<li>In the <strong>Display<\/strong> box, enter the text you would like to display<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/Keynote09_11.png\" alt=\"Image demonstrates location of Hyperlink inspector button and Display text box in Inspector dialog.\" width=\"187\" height=\"139\" \/><\/li>\n<\/ol>\n<h3>10.3 Accessible Presentations<\/h3>\n<p>It is important to consider accessibility before, during, and after presentations. Below is a helpful link with guidance on how to make presentations accessible to all:<\/p>\n<ul>\n<li>\u201cHow to Make Presentations Accessible to All\u201d <a href=\"http:\/\/www.w3.org\/WAI\/training\/accessible\" target=\"_blank\" rel=\"noopener noreferrer\">(Source: W3C-WAI Draft)<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n<p><a id=\"key11\"><\/a><\/p>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 11. Check Accessibility<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\nAt this time, Keynote \u201909 does not offer a mechanism to check for potential accessibility errors in your document prior to publishing. <strong>[Tested: September 30th, 2010]<\/strong> In order to get some indication of the accessibility of your document or template (see <a href=\"#key1\">Technique 1<\/a>), then you may consider saving the file into HTML or PDF in order to perform an accessibility check in one of those formats, as described below.<\/p>\n<h4>To evaluate HTML accessibility<\/h4>\n<p>If you wish to check the accessibility of your document or template (see <a href=\"#key1\">Technique 1<\/a>), one option is to save it into HTML format and use one of the web accessibility checkers available online. Such as:<\/p>\n<ul>\n<li><a href=\"https:\/\/achecker.achecks.ca\/checker\/index.php\" target=\"_blank\" rel=\"noopener noreferrer\">AChecker<\/a><\/li>\n<li><a href=\"http:\/\/wave.webaim.org\/\" target=\"_blank\" rel=\"noopener noreferrer\">WebAIM Wave Web Accessibility Evaluation Tool<\/a><\/li>\n<\/ul>\n<h4>To evaluate PDF accessibility<\/h4>\n<p>If you saved your document in tagged PDF format, you can use the following tools and steps to evaluate the accessibility of the PDF document:<\/p>\n<ul>\n<li><a href=\"https:\/\/acrobat.adobe.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">Adobe Acrobat Professional<\/a><\/li>\n<li><a href=\"https:\/\/commonlook.com\/accessibility-software\/pdf-validator\/\" target=\"_blank\" rel=\"noopener noreferrer\">CommonLook PDF Evaluator<\/a><\/li>\n<li><a href=\"https:\/\/www.access-for-all.ch\/en\/pdf-lab\/pdf-accessibility-checker-pac.html\" target=\"_blank\" rel=\"noopener noreferrer\">PDF Accessibility Checker (PAC)<\/a> \u2013 a free alternative provided by \u201cAccess for all\u201d<\/li>\n<\/ul>\n<h4>To evaluate PDF accessibility in Adobe Acrobat Professional<\/h4>\n<ol>\n<li>Go to menu item: <strong>Advanced &gt; Accessibility &gt; Full Check\u2026<\/strong><\/li>\n<li>In the <strong>Full Check<\/strong> dialog, select all the checking option<\/li>\n<li>Select the <strong>Start Checking<\/strong> button<\/li>\n<\/ol>\n<div class=\"textbox textbox--learning-objectives\">\n<div class=\"textbox__content\">\n<p><strong>Editor&#8217;s note: <\/strong>For detailed instructions, see our section on <a href=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/chapter\/adobe-acrobat-11-pro-and-dc\/\" target=\"_blank\" rel=\"noopener noreferrer\">how to check accessibility using Adobe Acrobat Professional<\/a>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p><a id=\"key12\"><\/a><\/p>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 12. Use Accessibility Features when Saving\/Exporting to Other Formats<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>In some cases, additional steps must be taken in order to ensure accessibility information is preserved when saving\/exporting to formats other than the default.<\/p>\n<h4>To export to a different format<\/h4>\n<ol>\n<li>Go to menu item: <strong>Share &gt; Export<\/strong><\/li>\n<li>Select the file format you would like to export<\/li>\n<li>Customize the settings relevant to the selected file format<\/li>\n<li>Click <strong>Next<\/strong><\/li>\n<li>In the <strong>Save As<\/strong> box, enter a descriptive file name<\/li>\n<li>In the <strong>Where <\/strong>drop-down menu, specify the location you would like the exported file to be saved<\/li>\n<li>Click <strong>Export <\/strong><\/li>\n<\/ol>\n<h3>PDF<\/h3>\n<p>PDF documents are not always accessible. Accessible PDF documents are often called \u201cTagged PDF\u201d because they include \u201ctags\u201d that encode structural information required for accessibility. To evaluate the accessibility of your PDF document, see Technique 11 (above).<\/p>\n<h4>To clean up your HTML file<\/h4>\n<ul>\n<li>Remove unnecessary styles, line breaks, etc.<\/li>\n<li>Remove unnecessary id, class, and attributes<\/li>\n<li>Remove font tags<\/li>\n<li>Remove styles in the &lt;head&gt; tag<\/li>\n<li>Ensure the &lt;th&gt; tags have a scope attribute<\/li>\n<li>Remove &lt;p&gt; tags nested inside &lt;th&gt; and &lt;td&gt; tags<\/li>\n<li>Check for accessibility (see <a href=\"#key11\">Technique 11<\/a>) <em>Note:<\/em> you may wish to use HTML editors or utilities to help with this process.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Technique 13. Consider Using Accessibility Support Applications\/Plugins<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p><em>Disclaimer:<\/em> This list is provided for information purposes only. It is not exhaustive and inclusion of an application or plug-in on the list does not constitute a recommendation or guarantee of results. The following accessibility related plug-ins and support are available for Keynote \u201809:<\/p>\n<ul>\n<li>PowerTalk \u2013 an accessibility tool that provides a good approximation of how presentations will sound with a screen reader. [<strong>Editor&#8217;s note:<\/strong> Tool no longer available.]<\/li>\n<li><a href=\"http:\/\/www.apple.com\/support\/keynote\/\" target=\"_blank\" rel=\"noopener noreferrer\">Keynote Support<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Accessibility Help<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\nIf you are interested in what features are provided to make using Keynote \u201809 more accessible to users, documentation is provided in the Help system:<\/p>\n<ol>\n<li>Go to menu item: <strong>Help<\/strong><\/li>\n<li>Enter your search term in the <strong>Search<\/strong> box<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">References and Resources<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<ol>\n<li><a href=\"https:\/\/support.apple.com\/en-ca\/guide\/keynote\/welcome\/mac\" target=\"_blank\" rel=\"noopener noreferrer\">Keynote User Guide for Mac <\/a><\/li>\n<li><a href=\"https:\/\/support.apple.com\/en-ca\/HT210563\" target=\"_blank\" rel=\"noopener noreferrer\">Apple: Create accessible presentations with Keynote<\/a><\/li>\n<li><a href=\"http:\/\/www.gawds.org\/show.php?contentid=28\" target=\"_blank\" rel=\"noopener noreferrer\">GAWDS Writing Better Alt Text<\/a><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<div class=\"rl-collapsible-section rl-collapsed\">\n<h2 class=\"rl-collapsible-section-title\"><button aria-expanded=\"false\">Acknowledgments<span class=\"rl-collapsible-section-button-indicator\"><\/span><\/button><\/h2>\n<div class=\"rl-collapsible-section-content\">\n<p>This document was produced as part of the <a href=\"https:\/\/adod.idrc.ocadu.ca\" target=\"_blank\" rel=\"noopener noreferrer\">Accessible Digital Office Document (ADOD) Project<\/a><a href=\"http:\/\/adod.idrc.ocad.ca\/\"><\/a>.<\/p>\n<p>This project has been developed by the Inclusive Design Research Centre, OCAD University as part of an EnAbling Change Partnership project with the Government of Ontario and UNESCO (United Nations Educational, Scientific and Cultural Organization).<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/pressbooks.library.ryerson.ca\/docs\/wp-content\/uploads\/sites\/78\/2019\/08\/partners.png\" alt=\"Partner logos: UNESCO-United Nations Educational, Scientific and Cultural Organization, the Government of Ontario and the Inclusive Design Research Centre (OCAD University)\" width=\"626\" height=\"166\" \/><br \/>\n<a href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/deed.en_US\" rel=\"license\"><img decoding=\"async\" src=\"https:\/\/i.creativecommons.org\/l\/by-sa\/3.0\/88x31.png\" alt=\"Creative Commons License\" \/><\/a>\n<\/div>\n<\/div>\n<hr \/>\n<p><strong>Source:<\/strong> <a href=\"https:\/\/adod.idrc.ocadu.ca\/keynote.html\" target=\"_blank\" rel=\"noopener noreferrer\">Authoring Techniques for Accessible Office Documents: iWork Keynote &#8217;09<\/a> by the <a href=\"https:\/\/idrc.ocadu.ca\/\" target=\"_blank\" rel=\"noopener noreferrer\">Inclusive Design Research Centre (IDRC)<\/a> used under <a href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\" target=\"_blank\" rel=\"noopener noreferrer\">CC-BY-SA 3.0<\/a>.<\/p>\n","protected":false},"author":100,"menu_order":5,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-120","chapter","type-chapter","status-publish","hentry"],"part":60,"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/chapters\/120","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/wp\/v2\/users\/100"}],"version-history":[{"count":46,"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/chapters\/120\/revisions"}],"predecessor-version":[{"id":2327,"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/chapters\/120\/revisions\/2327"}],"part":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/parts\/60"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/chapters\/120\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/wp\/v2\/media?parent=120"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/pressbooks\/v2\/chapter-type?post=120"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/wp\/v2\/contributor?post=120"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/docs\/wp-json\/wp\/v2\/license?post=120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}