Pedestrian Design for Accessibility. Within Public Right-of-Way, FHWA (FHWA-SA- 10-005).
Pedestrian Design for Accessibility Sample Clauses
Related to Pedestrian Design for Accessibility
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.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
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.
ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.
System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.
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.
Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:
Connecting Transmission Owner’s Scope of Work and Responsibilities The Connecting Transmission Owner will design, construct, own, operate and maintain all Connecting Transmission Owner’s Interconnection Facilities, except as otherwise stated above and in the Project Specific Specifications. The Connecting Transmission Owner will complete all engineering reviews, field verifications and witness testing, etc. in accordance with the ESBs and the Project Specific Specifications. Connecting Transmission Owner shall provide the revenue metering CT/PT units and meter socket enclosure. The Connecting Transmission Owner shall: provide, run, and wire both ends of the color-coded cable for the revenue metering instrument transformer secondary wiring; perform all terminations; and supply and install the meter. The revenue meter may require a communications link to the RTU. The Connecting Transmission Owner will specify and run those communications cables. The Connecting Transmission Owner shall complete all wiring, testing and commissioning of the RTU.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
