We want everyone to be able to use Vendor — the people who run stores on the platform and the shoppers who buy through it — regardless of how they browse or what assistive technology they rely on. This statement sets out the standard we hold ourselves to, what we do to get there, the gaps we already know about, and how to tell us when we've missed something.
1. Conformance target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across this marketing site and the platform admin, and we build new features against that standard rather than retrofitting them later.
For procurement teams that need formal documentation — common for public-sector and enterprise contracts — we can prepare an accessibility conformance report (a VPAT, mapped to WCAG 2.1 AA and EN 301 549) on request.
2. What we do
Accessibility is built into our design system rather than bolted on. Our components use semantic HTML and are built on accessible Radix UI primitives, so keyboard navigation, focus management, and ARIA roles come as standard. On top of that we check colour contrast, keep visible focus indicators, never disable browser zoom, and honour the prefers-reduced-motion setting so animations don't play for people who'd rather they didn't.
We test key flows with screen readers — VoiceOver on macOS and NVDA on Windows — and accessibility is part of our review checklist before a release goes out. When we find a regression, we treat it like any other bug.
3. Known limitations
We'd rather be honest about where we fall short than claim perfection. These are the gaps we're aware of and actively working on:
- Some embedded third-party content — video players and payment iframes — brings its own accessibility behaviour that we don't fully control.
- The data-table component on some older admin screens doesn't yet support full keyboard navigation to column headers. A fix is planned for Q3 2026.
- PDF exports generated by the platform aren't always tagged for screen readers yet. Improving this is in progress.
4. Reporting issues
If you hit an accessibility barrier anywhere on vendor.com.mk or inside the platform, please tell us — it's the fastest way for us to fix it. It helps if you can include the page URL, the assistive technology and browser you're using, and a short description of what went wrong.
We'll acknowledge accessibility reports within 2 business days and follow up with a remediation plan within 14 days.
5. Alternative formats
If you need documentation, a contract, or a report in an alternative format — large print, braille, or audio — just ask and we'll arrange it. Contact our accessibility team and tell us what works best for you.