Accessibility

vivaBooks is used by accounting staff all day and by employees checking a pay stub once a fortnight. Both groups include people using screen readers, keyboard-only navigation, and magnification, and payroll is not optional work — if someone cannot reach their own pay information, that is a real harm rather than an inconvenience.

Our target

We work to WCAG 2.1 Level AA. That meets the standard the Accessibility for Ontarians with Disabilities Act applies to web content, which is currently WCAG 2.0 Level AA, and moves us toward the WCAG 2.2 standard Ontario has signalled it will adopt.

Where we actually are

We have not completed a full third-party audit, so we are not claiming conformance. What we can state:

• The interface is built on an accessible component library with keyboard interaction and focus management handled at the component level.
• Layouts are responsive and usable at 200% zoom and on small screens.
• Colour is not used as the only way to convey status.
• Confirmations are proper dialogs rather than browser pop-ups, so they are announced correctly.

Known gaps we are working on:

• Some data-dense payroll tables need better header association and a more predictable keyboard order.
• Not every icon-only control has been checked for an accessible name.
• Generated PDF documents — pay stubs, T4 slips, job letters — are not yet tagged for screen readers.
• Colour contrast has not been verified across every state of every component in both light and dark themes.

Telling us about a barrier

If something in vivaBooks stops you doing your job, tell us through the contact page. Describe what you were trying to do and what assistive technology you use, and we will reply. If you need payroll information that you cannot reach in the interface, say so and we will get it to you in a format you can use while we fix the underlying problem.

Firms with their own accessibility obligations can request this statement and our current known-gaps list in writing for their compliance records.