Skip to main content
RILayer Infrastructure
Inclusive by Design

Accessibility Statement.

RILayer is committed to making this infrastructure accessible and usable for as many people as possible. We design and build our systems with absolute inclusion in mind.

Our commitment

We aim to follow recognised accessibility best practices, including the principles of the Web Content Accessibility Guidelines (WCAG), to ensure the site is usable by people with a wide range of abilities and devices.

We focus on:

  • Clear typography and readable font sizes
  • Meaningful headings and structured content
  • High colour contrast ratios
  • Keyboard-friendly navigation
  • Logical page structure
  • Avoiding unnecessary visual noise
  • Text alternatives for images
  • Simple, direct language

What we are doing

We systematically aim to:

  • Use semantic headings and architecture
  • Ensure responsive readability on all screens
  • Maintain pristine spacing and typography
  • Keep navigation distinct and consistent
  • Avoid flashing content or heavy animation
  • Ensure interactive elements are identifiable
  • Test across multiple browsers and devices

Accessibility is an architectural requirement whenever new content or systems are deployed.

Known limitations

Some third-party tools (such as scheduling software, embedded forms, or external analytical widgets) may introduce accessibility limitations that exist outside our direct code environment.

We audit providers carefully and implement systemic improvements where possible.

Feedback and support

If you encounter any accessibility barriers while using this infrastructure, please contact us and include:

1

The specific URL or page accessed

2

The action you were attempting

3

The device and browser used

We review telemetry and user reports to prioritise architectural fixes.

Accessibility is continuous

System accessibility is not a one-time deployment. We audit and refine access as the platform evolves, new modules are integrated, and web standards advance.

Your feedback directly influences our development roadmap.

Need assistance?

If you encounter any accessibility barriers, please let us know so we can help.

Contact Support