Catalyst Enablement Pty Ltd is committed to ensuring pur platforms are accessible to all users, regardless of disability or assistive technology. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
Accessibility is an ongoing effort. This statement describes our current conformance status, the improvements we have made, known limitations, and how to contact us if you experience barriers.
Conformance Status
The Known By Name platform is partially conformant with WCAG 2.1 Level AA. Partial conformance means that some parts of the content do not yet fully conform to the accessibility standard. We are actively working to close these gaps.
What We Have Done
We have implemented the following accessibility improvements across the platform:
Colour and Contrast
- All body text and UI labels meet or exceed the 4.5:1 contrast ratio required by WCAG 2.1 AA.
- Interactive elements (buttons, links) maintain sufficient contrast in all states including hover and focus.
- Muted and secondary text has been reviewed and updated to meet contrast requirements.
- The rating scale colour gradient (assessment sliders) uses both colour and text labels. Colour is never the sole means of conveying information.
Keyboard Navigation
- A "Skip to content" link is provided to allow keyboard users to bypass repetitive navigation.
- All interactive elements (buttons, links, form fields, sliders) are reachable and operable via keyboard.
- The assessment slider supports Arrow keys (Left/Right/Up/Down), Home, and End for precise value selection.
- Dropdown menus close on Escape key press.
Screen Reader Support
- ARIA roles, labels, and properties are used throughout to communicate component purpose and state.
- Assessment sliders use role="slider" with aria-valuemin, aria-valuemax, aria-valuenow, and aria-valuetext (e.g., "Consistently") for meaningful announcements.
- Toggle buttons (e.g., chart view switcher, status buttons) use aria-pressed to communicate their state.
- Expandable sections use aria-expanded on their trigger buttons.
- Auto-save status and progress indicators use aria-live="polite" regions so updates are announced non-intrusively.
- Decorative icons are hidden from assistive technologies with aria-hidden="true".
- Navigation elements use aria-label, aria-current="page", and appropriate role attributes.
Forms and Inputs
- All form fields have associated visible labels or aria-label attributes.
- Error messages are associated with their respective fields.
- Input fields on mobile prevent unintentional zoom (font-size 16px minimum).
Structure and Semantics
- Pages use a logical heading hierarchy (H1 to H3).
- Navigation regions are marked with appropriate landmark roles.
- The document language is set to English (lang="en").
Motion and Animations
- Page transition animations are subtle (fade + gentle upward motion, 280ms) and do not loop.
- The prefers-reduced-motion OS preference is respected across the platform. Page transitions, hover animations, scroll reveals, and celebratory effects are all disabled when this setting is active.
Charts and Data Visualisations
- All charts (bar, radar, and gap charts) include a "Show data as table" toggle, providing the same data in an accessible HTML table format.
- Colour is never the sole means of conveying information. Chart legends, labels, and data tables provide text alternatives.
Known Limitations
Despite our efforts, there is one area where we are still working to improve accessibility:
PDF reports: Downloaded PDF reports include document metadata (title, author, language) and logical reading order. Full PDF/UA tagging (structured heading roles, reading order markup) is not yet supported by the underlying PDF generation library. Please contact us if you need assistance accessing your report content.
Technical Approach
The Known By Name platform is built using React, with Tailwind CSS for styling. We test with:
- Keyboard-only navigation testing across all major features.
- WAVE browser extension for automated accessibility checks.
- Manual review of ARIA implementation against WCAG 2.1 success criteria.
We test primarily on Chrome and Firefox on Windows and macOS, using NVDA and VoiceOver screen readers. We aim to expand testing coverage over time.
Formal Complaints
If you are not satisfied with our response to your accessibility enquiry, you have the right to lodge a formal complaint:
- Australia: Australian Human Rights Commission
- United Kingdom: Equality and Human Rights Commission
Feedback and Contact
We welcome feedback on the accessibility of the Known By Name platform. If you experience any barriers or have suggestions for improvement, please contact us:
Accessibility Contact
Catalyst Enablement Pty Ltd
Email: info@catalystenablement.com.au
Phone: 0404 345 591
We aim to respond to accessibility feedback within 5 business days. If you are not satisfied with our response, you may contact the Australian Human Rights Commission or, for UK users, the Equality and Human Rights Commission.