Accessibility
- Home
- About Us
Accessibility Statement for DUG Health
Effective Date: March 5, 2026
Last Audit Date: March 1, 2026
At DUG Health, we are committed to ensuring digital accessibility for all users, including people with disabilities. We strive to provide a website experience that is accessible, inclusive, and user-friendly for everyone, regardless of ability or technology.
Accessibility Standards
Our goal is to conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as established by the World Wide Web Consortium (W3C). These guidelines help make web content more accessible to a wide range of people with disabilities, including visual, auditory, motor, and cognitive challenges.
We continually work to improve accessibility and to adhere to best practices in accessibility design and evaluation.
Ongoing Monitoring and Maintenance Policy
To maintain and improve accessibility:
We conduct regular internal accessibility reviews of the website.
We perform external audits at least annually to ensure WCAG 2.1 AA compliance.
Accessibility checks are integrated into our ongoing website update and development processes.
We actively monitor changes in accessibility standards and emerging technologies to improve accessibility where possible.
Known Limitations
While we are committed to accessibility, there may be some areas of the site that still need improvement. We are actively working on enhancements and welcome feedback to identify issues we may have missed.
If you encounter accessibility barriers, please contact us using the details below so we can resolve the issue.
Feedback and Contact
We welcome your feedback about the accessibility of dughealth.org.
Accessibility Contact Email:
📧 info@dughealth.org
Please include the following when reporting an issue:
- Web page URL
- A description of the accessibility concern
- The device and browser you were using (if known)
Response Timeframe
We aim to respond to all accessibility inquiries within 5 business days. If you need assistance right away, please indicate that in your message.