Accessibility

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the standard most accessibility laws and policies point to.

Where we are now

Rigcall is partially conformant with WCAG 2.2 Level AA. That means some parts don't fully meet the standard yet. The known gaps are listed below, and we're working on them.

What already helps

• Keyboard: everything can be reached with Tab and used with Enter or Space. A teal ring shows where you are, “Skip to content” jumps past the header, and pop-ups keep focus inside, close with Escape and return you to where you were.
• Screen readers: buttons that show only an icon have spoken names, pages have one main heading and clear sections, and messages like “Saved”, errors and scan results are announced.
• No camera needed: everywhere you can scan a code (Scan, checkouts, returns, pack lists, audits), you can also type the gear's tag, such as CAM-03. Printed labels show the tag in text under each code.
• Not color alone: statuses like Overdue, Missing or Approved are always written out in words, not only shown as a color.
• Zoom and small screens: pages work on a phone 320 pixels wide and when zoomed to 200%, without scrolling sideways.
• Motion: the moving background stops if your device is set to Reduce motion, or with “Still background” in More → Your account. Busy screens never move. Videos only play when you press Play.
• Contrast and transparency: text is checked against the real colors behind it, in both looks. If your device is set to Reduce transparency, cards become solid. You can choose Dark, Light or Automatic in More → Your account.

Known limitations

• Some fields have hint text instead of a label. Search boxes, notes and the “type a tag” boxes show grey example text that disappears once you start typing. Screen readers still hear the field's name. We plan to add visible labels.
• Your phone's text size setting doesn't change Rigcall's text. Use your browser's zoom instead (on iPhone: the aA button in Safari).
• Videos and files are hosted elsewhere. Work is shared as links (YouTube, Vimeo, Google Drive, Dropbox). Captions and transcripts depend on whoever uploaded them, and the players belong to those services.
• Signing in happens on Google's pages, which Google designs and maintains.
• The moving background: we measure text contrast with the background held still. While it drifts, a colored glow can briefly pass behind text. “Still background” or Reduce motion avoids this.
• Not yet tested by people who use assistive technology every day. We'd welcome your feedback.

How we test

• An automatic check (axe-core) on the main screens, in both looks, on a phone-sized screen, plus our own checks for contrast on the glass background, visible field labels, headings and sideways scrolling at 320 pixels.
• Google Chrome with the keyboard only: an automated run of Tab, Enter and Escape through the skip link and a pop-up. A full manual pass: [TODO: confirm]
• VoiceOver with Safari on iPhone (iOS). [TODO: confirm]
• VoiceOver with Safari on a Mac. [TODO: confirm]
• Zoom to 200% in Chrome and Safari. [TODO: confirm]

We haven't tested with TalkBack on Android, Windows screen readers or voice control yet.

Tell us about a barrier

If you can't do something in Rigcall, or something is hard to use, email support@rigcall.app. Tell us the page, what you were trying to do, and the device or assistive technology you use, if you're happy to.

We'll reply within 5 business days. If we can't fix it quickly, we'll help you get the task done another way in the meantime.

About this statement

This statement was made on October 5, 2026 and last reviewed on October 5, 2026. We review it every 6 months (next by April 2027) and whenever we make big changes.

Questions about this statement: support@rigcall.app. See also our privacy policy and terms.