Swym Wishlist Plus Accessibility Repprt

Section 01

Executive Summary

Swym Wishlist Plus enables Shopify merchants to offer wishlist, save-for-later, and shopper engagement capabilities to their customers. The product is adopted feature-by-feature; merchants switch on the capabilities relevant to their storefront. Accessibility conformance is therefore most meaningfully reported at the feature level.

Swym delivers each feature through one of two implementation variants. The Current implementation (built on Shopify Theme App Extensions, branded as Control Centre) is the actively developed, fully tested path. The Legacy implementation (a JavaScript-rendered storefront layer) serves merchants who have not yet migrated; it remains supported but is on a structured end-of-support timeline as the Current implementation matures.

Install Base

~50K

Shopify merchants globally

Current Implementation

Supports

WCAG 2.1 AA — tested & conformant

Legacy Implementation

Partial

Infrastructure tested; features on Q2 roadmap

End-of-Support Variants

EOL/EOS

Migration path & timeline published

Known Issues Resolved

2

LE-4080, LE-4112 — both closed

Overall product conformance: Partially Conformant. Merchants on the Current implementation (Control Centre) have access to a fully conformant feature set. Merchants on the Legacy implementation are on a published migration and remediation roadmap. Swym's recommendation to all merchants is to adopt the Current implementation, which is the accessibility-conformant path and the future of the product.

Section 02

How to Read This Report

Conformance is reported per feature and per implementation variant — because a merchant using the Current implementation has a different accessibility experience than one on the Legacy implementation. Current implementation = Swym's modern Shopify Theme App Extension layer (Control Centre), fully tested. Legacy implementation = earlier JS-rendered layer, infrastructure tested, feature-level testing Q2 2026. Reaching End of Support = variant receiving no further updates; migration guide available. Items tagged Assumed are inferred from code analysis pending manual confirmation — see Assumption Register (Section 06).

Section 03

Feature Conformance Matrix

The table below is the primary reference for merchants and procurement teams. Locate the feature(s) you use and identify which implementation variant you are on. If you are unsure which variant your store uses, contact [email protected].

Feature	Current Implementation	Status	Legacy Implementation	Status
Wishlist — Core
Wishlist Button (PDP) Add-to-wishlist CTA on product pages	App Block Button Control Centre	Supports	Legacy Button ~46% of merchants	Reaching EOS Migration campaign active. Not evaluated for WCAG.
Wishlist Popup / Modal Multi-list management panel	Control Centre Panel ~9% of merchants on this feature	Supports	Legacy Modal ~91% of merchants on this feature	Q2 2026 Testing
Add-to-Wishlist Popup Popup after adding an item	Control Centre ~39% of merchants on this feature	Supports	Legacy Popup ~61% of merchants on this feature	Q2 2026 Testing
Wishlist Page Dedicated wishlist page surface	Control Centre Page ~41% of merchants on this feature	Supports	Legacy Page ~59% of merchants on this feature	Q2 2026 Testing
Share Wishlist Share wishlist with others via link	— No current implementation yet	Not Available	Legacy Modal 100% of merchants on this feature	Q2 2026 Testing No modern alternative exists yet. Testing is higher priority as a result.
Auto Wishlist Popup Automated wishlist prompts	App Embed + Metafields 100% of merchants on this feature	Supports	— Single variant; no legacy path	N/A
Collections
Collections Button Add-to-wishlist on collection pages	Collections App Embed / Advanced ~68% of merchants on this feature	Supports	Custom Render ~32% of merchants on this feature	Reaching EOS Merchant-custom. Not evaluated. Migration guide available.
Launcher
Wishlist Launcher Floating or header-embedded entry point to wishlist	Floating / Advanced Launcher ~89% of merchants on this feature	Supports	Script Tag Launcher ~11% of merchants on this feature	Reaching EOS Deprecation notice published Q2 2026.
Advanced Header Wishlist embedded in storefront header	Advanced Header (Extensions) ~99.8% of merchants on this feature	Supports	Custom Header 11 merchants (0.2%)	End of Support Forced migration in progress.
Save for Later (SFL)
SFL Page Dedicated save-for-later page	Control Centre SFL Block ~69% of merchants on this feature	Supports	Legacy SFL Page ~31% of merchants on this feature	Q2–Q3 2026 Testing
SFL Popup Save-for-later panel / popup	Control Centre ~44% of merchants on this feature	Supports	Legacy SFL Popup ~56% of merchants on this feature	Q2 2026 Testing
Shopper Engagement & Notifications
Push Notifications Shopper toast / push notification	Shopper Engagement Toast (Extensions) Current implementation	Supports LE-4080 resolved — nested button conflict fixed	—	N/A
Wishlist Nudges Contextual prompts on storefront	Wishlist Nudges (Extensions) Current implementation	Supports	—	N/A
Tooltip / Smallflower Options Inline contextual menu (add/remove from list)	Extensions Current implementation	Supports LE-4112 resolved — ARIA role alignment corrected	—	N/A
Customer Account Surfaces
Customer Account — Wishlist Data Wishlisted items, orders, saved carts, back-in-stock, in-store lists	Engage My Account (Extensions) 100% of merchants on this feature	Supports	—	N/A
Customer Account — Discovery You May Like, Recently Viewed recommendations	Engage My Account (Extensions) 100% of merchants on this feature	Supports	—	N/A
Variant Selection
Variant Selector Product variant selection within wishlist flows	Extensions Built-in ~5% of merchants on this feature	Supports	Custom Variant Selector ~95% of merchants on this feature	Partially Supports Assumed keyboard gap in div-based dropdowns. Q2 testing to confirm. See ASM-005.
Side Drawer
Wishlist Side Drawer Slide-in wishlist panel	Control Centre Side Drawer 100% of merchants on this feature	Supports	—	N/A Single variant only. No legacy path exists.

Legacy implementation usage. Usage percentages shown in the matrix are drawn from active merchant data (February 2026). Where Legacy implementation figures appear high, this reflects the scale of Swym's ongoing migration effort — not an absence of a conformant path. The Current implementation is available to all merchants and is the recommended accessibility-conformant route.

Section 04

WCAG 2.1 Criteria Assessment — Current Implementation

This section maps the Current implementation (Extensions / Control Centre) against individual WCAG 2.1 success criteria. It is provided for procurement teams and auditors who require criteria-level detail. The Legacy implementation will be mapped to WCAG criteria following Q2 2026 feature-level testing.

Level A Criteria

Criteria	Conformance	Remarks
1.1.1 Non-text Content	Partially Supports	Decorative SVG elements and some image instances lack appropriate alt/aria-hidden attributes. P0/P1 fixes in progress (target: March 27, 2026).
1.3.1 Info and Relationships	Partially Supports	Modal/popup containers missing `role="dialog"` in current scan. P0 fix in progress. Core semantic structure of wishlist features is correct.
1.3.2 Meaningful Sequence	Supports	Reading order follows DOM order throughout tested blocks. No sequence errors identified.
1.4.1 Use of Color	Supports	No information conveyed via colour alone detected.
2.1.1 Keyboard	Partially Supports	Core wishlist add/remove, PDP button, and launcher are keyboard-accessible. Some interactive elements in secondary flows lack keyboard handlers. P0 remediation in progress.
2.1.2 No Keyboard Trap	Supports	No keyboard trap patterns detected in static analysis or manual testing.
2.4.3 Focus Order	Partially Supports	Modal focus containment Assumed incomplete based on code analysis. Manual verification in progress. See ASM-001.
3.1.1 Language of Page	Supports	HTML `lang` attributes present across all tested blocks.
4.1.2 Name, Role, Value	Partially Supports	Modal ARIA roles partially missing (P0 fix in progress). LE-4080 (nested button conflict) and LE-4112 (ARIA menu role mismatch) both Resolved.

Level AA Criteria

Criteria	Conformance	Remarks
1.4.3 Contrast (Minimum)	Pending Manual	Assumed: representative toast colour combination may fail 4.5:1 threshold. Full colour audit in Week 2 manual testing. Merchant theme colours are outside Swym's control and are excluded from this criterion. See ASM-003.
1.4.4 Resize Text	Supports	Relative CSS units used throughout, supporting 200% text resize.
1.4.10 Reflow	Supports	Responsive CSS with media queries. No fixed-width layouts identified that would cause horizontal scroll at 320px.
2.4.7 Focus Visible	Partially Supports	Assumed: `outline: 0 !important` detected in CSS. Scope of this rule under manual verification. Merchant theme focus styles are subject to the theme carve-out. See ASM-002.
3.2.3 Consistent Navigation	Supports	Navigation components are shared across the extension layer and render consistently.
4.1.3 Status Messages	Supports	Toast notifications use `role="status"`. Wishlist confirmation announcements verified with VoiceOver.

Section 05

Remediation & Testing Roadmap

This roadmap is a published commitment. It will be updated in step with this document as milestones are completed. The Feature Conformance Matrix (Section 03) will reflect results as they become available.

Now → Mar 27, 2026

Current Implementation — P0 Fixes

Modal role="dialog" — all 13 instances
Keyboard handlers on non-button interactive elements
Missing alt / aria-hidden on images and SVGs
LE-4080 & LE-4112 — ✅ Already resolved

Apr – Jun 2026 (Q2)

Legacy Implementation — P1 Feature Testing

Wishlist Popup / Modal (91% of users on this feature)
Add-to-Wishlist Popup (61%)
Share Wishlist (100% — highest priority, no modern alt)
SFL Popup (56%)
Wishlist Page (59%)
Variant Selector — Custom (95%)

Jul – Sep 2026 (Q3)

VPAT v2.0 — Full Legacy Coverage

All Q2 test results published in Feature Matrix
All Assumed tags replaced with direct evidence
Legacy PDP Button migration progress reported
EOS variant sunset confirmed

2027 Target

Full Conformance Goal

80%+ merchant adoption of Current implementation
Legacy variants retired or fully remediated
Continuous accessibility gate in CI/CD pipeline

Section 06

Assumption Register

Every item tagged Assumed in this document is recorded here. Each entry will be closed with direct evidence as manual testing progresses. This register is the audit trail for procurement reviewers.

ASM-001

Modal Focus Containment (2.4.3)

No focus trap logic detected in layout JavaScript. Focus assumed to leak outside modal boundaries when open. Rated "Partially Supports." Will be replaced with keyboard + VoiceOver evidence from Week 2 manual testing (target: March 20).

ASM-002

Focus Ring Suppression (2.4.7)

outline: 0 !important detected in CSS. Assumed to suppress visible focus indicators in some contexts. Scope of the rule and interaction with merchant theme styles requires manual visual verification.

ASM-003

Toast Colour Contrast (1.4.3)

Toast background is merchant-theme configurable. White text on sky blue (#7DD3FC) assumed as a representative failing case (contrast ~2.5:1, below 4.5:1 threshold). Full colour audit scheduled. Merchant theme carve-out may apply.

ASM-004

SVG Icon Announcements (1.1.1)

Unlabelled SVG elements assumed to be announced by screen readers via file reference or generic "Button." Based on standard browser/AT behaviour with missing ARIA labels. Will be confirmed in VoiceOver testing session.

ASM-005

Variant Selector Keyboard Accessibility (2.1.1)

Custom variant selector uses div-based dropdowns with no keydown event listeners detected in static analysis. Assumed keyboard-inaccessible for variant selection. Rated "Partially Supports" rather than "Does Not Support" because the wishlist add/remove action itself is keyboard-accessible. Q2 testing to confirm.

Section 07

End-of-Support Variants — Migration Path Available

The variants below are not assessed for WCAG conformance. The fastest path to a conformant storefront for merchants on these variants is migration to the Current implementation. Migration guides and assisted migration are available at support@getswym.com.

Variant	Merchants	Status	Migration Path
Custom Header	11 (0.2%)	End of Support	Migrate to Header Launcher (Extensions) — Swym support team engaged directly.
Script Tag Launcher	432 (11%)	Deprecating Q2 2026	Migrate to Floating or Advanced Launcher. Deprecation notice and migration guide published Q2 2026.
Legacy PDP Button	6,459 (46%)	Active Migration Campaign	Migrate to App Block Button (Extensions) — the conformant path. WCAG testing of this variant in parallel per Q2 roadmap.
Custom PDP Button	1,168 (8%)	Not Evaluated	Merchant-custom implementations. Merchants encouraged to migrate to App Block Button.
SFS Qty (Old UI)	3 (<0.01%)	Not Evaluated	Negligible usage. Document-only record.

Section 08

Legal Notice & Scope Limitations

Point-in-time declaration. This report reflects the state of Swym Wishlist Plus as of March 10, 2026. It is not a legal certification or warranty of WCAG conformance. It is provided in good faith to support accessibility evaluation by customers, prospects, and procurement teams.

Merchant theme carve-out. Swym Wishlist Plus renders within a Shopify merchant-controlled theme. Colour contrast for merchant-supplied typography, focus ring styles overridden by theme CSS, and layout reflow governed by the theme grid are outside Swym's control and are excluded from this report's conformance claims.

Shopify platform scope. This report covers Swym Wishlist Plus on Shopify only. Shopify platform-level accessibility (checkout, account pages, Shopify admin) is governed by Shopify's own ACR and is not within scope here.

Custom implementations. Merchants who have implemented Swym UI components using custom code outside Swym's standard delivery method are responsible for the accessibility of those customisations.

Canonical URL. The current and most recent version of this report is maintained at getswym.com/accessibility. Printed or cached copies may not reflect the latest updates.

VPAT® is a registered trademark of the Information Technology Industry Council (ITI). Use of the VPAT framework does not imply certification or endorsement by ITI.