Our approach
Accessibility is treated as a product-quality requirement rather than a separate mode. Controls should have meaningful labels, state should not rely on color alone, and the editor should remain usable with a keyboard, screen reader, zoom or reduced-motion preference.
Supported considerations
- Keyboard-operable controls and visible focus indicators
- Semantic headings, landmarks, labels and status messages
- Text and interface contrast designed for WCAG 2.2 AA
- Responsive reflow from small mobile screens to desktop
- Reduced-motion behavior for non-essential transitions
- Touch targets sized for practical mobile use
Ongoing work
Automated checks cannot identify every barrier, and support can vary across browser and assistive-technology combinations. We continue to test the main content, customization, preview and download workflows as the studio changes.
Accessibility feedback
If a feature is difficult to use, email support@customqrgenerator.com with the page, control, browser, assistive technology and a description of the barrier. Please do not include confidential QR payloads.