The product has to
hold up when you use it.

Winglo is for operators. An operator who uses a keyboard, a screen reader, a reduced motion setting, or a higher contrast preference should be able to hire an AI department, read a brief, and approve work without a workaround that only a mouse user has.

That is a design rule, not a badge. This page says what we aim at, what is already built into the surfaces, what we know is unfinished, and how to ask for help.

This statement covers:

• The public marketing site at winglo.ai, including this page
• The signed-in Service (the workspace and the operator console)
• Documents we publish here: Privacy, Terms, the DPA, Security, and this statement

It does not cover third-party tools you connect (for example Slack, HubSpot, or a model provider's own console), or content a Customer pastes into a workspace. Those surfaces follow their owners' statements.

We design and review against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. For European procurement, that is the technical path we use to align with EN 301 549.

Designing toward a level is not the same as conforming to it. We will not say the Service is WCAG 2.2 AA conformant, ADA compliant, or EN 301 549 certified until a dated assessment says so. When that assessment exists, this page will carry the date and the report will be available under the process in Section 8.

These controls are already part of how the surfaces are built:

• A single token system for colour, type, and focus. Contrast is a property of the tokens, not a one-off choice in a screen
• Status and severity are never colour alone. Labels, copy, or an icon travel with the colour
• Visible focus on interactive controls
• Semantic headings, labels, and landmarks on the marketing site and on the main workspace shells
• Keyboard operation of primary navigation, forms, and dialogs
• Respect for prefers-reduced-motion: authored motion is off unless the user has no such preference
• Text alternatives on informative images. Decorative images are hidden from assistive technology
• A cookie banner that can be accepted or rejected with a keyboard

An honest statement names the gaps. These are the ones we will not pretend are closed:

• No third-party WCAG audit and no published VPAT or ACR on this site
• Some marketing compositions are visual first (workspace previews, boards, logs). They have accessible names, but they are not a full equivalent of the signed-in product
• Customer-generated Output and connected third-party views are outside our control. We cannot certify a PDF, image, or embed a Customer publishes
• Complex data views in the Service (tables, live feeds, report bodies) are still being brought to the same keyboard and reader quality as the simpler screens

Finding a gap and writing it down is not the same as leaving it. A report to [email protected] is how a gap becomes work.

We test against current versions of Chrome, Firefox, and Safari, with keyboard only, and with a screen reader on the primary flows (VoiceOver on macOS, NVDA on Windows) when we change those flows. We do not claim support for every browser, every reader, or every assistive device.

The Service is a web application. It is not a native iOS or Android app.

If a part of the site or the Service is harder to use than it should be, ask. We will work with you on a reasonable accommodation: an alternate format, a described walk through a flow, or a change to the surface when that is the right fix.

We aim to reply within 5 business days. If the request is urgent because you cannot complete a step you need (sign-in, billing, an approval), say so in the subject.

Enterprise customers who need a VPAT, an ACR, or a written mapping to EN 301 549 should request it. We will say what exists, what is in draft, and what is not yet written. We will not send a completed report we do not have.

Security documentation that is not public is shared under NDA, as described on Security. An accessibility report is not a security document. It can be public once it exists.

Email [email protected]. Include the URL, what you were trying to do, the browser and assistive technology if you use one, and what went wrong.

You can also use the contact form with the Accessibility topic. Legal questions about this statement: [email protected].