ATTACHMENT 6.12 Vendor Product Accessibility Statement and Documentation Purpose of Accessibility Statement An effective Accessibility Statement includes several key components including: A clear statement of commitment to ensuring equal access for all users Required written documentation on the of conformance with THEC/TBR accessibility standards Information for users with disabilities regarding product/service accessibility features and gaps A mechanism to allows users to provide accessibility feedback Links to resources (internal or external) that provide additional or related information Key Components Commitment Statement Emphasize commitment to ensuring the accessibility of the product/service. Note any ongoing efforts to monitor for and remediate accessibility issues as they are identified. Required Documentation Provide written documentation on how the product/service meets the THEC/TBR accessibility standards, / Voluntary Product Accessibility Template () And (if applicable) any available accessibility testing results List any third-party agencies with whom you have worked to evaluate accessibility support Describe any formal testing process you use to determine accessibility support Indicate if you conduct user testing with persons with disabilities to verify accessibility support and include the Form when standards conformance is not fully achieved to demonstrate vendor’s planned roadmap to full conformance. Provide links to any other internal accessibility documentation (e.g., accessibility information within general product documentation, FAQs, best practices, tutorials, case studies, or white papers). Note any other best practices or guidelines utilized during design and development (if applicable). Product Usage Information for Users with Disabilities Describe any product features that may improve accessibility for users with disabilities including: Accessibility-specific features (e.g. the ability to adjust font size and color/contrast settings for text or the availability of closed captions for videos) General product features that may especially benefit users with disabilities (e.g. an 5’ ‘HTML mode optimized for mobile platforms that also improves keyboard-only navigation). Describe any high-impact product accessibility gaps along with suggested interim workarounds that allow users to complete key tasks until the gaps are resolved. For example, if a technical support website isn’t compatible with screen readers used by the blind, appropriate interim workarounds might include: Alternative business processes that bypass the accessibility barrier (e.g. providing phone-based support until the web-based support site is accessible) Use of a product to replace or supplement inaccessible product functions (e.g. indicating that users may submit or check the status of technical support tickets via email).
ATTACHMENT 6.12 Vendor Product Accessibility Statement and Documentation Purpose of Accessibility Statement An effective Accessibility Statement includes several key components including: A clear statement of commitment to ensuring equal access for all users Required written documentation on the of conformance with THEC/TBR accessibility standards Information for users with disabilities regarding product/service accessibility features and gaps A mechanism to allows users to provide accessibility feedback Links to resources (internal or external) that provide additional or related information Key Components Commitment Statement Emphasize commitment to ensuring the accessibility of the product/service. Note any ongoing efforts to monitor for and remediate accessibility issues as they are identified. Required Documentation Provide written documentation on how the product/service meets the THEC/TBR accessibility standards, / Voluntary Product Accessibility Template () And (if applicable) any available accessibility testing results List any third-party agencies with whom you have worked to evaluate accessibility support Describe any formal testing process you use to determine accessibility support Indicate if you conduct user testing with persons with disabilities to verify accessibility support and include the Form when standards conformance is not fully achieved to demonstrate vendor’s planned roadmap to full conformance. Provide links to any other internal accessibility documentation (e.g., accessibility information within general product documentation, FAQs, best practices, tutorials, case studies, or white papers). Note any other best practices or guidelines utilized during design and development (if applicable). Product Usage Information for Users with Disabilities Describe any product features that may improve accessibility for users with disabilities including: Accessibility-specific features (e.g. the ability to adjust font size and color/contrast settings for text or the availability of closed captions for videos) General product features that may especially benefit users with disabilities (e.g. an ‘HTML 5’ mode optimized for mobile platforms that also improves keyboard-only navigation). Describe any high-impact product accessibility gaps along with suggested interim workarounds that allow users to complete key tasks until the gaps are resolved. For example, if a technical support website isn’t compatible with screen readers used by the blind, appropriate interim workarounds might include: Alternative business processes that bypass the accessibility barrier (e.g. providing phone-based support until the web-based support site is accessible) Use of a product to replace or supplement inaccessible product functions (e.g. indicating that users may submit or check the status of technical support tickets via email).
rfp-tbr-template-for-etsu-format-use-this-one-as-of-6-2-17-dl.docx