Accessibility on this website.
At The High Lonesome Ranch, we want everyone to have the best possible experience, both in person and online. https://thehighlonesomeranch.com/ provides several methods that can help with access to our website, including supporting accessibility features outlined in the Web Content Accessibility Guidelines (WCAG) 2.1. We constantly monitor ADA compliance through Site Improve to ensure WCAG 2.1 standards are being met.
Despite the efforts we may have made regarding accessibility, some content or features may be improved, so we welcome your feedback. Email us at firstname.lastname@example.org with any questions or comments you have.
Tech stack and third party services.
https://thehighlonesomeranch.com/ is optimized for both Chrome and Safari web browsers on desktop computers and mobile phones. To ensure the best experience, please keep your technology up to date. Use the latest version of your web browser and the latest version of any assistive technology.
This website may use third-party add-ons for certain functionality, such as displaying maps via Google Maps, optimizing images, email marketing and other applications that are used to improve your browsing experience.
We do not control the functionality of third-party services, and some features may not work the same for every user or every type of disability. We cannot always modify these apps and services to accommodate every user as we don’t have full control over them. We are not responsible for any of these elements that we do not control.
Do you need assistance?
The High Lonesome Ranch will work with you to ensure that you have full access to the information available to the public on our site. If you have found an inaccessible part of our website, please specify the website page and or element and any relevant information so we can locate and fix the problem. If we cannot make this element accessible, we will work to serve you this content via an alternative method.
Please contact us at either of the following if you are having accessibility issues: