xavriqon.com aims for WCAG 2.2 AA, and four gaps are still open.

We build xavriqon.com to the Web Content Accessibility Guidelines 2.2 at level AA. That is a target, not a certificate. Nobody outside the office has audited the site and we do not display a seal or a score from an automated checker, because a green number from a scanner tells you very little about whether a person using a screen reader can send us a letter.

Our assessment is partial conformance. Most pages meet the target. The gaps listed under A.3 are the ones we know about.

• Every page opens with a skip link to the main content, and has exactly one top-level heading.
• Body text is near-black ink on warm paper. The ink-on-paper pair measures above 15:1; the stone gray used for captions and meta lines stays above 4.5:1 on the paper ground.
• Buttons, links, chips and form controls are at least 44 by 44 CSS pixels. Labels wrap instead of clipping.
• Focus is drawn as a clay-colored ring two pixels wide, offset from the control so it never hides the label.
• The giant index numerals are decorative. They are hidden from assistive technology or duplicated by real text beside them.
• Every form field has a visible label. Errors are written in words next to the field, not shown by color alone.
• The layout reflows from 320 CSS pixels wide without sideways scrolling, and text can be zoomed to 200% without loss.
• When your system asks for reduced motion, the sticky photographs on the contents page stop pinning and stack as plain figure and text, and the read-progress bar is removed.

Four things fall short today. We would rather list them than pretend.

• Chat widget announcements. New replies in the support chat are announced through a polite live region, but some screen reader and browser pairs read the whole message log again instead of the new line. Written email avoids the problem entirely.
• Date inputs on the fit checker. The fit checker uses the browser's own date field. On a few older mobile browsers that field is awkward with a screen reader. The checker still lists every route as plain text below the panel, so the answer is reachable without the inputs.
• Web fonts. The type is loaded from Google Fonts. If that request is blocked, text falls back to Georgia and a system sans. It stays readable, but line lengths shift and one or two headings break on a different word.
• Photograph descriptions. Alt text describes what is in each photograph in one line. It does not describe mood or light. If a picture carries meaning you are missing, tell us and we will write a longer description.

Each page is walked with a keyboard only, then with VoiceOver on Safari and NVDA on Firefox, then at 320 pixels wide and at 400% zoom on a desktop browser. We check widths of 320, 360, 414, 768, 1024, 1440 and 1920 pixels. That is the whole method. It catches most problems and misses some, which is why A.5 exists.

Email [email protected] with the word "accessibility" in the subject, or call +1 (378) 555-8712. A letter to 152 Oak Lane, Suite 4, Austin, Texas 33038 also works and gets the same treatment. Useful things to include, if you have them:

• The page address, or just its name from the index.
• What you were trying to do, and where it stopped.
• Your browser and any assistive technology you use.
• Whether the problem shows up on a phone, a desktop, or both.

You do not need technical words. "The button on the contact page does nothing when I press Enter" is a perfect report.

We aim to acknowledge a barrier report within three business days, the same working rule as every other letter, and to say plainly whether and when we can fix it. If the barrier blocks you from sending a letter, we will take the letter by phone or post instead. The contact page lists every route.

Links leave the site in a few places: the Microsoft privacy statement on the privacy page, a plain map link under the address, and your own mail client when you press an email address. We cannot fix the accessibility of those destinations. We can tell you the same information another way, so ask.

Personal data questions have their own route and clock. Use the data request page for those, and the terms of use for what the site does and does not promise.