Accessibility

• Visible keyboard focus on every interactive element. Tab order matches the visual order of the page; no hidden focus traps outside of intentional modals.
• Contrast ≥4.5:1for body text and ≥3:1 for large text and graphic elements. The QR editor’s Scan Test panel surfaces contrast ratios in real time, and the AI Brand Sync feature automatically nudges palettes that fall below the threshold.
• Semantic markup — headings in order, landmark roles, descriptive alt text on every meaningful image, and aria-label on icon-only controls.
• Reduced motionrespect. Animations honor the operating system’s prefers-reduced-motion setting.
• Mobile parity. The editor’s sidebars collapse to bottom sheets on phone, touch targets stay ≥44px, and every QR type is fully usable on a 360px-wide viewport.
• No keyboard traps in modals. Every dialog supports Esc to close and returns focus to the trigger element on dismiss.

The QR canvas itself renders as an SVG, but the preview at very small zoom levels can render details below the recommended visual size. We surface scannability warnings when a configuration risks failing camera capture in low-light conditions.

We don’t currently offer a dedicated high-contrast theme — the default palette already targets WCAG AA. If you need stronger contrast or a different color scheme, the editor exposes manual foreground, eyes, and background color pickers.

If anything on QRBliss is hard to use with assistive technology, please tell us. We treat accessibility reports the same as bug reports — they jump the queue.

Reach us at hello@qrbliss.com or via the contact page. We aim to reply within one business day and resolve confirmed issues in the next release.

• Web Content Accessibility Guidelines (WCAG) 2.2 Level AA
• Section 508 of the Rehabilitation Act (US federal accessibility requirements)
• EN 301 549 / European Accessibility Act (EU baseline)