Accessibility statment
The following statement applies to our online checkout iframe and software development kit (SDK) solutions. It outlines how Kustom AB works to meet or exceed accessibility standards. You’ll also find a list of known accessibility issues, and information on how to report new ones.
We take accessibility seriously. This isn’t just a checkbox exercise — it’s an ongoing commitment to making our products fully accessible to everyone.
Technical details on known issues
| Section or component | Problem | Proposed action |
|---|---|---|
| Address module | Wrong focus order when expanding address form | Auto-focus the first empty field when expanding an incomplete address form |
| Address module | ‘Submit’ button missing its focus marking | Restore focus marking on ‘submit’ button. |
| Address module | Tooltip button’s aria label points to a missing element | Refactor tooltip button to ensure correct aria labelling |
| Address module | Assistive technologies cannot read tooltip content | Use correct aria label |
| Address module | B2B/B2C dropdown selector allows user input. The component title/label caused confusion | Refactor B2B/B2C dropdown |
| Terms & Conditions | No indication that a PDF will open | Rework the link’s aria label to mention pdf |
| Terms & conditions | Using span as button or link (autofill settings) | Replace functional <span> components |
| Delivery module | There is a hidden element which is not announce by screen readers | Add aria- expanded to the button that controls the show/hide action |
| Delivery module | Intermittent error. Radio button can't be clicked with keyboard | Diagnose the bug on the radio component. Refactor as necessary. |
| Delivery module | Nested inputs in the delivery module & duplicated markup. | Refactor radio component. Remove unnecessary markup. Ensure correct labels. |
| General | Shipping & payment logos without alternative text | Add ‘alt’ attribute to non-decorative images. |
| General | Some headings are not marked as headings | Ensure correct semantic labels for headings to provide a clearer flow |
| Address module | ‘Add C/O’ button in address field is announced on focus. Misleading feedback. | Refactor the field, or have a C/O field open by default |
| Address module | Same aria labels announced twice | Remove redundant aria- labels |
This is a simplified breakdown of all WCAG 2.2 (AA) problems identified during our most recent audit (April 2025). Recommendations and best practices are omitted for clarity, but available on request.
Report an accessibility issue
If you’re having trouble using any part of our checkout, we want to hear about it — so we can fix it. Please fill out the form below to let us know what’s not working.
How we test the checkout
Certified accessibility specialists at Axess Lab have reviewed our checkout, including real-world testing with people who use various assistive technologies.
The most recent full assessment was conducted in April 2025