The full conformance report (VPAT 2.5) is available at getswym.com/accessibility. This article provides plain-language guidance for merchants, procurement teams, and anyone evaluating Wishlist Plus for accessibility compliance.
What standard does Wishlist Plus conform to?
Wishlist Plus targets WCAG 2.1 Level AA — the internationally recognised benchmark for web accessibility, published by the W3C Web Accessibility Initiative.
Our conformance report follows the VPAT 2.5 framework, the standard format used by software vendors for accessibility declarations. A VPAT is a self-declaration, not a third-party certification — this is the norm across the SaaS industry.
We are evaluating WCAG 2.2 for inclusion in a future update. See the WCAG 2.2 section below.
What is covered
Current implementation — Extensions / Control Centre This is the modern Shopify Theme App Extension layer. It is fully tested against WCAG 2.1 AA, with automated accessibility checks running on every code release. It covers:
Wishlist Button (PDP) — App Block Button
Wishlist Popup / Modal — Control Centre Panel
Add-to-Wishlist Popup — Control Centre
Wishlist Page — Control Centre
Auto Wishlist Popup — App Embed + Metafields
Collections Button — App Embed / Advanced
Wishlist Launcher — Floating / Advanced
Advanced Header — Extensions
Save For Later Page — Control Centre Block
Save For Later Popup — Control Centre
Push Notifications — Extensions
Wishlist Nudges — Extensions
Tooltip / Smallflower — Extensions
Account — Wishlist Data — Engage My Account
Account — Discovery — Engage My Account
Variant Selector — Extensions Built-in
Wishlist Side Drawer — Control Centre
If you are on the current implementation, this coverage applies to you. Migrating to the current implementation is the fastest path to a conformant storefront.
What is not covered
Legacy implementation An earlier JS-rendered layer used by a portion of merchants. Accessibility testing for legacy features is on our roadmap. Merchants on legacy are encouraged to migrate to the current implementation.
Merchant-controlled theme Wishlist Plus renders within your Shopify theme. The following are outside Swym's control and are not covered by our conformance report:
Colour contrast for your theme's typography
Focus ring styles if your theme overrides them with CSS
Layout reflow governed by your theme grid
Merchant-custom implementations If you have implemented Swym UI components using custom code outside our standard delivery method, you are responsible for the accessibility of those customisations.
SBiSA SBiSA is a separate Swym product with its own accessibility scope. It is not covered by this report.
Shopify platform Shopify's own platform — checkout, customer accounts, Shopify admin — is governed by Shopify's accessibility conformance report, not ours.
WCAG 2.1 AA — current status
Current extension layer: largely conformant. Two items are planned for a future update — modal/popup containers missing role="dialog", and some secondary-flow interactive elements lacking keyboard handlers. All other tested criteria support or partially support WCAG 2.1 AA.
Automated CI checks: every code change to the storefront extension layer runs an accessibility linter before it ships. This has been in place since April 2026.
VoiceOver manual testing: conducted on the current layer. Results will be formally committed as part of the next VPAT update.
For the full criteria-level breakdown, see Section 04 of the conformance report.
WCAG 2.2 — our position
WCAG 2.2 was published by the W3C on 5 October 2023. It adds new criteria around focus visibility, touch target sizes, and drag interactions. It is backward-compatible with WCAG 2.1.
We have not yet assessed Wishlist Plus against WCAG 2.2. We are evaluating this for a future update. Our published conformance report targets WCAG 2.1 AA.
Does WCAG 2.2 apply to you? It depends on your market:
Your market | Current legal standard | WCAG 2.2 status |
US (private sector / e-commerce) | WCAG 2.1 AA (de facto) | Not yet legally mandated |
European Union | WCAG 2.1 AA (EAA, enforceable June 2025) | Not yet binding; expected via EN 301 549 update |
UK (public sector) | WCAG 2.2 AA | Already operative since Oct 2023 |
UK (private sector) | No specific version mandated | 2.2 emerging benchmark |
Australia | WCAG 2.2 AA (AHRC, April 2025) | Already stated standard for private sector SaaS |
Canada | WCAG 2.1 AA | Expected to adopt 2.2 post EN 301 549 update |
If your procurement process specifically requires WCAG 2.2, contact us at [email protected] before making a decision. We can discuss our roadmap and what that means for your requirements.
Remediation roadmap
Status | Milestone |
Done | Nested button conflict + ARIA menu role mismatch resolved |
Done (Apr 2026) | 68 SVG aria-hidden fixes, 10 image alt fixes, 10 role="button" keyboard fixes, Playwright/axe CI suite live |
Planned | Legacy feature testing — WishlistModal, AddWishlistModal, ShareWishlistModal, SFLPopup, WishlistPage, Variant Selector Custom |
Planned | Modal role="dialog" and secondary keyboard handler fixes |
Planned | VPAT v2.0 publication — updated results, all open items resolved or formally deferred |
Planned | Full conformance target — 80%+ merchant adoption of current implementation, legacy variants retired or fully remediated |
Questions we get asked
Is your VPAT certified by a third party? No. Our VPAT is a self-declaration in the VPAT 2.5 format published by the IT Industry Council (ITI). Third-party accessibility certification is uncommon across the SaaS industry. We are happy to share the full report and walk through it with your team.
Does this cover all Swym products? No. This report covers Wishlist Plus on Shopify only.
We are on the legacy implementation. What should we do? Migrate to the current implementation. It is the fastest path to a conformant storefront and is actively supported by our team. Contact [email protected] to get started.
A competitor says they are WCAG 2.2 compliant. How do we compare? Ask them for their VPAT or completed audit against specific WCAG 2.2 criteria. A claim without evidence is not a compliance position. We do not make claims we cannot back up, and we can show our work on 2.1.
Your roadmap has changed since the April 2026 report. Why? Accessibility priorities are updated as our product roadmap evolves. The current report reflects our latest planning. We are committed to transparency — every update to this report is dated and versioned so you can track how our position develops over time.
We need accessibility documentation for a vendor assessment or RFP. The full VPAT is at getswym.com/accessibility. If you need additional documentation or a conversation with our team, contact [email protected].
Further reading
For questions not answered here, contact [email protected].