Overview
The Empower PWA aims to increase accessibility for all visitors by offering automated system supports alongside rich content customization options. While many features respond directly to a visitor's device settings, others rely on customers populating specific accessibility fields within the Console.
Accessibility and WCAG 2.2 Level AA
Pladia is committed to providing an accessible digital experience through the Empower PWA. We target WCAG 2.2 Level AA across the platform and support screen readers, semantic navigation, transcripts and captions, and other accessibility features.
Our approach combines accessible design and development practices, automated accessibility testing, manual testing with assistive technologies, independent accessibility review, and ongoing improvements as the platform evolves.
In August 2026, automated accessibility testing using Google Lighthouse achieved a 100% accessibility score across the pages tested. Empower also underwent an independent accessibility review by Access to Arts in 2026, with findings from that review informing subsequent improvements to the platform.
Accessibility is also a shared responsibility between the platform and the content published within it. Empower provides features that support accessible content, while venues are responsible for appropriately configuring and populating content such as transcripts, captions and alternative text.
Our Empower PWA is being actively developed to align with WCAG 2.2 Level AA, in accordance with the Victorian Government Accessible Communications Policy. Our approach combines internal audit, independent third-party review, and continuous improvement.
Empower underwent an independent accessibility review by Access to Arts in 2026. The review found results were strong overall, with minor enhancements identified and since addressed.
Built-in Platform & Visitor Device Features
The Empower PWA respects and adapts automatically to individual visitor browser and device settings to ensure a seamless experience.
Dynamic Font & Display Size: The UI automatically responds to the dynamic font or display size configured on a visitor's device or browser.
Device Language Detection: Automatically detects the language assigned to the visitor's browser or device and displays matching content if supported by your Venue. Visitors can also manually switch languages via the Settings icon in the My Visit tab.
Screen reader & mobile compatibility: Native semantic HTML and ARIA attributes support standard screen readers and mobile iOS VoiceOver/Android TalkBack. When viewing the landing map, screen readers will be prompted to take the user to a list view of Spaces.
Mobile navigation: Logical DOM order supports sequential swipe navigation, with focus management preventing common navigation traps in modals and menus.
Content Setup Best Practices
To deliver a fully inclusive experience, venue content creators must populate key accessibility fields during setup in the Console.
Audio Transcripts & Captions:
Populate the Transcript field for any audio file uploaded to the Media Library. The Transcript button will only display to visitors in the audio player if this field contains text.
Include captions in all videos hosted through Vimeo.
Sign Language Support:
Create sign language interpretation videos for Space and Object descriptions, hosted through Vimeo.
Use a sign language symbol as the video thumbnail tile to help visitors quickly scan for accessible content.
Multiple Language Support:
Select your supported languages during your initial Pladia setup to populate language choices in the Console and PWA.
Use the translation icon within text fields or the language dropdown in Content Blocks to enter side-by-side translated content.
Include a language code in the file name or select the appropriate language dropdown when uploading audio to the Media Library.
Note: Un-translated fields will automatically fall back to display your default language content. Image and video files cannot be swapped by language, but their caption fields can be fully translated.
Screen Reader Compatibility:
Ensure full WCAG 2.2 Level AA alignment by populating the Alt Text field for each hero image uploaded to the Media Library. Screen readers rely on these descriptions to outline visual elements to vision-impaired visitors.
You're all set! Contact Customer Success if you have any further questions.