Accessibility

We want everyone who visits the Haldane website to feel welcome and find the experience rewarding.

To help us make the Haldane website a positive place for everyone, we've been using the Web Content Accessibility Guidelines (WCAG) 2.0. These guidelines explain how to make web content more accessible for people with disabilities, and user friendly for everyone.

 

Let us know what you think

If you enjoyed using the Haldane website, or if you had trouble with any part of it, please get in touch. We'd like to hear from you in any of the following ways:

 

Haldane Central School District Website Accessibility Policy

Draft 3/19/18 - under review by the Board of Education

It is the goal of the Haldane Central School District that the information contained in our website be accessible to individuals with visual, hearing, or cognitive disabilities.

Good faith efforts have been made to ensure that our site complies with New York State standards on website accessibility.

The majority of pages in our site are available in HTML format that can be deciphered by screen readers. Some documents are in Adobe PDF format, which require Adobe Acrobat Reader to view. If you do not already have Adobe Acrobat Reader on your computer, you can download it for free from the Adobe website.

If you are unable to access any page(s) or documents on our site, please contact mshields@haldaneschool.org with detailed information on the location of the page or document you were attempting to access. Be sure to include your name, email address, and phone number so that we may follow up with you to provide you with the information in another format. You may also call 845-265-9254, ext. 220 if you are having trouble.

Please note that some pages on the Haldane website contain links to third party sites, which are not within our control and may not comply with accessibility standards. The district is not responsible for the content or accessibility of third-party sites.

 

This accessibility statement was generated on November 10, 2017 using the Accessibility Statement Generator.