Veva Law

Veva Law aims to meet WCAG 2.2 Level AA on every page of this site. We treat accessibility as part of the product, not a retrofit. Last reviewed 16 May 2026.

Conformance target

Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, as published by the W3C. Where the South African Government Web Accessibility Guidelines diverge, we follow the stricter of the two. The site is served in South African English (lang="en-ZA").

What we conform to (the four WCAG pillars)

• Perceivable. Body text and meaningful UI maintain a contrast ratio of at least 4.5:1 against their background; large text and non-text controls clear 3:1. Animation and parallax respect prefers-reduced-motion. Images carry meaningful alt text, decorative images are marked aria-hidden, and no information is conveyed by colour alone.
• Operable. Every interactive control is reachable in DOM order with the keyboard and shows a visible focus indicator (focus ring ≥ 3:1 contrast). No keyboard traps. Tap targets on touch viewports are at least 44 × 44 CSS pixels. Nothing on the page flashes more than three times per second.
• Understandable. Page language is declared (en-ZA), navigation is consistent across the site, headings descend in logical order, form fields are labelled, and error messages are explicit (what went wrong, how to fix it).
• Robust. Markup is semantic HTML first (nav, main, article, button, a). ARIA is used only where a native element does not exist; we never duplicate roles.

How we test

• Automated checks run on every pull request: Lighthouse Accessibility ≥ 95 on home + at least one inner page, and `@axe-core/playwright` against the home, contact and privacy-policy routes with zero violations.
• Keyboard-only navigation: every interactive control reachable in DOM order with a visible focus indicator (≥ 3:1 contrast).
• Screen reader smoke on iOS VoiceOver + Android TalkBack on each release before we promote to production.
• Reflow checks at 200% and 400% zoom; no horizontal scroll on a 320px viewport.

Known limitations

These are the items we know about and are working on. If you hit one not listed here, please tell us — see “Report an issue” below.

• Some legacy PDF assets (older policies, the PAIA manual) are scanned images rather than tagged PDFs. We replace each with a tagged version on its next revision; until then, we will read the content aloud or send a plain-text version on request.
• The contact form currently uses a hidden honeypot field plus IP/ARM rate-limiting — no third-party CAPTCHA iframe is rendered today, so there is no embedded widget that screen readers must navigate. If we later add a visible anti-bot challenge (Cloudflare Turnstile is on the roadmap), we will publish an accessible alternative before it ships.

What we do not use

• Auto-playing video or audio.
• Custom mouse-only widgets (every interactive control is keyboard-operable).
• CAPTCHAs without an accessible alternative.

Report an accessibility issue

Two ways to reach us:

• Email. info@vevalaw.co.za — include the URL, the device + assistive technology you were using, and a short description of what went wrong.
• Web form. /contact?topic=accessibility — routed to the same triage queue as email; no account required.

Response SLA. We acknowledge every report within 7 business days. Where the issue is a barrier to access, we aim to ship a fix within ten working days; complex remediation gets a written plan with milestones.

Audit cadence

Internal automated and manual checks run on every release (see “How we test” above). In addition, we commission a bi-annual external WCAG 2.2 AA audit by an independent accessibility specialist (next audit: H2 2026 — firm to be confirmed). The audit report and our remediation plan are summarised in our annual transparency note.

Formal complaint

If our response is not adequate, the South African Human Rights Commission accepts complaints on grounds of disability under the Equality Act (PEPUDA). Their intake form is at sahrc.org.za.