Accessibility statement
Building software by describing it should work for everyone — including people who use assistive technology, and the people who use the apps you build.
Last updated: October 1, 2026
Our goal
We aim for maker77.com, the dashboard and the builder to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Accessibility is an ongoing effort, and we treat issues as bugs, not nice-to-haves.
What we do today
- Semantic HTML with proper headings, landmarks, labels and buttons.
- Keyboard navigation with visible focus indicators across marketing pages and forms.
- Text and interface colors chosen for readable contrast on our dark theme.
- Respect for your system's "reduce motion" setting — animations are effectively disabled when it's on.
- Responsive layouts that work from small phones to large monitors, and support browser zoom.
- Status information (such as on our status page) communicated with text labels, not color alone.
Apps you build with maker77
maker77 is instructed to generate accessible apps by default: readable contrast, responsive layouts, labeled form fields and large touch targets on mobile. You can make your app more accessible by asking for it directly, for example:
- "Add descriptive alt text to every image."
- "Make sure all interactive elements are reachable and usable with the keyboard."
- "Check color contrast against WCAG AA and fix anything that fails."
- "Add ARIA labels to icon-only buttons."
AI-generated code can still contain accessibility issues. As the owner of your app, you're responsible for reviewing it — and we recommend testing with a screen reader and keyboard before launch. Your code is fully editable in the code editor.
Known limitations
- The live preview inside the builder shows your app in an embedded frame; assistive technology support inside it depends on the app's own markup.
- The code editor is a rich editing component; some screen reader interactions may be less smooth than in a dedicated desktop editor.
- Click-to-select editing is a pointer-based feature. Everything it does can also be done by describing the change in the chat.
Feedback
If you run into an accessibility barrier on maker77, please tell us — we want to fix it. Use our contact form with the page or feature, what you were trying to do, and the browser and assistive technology you use. We aim to respond within 3 business days.