Microsoft + ClaudeOne partner for the cloud you run and the AI you put on top of it.
Avalon Web ServicesMicrosoft · Claude · Security
Accessibility

Built for every visitor.

We want every prospective customer, employee, partner, and auditor to be able to read, navigate, and act on this site — regardless of assistive technology in use.

Last reviewed · May 2026

01 · Commitment

Our conformance target

Avalon Web Services targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across awservices.org. WCAG 2.1 AA aligns with U.S. federal procurement expectations under Section 508 of the Rehabilitation Act and the Americans with Disabilities Act (ADA) Title III as currently interpreted.

We treat accessibility as part of the engineering definition of done. New page templates are reviewed against WCAG 2.1 AA criteria — semantic structure, color contrast, focus visibility, keyboard reachability, alternative text, and assistive-technology compatibility — before they ship.

02 · Measures we take

How we get there

Semantic HTML for headings, lists, landmarks, and form controls. ARIA only where native semantics fall short. Visible focus indicators on every interactive element. A color palette tuned for AA contrast on body and interactive text — with two small decorative brand-accent labels excepted (see Known limitations).

Keyboard-first navigation: every link, button, and form field is reachable and operable without a pointing device. Form errors are announced to assistive technology, not just rendered visually. Motion-reduced experiences honor the prefers-reduced-motion media query.

03 · Known limitations

What we haven't fixed yet

No commitment is credible without an honest gap list. As of the date above, the following are known limitations we are tracking to remediate:

  • Decorative third-party badges and partner marks may lack long-form descriptions; we are working with partners on accessible alternates.
  • Embedded PDFs (resource downloads) are not yet uniformly tagged for screen readers. We tag new PDFs as they are published and are migrating older assets.
  • Some animated reveal effects rely on prefers-reduced-motion detection; users without that preference set still receive motion. We may move to a site-level reduced-motion toggle.
  • Two small decorative labels rendered in our brand accent color (the top-banner ticker and the “Pricing” label on package cards) measure below the 4.5:1 AA contrast ratio in light mode. This is a deliberate brand exception: the information they carry is duplicated by adjacent AA-conformant text, and all body, heading, and interactive text meets AA.

04 · Reporting a barrier

If something doesn't work for you

Email sales@awservices.org with the URL, the assistive technology in use (if any), a description of the barrier, and any screenshots or screen-reader output that help us reproduce it. We acknowledge within one business day and provide a written response within ten business days with either a fix or a documented remediation plan.

If we cannot make a specific page or function accessible, we will provide the equivalent information through an alternative channel — typically email or a 30-minute walkthrough call.

05 · Formal standards

What we conform to

Standard: Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Tested with: automated axe-core audits run against both color themes, plus keyboard-only navigation across current versions of Chrome, Edge, and Firefox. Screen-reader passes (NVDA, VoiceOver) are performed as page templates change — if you hit a barrier our tooling missed, the channel below gets a response within one business day.

Last review: May 2026. We re-review against the latest WCAG version at least annually and when major template changes ship.