Skip to main content
Trellis Internet

DRAFT — Pending attorney review

This document is a working draft prepared by Trellis Internet staff for review by counsel. It is not a final policy and should not be relied upon as a binding agreement until it is published in non-draft form.

Accessibility Statement

Last updated:

Trellis Internet is committed to making trellisinternet.com usable by everyone, including people with disabilities. This statement describes our approach, the standards we follow, the features we have built in, and how you can reach us if you encounter a barrier.

1. Our Commitment

We believe broadband internet is essential infrastructure, and a provider’s website should not be a barrier to obtaining service. We are continuously working to bring our website into conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We treat accessibility as part of normal product quality, not as an afterthought.

2. Conformance Standard

We target conformance with WCAG 2.1 Level AA, which is the standard cited under Title III of the Americans with Disabilities Act, by federal courts, and by California accessibility case law. Where individual pages or components have not yet reached full Level AA conformance, we treat the gap as a defect to be fixed.

We do not use third-party accessibility “overlay” widgets (such as accessiBe or UserWay). These products have been shown not to provide compliance and can interfere with users’ own assistive technology.

3. Measures We Take

  • Accessibility requirements are part of our design system: color tokens are paired with contrast ratios that meet WCAG AA for normal text and large text.
  • Every interactive component is tested for keyboard operation before it ships. We do not rely on hover for any critical interaction.
  • We run automated accessibility checks (axe-core, Lighthouse) as part of our development workflow.
  • We test major flows with screen readers, including NVDA on Windows and VoiceOver on macOS and iOS.
  • We honor the operating-system prefers-reduced-motion setting throughout the site; ambient animation is disabled and functional transitions are minimized.

4. Accessibility Features

  • Semantic structure: proper heading hierarchy (h1 to h3), landmark regions, lists, and tables with header cells.
  • Keyboard accessibility: every interactive control is reachable and operable from the keyboard. A visible focus indicator is shown on focused elements.
  • Skip-to-content link: a “Skip to main content” link is the first focusable element on every page.
  • Text alternatives: meaningful images have descriptive alt text; decorative images use empty alt attributes so screen readers skip them.
  • Forms: every input has a programmatically associated label; error messages are descriptive and announced to assistive technology; standard fields use autocomplete attributes.
  • Color and contrast: text meets at least 4.5:1 contrast for normal text and 3:1 for large text and UI components, as required by WCAG 1.4.3 and 1.4.11.
  • Resizing and reflow: the site is readable and functional at 200% zoom and reflows to a single column at 320 CSS pixels wide.
  • Language declaration: the page language is set via the lang attribute so screen readers pronounce content correctly.
  • Coverage map alternatives: a text-based address checker provides the same functionality as the visual coverage map for users who cannot interact with maps.

5. Known Limitations

Despite our efforts, some areas of the website may not yet meet full WCAG 2.1 AA conformance. Known limitations as of the date above include:

  • Interactive coverage map: the map is keyboard-operable and includes a text alternative, but some zoom and pan gestures are more discoverable with a pointing device. We continue to improve the keyboard experience.
  • Embedded marketing media: some embedded videos may lack synchronized captions or audio descriptions. We are adding captions as content is produced.
  • Broadband Facts labels: the FCC mandates a specific layout for these labels; we have implemented them as real HTML text with table semantics, but the visual layout is constrained by the regulation.

If you encounter another barrier, please tell us using the contact information in Section 9. We track every accessibility report and use it to prioritize fixes.

6. Third-Party Content

Our website integrates a small number of third-party services (for example, payment processing and analytics). We choose vendors that publish their own accessibility conformance information, but we cannot guarantee the accessibility of content or interfaces controlled by third parties. If you encounter a barrier in third-party content, please report it to us so we can work with the vendor or provide an alternative.

7. Assistive Technology Compatibility

The site is designed to be compatible with recent versions of:

  • NVDA (Windows)
  • JAWS (Windows)
  • VoiceOver (macOS and iOS)
  • TalkBack (Android)
  • System-level keyboard navigation
  • Browser-level zoom up to 200% and reflow at 320 CSS pixels

We test in current versions of Safari, Chrome, Edge, and Firefox. Older or non-standard browsers may have degraded support.

8. Alternative Formats

If a page on our website is not accessible to you, we are happy to provide the information in an alternative format — including by telephone, large print, or plain-text email. There is no charge for this service. Contact us using the information in Section 9.

9. Feedback and Assistance

We welcome feedback on the accessibility of our website. If you encounter a barrier, please tell us so we can fix it. We aim to acknowledge accessibility feedback within two (2) business days and resolve specific issues within thirty (30) days, depending on complexity.

10. Formal Complaints

If you are not satisfied with our response, you may file a complaint with:

11. Updates to This Statement

We update this statement when our accessibility posture materially changes — including when we close a known limitation, when we add a major feature, or when applicable standards are revised. The “Last updated” date at the top of the page reflects the most recent revision.