Accessibility is ongoing work.
Our target is WCAG 2.2 Level AA for the public website and web application. We use semantic structure, platform accessibility APIs, automated checks, and manual review to move toward that target. We do not yet claim complete conformance or certification.
1. Current design support
- Skip links, landmarks, headings, labels, descriptive page titles, and logical reading order on public pages.
- Visible keyboard focus and large interactive targets for primary navigation and actions.
- Responsive layouts that avoid horizontal page scrolling at supported viewport sizes.
- Text and controls designed for high contrast against their backgrounds.
- Form labels, validation messages, accessible button names, and status messaging in account flows.
- Support for browser zoom and text resizing without requiring a fixed device orientation.
- Reduced decorative motion when the operating system or browser requests reduced motion.
2. Images, video, and visual concepts
Decorative imagery is hidden from assistive technology. Informative images use text alternatives or nearby descriptions. The landing-page hero video is muted, has no spoken content, does not require interaction, and falls back to a static poster when reduced motion is preferred.
AI-generated appearance concepts are inherently visual. We are working to improve nonvisual summaries and comparison descriptions so important product meaning is not available only through an image.
3. Accessible authentication
Sign-in and account creation support password managers, paste, and standard email/password input. We do not use puzzles, memory tests, or appearance-based challenges as the only way to authenticate. Provider sign-in buttons include accessible names, and errors are written to explain the next action.
Security and accessibility can conflict if implemented carelessly. We aim to meet both by using secure recovery links, clear timeouts, and alternatives that do not depend on a user's ability to transcribe or memorize information.
4. Known limitations and current priorities
Glowgen is still being tested across browser, screen-reader, keyboard, zoom, VoiceOver, Voice Control, Larger Text, and reduced-motion combinations. Current priorities include:
- More complete screen-reader descriptions for visual comparison and image-generation results.
- Rendered accessibility and keyboard regression tests across every authenticated web route.
- Focus management and announcements for modal dialogs, toasts, navigation changes, and asynchronous AI jobs.
- Alternatives for gesture-led comparisons and better support at very large text sizes.
- Consistent error summaries and help placement across long forms.
5. Tell us what is blocking you.
If a page, feature, document, or support process is difficult to use, email support@glowgen.ai. Include the page or feature, what you were trying to do, your browser or device, and any assistive technology you use. Do not include passwords or sensitive photos.
We aim to acknowledge accessibility reports within two business days and provide an accessible alternative when one is reasonably available.