Qwrki

Accessibility

Our target: WCAG 2.1 level AA

Our target

Qwrki aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA across the product.

Each change is checked on the routes listed below. A check that fails blocks the change.

What is tested

On every change to the application, an automated gate opens a built copy of the app as a signed out visitor and as an organisation owner, then scans these 64 routes:

Every scan runs axe with the wcag2a and wcag2aa rule sets and fails on any finding rated serious or critical.

  • Sign in (/sign-in, signed out)
  • Home (/)
  • Customers list (/customers)
  • Cases list (/cases)
  • Finance (/finance)
  • Approvals (/approvals)
  • Settings (/settings)
  • Admin people (/admin/people)
  • Audit trail (/admin/audit)
  • Customer import form (/customers/import)
  • Contract import form (/contracts/import)
  • Deal import form (/deals/import)
  • Invoice import form (/finance/invoices/import)
  • Item import form (/finance/items/import)
  • Project import form (/projects/import)
  • Task import form (/tasks/import)
  • Asset import form (/assets/import)
  • Time import form (/time/import)
  • New contract form (/contracts/new)
  • Invoices (/finance/invoices)
  • Estimates (/finance/estimates)
  • Proposals (/finance/proposals)
  • Credit notes (/finance/credit-notes)
  • Contracts (/contracts)
  • Recurring invoices (/finance/recurring)
  • Collections (/finance/collections)
  • Expenses (/finance/expenses)
  • Price book (/finance/items)
  • Policies (/legal)
  • Website Chat (/chat/conversations)
  • Conversations (/conversations)
  • Connected data (/integrations)
  • Deals (/deals)
  • Tasks (/tasks)
  • Projects (/projects)
  • Leads (/leads)
  • Employees (/ai/employees)
  • Missions (/ai/missions)
  • Calendar (/calendar)
  • Automations (/automations)
  • Playbooks (/playbooks)
  • Rules (/rules)
  • Pipelines (/pipelines)
  • Lead forms (/leads/forms)
  • Content templates (/content/templates)
  • Templates (/projects/templates)
  • Content (/content)
  • Knowledge (/knowledge)
  • AI writer (/write)
  • Files (/files)
  • Drive (/drive)
  • Assets (/assets)
  • Media (/media)
  • Time (/time)
  • Workload (/workload)
  • My work (/my-work)
  • Meetings (/meetings)
  • Surveys (/surveys)
  • Reports (/reports)
  • Analytics (/analytics)
  • Mail (/mail)
  • Notifications (/notifications)
  • Actions (/actions)
  • Announcements (/announcements)
  • Customer detail (/customers/[id], one seeded customer)

What automation cannot prove

The automated gate reads rendered markup and styles. It cannot prove that a screen reader announces the right thing in the right order, that keyboard focus moves where a person expects, or that a chart or diagram makes sense without seeing it.

Those checks are manual, and they happen when a screen changes in a way the gate cannot judge. If you find a barrier the gate missed, we want to hear about it.

Report a barrier

Email support@qwrki.com with the page address, what you were trying to do, and what assistive technology you use if you are comfortable sharing it. We will confirm receipt and tell you what happens next.