Large Print Standards Sample Clauses

Large Print Standards. Large Print materials provided pursuant to this Agreement shall have the following features: (i) a font size of at least 18 points; (ii) a sans serif font, such as Arial or Verdana, in bold; (iii) limited, if any, use of ALL CAPITALS; (iv) no use of italics; (v) print on suitable non- glossy paper; (vi) block paragraphs; (vii) page numbers in the top outer corner of each page in the same font as other text on the page; (viii) emphasis provided by setting text apart with stars or lines, and not using colored text; (ix) appropriate use of white space. If, during the Term of this Agreement, Claimant notifies ACS in writing that Large Print materials provided pursuant to this Agreement do not have the features set forth in this Section, ACS will forward the notice to its Large Print vendor(s) for response. ACS will use good faith efforts to arrange a conference call with Xxxxxxxx and the vendor to discuss the vendor’s response to the notice. No dispute regarding this section will be initiated under Section 9 of this Agreement until at least 90 days after such notice.
AutoNDA by SimpleDocs
Large Print Standards. Large Print materials provided pursuant to this Agreement shall comply, whenever possible, with the Best Practices and Guidelines for Large Print Documents used by the Low Vision Community, issued by the Council of Citizens with Low Vision (“CCLVI Standards”) for printing and binding Large Print materials, currently found at xxxx://xxx.xxxxx.xxx/large-print-guidelines.html. If, during the Term of this Agreement, Claimants notify Weight Watchers in writing that Large Print materials provided pursuant to this Agreement are not in compliance with the CCLVI Standards, Weight Watchers will forward the notice to its Large Print vendor(s) for response. Weight Watchers swill use good faith efforts to arrange a conference call with Claimants and the vendor to discuss the vendor’s response to the notice. No dispute regarding this section will be initiated under Section 11 of this Agreement until at least 30 days after such notice.

Related to Large Print Standards

  • Content Standards You agree that you will not upload or provide content or otherwise post, transmit, distribute, or disseminate through the Zelle® Payment Service any material that: (1) is false, misleading, unlawful, obscene, indecent, lewd, pornographic, defamatory, libelous, threatening, harassing, hateful, abusive, or inflammatory; (2) encourages conduct that would be considered a criminal offense or gives rise to civil liability; (3) breaches or infringes any duty toward or rights of any person or entity, including rights of publicity, privacy or intellectual property; (4) contains corrupted data or any other harmful, disruptive, or destructive files; (5) advertises products or services competitive with Zelle®, as determined by Zelle® in its sole discretion; or (6) in Zelle®’s or our sole judgment, is objectionable, restricts or inhibits any person or entity from using or enjoying any portion of the Zelle® Payment Service, or which may expose us, Zelle® or our respective affiliates or customers to harm or liability of any nature.

  • Procurement Standards For projects being managed by the Local Government and on the State highway system or that include state funding, the Local Government must obtain approval from the State for its proposed procurement procedure for the selection of a professional services provider, a contractor for a construction or maintenance project, or a materials provider.

  • Development Standards For any structure built on the Property following the Effective Date, it shall comply with the requirements contained in Exhibit B, “Building Materials,” attached hereto and incorporated herein. The Parties agree and acknowledge that the provisions of this Paragraph shall apply to any structure constructed subsequent to the execution of this Agreement. Nothing in this Agreement shall be deemed to modify or otherwise amend any zoning regulation duly adopted by the Town, previously or in the future.

  • APARTMENT OWNERSHIP ACT (OF THE RELEVANT STATE The Promoter has assured the Allottees that the project in its entirety is in accordance with the provisions of the [Please insert the name of the state Apartment Ownership] Act). The Promoter showing compliance of various laws/regulations as applicable in .

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • OMB Standards Unless specified otherwise within this agreement, the Subrecipient shall procure all materials, property, or services in accordance with the requirements of 24 CFR 84.40−48.

  • General Guidelines Conduct yourself in a responsible manner at all times in the laboratory.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Applicable Standards The requirements and guidelines of NERC, the Applicable Regional Entity, and the Control Area in which the Customer Facility is electrically located; the PJM Manuals; and Applicable Technical Requirements and Standards.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!