Accessibility
AIDomainForge · Operated by Makingmoreland LLC, Leon County, Texas
Last Updated: 2026-05-25 · Version: v2026-06-02.1
This is not a boilerplate statement. One of our own operators uses a screen reader every day. Accessibility is not a checkbox for us — it is personal.
Our Target
We aim for WCAG 2.1 Level AA.
WCAG 2.1 (Web Content Accessibility Guidelines, version 2.1) is the internationally recognized standard for accessible content. Level AA is the standard most commonly required by law and industry practice. It covers things like:
- Sufficient color contrast between text and background
- Keyboard navigability — everything reachable without a mouse
- Screen reader compatibility — meaningful labels, logical reading order, descriptive link text
- Scalable text — content that works at 200% zoom without horizontal scrolling
- No flashing content above the seizure threshold
- Descriptive alternatives for images that carry meaning
We review these criteria on every page we build. We do not always get it perfect, but we check — and we fix things when we find gaps or when you tell us about them.
Screen Reader Compatibility
We build to be heard, not just seen.
Every page we produce is designed to work with screen reader software. Specifically, we build for compatibility with:
- JAWS (Job Access With Speech) — Windows
- NVDA (NonVisual Desktop Access) — Windows, free
- VoiceOver — macOS and iOS
- TalkBack — Android
We use semantic HTML (headings in logical order, lists for list content, buttons for actions). We provide skip-navigation links at the top of every page. We label interactive elements. Decorative images are marked with aria-hidden="true" so screen readers skip them. Images that carry meaning have descriptive alt text.
If something on this site is not working with your screen reader or assistive technology, please tell us. We want to know, and we will fix it.
Known Limitations
We are honest about where we are not perfect yet.
- Third-party content (Stripe's checkout form, embedded fonts, our analytics dashboard) is controlled by those vendors and may not fully conform to WCAG 2.1 AA. We cannot change their code, but we report issues to them when we find them.
- AI-generated images included in customer bundles may not always have specific descriptive alt text. We are building a review workflow to improve this before each bundle is delivered.
- The optional welcome audio is offered as an extra channel, not a replacement — every word it says is also written on the page.
We update this list when we identify new issues, and we remove items when they are resolved.
How to Reach Us
Tell us what is not working.
If you encounter a barrier on this site or in any deliverable we send you, contact us. We respond to accessibility reports within 1–3 business days.
Makingmoreland LLC d/b/a AIDomainForge
Email: support@aidomainforge.net
Subject line: Accessibility — this helps us route your message quickly.
Please tell us: what page, what assistive technology you use, and what happened (or did not happen) that you expected it to.
Alternate Formats
Need something in a different format?
If you need any document or deliverable in a different format to access it — plain text, large print, high-contrast version, or another format — email us at support@aidomainforge.net and describe what you need. We will do our best to provide it at no additional cost.
Formal Complaints
If you are not satisfied with our response to an accessibility issue, you may contact the relevant authority in your jurisdiction. In the United States, the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act govern accessibility obligations for covered entities. You may file a complaint with the U.S. Department of Justice Civil Rights Division or the relevant federal agency.
We prefer to fix problems before they reach that stage. Please give us the chance to respond first.