Accessibility statement. Including the parts we have not fixed.

Everyone should be able to use this site.

Pyxl is committed to making pyxl.com usable by everyone, including people who use screen readers, keyboard-only navigation, magnification, voice control, or other assistive technology. Accessibility is something we work on continuously rather than something we finish.

We publish a field brief on accessibility litigation and what remediation actually involves. It would be poor form to publish that and not hold this site to the same test, so this page names what we have done and what we have not, specifically enough that you can check it.

WCAG 2.2 Level AA.

These guidelines are the widely accepted standard for making web content perceivable, operable, understandable and robust. They are also the standard most commonly cited in demand letters, which is a second reason to meet them.

This site is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the site meets the standard and we are actively working on the parts that do not. The parts that do not are listed below by name.

Built in, rather than added on.

• One focus ring, authored centrally. Every link, button, summary, input and tabbable element gets the same visible 2px outline with a 3px offset, declared once in the stylesheet so no inline style can silently drop it. It flips to paper on dark grounds.
• Colour is never the only carrier. Where the two practices are coded blue and coral — the hero weave, the client index, the sector chart — the same distinction is also stated in words. Contrast ratios for every text colour on both grounds are documented in the colour tokens, with the failing variants remapped rather than used.
• A type floor on phones. Nothing renders below 11px at phone width. Our micro-label is an editorial device at a 1240px measure; carried down unchanged it becomes small print, so below 700px it steps up rather than shrinking with the layout.
• Targets sized for a thumb. Stacked links, list rows, filters and form controls are at least 24px, and interactive rows in the instruments are at least 44px.
• Motion that can be switched off. Every animation on the site, including the hero, resolves instantly to its final state under prefers-reduced-motion. Nothing flashes, and nothing moves without the reader having done something.
• Keyboard operation throughout. A skip link on every page, a real focus trap in the phone menu, arrow-key traversal in the sector list, and Escape closing anything that opens.
• Reflow to 320px. At 400% zoom on a 1280px viewport the content box is 320px. Nothing scrolls sideways at that width on any page.
• Alternative text with a decision behind it. Images that carry meaning are described. Decorative artwork — the dot fields, the ribbon, the registration marks — is marked so screen readers skip it rather than reading a filename.
• Analytics off until you say yes. No measurement script runs before consent, and the choice is reversible.

Where the gaps are.

We would rather publish these than have you find them.

• This site requires JavaScript to render. It is a client-rendered application: with scripts blocked or failing, the page is empty rather than degraded. That is the largest accessibility and discoverability limitation here, we know it, and pre-rendering the pages to static HTML is the open engineering item on this build. Until it ships, everything on this site is also available by phone or email.
• Fourteen strings still render below 11px on a phone. Across five pages. Our last measurement found 1,671 before the type floor and 14 after. They are individual cases rather than a systemic fault, and they are being worked through one at a time.
• The embedded live prototypes. Several pages embed working prototypes hosted separately. They are demonstrations of client work rather than part of this site, and they are not held to this standard. Every one of them can also be opened full size, and we will walk you through any of them.
• Third-party content. Forms, embedded maps and content served by outside providers may not fully meet WCAG 2.2 AA. We raise issues with those providers when we find them, and we will take your information over the phone rather than through a form if that is easier.
• Documents. PDFs and printable worksheets on this site may not be fully tagged. Ask and we will send the same content in an accessible format, at no cost.
• No published third-party audit yet. Our assessment to date is our own: automated testing plus manual keyboard and screen-reader review, run against every page with a harness we built for it. An independent audit is not yet commissioned. We would rather say that than imply one exists.

Tell us, and we will get you what you need in the meantime.

There is no formal process to follow and no ticket to raise. Tell us the page address, what you were trying to do, and what happened. If you use assistive technology, telling us which one helps us reproduce it.

We acknowledge every message within one business day and tell you when a fix is likely. If a fix will take time, we will give you another way to get the same information or complete the same task while you wait — by phone, by email, or in whatever format works for you.

Email

info@pyxl.com

Phone

615-647-6792

Mail

Pyxl, Inc.
1033 Demonbreun St, Suite 300
Nashville, TN 37203

Anything on this site is available from a person.

Call or email and we will answer questions about our services, walk you through any page or prototype, or take your information directly rather than through a form. We can provide materials in large print, plain text, or another format on request, at no cost. A senior person replies — this is not a queue.

What this site is built on, and what it is tested with.

This site relies on HTML, CSS, JavaScript and WAI-ARIA. JavaScript is currently required for the site to render at all, which is the first limitation named above.

It is designed to work with current versions of Chrome, Safari, Firefox and Edge on desktop and mobile, in combination with VoiceOver, NVDA, JAWS and TalkBack. It may not perform as well on older browsers no longer supported by their makers.

Measured, not estimated.

We evaluated this site with a combination of automated testing and manual review, including keyboard-only navigation and screen-reader testing, plus a harness that loads every page side by side at any viewport width so type size, target size and reflow can be counted rather than judged. The figures on this page come from that harness.

We review accessibility again whenever we make significant changes, and at minimum once a year. This page is edited in the same commit as any change that alters what it says.