IT Accessibility Standard Sample Clauses

IT Accessibility Standard. Contractor acknowledges and is fully aware that the State of Minnesota (Executive branch state agencies) has developed IT Accessibility Standard effective September 1, 2010. The standard entails, in part, the Web Content Accessibility Guidelines (WCAG) and Section 508 which can be viewed at: xxxxx://xx.xxx/mnit/government/policies/accessibility/. The Standards apply to web sites, software applications, electronic reports and output documentation, training delivered in electronic formats (including, but not limited to, documents, videos, and webinars), among others. As upgrades are made to the software, products, or subscriptions available through this Contract, the Contractor agrees to develop functionality which supports accessibility. If any issues arise due to nonconformance with the above-mentioned accessibility Standards, the Contractor agrees to provide alternative solutions upon request at no additional charge to the State. When updates or upgrades are made to the products or services available through this Contract, the Contractor agrees to document how the changes will impact or improve the product’s or service’s accessibility and usability. This documentation, upon request, must be provided to the State in advance of the change, occurring within an agreed upon timeframe sufficient for the state to review the changes and either approve them or request a remediation plan from the Contractor. Contractor warrants that its Products comply with the above-mentioned accessibility Standards and agrees to indemnify, defend, and hold harmless the State against any claims related to non-compliance of Contractor’s Product with the above-mentioned accessibility Standards. If agreed-upon updates fail to improve the product or service’s accessibility or usability as planned, the failure to comply with this requirement may be cause for contract cancellation or for the State to consider the Contractor in default. Nonvisual Access Standards.
AutoNDA by SimpleDocs
IT Accessibility Standard. The State of Minnesota (Executive branch state agencies) has developed IT Accessibility Standard effective September 1, 2010. The standard entails, in part, the Web Content Accessibility Guidelines (WCAG) 2.0 (Level AA) and Section 508 which can be viewed at: xxxxx://xx.xxx/mnit/government/policies/accessibility/. The Standards apply to web sites, software applications, electronic reports and output documentation, training delivered in electronic formats (including, but not limited to, documents, videos, and webinars), among others. As upgrades are made to the software/products/subscriptions available through this Contract, the Contractor agrees to develop functionality which supports accessibility. If any issues arise due to nonconformance with the above mentioned accessibility Standards, the Contractor agrees to provide alternative solutions upon request at no additional charge to the State. When updates or upgrades are made to the products or services available through this Contract, the Contractor agrees to document how the changes will impact and/or improve the product’s/service’s accessibility and usability. This documentation, upon request, must be provided to the State in advance of the change, occurring within an agreed upon timeframe sufficient for the state to review the changes and either approve them or request a remediation plan from the Contractor. If agreed-upon updates fail to improve the product or service’s accessibility or usability as planned, the failure to comply with this requirement may be cause for contract cancellation or for the State to consider the Contractor in default.
IT Accessibility Standard. ‌‌ The State of Minnesota requires all information and communication technology (ICT) products or services to support the Minnesota IT Accessibility Standard. The standard, effective September 1, 2010, entails, in part, the Web Content Accessibility Guidelines (WCAG) 2.0 (Level AA) and Section 508. Select this link to view a PDF of the standard. All contracted products and services must include documentation of how they support the standard.‌ The Standards apply to web sites, software applications, electronic reports and output documentation, training delivered in electronic formats (including, but not limited to, documents, videos, and webinars), among others. As upgrades are made to the software/products/subscriptions available through this Contract, the Contractor agrees to develop functionality which supports accessibility. If any issues arise due to nonconformance with the above-mentioned accessibility Standards, the Contractor agrees to provide alternative solutions upon request at no additional charge to the State.

Related to IT Accessibility Standard

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • Reliability Standard Seller agrees to abide by (i) CPUC General Order No. 167, “Enforcement of Maintenance and Operation Standards for Electric Generating Facilities”, and (ii) all applicable requirements regarding interconnection of the Project, including the requirements of the interconnected Participating Transmission Owner.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference. Adherence to these accessible technology standards is one way to ensure compliance with the College’s underlying legal obligations to ensure that people with disabilities are able to acquire the same information, engage in the same interactions, and enjoy the same benefits and services within the same timeframe as their nondisabled peers, with substantially equivalent ease of use; that they are not excluded from participation in, denied the benefits of, or otherwise subjected to discrimination in any College programs, services, and activities delivered online, as required by Section 504 and the ADA and their implementing regulations; and that they receive effective communication of the College’s programs, services, and activities delivered online.

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Accessibility Supplier warrants that all Products will meet the requirements set forth in all federal, state, local and foreign laws, rules, and regulations applicable to accessibility of information technology for people with disabilities. Supplier agrees to use personnel trained and knowledgeable in supporting the needs of persons with disabilities in performance of Services under this Order.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

Time is Money Join Law Insider Premium to draft better contracts faster.