We are committed to making this site accessible to everyone, including people who use assistive technologies such as screen readers, keyboard-only navigation, or speech-input devices.
Our commitment
We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We describe this as a target we work towards rather than a claim that the whole site conforms. The pages and journeys we have tested by hand are set out below, together with what that testing found; the rest of the site is covered by automated testing, which catches only some kinds of problem.
How we test. Before changes are released to the live site, automated tests check every page, together with its error, empty and confirmation messages, against WCAG 2.2 Level AA in light and dark themes and at desktop and phone widths, and Lighthouse scores the accessibility of each public page, which we use as a release gate rather than as a measure of conformance. Automated tooling only detects a minority of accessibility problems, so we also test by hand. In October 2026 we went through checkout (by card and by PayPal), made-to-order configuration, order follow-up and messages, and signing in, using only a keyboard and with screen readers: VoiceOver on Mac and iPhone, NVDA on Windows and TalkBack on Android. We repeat this manual testing before we release any change to checkout, to made-to-order configuration, to signing in or to the account area, and at least once every six months in any event. We keep a record of each round, and we will tell you what the most recent one covered if you ask.
Third-party components. Some parts of the site are supplied by other companies: the cookie-consent banner, the card-payment fields (Stripe), the PayPal window, and the Google and Apple sign-in buttons. We test how they work within our pages, match their colors to our themes where the provider allows it, and raise accessibility defects with the provider. We do not control their code and cannot guarantee its conformance.
Which accessibility laws apply to us
We sell to customers in the United States, Canada, the United Kingdom, the European Union and the EEA, and Australia. Accessibility obligations differ across those markets. In the United States, Title III of the Americans with Disabilities Act is applied to commercial websites. In the United Kingdom, the Equality Act 2010 requires reasonable adjustments for disabled people. In Australia, the Disability Discrimination Act 1992 applies. In Canada, federal and provincial accessibility legislation may apply depending on the province.
European Accessibility Act. Directive (EU) 2019/882 has applied to e-commerce services since 28 June 2025 and requires covered traders to meet accessibility requirements and to publish an accessibility statement. The Directive exempts microenterprises providing services — businesses with fewer than 10 people and an annual turnover or balance-sheet total of no more than €2 million. We publish this statement and work to the standard above regardless of whether the exemption applies to us.
Known limitations
Accessibility is a continuous effort rather than a one-time milestone, and we would rather tell you where we currently fall short than imply the site is perfect.
Known issues at the date of this statement:
- Error lists on iPhone. When a form cannot be submitted, a box headed “Please fix the following” lists what needs correcting and receives focus. On iPhone, VoiceOver reads the heading but not the list beneath it; swipe right to hear each item. Each field also announces its own error when you leave it.
- Card number field read as already filled. Screen readers read the example text in the card-payment fields, such as “1234 1234 1234 1234”, as though a number had already been entered. The fields are supplied by Stripe and we cannot change that text. We have raised it with them. If you are using a screen reader, the field is empty until you type into it, and you can enter your card number in the normal way.
Our most recent review was completed on . Automated testing covered every page of the shop together with its error, empty and confirmation messages. Checkout, made-to-order configuration, order follow-up and signing in were also tested by hand, with a keyboard and with four screen readers.
In those journeys the review found no outstanding WCAG 2.2 Level AA failures in the parts of the site we build ourselves, apart from the issues listed above. Browsing and product pages were covered by automated testing but not by the manual round, so we do not claim the same for them; they are next on our list. We will list any further issues here as they are found, together with the pages affected and when we expect to fix them.
If you find a problem that is not listed here, please tell us — a report from someone using the site is the fastest route to a fix.
How to report an accessibility issue
Email accessibility@velimiradesigns.com with a description of the problem, the address of the page where you met it, and — if you were using one — the assistive technology and browser you were using. You do not need to use technical language; telling us what you were trying to do and what happened is enough. You can also contact us through the site.
We aim to acknowledge your report within five business days and to tell you what we intend to do about it and when. If you need the information or the transaction in another format in the meantime — for example if you cannot complete checkout — tell us and we will help you complete your order another way.
If you are not satisfied with our response, tell us and we will look at it again. You may also be able to take the matter further under the accessibility or equality law of your own country, and you can ask us who to approach and we will help you find the right body.
Standards and guidelines
Our accessibility work is informed by:
- W3C Web Content Accessibility Guidelines 2.2 (Level AA conformance target)
- The WAI-ARIA Authoring Practices 1.2
- EN 301 549, the European harmonized standard for ICT accessibility, which is the reference point for the European Accessibility Act and currently maps to WCAG 2.1 Level AA — our WCAG 2.2 Level AA target sits above it
- Automated checks via axe-core, integrated into our test suite
- Lighthouse accessibility audits of every public page, as part of our automated tests
- Manual testing with a keyboard and with the VoiceOver, NVDA and TalkBack screen readers