Hold Right Plumbing

Accessibility Statement

Last updated: June 8, 2026

Our commitment

Hold Right Plumbing is committed to making our website accessible to as many people as possible, including people with disabilities. We work to follow widely accepted accessibility guidelines and to continually improve the experience for every visitor.

Standards we follow

We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, hearing, cognitive, and motor impairments.

What we do

  • Provide descriptive alt text for meaningful images.
  • Use semantic HTML and ARIA landmarks for screen reader navigation.
  • Maintain visible focus indicators for keyboard users.
  • Keep color contrast at or above WCAG 2.1 AA minimums.
  • Ensure form fields have labels and clear error messages.
  • Support keyboard navigation throughout the site.
  • Provide a “Skip to main content” link on every page.
  • Use responsive layouts that adapt to mobile, tablet, and desktop.

Limitations

Despite our efforts, some content on our site may not yet be fully accessible. We are actively working on improvements and welcome feedback so we can address issues quickly.

Reporting an accessibility issue

If you encounter an accessibility barrier on our website, or if you need information in a different format, please contact us:

Please describe the page, the issue, and the device or assistive technology you were using. We aim to respond to accessibility feedback within five business days.

Service accessibility

Beyond the website, Hold Right Plumbing is committed to delivering plumbing services to customers of all abilities. If you need accommodations during a service visit, please let us know when you call so we can plan ahead.

Website accessibility edits

For technical changes to the website itself — fixes to alt text, contrast, focus states, screen-reader behavior, or any other code-level accessibility issue — reach out to our developer directly: