PayToMe accessibility statement: our WCAG 2.2 AA goal

This is the PayToMe accessibility statement. We want everyone to be able to read this website and use its free tools, including people who use screen readers, keyboards, magnification, voice control or other assistive technology. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. A target is not a guarantee, and this page tells you what we do, and where we know we fall short.

Our accessibility statement and commitment

Accessibility is part of how we build, not a late fix. PayToMe is in public beta. The scope of this statement is the website and the free tools on it. The app at app.paytome.si (accounts, invoices, payments and the Via assistant) has not been covered by the checks described here yet; we plan to hold it to the same target and to extend this statement to cover it. The mobile app is in development.

We have not had a formal third-party accessibility audit yet. We do not claim full conformance.

What we do

Keyboard use

• Pages can be used with a keyboard alone.
• Focus is visible when you move through links, buttons and form fields.
• Links to skip repeated navigation are provided so you can reach the main content quickly.

Color and contrast

• Text and interface elements are designed to meet the AA contrast ratios of WCAG 2.2.
• Colors come from a shared set of design tokens, and automated contrast tests run against them.
• We do not use color as the only way to show information.

Motion

• We respect the “reduce motion” setting in your operating system. When it is on, animations are removed or minimized.
• Nothing on the site flashes.

Works without JavaScript

The website is built to be usable without JavaScript. Reading pages, navigating and using the pricing page all work with scripts off. Some interactive parts of the free tools need JavaScript to calculate and render results, since they run in your browser.

Structure and content

• Pages use semantic headings in a logical order, landmarks and descriptive link text.
• Forms have visible labels and clear error messages.
• We write in plain language and use short sentences.
• Pages scale and reflow when you zoom the text or use a small screen, without sideways scrolling.

Testing

We run automated accessibility checks on the built site before release. Automated tools find only part of the problems, so we also test pages by hand with a keyboard. We are committed to testing with screen readers more often.

Known limitations

We prefer to be direct about what is not yet right.

• No independent audit. We have not yet had an external accessibility audit.
• Screen reader testing is limited. We have not tested every page with every combination of screen reader and browser, so some issues may remain.
• Free tools need JavaScript. The invoice generator and calculators do not work without scripts.
• Generated documents. Invoices produced by the tools, such as downloadable files, may not be fully accessible, for example a PDF may lack tags. We are working to improve this.
• Third-party content. Pages may link to other websites, and we do not control their accessibility.
• Language. The site is available in 13 languages. English is the original; the other versions are machine-translated and reviewed by native speakers after publication, so wording may occasionally be less precise than in English.

Feedback and contact

If you find a barrier, or you cannot use part of the site, please tell us. Email hello@paytome.si and include:

1. The page address.
2. What you were trying to do.
3. What happened, and the browser or assistive technology you use.

We read every report and aim to fix real barriers, and we will tell you what we can and cannot change. The contact page lists other addresses, and you can read how we handle problems in the editorial policy.

Technical notes

This statement applies to paytome.si. We aim to follow WCAG 2.2 level AA, which builds on WCAG 2.1 and adds criteria such as minimum target size and focus appearance. It was last updated on the date shown on this page, and we will revise it as the site and product change. To learn more about us, see the about page, or visit the security page for how we protect visitors.