Elafent Accessibility Statement

Last updated 20 October 2025

Introduction

Elafent is committed to providing digital experiences that are accessible and inclusive for people with disability. This statement explains how we approach accessibility.

Scope of this statement

This statement applies to Elafent’s web applications (Workspaces), including Elafent-hosted, public-facing Access Map deployments (for example, accessmap.hobartcity.com.au).

Measures to Support Accessibility

Elafent takes the following measures to ensure accessibility:

  • Include accessibility throughout our internal policies.

  • Assign clear accessibility goals and responsibilities.

  • Employ formal accessibility quality assurance methods.

  • Engage with accessibility advisory groups and external accessibility experts, including co-design with lived-experience participants where relevant.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) 2.2 define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

Elafent is largely conformant with WCAG 2.2 Level AA., however despite our best efforts to ensure accessibility, there may be some limitations due to the geospatial nature of the content. Below is a description of known limitations and potential alternative solutions.

Limitations and Alternatives

Interactive geospatial map view (blind users)

Limitation: Interactive geospatial maps can be difficult to make fully WCAG-conformant for people who are blind because key meaning is often conveyed through visual-spatial relationships (relative position, distance, boundaries, clustering). Even when elements are labelled, a screen reader user may not be able to perceive or explore the map view in an equivalent way.

Alternative: Where maps are provided, we provide a screen-reader and keyboard-accessible List View (or equivalent non-visual presentation) that contains the same underlying information (e.g., place names, attributes, statuses) so blind users can access the content without relying on spatial cues. This approach aligns with providing information “in formats that suit different needs” and with building solutions to support screen readers and keyboard navigation from the start.

Directions and routing using third-party apps

Limitation: Some deployments provide directions by launching Google Maps or Apple Maps. Accessibility and presentation in those experiences are controlled by the third-party provider and the user’s device settings.

Alternative: Use the in-app/on-site location details and List View to review accessible features before launching third-party directions.

Printable/PDF maps and offline formats

Limitation: Printable or PDF outputs may not convey every interactive feature available online, and some map content remains inherently visual.

Alternative: Use the List View for full text access to locations and attributes, and use PDF/print outputs as a complementary format for offline navigation.

Please contact us if you observe an issue not listed above.

Additional Accessibility Considerations & Success Criteria

Although our goal is WCAG 2.2 Level AA conformance, we have also applied some additional Success Criteria to enhance accessibility in certain cases:

  1. Audio screen reader support, keyboard navigation & adjustable contrast to enable easy access for a people with disabilities.

  2. Selectable Accessibility Profiles such as wheelchair, vision impairment, hearing assistance.

  3. Mobile & desktop support via an intuitive, adaptive design.

  4. Personalised & customisable PDF printable maps with a unique location centric grid reference system to support traditional paper-based like navigation.

  5. Multi-faceted accessibility filtering across facilities, attractions and businesses.

  6. Directions with Google Maps™ or Apple® Maps.

  7. Out-of-the-box integrations with the National Public Toilet Map and Australian Tourism Data Warehouse ensuring data stays up to date.

Assessment Approach

Elafent assesses accessibility using a combination of:

  • Self-evaluation (including accessibility QA)

  • External evaluation (including web accessibility evaluation tools)

  • Engagement and review with advisory groups / lived-experience participants (where applicable)

Compatibility

Elafent is designed to be compatible with the following assistive technologies:

  • Chrome (current) + NVDA (current) + Windows 10/11

  • Firefox (current) + NVDA (current) + Windows 10/11

  • Microsoft Edge (current) + JAWS (current) + Windows 10/11

  • Chrome (current) + JAWS (current) + Windows 10/11

  • Safari (current) + VoiceOver + macOS (current)

  • Chrome (current) + VoiceOver + macOS (current)

  • Safari + VoiceOver + iOS (current)

  • Chrome + TalkBack + Android (current)

Technical Specifications

Accessibility of Elafent relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML

  • WAI-ARIA

  • CSS

  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Feedback & Formal Complaints

We welcome your feedback on the accessibility of Elafent. Please let us know if you encounter accessibility barriers on Elafent:

We try to respond to feedback within 4 business hours.