Legal
Accessibility
This site is built to WCAG 2.1 Level AA. Every deploy is blocked automatically if the accessibility score drops below 95, so the standard is enforced by the build rather than by good intentions. If something here does not work for you, tell us and we will fix it.
What standard is this site built to?
WCAG 2.1 Level AA, published by the W3C. That sets a minimum contrast ratio of 4.5:1 for body text and 3:1 for large text and interface components, requires every function to be reachable by keyboard alone, and requires the page to reflow to a 320 px viewport and to 200% zoom without horizontal scrolling or loss of content.
How is that checked?
Two ways. Every push runs an automated audit as part of the Netlify build, with the accessibility threshold set to 0.95; a build that scores lower fails and the previous version stays live. On top of that the layout is checked at 320, 375 and 768 px, and interactive targets on phones are set to at least 30 px so they can be hit reliably with a thumb.
What has been done to the markup?
- Semantic HTML with one
mainlandmark per page and a skip link as the first focusable element - Keyboard operable navigation, dropdown menus, disclosure widgets and the multi-step form, all with visible focus indicators
- Every question on the FAQ and Answers pages sits in a real heading, so screen reader users can jump between them by heading level
- Text alternatives on all 23 photographs and on every icon that carries meaning; decorative marks are hidden from assistive technology
- Animation and transitions are disabled automatically when the operating system requests reduced motion
- Form fields have persistent labels rather than placeholder-only labels, and errors are announced rather than shown by color alone
- Tables of specifications and comparisons use real row and column headers, so a screen reader can announce the cell context
What are the known limitations?
Two. Comparison tables on the packages pages are wider than a phone screen and scroll horizontally inside their own container; the content is reachable but it takes more swiping than we would like. And the embedded map on the service-area pages is a third-party component whose keyboard behavior we do not control. We will replace both when there is a better option.
What do you do if something does not work?
Tell us and we will fix it. Email sales@eliteconnectva.com or call 804-445-9674 and describe what you were trying to do and what happened instead. We treat an accessibility defect as a bug rather than a feature request, and we will confirm receipt and tell you what we intend to do about it.