1.Our commitment
Pikorua Security aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across pikoruasecurity.com, the Pikorua Security web application, the broker and vendor upload pages, and the emails the service sends.
This matters beyond our own users. Public-sector customers, such as municipalities, transit authorities and school districts, have accessibility obligations under Section 508 of the Rehabilitation Act and Title II of the Americans with Disabilities Act. The vendors and brokers who receive our deficiency notices include people who use screen readers, magnification, voice control or a keyboard alone, and they need to fix a missing endorsement as easily as anyone else.
2.What we build in
- Semantic HTML with landmarks, one H1 per page and a logical heading order, so screen reader users can move through a vendor record by heading.
- Full keyboard operation for every control, including the endorsement validator, rule builder and permission settings, with a clearly visible focus indicator.
- Text contrast of at least 4.5:1 for body copy and 3:1 for large text and interface components.
- Compliance status never shown by color alone: every Compliant, Deficient, Expiring and Pending pill carries a text label.
- Labels on every form field, with errors described in text, tied to the field and announced to assistive technology.
- Motion limited to short opacity and position changes, and reduced further when your system asks for reduced motion.
- Session time-outs that warn you first and can be extended without losing work.
3.WCAG 2.2 criteria we paid particular attention to
WCAG 2.2 added six success criteria at Levels A and AA. This is how Pikorua Security meets each one:
| Criterion | Name | How Pikorua Security meets it |
|---|---|---|
| 2.4.11 | Focus Not Obscured (Minimum) | Sticky headers and drawers never cover the element that has keyboard focus. |
| 2.5.7 | Dragging Movements | Every drag-and-drop upload and column reorder has a button or file picker alternative. |
| 2.5.8 | Target Size (Minimum) | Interactive targets are at least 24 by 24 CSS pixels; most buttons are 44 pixels tall. |
| 3.2.6 | Consistent Help | The help menu and support contact sit in the same place on every screen. |
| 3.3.7 | Redundant Entry | Vendor and broker details entered once are prefilled in later steps and notices. |
| 3.3.8 | Accessible Authentication (Minimum) | Sign-in supports password managers, paste and SSO; no puzzles or memory tests. |
4.Documents and reports
Certificates and endorsement pages usually arrive from brokers as scanned images. We cannot make another organization's scan accessible, so Pikorua Security extracts the fields from every document and presents them as structured text: insurer, policy number, limits, endorsement form numbers and editions, and each deficiency in plain language.
Reports and tender packets that Pikorua Security generates are tagged PDFs with a defined reading order, real text rather than images, and table headers marked up for assistive technology.
5.How we test
- Automated accessibility checks run on every pull request against our core flows: sign-in, vendor list, document review, deficiency notice and broker upload.
- Each quarter we test manually with a keyboard alone, VoiceOver on macOS and iOS, NVDA and JAWS on Windows, and TalkBack on Android.
- We check zoom to 400%, reflow at 320 CSS pixels wide, and Windows high contrast mode.
- An independent accessibility specialist audits the application once a year, and new features are reviewed against WCAG 2.2 AA before release.
6.Known limitations
We know about the following gaps and are working on them:
- Original scanned documents. The image of a broker's certificate is not accessible in itself. The extracted fields and text summary beside it are the accessible alternative.
- Endorsement comparison on small screens. The side-by-side edition comparison needs horizontal scrolling below 400 CSS pixels. The same comparison is available as a linear list in the document detail view.
- Third-party screens. Procore, Yardi and other systems opened from Pikorua Security follow their own providers' accessibility standards.
7.Accessibility Conformance Report
Procurement teams can request our Accessibility Conformance Report, prepared on the ITI VPAT template and covering WCAG 2.2 and the Revised Section 508 Standards. Request it through the Trust Center or by email.
8.Report a barrier or request an alternative format
Email support@pikoruasecurity.com with "Accessibility" in the subject line, or call toll-free 1800-425-0619, 24 hours a day, Monday to Friday. Tell us the page or feature, what you were trying to do and the assistive technology you use, if any.
We reply within 2 business days. If we cannot fix the barrier quickly, we will give you another way to complete the task, such as having our support team process an upload with you, and tell you when the fix will ship. Any document on this website is available in an alternative format on request.
If you are not satisfied with our response, write to legal@pikoruasecurity.com and a member of our leadership team will review it.