Accessibility statement

Current design approach

• Semantic headings, landmarks, labels and native controls are used across public pages.
• Keyboard access, visible focus and a skip link are included in the main public navigation.
• Content is designed to reflow from small mobile screens to large displays without relying on hover alone.
• Color is not intended to be the only way a status or evidence level is communicated.
• Motion is limited and should respect reduced-motion preferences where animation is present.

Known limitations

The authenticated prototype is still developing and may contain complex tables, charts, generated PDFs or third-party components that need further keyboard, screen-reader or zoom testing. Some uploaded project documents may not be accessible if the organization that supplied them did not provide an accessible source.

Compatibility and testing

We aim to support current versions of major browsers and common assistive technologies. Public pages are checked at mobile, tablet and desktop sizes and with keyboard navigation, but combinations of older browsers, operating systems and assistive software can behave differently.

Alternative access

If a page, document or workflow is difficult to use, contact RubblePass and describe the page, task, device and assistive technology involved. Where practical, we will provide the information in another format or help complete the intended task.

Feedback and response

Use the contact page with “accessibility” in your message. Please do not include sensitive medical information. We will acknowledge the issue, assess its impact and share the next action or an available workaround.

Ongoing work

Accessibility is part of product review rather than a one-time statement. Material changes to navigation, forms, data tables and generated artifacts should be rechecked, and this statement should be updated as formal testing is completed.