Sample Accessibility Statement<\/p>\n\n<\/header>\n

\n\nBCcampus Open Education believes that education needs to be available to everyone, which means supporting the creation of free, open, and accessible educational resources. We are actively committed to increasing the accessibility and usability of the textbooks we produce.\n

Accessibility features of the web version for this resource<\/h4>\nThe web version of the Accessibility Toolkit - 2nd Edition<\/em><\/a> has been designed with accessibility in mind by incorporating the following features:\n\n \t
It has been optimized for people who use screen-reader technology.\n
\n \t
all content can be navigated using a keyboard<\/li>\n \t
links, headings, tables, and images have been designed to work with screen readers<\/li>\n<\/ul>\n<\/li>\n \t
It has the option to increase font size (see tab on top right of screen).<\/li>\n<\/ul>\n
Other file formats available<\/h4>\nIn addition to the web version, this book is available in a number of file formats, including PDF, EPUB (for eReaders), MOBI (for Kindles), and various editable files. You can also purchase a print copy. Here is a link to where you can download this book in another file format<\/a>. Look for the \"Download this book\" drop-down menu to select the file type you want.\n
Known accessibility issues and areas for improvement<\/h4>\nWhile we strive to ensure that this textbook is as accessible and as usable as possible, we might not always get it right. Any issues we identify will be listed below.\n\n\n\n\n
List of Known Accessibility Issues<\/caption>\n
Location of issue<\/th>\n Need for improvement<\/th>\n Timeline<\/th>\n Work around<\/th>\n<\/tr>\n
<\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n
<\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Accessibility standards<\/h4>\nThe web version of this resource has been designed to meet Web Content Accessibility Guidelines 2.0<\/a>, level AA. In addition, it follows all guidelines in \"Appendix A: Checklist for Accessibility<\/a>.\" The development of the toolkit involved working with students with various print disabilities who provided their personal perspectives and helped test the content.\n
Let us know if you are having problems accessing this textbook<\/strong><\/h4>\nWe are always looking for how we can make our resources more accessible. If you are having problems accessing this resource, please contact us to let us know so we can fix the issue.\n\nPlease include the following information:\n
\n \t
The location of the problem by providing a web address or page description<\/li>\n \t
A description of the problem<\/li>\n \t
The computer, software, browser, and any assistive technology you are using that can help us diagnose and solve your issue\n
\n \t
e.g., Windows 10, Google Chrome (Version 65.0.3325.181), NVDA screenreader<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nYou can contact us one of the following ways:\n
\n \t
Email: helpdesk@bccampus.ca<\/a><\/li>\n \t
Web form: Report an Open Textbook Error<\/a> form<\/li>\n<\/ul>\nThis statement was last updated on August 21, 2018. <\/strong>\n\n<\/div>\n<\/div>\n
Additional resources<\/h1>\nFor more information, refer to the following resources:\n
\n \t
Web Content Accessibility Guidelines: Conformance Claims<\/a><\/li>\n \t
Nomensa: How to Write an Accessibility Statement<\/a><\/li>\n \t
Access 8878's Accessibility Statement<\/a><\/li>\n<\/ul>\nFor sample accessibility statements, refer to the following pages:\n
\n \t
B.C. Government Website's Accessibility Statement<\/a><\/a><\/li>\n \t
Hassell Inclusion's Accessibility Statement<\/a><\/li>\n<\/ul>\n","rendered":"
Once you have created an accessible textbook, you should provide an accessibility statement. While an accessibility statement is not required, it can be an important and useful addition to a resource for which you have worked to make accessible. This section will outline guidelines and recommendations about what to include in an accessibility statement and who the accessibility statement is for.<\/p>\n
What is an accessibility statement?<\/h1>\n
An accessibility statement acts as resource for those who have questions about the accessibility features of your resource. It should provide an overview of accessibility features and contact information in case there are any problems.<\/p>\n
Who are you doing this for?<\/h1>\n
When writing an accessibility statement, it is important to keep in mind who the statement is for. This will guide the language you use and the type of information you include. Ultimately, the accessibility statement is for people who have disabilities.<\/p>\n
Hassell Inclusion’s blog post on “How to write an effective Accessibility Statement”<\/a> notes that many accessibility statements ignore who will be accessing the accessibility statement or why. Instead, they make statements about the organization’s commitment to accessibility, combined with technical jargon related to web development, accessibility, and accessibility legislation. Rather than acting as a helpful resource for people with disabilities, this type of accessibility statement “read[s] like a combination of a sales pitch on how socially responsible the organization is, a technology manual, and some legal small print.”^{[1]<\/sup><\/a><\/p>\n}
Chances are, the only time people will be interested in an accessibility statement is when they have trouble accessing content in the textbook or resource. Therefore, make sure your accessibility statement provides the information readers are looking for.<\/p>\n
What do you need to do?<\/h1>\n
Here are tips for writing a useful accessibility statement:<\/p>\n
\n
Use clear and simple language, avoiding jargon and technical terms<\/li>\n
Include information about how people can personalize their experience. This might include information about:\n
\n
features of the platform used for the resource (e.g., if a book is in Pressbooks, mention the ability of users to increase the font size in the web book)<\/li>\n
the ability to change browser settings<\/li>\n
a link to each available file format<\/li>\n
assistive technologies<\/li>\n<\/ul>\n<\/li>\n
Outline specific accessibility features and how to use them when relevant<\/li>\n
Do not make false claims or ignore known accessibility issues. Be as transparent and open about accessibility barriers as possible. This means:\n
\n
describing what is being done to fix the problem and a timeline<\/li>\n
providing any temporary workarounds<\/li>\n<\/ul>\n<\/li>\n
Include information about who is responsible for the accessibility of the content and their contact information so people can submit issues, suggestions, or complaints related to accessibility.<\/li>\n
Describe the organization’s accessibility policy, and the work that has been done to make the resource accessible. Here, you can provide information like:\n
\n
accessibility guidelines you are following (e.g., WCAG 2.0)<\/li>\n
any federal, provincial, or state legislation you are conforming to<\/li>\n
any user testing you performed^{[2]<\/sup><\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\nHere is a sample accessibility statement that you can adapt for your own purposes:<\/p>\n}
\n
\n
Sample Accessibility Statement<\/p>\n<\/header>\n
\n
BCcampus Open Education believes that education needs to be available to everyone, which means supporting the creation of free, open, and accessible educational resources. We are actively committed to increasing the accessibility and usability of the textbooks we produce.<\/p>\n
Accessibility features of the web version for this resource<\/h4>\n
The web version of the Accessibility Toolkit – 2nd Edition<\/em><\/a> has been designed with accessibility in mind by incorporating the following features:<\/p>\n
\n
It has been optimized for people who use screen-reader technology.\n
\n
all content can be navigated using a keyboard<\/li>\n
links, headings, tables, and images have been designed to work with screen readers<\/li>\n<\/ul>\n<\/li>\n
It has the option to increase font size (see tab on top right of screen).<\/li>\n<\/ul>\n
Other file formats available<\/h4>\n
In addition to the web version, this book is available in a number of file formats, including PDF, EPUB (for eReaders), MOBI (for Kindles), and various editable files. You can also purchase a print copy. Here is a link to where you can download this book in another file format<\/a>. Look for the “Download this book” drop-down menu to select the file type you want.<\/p>\n
Known accessibility issues and areas for improvement<\/h4>\n
While we strive to ensure that this textbook is as accessible and as usable as possible, we might not always get it right. Any issues we identify will be listed below.<\/p>\n\n\n\n\n\n
List of Known Accessibility Issues<\/caption>\n
Location of issue<\/th>\n Need for improvement<\/th>\n Timeline<\/th>\n Work around<\/th>\n<\/tr>\n
<\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n
<\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Accessibility standards<\/h4>\n
The web version of this resource has been designed to meet Web Content Accessibility Guidelines 2.0<\/a>, level AA. In addition, it follows all guidelines in “Appendix A: Checklist for Accessibility<\/a>.” The development of the toolkit involved working with students with various print disabilities who provided their personal perspectives and helped test the content.<\/p>\n
Let us know if you are having problems accessing this textbook<\/strong><\/h4>\n
We are always looking for how we can make our resources more accessible. If you are having problems accessing this resource, please contact us to let us know so we can fix the issue.<\/p>\n
Please include the following information:<\/p>\n
\n
The location of the problem by providing a web address or page description<\/li>\n
A description of the problem<\/li>\n
The computer, software, browser, and any assistive technology you are using that can help us diagnose and solve your issue\n
\n
e.g., Windows 10, Google Chrome (Version 65.0.3325.181), NVDA screenreader<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
You can contact us one of the following ways:<\/p>\n
\n
Email: helpdesk@bccampus.ca<\/a><\/li>\n
Web form: Report an Open Textbook Error<\/a> form<\/li>\n<\/ul>\n
This statement was last updated on August 21, 2018. <\/strong><\/p>\n<\/div>\n<\/div>\n
Additional resources<\/h1>\n
For more information, refer to the following resources:<\/p>\n
\n
Web Content Accessibility Guidelines: Conformance Claims<\/a><\/li>\n
Nomensa: How to Write an Accessibility Statement<\/a><\/li>\n
Access 8878’s Accessibility Statement<\/a><\/li>\n<\/ul>\n
For sample accessibility statements, refer to the following pages:<\/p>\n
\n
B.C. Government Website’s Accessibility Statement<\/a><\/a><\/li>\n
Hassell Inclusion’s Accessibility Statement<\/a><\/li>\n<\/ul>\n
\"Accessibility Statement,\" Hassellinclusion<\/em>, accessed August 23, 2018, http:\/\/www.hassellinclusion.com\/accessibility\/. ↵<\/a><\/li>
\"Creating an Accessibility Statement,\" Access 8878<\/em>, accessed August 30, 2018, https:\/\/web.archive.org\/web\/20161203101842\/https:\/\/www.access8878.co.uk\/getting-started-with-bs-8878\/creating-an-accessibility-statement.aspx. ↵<\/a><\/li><\/ol><\/div>","protected":false},"author":1,"menu_order":9,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":["jgray"],"pb_section_license":""},"chapter-type":[],"contributor":[60],"license":[],"part":33,"_links":{"self":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters\/54"}],"collection":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters\/54\/revisions"}],"part":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/parts\/33"}],"metadata":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters\/54\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/media?parent=54"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapter-type?post=54"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/contributor?post=54"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/license?post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

List of Known Accessibility Issues<\/caption>\n
Location of issue<\/th>\n	Need for improvement<\/th>\n	Timeline<\/th>\n	Work around<\/th>\n<\/tr>\n
<\/td>\n	<\/td>\n	<\/td>\n	<\/td>\n<\/tr>\n
<\/td>\n	<\/td>\n	<\/td>\n	<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Accessibility standards<\/h4>\nThe web version of this resource has been designed to meet Web Content Accessibility Guidelines 2.0<\/a>, level AA. In addition, it follows all guidelines in \"Appendix A: Checklist for Accessibility<\/a>.\" The development of the toolkit involved working with students with various print disabilities who provided their personal perspectives and helped test the content.\n Let us know if you are having problems accessing this textbook<\/strong><\/h4>\nWe are always looking for how we can make our resources more accessible. If you are having problems accessing this resource, please contact us to let us know so we can fix the issue.\n\nPlease include the following information:\n \n \t The location of the problem by providing a web address or page description<\/li>\n \t A description of the problem<\/li>\n \t The computer, software, browser, and any assistive technology you are using that can help us diagnose and solve your issue\n \n \t e.g., Windows 10, Google Chrome (Version 65.0.3325.181), NVDA screenreader<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nYou can contact us one of the following ways:\n \n \t Email: helpdesk@bccampus.ca<\/a><\/li>\n \t Web form: Report an Open Textbook Error<\/a> form<\/li>\n<\/ul>\nThis statement was last updated on August 21, 2018. <\/strong>\n\n<\/div>\n<\/div>\n Additional resources<\/h1>\nFor more information, refer to the following resources:\n \n \t Web Content Accessibility Guidelines: Conformance Claims<\/a><\/li>\n \t Nomensa: How to Write an Accessibility Statement<\/a><\/li>\n \t Access 8878's Accessibility Statement<\/a><\/li>\n<\/ul>\nFor sample accessibility statements, refer to the following pages:\n \n \t B.C. Government Website's Accessibility Statement<\/a><\/a><\/li>\n \t Hassell Inclusion's Accessibility Statement<\/a><\/li>\n<\/ul>\n","rendered":" Once you have created an accessible textbook, you should provide an accessibility statement. While an accessibility statement is not required, it can be an important and useful addition to a resource for which you have worked to make accessible. This section will outline guidelines and recommendations about what to include in an accessibility statement and who the accessibility statement is for.<\/p>\n What is an accessibility statement?<\/h1>\n An accessibility statement acts as resource for those who have questions about the accessibility features of your resource. It should provide an overview of accessibility features and contact information in case there are any problems.<\/p>\n Who are you doing this for?<\/h1>\n When writing an accessibility statement, it is important to keep in mind who the statement is for. This will guide the language you use and the type of information you include. Ultimately, the accessibility statement is for people who have disabilities.<\/p>\n Hassell Inclusion’s blog post on “How to write an effective Accessibility Statement”<\/a> notes that many accessibility statements ignore who will be accessing the accessibility statement or why. Instead, they make statements about the organization’s commitment to accessibility, combined with technical jargon related to web development, accessibility, and accessibility legislation. Rather than acting as a helpful resource for people with disabilities, this type of accessibility statement “read[s] like a combination of a sales pitch on how socially responsible the organization is, a technology manual, and some legal small print.”^{[1]<\/sup><\/a><\/p>\n} Chances are, the only time people will be interested in an accessibility statement is when they have trouble accessing content in the textbook or resource. Therefore, make sure your accessibility statement provides the information readers are looking for.<\/p>\n What do you need to do?<\/h1>\n Here are tips for writing a useful accessibility statement:<\/p>\n \n Use clear and simple language, avoiding jargon and technical terms<\/li>\n Include information about how people can personalize their experience. This might include information about:\n \n features of the platform used for the resource (e.g., if a book is in Pressbooks, mention the ability of users to increase the font size in the web book)<\/li>\n the ability to change browser settings<\/li>\n a link to each available file format<\/li>\n assistive technologies<\/li>\n<\/ul>\n<\/li>\n Outline specific accessibility features and how to use them when relevant<\/li>\n Do not make false claims or ignore known accessibility issues. Be as transparent and open about accessibility barriers as possible. This means:\n \n describing what is being done to fix the problem and a timeline<\/li>\n providing any temporary workarounds<\/li>\n<\/ul>\n<\/li>\n Include information about who is responsible for the accessibility of the content and their contact information so people can submit issues, suggestions, or complaints related to accessibility.<\/li>\n Describe the organization’s accessibility policy, and the work that has been done to make the resource accessible. Here, you can provide information like:\n \n accessibility guidelines you are following (e.g., WCAG 2.0)<\/li>\n any federal, provincial, or state legislation you are conforming to<\/li>\n any user testing you performed^{[2]<\/sup><\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\nHere is a sample accessibility statement that you can adapt for your own purposes:<\/p>\n} \n \n Sample Accessibility Statement<\/p>\n<\/header>\n \n BCcampus Open Education believes that education needs to be available to everyone, which means supporting the creation of free, open, and accessible educational resources. We are actively committed to increasing the accessibility and usability of the textbooks we produce.<\/p>\n Accessibility features of the web version for this resource<\/h4>\n The web version of the Accessibility Toolkit – 2nd Edition<\/em><\/a> has been designed with accessibility in mind by incorporating the following features:<\/p>\n \n It has been optimized for people who use screen-reader technology.\n \n all content can be navigated using a keyboard<\/li>\n links, headings, tables, and images have been designed to work with screen readers<\/li>\n<\/ul>\n<\/li>\n It has the option to increase font size (see tab on top right of screen).<\/li>\n<\/ul>\n Other file formats available<\/h4>\n In addition to the web version, this book is available in a number of file formats, including PDF, EPUB (for eReaders), MOBI (for Kindles), and various editable files. You can also purchase a print copy. Here is a link to where you can download this book in another file format<\/a>. Look for the “Download this book” drop-down menu to select the file type you want.<\/p>\n Known accessibility issues and areas for improvement<\/h4>\n While we strive to ensure that this textbook is as accessible and as usable as possible, we might not always get it right. Any issues we identify will be listed below.<\/p>\n\n\n\n\n\n List of Known Accessibility Issues<\/caption>\n Location of issue<\/th>\n Need for improvement<\/th>\n Timeline<\/th>\n Work around<\/th>\n<\/tr>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Accessibility standards<\/h4>\n The web version of this resource has been designed to meet Web Content Accessibility Guidelines 2.0<\/a>, level AA. In addition, it follows all guidelines in “Appendix A: Checklist for Accessibility<\/a>.” The development of the toolkit involved working with students with various print disabilities who provided their personal perspectives and helped test the content.<\/p>\n Let us know if you are having problems accessing this textbook<\/strong><\/h4>\n We are always looking for how we can make our resources more accessible. If you are having problems accessing this resource, please contact us to let us know so we can fix the issue.<\/p>\n Please include the following information:<\/p>\n \n The location of the problem by providing a web address or page description<\/li>\n A description of the problem<\/li>\n The computer, software, browser, and any assistive technology you are using that can help us diagnose and solve your issue\n \n e.g., Windows 10, Google Chrome (Version 65.0.3325.181), NVDA screenreader<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n You can contact us one of the following ways:<\/p>\n \n Email: helpdesk@bccampus.ca<\/a><\/li>\n Web form: Report an Open Textbook Error<\/a> form<\/li>\n<\/ul>\n This statement was last updated on August 21, 2018. <\/strong><\/p>\n<\/div>\n<\/div>\n Additional resources<\/h1>\n For more information, refer to the following resources:<\/p>\n \n Web Content Accessibility Guidelines: Conformance Claims<\/a><\/li>\n Nomensa: How to Write an Accessibility Statement<\/a><\/li>\n Access 8878’s Accessibility Statement<\/a><\/li>\n<\/ul>\n For sample accessibility statements, refer to the following pages:<\/p>\n \n B.C. Government Website’s Accessibility Statement<\/a><\/a><\/li>\n Hassell Inclusion’s Accessibility Statement<\/a><\/li>\n<\/ul>\n \"Accessibility Statement,\" Hassellinclusion<\/em>, accessed August 23, 2018, http:\/\/www.hassellinclusion.com\/accessibility\/. ↵<\/a><\/li> \"Creating an Accessibility Statement,\" Access 8878<\/em>, accessed August 30, 2018, https:\/\/web.archive.org\/web\/20161203101842\/https:\/\/www.access8878.co.uk\/getting-started-with-bs-8878\/creating-an-accessibility-statement.aspx. ↵<\/a><\/li><\/ol><\/div>","protected":false},"author":1,"menu_order":9,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":["jgray"],"pb_section_license":""},"chapter-type":[],"contributor":[60],"license":[],"part":33,"_links":{"self":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters\/54"}],"collection":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters\/54\/revisions"}],"part":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/parts\/33"}],"metadata":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapters\/54\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/media?parent=54"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/pressbooks\/v2\/chapter-type?post=54"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/contributor?post=54"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pb.malartu.org\/accessibilitytoolkit\/wp-json\/wp\/v2\/license?post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

What is an accessibility statement?<\/h1>\nAn accessibility statement acts as resource for those who have questions about the accessibility features of your resource. It should provide an overview of accessibility features and contact information in case there are any problems.\n

What do you need to do?<\/h1>\nHere are tips for writing a useful accessibility statement:\n\n \tUse clear and simple language, avoiding jargon and technical terms<\/li>\n \t

What is an accessibility statement?<\/h1>\nAn accessibility statement acts as resource for those who have questions about the accessibility features of your resource. It should provide an overview of accessibility features and contact information in case there are any problems.<\/p>\n

Who are you doing this for?<\/h1>\nWhen writing an accessibility statement, it is important to keep in mind who the statement is for. This will guide the language you use and the type of information you include. Ultimately, the accessibility statement is for people who have disabilities.<\/p>\n

What do you need to do?<\/h1>\nHere are tips for writing a useful accessibility statement:<\/p>\n\nUse clear and simple language, avoiding jargon and technical terms<\/li>\n

What is an accessibility statement?<\/h1>\n
An accessibility statement acts as resource for those who have questions about the accessibility features of your resource. It should provide an overview of accessibility features and contact information in case there are any problems.<\/p>\n