Mayd It LLC / Accessibility

Accessibility Statement

Last updated 12 September 2026. We want everyone to be able to use the May’d It tools. This page says what we aim for, where we honestly stand today, what is not yet fully accessible, and — most importantly — how to reach a real person if something is getting in your way.

The short version

We aim for WCAG 2.1 Level AA across mayd-it.com and our tools.
Every non-game page passes our automated WCAG 2.1 AA checks. The browser games are the known exception (below).
Our browser games are not fully accessible — they are fast, visual, mouse and controller experiences.
Hit a barrier? Email bmay@mayd-it.com. A real person answers, aims to reply within 5 business days, and will get you the information or service another way.

1. Our commitment

Mayd It LLC is committed to making its website and tools usable by as many people as possible, including people who use screen readers, keyboard-only navigation, screen magnification, or other assistive technology. Our target standard is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and we treat accessibility as ongoing work rather than a one-time box to tick.

2. Where we stand today (the honest version)

We test our pages with the axe-core automated engine and with manual checks. We would rather tell you the real state than claim a badge we have not earned. As of the date above:

Our main site, including this page, the Terms and Privacy pages, passes our automated WCAG 2.1 AA checks with no violations.
As of this update, every non-game page — the main site and all tool pages — passes our automated axe-core WCAG 2.1 AA checks with zero violations, including colour contrast, page structure, labels and zoom.
The browser games are the exception and are not fully accessible (see below).

We still say "substantially conformant" rather than "fully conformant" on purpose: automated testing catches a large share of issues but not all of them — things like fine keyboard-navigation order and screen-reader semantics need human judgement, and we have not finished that review. So we are telling you plainly that passing the automated checks is not the same as guaranteeing every page is perfect for every assistive technology.

3. Known limitations

Please read this one

Our browser games (including Veilbreak and any web playable) are real-time graphics experiences and are not fully accessible. They rely on a visual canvas, quick reactions, and a mouse, touch or game controller, and they are not currently operable with a screen reader or by keyboard alone.

We are not able to make a fast action game fully screen-reader accessible today, and we would rather say so than pretend otherwise. If you want to know what one of our games is about, or want help with anything around it, contact us and we will help however we can.

Other known limitations we are tracking: some third-party content we embed or link to (for example our data tools run on the Apify platform, and our game DEFLEKT is sold through Steam) is outside our control and governed by those platforms’ own accessibility practices.

4. How to report a problem or get help

This is the important part. If any part of our site or tools is hard or impossible for you to use, or you need information or a service in a different format, contact us:

Email: bmay@mayd-it.com
Please include: the page or tool, what you were trying to do, and the assistive technology or browser you were using, if you can.

A real person reads that inbox. We aim to acknowledge your message within 5 business days, and where something is not yet accessible we will work with you to provide the same information or service in a way that works for you while we fix the underlying issue. There is no charge for this.

5. How we test

We run the axe-core automated accessibility engine against our pages and review the results, alongside manual checks such as keyboard navigation, zoom and page structure. Automated testing catches a large share of issues but not all of them, which is why the feedback channel above matters: real reports from real people are part of how we find and fix things.

6. Measures we take

Semantic HTML with proper headings, landmarks and page titles.
Text alternatives for meaningful images and labels for form controls.
Support for browser zoom and reflow; we do not disable pinch-to-zoom.
Accessibility considered as part of building and updating each tool, not bolted on afterward.

7. This statement

This statement applies to mayd-it.com and the May’d It tools on its subdomains. It does not cover third-party platforms we link to. We review it as our tools change and update the date above when we do. It is linked from the footer of our site so it stays easy to find.

8. Enforcement

If you contact us about an accessibility barrier and are not satisfied with our response, you may have rights under applicable law, including the Americans with Disabilities Act (ADA) in the United States. We would always prefer to hear from you first and put it right — please give us the chance at bmay@mayd-it.com.

This statement describes the real, tested state of our sites as of the date above, not an aspiration. If you find something that this statement does not describe, that is useful to us — tell us at bmay@mayd-it.com and we will fix the page and this statement.