EBBE SignalBack
EBBE Signal
Last updated · February 2026

Accessibility Statement

EBBE Signal is committed to digital accessibility. This statement explains how we conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the accessibility standard set by the W3C and adopted by the Australian, UK, EU and US governments for public-facing digital services.

Conformance target: WCAG 2.1 Level AA
Signal partially conforms with WCAG 2.1 AA. Full conformance across every screen is our stated goal — the roadmap and known gaps are listed below.

Scope

This statement applies to the EBBE Signal web application and marketing site published at signal.ebbe.com.au and every custom-slug variant of the app (e.g. signal.ebbe.com.au/<organisation>). It covers every page reachable from the public landing site and every logged-in screen inside the product.

Conformance status

Signal partially conforms with WCAG 2.1 Level AA. Partially conformsmeans that some parts of the content do not fully conform to the accessibility standard — we list those gaps explicitly under Known limitations below and track each one to a fix in an upcoming release.

What Signal does well today

1.3.1

Meaningful structure

Conforms
Every page uses semantic HTML5 landmarks (<header>, <nav>,<main>, <footer>) and a single <h1>followed by a strict heading hierarchy. Data tables use proper <th> scope attributes.
1.4.3

Contrast (minimum)

Conforms
Body text on both marketing surfaces (cream #F7F4ED on ink #072025) and in-product surfaces (#111110 on #F9F9F8) exceeds the 4.5:1 ratio required at AA. Interactive elements exceed 3:1 against their background.
1.4.4

Resize text

Conforms
The app is fully responsive and supports browser zoom up to 200% without loss of content or functionality. Type scale uses relative units so text respects the operating-system font-size preference.
2.1.1

Keyboard operable

Conforms
Every interactive element (navigation, buttons, forms, tables with sortable headers, filters, dialogs, the opportunity form and the Ad Kit downloads) can be reached and operated with a keyboard alone. Focus order matches the visual order.
2.4.3

Focus order

Conforms
Tab order follows the visual reading order in every page and in every dialog. Modal dialogs (login, invite user, cascade-delete confirms, photo crop) trap focus while open and restore focus to the trigger element on close.
2.4.7

Focus visible

Conforms
Every focusable element carries a visible focus indicator — a 1px solid outline in the brand ink colour (#111110) — which never relies on colour alone.
3.1.1

Language of page

Conforms
Every HTML document declares lang="en".
3.3.1

Error identification

Conforms
Form errors (login, register, invite, opportunity form) are shown inline next to the field they refer to and are also announced via toast notifications with role=alert.
3.3.2

Labels or instructions

Conforms
Every form input carries a visible label. Placeholder text is never used as the only label. Required fields are marked textually, not with colour alone.
4.1.2

Name, role, value

Conforms
All interactive components use accessible primitives from Radix UI (via shadcn/ui) — buttons, dialogs, dropdowns, tabs, tooltips and toasts ship with correct ARIA roles, states and properties out of the box.

Known limitations

We track every non-conforming element to a fix. If you find something we’ve missed, please tell us — see how to report a barrier below.

1.1.1

Non-text content (marketing imagery)

Partially conforms
Decorative marketing photos on the landing page carry alt="" as required, but a small number of illustrative brand photos still need descriptive alt text. Scheduled: next marketing release.
1.4.11

Non-text contrast (chart legends)

In review
A handful of dashboard chart legends sit slightly below the 3:1 contrast threshold on the light theme. We’re re-tuning the chart palette to bring every state above 3:1.
2.4.1

Bypass blocks (skip to content)

Partially conforms
A visible “Skip to main content” link is present on the marketing site; it is on the roadmap for every in-app screen so screen-reader users can jump past the top nav on each route change.
1.4.13

Content on hover or focus (tooltips)

Partially conforms
Every tooltip is dismissable via the Escape key, but a few tooltips currently disappear when the pointer moves. We’re migrating remaining custom tooltips to Radix Tooltip so the WCAG 2.1 dismissable/hoverable/persistent rule is met throughout.

How we test

  • Automated: every build runs axe-core over the landing and core in-app routes. New rule violations block the release.
  • Manual keyboard: every new feature is walked through with the mouse disconnected before it ships.
  • Screen readers: spot-checked with VoiceOver (macOS/iOS), NVDA (Windows) and TalkBack (Android) on the login, dashboard, pipeline, opportunity form and contacts screens.
  • Contrast: the brand palette (see our Security & Trust page and the internal visual style guide) has been audited against WCAG contrast requirements.

Assistive technology compatibility

Signal is designed to work with the current major versions of:

  • Screen readers — VoiceOver (macOS 14+, iOS 17+), NVDA 2024+, JAWS 2024+, TalkBack (Android 13+)
  • Browsers — Chrome, Edge, Firefox, Safari (latest two major versions)
  • OS-level zoom and high-contrast modes
  • Speech-input software (Dragon, Voice Control) for keyboard-driven workflows

Report a barrier

If you encounter a barrier while using Signal — a page you can’t navigate, content you can’t read, or a form you can’t submit — please tell us. We aim to acknowledge every report within two business days and to fix or provide a workaround within ten business days for issues that block core tasks.

Accessibility contact
Email hello@ebbe.com.au with the subject line “Accessibility feedback — Signal”.
Please include the page URL, what you were trying to do, and the assistive technology and browser you were using so we can reproduce the issue.

Formal complaints

Australian users who are not satisfied with our response may contact the Australian Human Rights Commission under the Disability Discrimination Act 1992 (Cth). International users may refer to the equivalent regulator in their jurisdiction.

Preparation of this statement

This statement was last reviewed and updated in February 2026. It was prepared by the EBBE product team following a self-evaluation of the platform against WCAG 2.1 Level AA using a combination of automated tooling (axe-core, Lighthouse) and manual keyboard and screen-reader testing.

The next scheduled review is August 2026, or sooner if there is a material change to the platform.

© 2026 EBBE. All rights reserved.
SecurityPrivacyTermsAccessibilityebbe.com.au