RainbookVPAT - for (rainbook-crm)
Accessibility Conformance Report for Rainbook CRM for Jira, WCAG 2.2 edition, in the format of VPAT 2.5.
| Item | Detail |
|---|---|
| Name of product | Rainbook CRM for Jira |
| Report date | 2026-10-13 |
| Product description | A CRM inside Jira Cloud: deals, accounts, contacts, email and meetings as Jira work items, with reports, Ask and record pages in the Rainbook workspace. |
| Contact | support@rainbook.humanr.ai |
| Evaluation methods used | Automated checks with axe-core on each captured screen state, in light and dark themes and at phone width, and for the workspace also at tablet widths, 200% zoom and 320 px; Automated layout checks on each captured screen state: targets of at least 24 px, reflow at 320 px, WCAG text spacing, and a keyboard pass that finds any focused control hidden under other content; Keyboard-only walkthroughs of the grid, the deal board, the record page and Ask, recorded on video; Colour contrast checks of every text and mark colour in the design tokens, in both themes; Review of each criterion against the interface, its automated interface tests and the captured screens |
| Applicable standard | Web Content Accessibility Guidelines 2.2, Level A and Level AA |
Every Level A and AA success criterion has been evaluated.
Testing with screen readers and other assistive technology has not been done yet.
Terms
- Supports: the functionality has at least one method that meets the criterion without known defects.
- Partially Supports: some functionality does not meet the criterion.
- Does Not Support: the majority of functionality does not meet the criterion.
- Not Applicable: the criterion is not relevant to the product.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Every icon-only button has a text label, decorative icons and account tiles are hidden from assistive technology, and every chart is a captioned figure with a written summary; Ask answers can be shown as a table. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | Rainbook has no audio or video content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | Rainbook has no audio or video content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | Rainbook has no audio or video content. |
| 1.3.1 Info and Relationships (Level A) | Supports | Headings, lists, tables, form labels and landmarks are marked up so their structure reaches assistive technology; the grid uses the ARIA grid pattern. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | Reading and focus order follow the visual order at every width, including the phone layout and 320 px reflow. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Instructions name the control or field they refer to; none relies on shape, size, position or sound alone. |
| 1.4.1 Use of Color (Level A) | Partially Supports | The health block on accounts and deals shows the score number but tells Healthy, Watch and At risk apart only by colour; the band name is available to screen readers but not shown. Charts, status lines and the health meter label every colour with text. |
| 1.4.2 Audio Control (Level A) | Not Applicable | Rainbook plays no audio. |
| 2.1.1 Keyboard (Level A) | Supports | Every function works from the keyboard: the grid, the deal board (move a card with the keyboard or the Move to stage menu), record pages, Ask and its charts, menus and dialogs. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus never gets trapped: dialogs, sheets and menus close with Escape and return focus to where it was. |
| 2.1.4 Character Key Shortcuts (Level A) | Supports | Single-key shortcuts can be turned off in Settings (Keyboard), and they are off by default on touch devices; they never fire while typing in a field. |
| 2.2.1 Timing Adjustable (Level A) | Supports | There are no session time limits. An Undo message stays while the pointer or focus is on it and can be undone with Ctrl+Z or Command+Z; applied changes keep a standing Undo, deleted records can be restored, and an import can be undone for 14 days. |
| 2.2.2 Pause, Stop, Hide (Level A) | Partially Supports | Nothing blinks or scrolls on its own, and animation follows the reduced-motion setting. The live agent board and the Inbox refresh their contents every 60 seconds with no control to pause the updates. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | Nothing flashes. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Each page has header, navigation and main landmarks, and moving to a new area puts focus on its heading. |
| 2.4.2 Page Titled (Level A) | Supports | Each page has a title: the workspace names the open area, and admin pages are titled in Jira. |
| 2.4.3 Focus Order (Level A) | Supports | Focus moves in a logical order, goes to the heading of a newly opened area or panel, and returns to the trigger when a dialog closes. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Every link says where it goes, alone or with its sentence. |
| 2.5.1 Pointer Gestures (Level A) | Supports | No function needs a multi-finger or path gesture. |
| 2.5.2 Pointer Cancellation (Level A) | Supports | Controls act when the pointer is released; a drag can be cancelled by dropping it back or pressing Escape. |
| 2.5.3 Label in Name (Level A) | Supports | Every control's accessible name contains its visible label; icon-only buttons have no visible text. |
| 2.5.4 Motion Actuation (Level A) | Not Applicable | Rainbook has no motion-operated function. |
| 3.1.1 Language of Page (Level A) | Supports | Every page declares English, the language of its text. |
| 3.2.1 On Focus (Level A) | Supports | Focusing a control never changes the page or opens something on its own. |
| 3.2.2 On Input (Level A) | Supports | Changing a setting or field never moves the user to another page; changes apply where they are made. |
| 3.2.6 Consistent Help (Level A) | Supports | Send feedback is in the same place, the person menu in the header, on every workspace area. |
| 3.3.1 Error Identification (Level A) | Supports | A field with an error is marked invalid, the error is described in text beside it, and focus moves to the first field to fix. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Every field has a visible label, with instructions where a format is needed. |
| 3.3.7 Redundant Entry (Level A) | Supports | Multi-step flows carry earlier answers forward and never ask for the same information twice. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Every control exposes its name, role, state and value, using native elements or the matching ARIA pattern for the grid, menus, tabs and dialogs. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | Rainbook has no audio or video content. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | Rainbook has no audio or video content. |
| 1.3.4 Orientation (Level AA) | Supports | Content works in portrait and landscape; no view locks the orientation. |
| 1.3.5 Identify Input Purpose (Level AA) | Not Applicable | Rainbook has no field that collects the user's own personal details; contact fields record other people's details. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text meets 4.5:1 (3:1 for large text) in light and dark themes. Automated checks found no failure; where they could not decide (text over layered backgrounds), the colours are design tokens checked in pairs. |
| 1.4.4 Resize Text (Level AA) | Supports | Text resizes to 200% without loss of content or function; the workspace is checked at 200% zoom and pages at phone width. |
| 1.4.5 Images of Text (Level AA) | Supports | Text is real text, never an image of text. |
| 1.4.10 Reflow (Level AA) | Partially Supports | Workspace pages reflow to a 320 px width without scrolling in two directions; data grids and the deal board scroll sideways by design, and each also has a phone list. Four places run past a 320 px window: an account's page and the record summary panel in Jira, where the open-deals total with its "Excludes 1 deal you can't open" note does not wrap (an account's page also runs 8 px past a 390 px phone); the deal panel in Jira, whose activity list runs 27 px past the edge; the close button of an Undo message, 4 px past the edge; and the admin pages, whose section navigation does not wrap below about 360 px (they fit a 390 px phone). |
| 1.4.11 Non-text Contrast (Level AA) | Supports | Control borders, focus rings, chart marks and status markers meet 3:1 against their background in both themes. |
| 1.4.12 Text Spacing (Level AA) | Partially Supports | With WCAG's increased line, letter, word and paragraph spacing, most text wraps and nothing overlaps, but some single-line labels are cut short: stage names and deal names on the deal board's Needs setup lane, people's names in pivot headers, one-line email previews in Conversations, and, in Jira's 360 px record summary and customer panels, the open-deals total and the add-deal note, which run past the edge. |
| 1.4.13 Content on Hover or Focus (Level AA) | Partially Supports | Tooltips appear on hover and on focus and stay while the trigger is hovered or focused, but the pointer cannot move onto a tooltip, and Escape hides a tooltip only when its trigger has keyboard focus. Menus and popovers stay open until dismissed and close with Escape. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Areas are reached from the navigation, the command palette (Command or Ctrl+K), search and links between records. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | Every focusable control shows a 2 px focus ring in both themes. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA) | Partially Supports | Tabbing through every screen, focused controls stay in view, and in the grid and Ask's charts none is hidden under a sticky header, pinned column or totals row. Four places can hide one: on the Proposals page, a person's link scrolls under the workspace header's quarter strip; on a record with a possible duplicate, the owner field scrolls under the header; on a record with a masked note, the related links sit under the message at the bottom of the screen until it is closed; and in Ask, with a chart's chips menu open, Tab can reach a menu item drawn outside the window. |
| 2.5.7 Dragging Movements (Level AA) | Supports | Every drag has a single-pointer alternative: Move to stage on board cards, the column menu for moving and sizing columns, and Choose files beside file drop. |
| 2.5.8 Target Size (Minimum) (Level AA) | Partially Supports | Every target is at least 24 by 24 px or spaced on desktop and tablet layouts, and 44 by 44 px on phones, with two exceptions: while a deal's page is still loading, its stage path segments are 22 px wide with no full-size Change stage beside them yet, and the setup wizard's Groups step lists its create-or-choose options as 20 px rows closer together than 24 px. |
| 3.1.2 Language of Parts (Level AA) | Partially Supports | Rainbook's own text is English. Email, notes and meeting text are shown as their authors wrote them, without marking a passage in another language. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | The header and navigation are the same on every area, and the admin navigation is the same on every admin page. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Controls with the same function have the same name and icon everywhere. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages say what happened and what to do next, with the accepted values when an entry is refused. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | An import is reviewed in a dry run first and can be undone for 14 days; bulk changes are confirmed and can be undone; deleted records are retired and can be restored; erasing a person's data shows everything to be erased for review first. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA) | Not Applicable | Signing in is Atlassian's; Rainbook adds no sign-in step. |
| 4.1.3 Status Messages (Level AA) | Supports | Saves, Undo messages, progress and errors are announced without moving focus, through status and alert regions. |
Questions about accessibility: support@rainbook.humanr.ai.