Sawoice should work with the way you navigate.

1. Our target

SAWANT CORE LLP targets WCAG 2.2 Level AA without relying on a possible microenterprise exemption. The target covers public information, signup, pricing, checkout, billing, account management, privacy requests, export, cancellation, deletion, and the controls needed to use Sawoice.

2. Design and engineering practices

• Skip navigation, semantic landmarks and headings, descriptive page titles, and meaningful link text.
• Keyboard-visible focus, keyboard-operable forms and dialogs, and no intentional keyboard traps.
• Programmatic labels, accessible names, instructions, error summaries, and status announcements.
• Contrast-conscious text, controls, focus indicators, and non-color status cues.
• Responsive reflow at 200% zoom and reduced-motion support.
• Semantic tables and lists with horizontal scrolling reserved for genuinely two-dimensional data.
• Distinct, keyboard-operable export, cancellation, privacy-request, and deletion actions.

3. Testing

Automated linting and axe checks are used to catch common failures. Release evidence also requires manual keyboard navigation, zoom/reflow, contrast, error recovery, and screen-reader checks with representative browsers and desktop operating systems.

Automated results do not establish complete conformance. Platform-native controls, payment-provider pages, and third-party content require separate verification.

4. Current limits

• A full independent WCAG audit has not yet been attached to this version.
• Polar-hosted checkout and portal accessibility must be verified during the separate payment workstream.
• Windows screen-reader and ACL behavior require native Windows qualification.
• Provider and operating-system dialogs can have accessibility behavior outside Sawoice's direct control.

5. Feedback and alternatives

If a Sawoice page or control is difficult to use, email support@sawoice.com or submit a tracked privacy/general inquiry. Describe the page or feature, assistive technology, browser or operating system, and the outcome you need. Do not include passwords, access tokens, private audio, or unnecessary sensitive content.

We will acknowledge the report, offer a reasonable alternative where practicable, and track remediation by severity and user impact.