Shopify Empire theme — accessibility hot-spot audit
Accessibility hot-spots in Empire
Quick-view modal dialog pattern
Fix may be available after matchingWCAG: 2.1.2 No Keyboard Trap
Quick-view modal needs role="dialog" + focus trap + Escape + focus return. Test the actual theme version, settings, apps, content, breakpoints, and interactive states before deciding whether a source change is safe.
Sticky header obscuring focus
Fix may be available after matchingWCAG: 2.4.11 Focus Not Obscured
Sticky header overlaps focused fields when scrolled. Test the actual theme version, settings, apps, content, breakpoints, and interactive states before deciding whether a source change is safe.
Product image alt text passthrough
Fix may be available after matchingWCAG: 1.1.1 Non-text Content
The theme renders alt text from the Shopify Admin product-image setting. Merchants who upload images without setting alt text get an empty `<img alt="">`, which screen readers skip silently. Test the actual theme version, settings, apps, content, breakpoints, and interactive states before deciding whether a source change is safe.
Cart drawer focus management
Fix may be available after matchingWCAG: 2.1.2 No Keyboard Trap
Cart-drawer modals open as overlays without enforcing a focus trap — keyboard users tabbing through the page after opening the drawer can land on background elements. Test the actual theme version, settings, apps, content, breakpoints, and interactive states before deciding whether a source change is safe.
Mobile tap-target size (WCAG 2.2)
Fix may be available after matchingWCAG: 2.5.8 Target Size (Minimum)
Header icons, mobile nav links, and quantity steppers ship at 16-20 px on mobile — below the 24×24 CSS-pixel WCAG 2.2 floor. Test the actual theme version, settings, apps, content, breakpoints, and interactive states before deciding whether a source change is safe.
FAQ
Is the Shopify Empire theme accessible by default?
This page does not certify the current Empire release. Verify current vendor documentation and test the actual storefront because version, colors, sections, content, custom code, and third-party apps can change accessibility behavior.
What WCAG criteria does Empire most often fail?
Useful checks for Empire include 1.1.1 Non-text Content, 1.4.3 Contrast Minimum, 4.1.2 Name, Role, Value, and 2.5.8 Target Size Minimum. The live result depends on customizations. Some detected instances support rule-based or AI-assisted fix suggestions; others need hands-on review.
Can AccessComply fix Empire accessibility issues automatically?
AccessComply can report supported automated issues on reachable Empire storefront pages and may suggest a fix when it can safely match the affected source to a protected Shopify workflow you control. Coverage depends on version, settings, source matching, content, and installed apps. Captions, third-party widgets, risky edits, and judgment-heavy issues still need a person.
How does AccessComply protect my Empire customizations?
No automated change can promise zero risk. AccessComply previews each supported suggestion or group of changes, saves the original value before making a change, and checks the result afterward. A failed check remains unresolved. Restoring an older value requires your confirmation because it can overwrite later edits.
Run a real Empire scan
AccessComply runs supported automated checks on the storefront pages and states it can reach. You can review safely matched suggestions before approval; supported changes keep the original value and are checked afterward.