{"id":788,"date":"2019-01-10T21:09:47","date_gmt":"2019-01-10T21:09:47","guid":{"rendered":"https:\/\/pressbooks.library.ryerson.ca\/wafd\/?post_type=back-matter&p=788"},"modified":"2022-12-16T17:23:51","modified_gmt":"2022-12-16T17:23:51","slug":"answer-key-self-tests","status":"publish","type":"back-matter","link":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/back-matter\/answer-key-self-tests\/","title":{"raw":"Answer Key: Self-Tests","rendered":"Answer Key: Self-Tests"},"content":{"raw":"

<\/a>Self-Test 1<\/h2>\r\n1.<\/strong> What options are there for submitting assignments? Choose all that apply.\r\n

[Incorrect] a. Upload files to the assignment dropbox in Pressbooks.\r\n[Correct] b. Submit a URL to your files on GitHub.<\/span>\r\n[Incorrect] c. Email your assignment to the instructor.\r\n[Correct] d. Submit a URL to your files on a server you have FTP access to.<\/span>\r\n[Incorrect] e. Upload files to the assignment DropBox folder.<\/p>\r\n

Feedback:<\/strong> You may submit a URL to your activity files either on GitHub (i.e., GitHub Pages), or on a web server you have FTP access to.<\/p>\r\n2.<\/strong> Where can you get a copy of the activity files? Choose all that apply.\r\n

[Incorrect] a. Downloading from the activity file manager\r\n[Correct] b. Forking and cloning from GitHub<\/span>\r\n[Correct] c. Downloading from GitHub<\/span>\r\n[Incorrect] d. Ask the instructor to email them to you\r\n[Incorrect] e. Download them from the assignment DropBox folder<\/p>\r\n

Feedback:<\/strong> You may download the learnaria.github.io repository files from github.com, or you may fork the repository to your own GitHub account and clone them from there into your own development environment.<\/p>\r\n3.<\/strong> What prerequisite knowledge is needed to be effective with the activities in this resource? Choose all that apply.\r\n

[Incorrect] a. No prerequisite knowledge is required.\r\n[Incorrect] b. The ability to write JavaScript\r\n[Correct] c. The ability to read and understand JavaScript<\/span>\r\n[Correct] d. The ability to read and understand HTML<\/span>\r\n[Incorrect] e. A strong understanding of WCAG 2<\/p>\r\n

Feedback:<\/strong> Coding experience is strongly recommended but not absolutely necessary to follow along. Your ability to read and understand JavaScript and HTML code will determine your success with the activities in this resource.<\/p>\r\n4.<\/strong> When working with ChromeVox, what key or key combination can be used to stop it from speaking?\r\n

[Incorrect] a. Alt\r\n[Incorrect] b. Cvox + Q\r\n[Incorrect] c. Cvox + D\r\n[Correct] d. Ctrl<\/span>\r\n[Incorrect] e. Cvox + S<\/p>\r\n

Feedback:<\/strong> The most asked question when using ChromeVox is how to stop it from speaking. Simply press the Ctrl (control) key.<\/p>\r\n5.<\/strong> When working with ChromeVox, what key or key combination can be used to turn it off, or on.\r\n

[Incorrect] a. Esc\r\n[Correct] b. Cvox + A + A<\/span>\r\n[Incorrect] c. Cvox + Q\r\n[Incorrect] d. Cvox + D\r\n[Incorrect] e. Ctrl + F5<\/p>\r\n

Feedback:<\/strong> The second most asked question is how to turn ChromeVox on or off without having to find your way through Manage Extensions. Press Cvox+A+A to turn the screen reader on or off while using the Chrome web browser.<\/p>\r\n6.<\/strong> WAI-ARIA is part of HTML5 and will not work when older versions of HTML are being used.\r\n

[Incorrect] a. True\r\n[Correct] b. False<\/span><\/p>\r\n

Feedback:<\/strong> WAI-ARIA works fine with older versions of HTML, though when validating older HTML, it will produce errors or warnings. These errors or warnings can be safely ignored.<\/p>\r\nBack to Self-Test 1<\/a>\r\n\r\n

\r\n\r\n

<\/a><\/a>Self-Test 2<\/h2>\r\n1.<\/strong> When creating a registration form for a website, it is important to use role=\"form\" with the element to ensure screen reader users understand they are entering a form.\r\n

[Incorrect] a. True\r\n[Correct] b. False<\/span><\/p>\r\n

Feedback:<\/strong> A form element has its semantics defined by default, and thus does not need a WAI-ARIA role defined. When using HTML in a standard way, WAI-ARIA should not be used, with a few exceptions.<\/p>\r\n2.<\/strong> When talking about WAI-ARIA, we are referring to:\r\n

[Incorrect] a. Roles, settings, and properties\r\n[Incorrect] b. Roles, options, and preferences\r\n[Correct] c. Roles, states, and properties<\/span>\r\n[Incorrect] d. Elements, attributes, and functions\r\n[Incorrect] e. Elements, options, and preferences<\/p>\r\n

Feedback:<\/strong> WAI-ARIA is made up of HTML attributes that define roles, states, and properties.<\/p>\r\n3.<\/strong> Which of the following are not WAI-ARIA roles? Choose all that apply.\r\n

[Incorrect] a. menu\r\n[Incorrect] b. navigation\r\n[Correct] c. aria-label<\/span>\r\n[Correct] d. tabindex<\/span>\r\n[Correct] e. aria-describedby<\/span>\r\n[Correct] f. aria-checked<\/span>\r\n[Incorrect] g. complementary\r\n[Correct] h. footer<\/span>\r\n[Incorrect] i. banner<\/p>\r\n

Feedback:<\/strong> Any WAI-ARIA attribute that is prefixed with \"aria-\" will be a state or property, not a role. The tabindex attribute is a special case, extending tabindex in previous versions of HTML, but it is not a role. Footer is not defined in WAI-ARIA.<\/p>\r\n4.<\/strong> WAI-ARIA Properties tend not to change.\r\n

[Correct] a. True<\/span>\r\n[Incorrect] b. False<\/p>\r\n

Feedback:<\/strong> True. States tend to change. Properties do not.<\/p>\r\n5.<\/strong> WAI-ARIA States tend not to change.\r\n

[Incorrect] a. True\r\n[Correct] b. False<\/span><\/p>\r\n

Feedback:<\/strong> False. States do tend to change.<\/p>\r\n6.<\/strong> Which of the following tend to be used dynamically, with values updated using scripting? Choose all that apply.\r\n

[Incorrect] a. role=\"menu\"\r\n[Correct] b. aria-disabled=\"true\"<\/span>\r\n[Incorrect] c. aria-haspopup=\"true\"\r\n[Incorrect] d. aria-modal=\"true\"\r\n[Correct] e. aria-checked=\"true\"<\/span>\r\n[Correct] f. aria-expanded=\"false\"<\/span>\r\n[Correct] g. aria-hidden=\"true\"<\/span><\/p>\r\n

Feedback:<\/strong> Typically states will be dynamically updated with scripting (aria-disabled, aria-checked, aria-expanded, aria-hidden) while properties tend to be static and do not usually change (aria-haspopup, aria-modal). Roles also tend to be static, and do not require updating values with scripting.<\/p>\r\n7.<\/strong> ______________ starts with a version that works for everyone, then adds features when they are supported.\r\n

[Incorrect] a. Graceful degradation\r\n[Correct] b. Progressive enhancement<\/span><\/p>\r\n

Feedback:<\/strong> Progressive enhancements starts with a base version that works for everyone, and are \u201cenhanced\u201d with additional features where they are supported.<\/p>\r\n8.<\/strong> Generally, which method is preferred?\r\n

[Incorrect] a. Graceful degradation\r\n[Correct] b. Progressive enhancement<\/span><\/p>\r\n

Feedback:<\/strong> For broadest support, progressive enhancement is generally preferred to ensure that regardless of the technology a person may be using, there will always be a functional version available.<\/p>\r\nBack to Self-Test 2<\/a>\r\n\r\n

\r\n\r\n

<\/a>Self-Test 3<\/h2>\r\n1.<\/strong> Which of the following are landmark roles? Choose all that apply.\r\n

[Incorrect] a. menu\r\n[Correct] b. navigation<\/span>\r\n[Incorrect] c. aria-label\r\n[Incorrect] d. tabindex\r\n[Incorrect] e. aria-describedby\r\n[Incorrect] f. aria-checked\r\n[Correct] g. complementary<\/span>\r\n[Incorrect] h. footer\r\n[Correct] i. banner<\/span><\/p>\r\n

Feedback:<\/strong> Navigation, complementary, and banner are landmark roles.<\/p>\r\n

2.<\/strong> Which would usually be the best approach to provide feedback to a screen reader user with a message that an operation just completed was successful or has failed presenting an error message?<\/p>\r\n

[Incorrect] a. aria-live=\"polite\"\r\n[Correct] b. role=\"alert\"<\/span>\r\n[Incorrect] c. role=\"alertdialog\"\r\n[Incorrect] d. role=\"dialog\"\r\n[Incorrect] e. aria-modal=\"true\"<\/p>\r\n

Feedback:<\/strong> Though you could use aria-live=\"polite\" to present feedback, the best approach is usually to use role=\"alert\".<\/p>\r\n3.<\/strong> Keyboard interaction in web widgets and applications should be (choose all that apply):\r\n<\/span>\r\n

[Correct] a. Predictable<\/span>\r\n[Incorrect] b. Redundant\r\n[Incorrect] c. Easy\r\n[Correct] d. Consistent<\/span>\r\n[Correct] e. Conventional<\/span><\/p>\r\n

Feedback:<\/strong> Keyboard interaction should be predictable, consistent, and conventional.<\/p>\r\n4.<\/strong> Which of the following WAI-ARIA roles, when active, would disable keyboard access to the file menu in a web browser?\r\n<\/span>\r\n

[Correct] a. Application<\/span>\r\n[Incorrect] b. Menu\r\n[Incorrect] c. Menubar\r\n[Incorrect] d. Navigation\r\n[Incorrect] e. Presentation<\/p>\r\n

Feedback:<\/strong> The application role would disable the browser\u2019s file menu.<\/p>\r\n5.<\/strong> When role=\"presentation\" is used on an unordered list element, semantics for which of the following elements would be fully suppressed? Choose all that apply.\r\n<ul role=\"presentation\">...<\/ul>\r\n<\/span>\r\n

[Correct] a. UL<\/span>\r\n[Correct] b. UL>LI<\/span>\r\n[Incorrect] c. UL>LI>UL\r\n[Incorrect] d. UL>LI>OL\r\n[Incorrect] e. UL>LI>UL>LI<\/p>\r\n

Feedback:<\/strong> Only the semantics of the top level UL and its immediate children will be suppressed. That is, the first level UL and its first level child LIs.<\/p>\r\n6.<\/strong> Which of the following create live regions that announce changes in the content to screen readers? Choose all that apply.\r\n<\/span>\r\n

[Correct] a. role=\"alert\"<\/span>\r\n[Correct] b. aria-live=\"polite\"<\/span>\r\n[Correct] c. role=\"timer\"<\/span>\r\n[Correct] d. role=\"log\"<\/span>\r\n[Incorrect] e. role=\"live-region\"<\/p>\r\n

Feedback:<\/strong> All except the last choice will create live regions. role=\"live-region\" is not a WAI-ARIA role or live region.<\/p>\r\n7.<\/strong> Which of the following would be good candidates for a live region? Choose all that apply.\r\n

[Incorrect] a. A timer counting down by seconds\r\n[Correct] b. A dynamically injected feedback message<\/span>\r\n[Correct] c. A news feed from a local news provider<\/span>\r\n[Correct] d. A Twitter feed that receives occasional updates<\/span>\r\n[Correct] e. A chat application, for communicating in real time<\/span><\/p>\r\n

Feedback:<\/strong> A timer may also be a live region, but counting down by seconds may make the content on the page it is embedded in unusable. A timer counting down by minutes (e.g., minutes until the end of a quiz) would be a better candidate.<\/p>\r\nBack to Self-Test 3<\/a>","rendered":"

<\/a>Self-Test 1<\/h2>\n

1.<\/strong> What options are there for submitting assignments? Choose all that apply.<\/p>\n

[Incorrect] a. Upload files to the assignment dropbox in Pressbooks.
\n[Correct] b. Submit a URL to your files on GitHub.<\/span>
\n[Incorrect] c. Email your assignment to the instructor.
\n[Correct] d. Submit a URL to your files on a server you have FTP access to.<\/span>
\n[Incorrect] e. Upload files to the assignment DropBox folder.<\/p>\n

Feedback:<\/strong> You may submit a URL to your activity files either on GitHub (i.e., GitHub Pages), or on a web server you have FTP access to.<\/p>\n

2.<\/strong> Where can you get a copy of the activity files? Choose all that apply.<\/p>\n

[Incorrect] a. Downloading from the activity file manager
\n[Correct] b. Forking and cloning from GitHub<\/span>
\n[Correct] c. Downloading from GitHub<\/span>
\n[Incorrect] d. Ask the instructor to email them to you
\n[Incorrect] e. Download them from the assignment DropBox folder<\/p>\n

Feedback:<\/strong> You may download the learnaria.github.io repository files from github.com, or you may fork the repository to your own GitHub account and clone them from there into your own development environment.<\/p>\n

3.<\/strong> What prerequisite knowledge is needed to be effective with the activities in this resource? Choose all that apply.<\/p>\n

[Incorrect] a. No prerequisite knowledge is required.
\n[Incorrect] b. The ability to write JavaScript
\n[Correct] c. The ability to read and understand JavaScript<\/span>
\n[Correct] d. The ability to read and understand HTML<\/span>
\n[Incorrect] e. A strong understanding of WCAG 2<\/p>\n

Feedback:<\/strong> Coding experience is strongly recommended but not absolutely necessary to follow along. Your ability to read and understand JavaScript and HTML code will determine your success with the activities in this resource.<\/p>\n

4.<\/strong> When working with ChromeVox, what key or key combination can be used to stop it from speaking?<\/p>\n

[Incorrect] a. Alt
\n[Incorrect] b. Cvox + Q
\n[Incorrect] c. Cvox + D
\n[Correct] d. Ctrl<\/span>
\n[Incorrect] e. Cvox + S<\/p>\n

Feedback:<\/strong> The most asked question when using ChromeVox is how to stop it from speaking. Simply press the Ctrl (control) key.<\/p>\n

5.<\/strong> When working with ChromeVox, what key or key combination can be used to turn it off, or on.<\/p>\n

[Incorrect] a. Esc
\n[Correct] b. Cvox + A + A<\/span>
\n[Incorrect] c. Cvox + Q
\n[Incorrect] d. Cvox + D
\n[Incorrect] e. Ctrl + F5<\/p>\n

Feedback:<\/strong> The second most asked question is how to turn ChromeVox on or off without having to find your way through Manage Extensions. Press Cvox+A+A to turn the screen reader on or off while using the Chrome web browser.<\/p>\n

6.<\/strong> WAI-ARIA is part of HTML5 and will not work when older versions of HTML are being used.<\/p>\n

[Incorrect] a. True
\n[Correct] b. False<\/span><\/p>\n

Feedback:<\/strong> WAI-ARIA works fine with older versions of HTML, though when validating older HTML, it will produce errors or warnings. These errors or warnings can be safely ignored.<\/p>\n

Back to Self-Test 1<\/a><\/p>\n

\n

<\/a><\/a>Self-Test 2<\/h2>\n

1.<\/strong> When creating a registration form for a website, it is important to use role=”form” with the element to ensure screen reader users understand they are entering a form.<\/p>\n

[Incorrect] a. True
\n[Correct] b. False<\/span><\/p>\n

Feedback:<\/strong> A form element has its semantics defined by default, and thus does not need a WAI-ARIA role defined. When using HTML in a standard way, WAI-ARIA should not be used, with a few exceptions.<\/p>\n

2.<\/strong> When talking about WAI-ARIA, we are referring to:<\/p>\n

[Incorrect] a. Roles, settings, and properties
\n[Incorrect] b. Roles, options, and preferences
\n[Correct] c. Roles, states, and properties<\/span>
\n[Incorrect] d. Elements, attributes, and functions
\n[Incorrect] e. Elements, options, and preferences<\/p>\n

Feedback:<\/strong> WAI-ARIA is made up of HTML attributes that define roles, states, and properties.<\/p>\n

3.<\/strong> Which of the following are not WAI-ARIA roles? Choose all that apply.<\/p>\n

[Incorrect] a. menu
\n[Incorrect] b. navigation
\n[Correct] c. aria-label<\/span>
\n[Correct] d. tabindex<\/span>
\n[Correct] e. aria-describedby<\/span>
\n[Correct] f. aria-checked<\/span>
\n[Incorrect] g. complementary
\n[Correct] h. footer<\/span>
\n[Incorrect] i. banner<\/p>\n

Feedback:<\/strong> Any WAI-ARIA attribute that is prefixed with “aria-” will be a state or property, not a role. The tabindex attribute is a special case, extending tabindex in previous versions of HTML, but it is not a role. Footer is not defined in WAI-ARIA.<\/p>\n

4.<\/strong> WAI-ARIA Properties tend not to change.<\/p>\n

[Correct] a. True<\/span>
\n[Incorrect] b. False<\/p>\n

Feedback:<\/strong> True. States tend to change. Properties do not.<\/p>\n

5.<\/strong> WAI-ARIA States tend not to change.<\/p>\n

[Incorrect] a. True
\n[Correct] b. False<\/span><\/p>\n

Feedback:<\/strong> False. States do tend to change.<\/p>\n

6.<\/strong> Which of the following tend to be used dynamically, with values updated using scripting? Choose all that apply.<\/p>\n

[Incorrect] a. role=”menu”
\n[Correct] b. aria-disabled=”true”<\/span>
\n[Incorrect] c. aria-haspopup=”true”
\n[Incorrect] d. aria-modal=”true”
\n[Correct] e. aria-checked=”true”<\/span>
\n[Correct] f. aria-expanded=”false”<\/span>
\n[Correct] g. aria-hidden=”true”<\/span><\/p>\n

Feedback:<\/strong> Typically states will be dynamically updated with scripting (aria-disabled, aria-checked, aria-expanded, aria-hidden) while properties tend to be static and do not usually change (aria-haspopup, aria-modal). Roles also tend to be static, and do not require updating values with scripting.<\/p>\n

7.<\/strong> ______________ starts with a version that works for everyone, then adds features when they are supported.<\/p>\n

[Incorrect] a. Graceful degradation
\n[Correct] b. Progressive enhancement<\/span><\/p>\n

Feedback:<\/strong> Progressive enhancements starts with a base version that works for everyone, and are \u201cenhanced\u201d with additional features where they are supported.<\/p>\n

8.<\/strong> Generally, which method is preferred?<\/p>\n

[Incorrect] a. Graceful degradation
\n[Correct] b. Progressive enhancement<\/span><\/p>\n

Feedback:<\/strong> For broadest support, progressive enhancement is generally preferred to ensure that regardless of the technology a person may be using, there will always be a functional version available.<\/p>\n

Back to Self-Test 2<\/a><\/p>\n

\n

<\/a>Self-Test 3<\/h2>\n

1.<\/strong> Which of the following are landmark roles? Choose all that apply.<\/p>\n

[Incorrect] a. menu
\n[Correct] b. navigation<\/span>
\n[Incorrect] c. aria-label
\n[Incorrect] d. tabindex
\n[Incorrect] e. aria-describedby
\n[Incorrect] f. aria-checked
\n[Correct] g. complementary<\/span>
\n[Incorrect] h. footer
\n[Correct] i. banner<\/span><\/p>\n

Feedback:<\/strong> Navigation, complementary, and banner are landmark roles.<\/p>\n

2.<\/strong> Which would usually be the best approach to provide feedback to a screen reader user with a message that an operation just completed was successful or has failed presenting an error message?<\/p>\n

[Incorrect] a. aria-live=”polite”
\n[Correct] b. role=”alert”<\/span>
\n[Incorrect] c. role=”alertdialog”
\n[Incorrect] d. role=”dialog”
\n[Incorrect] e. aria-modal=”true”<\/p>\n

Feedback:<\/strong> Though you could use aria-live=”polite” to present feedback, the best approach is usually to use role=”alert”.<\/p>\n

3.<\/strong> Keyboard interaction in web widgets and applications should be (choose all that apply):
\n<\/span><\/p>\n

[Correct] a. Predictable<\/span>
\n[Incorrect] b. Redundant
\n[Incorrect] c. Easy
\n[Correct] d. Consistent<\/span>
\n[Correct] e. Conventional<\/span><\/p>\n

Feedback:<\/strong> Keyboard interaction should be predictable, consistent, and conventional.<\/p>\n

4.<\/strong> Which of the following WAI-ARIA roles, when active, would disable keyboard access to the file menu in a web browser?
\n<\/span><\/p>\n

[Correct] a. Application<\/span>
\n[Incorrect] b. Menu
\n[Incorrect] c. Menubar
\n[Incorrect] d. Navigation
\n[Incorrect] e. Presentation<\/p>\n

Feedback:<\/strong> The application role would disable the browser\u2019s file menu.<\/p>\n

5.<\/strong> When role=”presentation” is used on an unordered list element, semantics for which of the following elements would be fully suppressed? Choose all that apply.
\n<ul role=”presentation”>…<\/ul>
\n<\/span><\/p>\n

[Correct] a. UL<\/span>
\n[Correct] b. UL>LI<\/span>
\n[Incorrect] c. UL>LI>UL
\n[Incorrect] d. UL>LI>OL
\n[Incorrect] e. UL>LI>UL>LI<\/p>\n

Feedback:<\/strong> Only the semantics of the top level UL and its immediate children will be suppressed. That is, the first level UL and its first level child LIs.<\/p>\n

6.<\/strong> Which of the following create live regions that announce changes in the content to screen readers? Choose all that apply.
\n<\/span><\/p>\n

[Correct] a. role=”alert”<\/span>
\n[Correct] b. aria-live=”polite”<\/span>
\n[Correct] c. role=”timer”<\/span>
\n[Correct] d. role=”log”<\/span>
\n[Incorrect] e. role=”live-region”<\/p>\n

Feedback:<\/strong> All except the last choice will create live regions. role=”live-region” is not a WAI-ARIA role or live region.<\/p>\n

7.<\/strong> Which of the following would be good candidates for a live region? Choose all that apply.<\/p>\n

[Incorrect] a. A timer counting down by seconds
\n[Correct] b. A dynamically injected feedback message<\/span>
\n[Correct] c. A news feed from a local news provider<\/span>
\n[Correct] d. A Twitter feed that receives occasional updates<\/span>
\n[Correct] e. A chat application, for communicating in real time<\/span><\/p>\n

Feedback:<\/strong> A timer may also be a live region, but counting down by seconds may make the content on the page it is embedded in unusable. A timer counting down by minutes (e.g., minutes until the end of a quiz) would be a better candidate.<\/p>\n

Back to Self-Test 3<\/a><\/p>\n","protected":false},"author":100,"menu_order":3,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"back-matter-type":[],"contributor":[],"license":[],"class_list":["post-788","back-matter","type-back-matter","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/back-matter\/788","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/back-matter"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/types\/back-matter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/users\/100"}],"version-history":[{"count":26,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/back-matter\/788\/revisions"}],"predecessor-version":[{"id":2034,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/back-matter\/788\/revisions\/2034"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/back-matter\/788\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/media?parent=788"}],"wp:term":[{"taxonomy":"back-matter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/pressbooks\/v2\/back-matter-type?post=788"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/contributor?post=788"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/wafd\/wp-json\/wp\/v2\/license?post=788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}