Accessibility Statement
Last updated 15 July 2026
Our aim
Paymarka aims to make its public pages and deal workflows usable by as many people as possible, including people who use keyboards, screen readers, magnification, voice control, or reduced-motion settings. We use WCAG 2.2 as a development target, but this statement is not a claim of WCAG conformance or an accessibility audit.
Current implementation
The repository includes semantic form controls, accessible names for some interactive controls, and reduced-motion handling in parts of the UI. The application contains user-generated documents, PDFs, signatures, uploads, third-party provider surfaces, and responsive states that may require separate review. Accessibility can vary by browser, assistive technology, content, and deployment.
Known limitations and verification
We have not established a complete, independent WCAG 2.2 audit for every route, portal state, generated document, or third-party flow. We therefore do not claim Level A, AA, or AAA conformance. Keyboard navigation, focus visibility, contrast, error messaging, screen-reader output, zoom/reflow, document exports, and authentication flows should be tested before making a formal conformance statement.
Request an accommodation or report a barrier
If you cannot access a Paymarka page or workflow, contact us through the Paymarka contact form. Include the page or workflow, the barrier, your browser and assistive technology if relevant, and the outcome you need. Please do not include passwords, private keys, payment credentials, or unnecessary personal data. We will use the report to investigate a reasonable route to the requested information or task.