← All integrations
Searchby Simtech Development

Searchanise on Shopify — accessibility integration audit

Accessibility hot-spots in Searchanise

Instant-search dropdown ARIA combobox pattern

Partial auto-fix

WCAG: 4.1.2 Name, Role, Value

Most predictive search widgets render the dropdown as a styled list without combobox/listbox roles. Screen readers cannot announce the suggestion count or the active result. Auto-fix applies the WAI-ARIA 1.2 combobox pattern with aria-expanded, aria-activedescendant, role="listbox" on the panel, and role="option" on each suggestion.

Suggestion arrow-key navigation

Partial auto-fix

WCAG: 2.1.1 Keyboard

Most predictive-search dropdowns support mouse-only navigation through suggestions. Auto-fix patches the JavaScript to handle ArrowUp / ArrowDown / Home / End / Enter per the WAI-ARIA combobox spec.

FAQ

Is Searchanise accessible by default on Shopify?

Searchanise's vendor-default templates pass standard accessibility checks; merchant customization and the structural patterns the app injects are where regressions appear. The hot-spots above are the predictable failure modes when a real Shopify storefront is audited end to end with Searchanise installed.

Does AccessComply fix Searchanise accessibility issues automatically?

Yes — for the categories marked auto-fix above. AccessComply scans the live storefront with Searchanise active, identifies the WCAG failures the app surface contributes, and writes source-code fixes to your theme via the Shopify Admin API. Fixes that touch the Simtech Development layer directly are flagged for Simtech Development support follow-up.

Should I uninstall Searchanise for accessibility reasons?

No. Searchanise is a widely-used Shopify app and the accessibility issues are addressable without removing the app. The hot-spots above are predictable structural patterns — every app that does what Searchanise does has a similar list. The fix is to remediate at the storefront level, not to swap apps.

Will fixing Searchanise accessibility break my brand customizations?

No. AccessComply's fixes are scoped to specific WCAG-relevant attributes (aria-label, role, autocomplete, focus styles, contrast on text) and do not change merchant copy, layout, or branding. If a fix produces a regression, the post-fix re-scan triggers automatic rollback to the pre-fix state.

Do I need Searchanise-specific permissions for AccessComply to scan?

No additional permissions. AccessComply scans the rendered storefront the same way Googlebot or any visitor does — through Playwright + axe-core. The scan reads the same HTML the customer sees, including everything Searchanise injects at runtime.

Scan your store with Searchanise installed

AccessComply scans the live storefront — the same HTML Searchanise renders for your customers — and writes source-code fixes for the hot-spots above.