Develop a Plan to Maintain Accessible Features Sample Clauses

Develop a Plan to Maintain Accessible Features. The MDE will develop a Plan regarding how it intends to maintain the accessibility of the services, programs, and activities communicated or facilitated online, including updated testing and remediation protocols; revised procurement protocols and language; ongoing training for web developers, procurement officials, and content creators; designations of responsibility; and appropriate levels and sources of funding to support ongoing efforts
AutoNDA by SimpleDocs
Develop a Plan to Maintain Accessible Features. The District will develop a Plan regarding how it intends to maintain the accessibility of the services, programs, and activities communicated or facilitated online, including updated testing and remediation protocols; revised procurement protocols and language; ongoing training for web developers, procurement officials, and content creators; designations of responsibility; and appropriate levels and sources of funding to support ongoing efforts
Develop a Plan to Maintain Accessible Features. The University System will develop a Plan regarding how it intends to maintain the accessibility of the services, programs, and activities communicated or facilitated online, including updated testing and remediation protocols; revised procurement protocols and language; ongoing training for web developers, procurement officials, and content creators; designations of responsibility; and appropriate levels and sources of funding to support ongoing efforts.

Related to Develop a Plan to Maintain Accessible Features

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Reporting on Utilization of Subject Inventions 1. The Performer agrees to submit, during the term of the Agreement, an annual report on the utilization of a subject invention or on efforts at obtaining such utilization that are being made by the Performer or its licensees or assignees. Such reports shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the Performer, and such other data and information as the agency may reasonably specify. The Performer also agrees to provide additional reports as may be requested by DARPA in connection with any march-in proceedings undertaken by DARPA in accordance with Paragraph I of this Article. DARPA agrees it shall not disclose such information to persons outside the Government without permission of the Performer, unless required by law.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Implementation of and Reporting on the Project A. The Grantee shall implement and complete the Project in accordance with Exhibit A and with the plans and specifications contained in its Grant Application, which is on file with the State and is incorporated by reference. Modification of the Project shall require prior written approval of the State.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Internet Access to Contract and Pricing Information Access by Authorized Users to Contract terms and pricing information shall be made available and publically posted on the OGS website. To that end, OGS shall publically post the Contract Pricelist, including all subsequent changes in the Contract offerings (adds, deletes, price revisions), Contractor contact information, and the Contract terms and conditions, throughout the Contract term.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-­‐to-­‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • WHO WILL REVIEW THE INFORMATION DISCLOSED ON THE RELATIONSHIP DISCLOSURE FORM AND ANY UPDATES? The information disclosed on this form and any updates will be a public record as defined by Chapter 119, Florida Statutes, and may therefore be inspected by any interested person. Also, the information will be made available to the Mayor and the BCC members. This form and any updates will accompany the information for the applicant’s project or item. However, for development-related items, if an applicant discloses the existence of one or more of the relationships described above and the matter would normally receive final consideration by the Concurrency Review Committee or the Development Review Committee, the matter will be directed to the BCC for final consideration and action following committee review.

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