Accessibility

Accessibility Statement

RiverPen endeavours to design and deliver interfaces that are usable, readable, and keyboard-accessible as a matter of ordinary project delivery.

Our approach

  • Semantic structure, readable typography, sufficient contrast, keyboard-accessible controls, and clear focus states are used where feasible.
  • Where appropriate, alt text, labels, status messages, and a logical content order are provided to assist screen readers.
  • Accessibility is considered during design and build, not merely after launch.

What we try to include

  • Keyboard navigation support where the implementation permits it.
  • Readable heading structure and plain-language labels.
  • Responsive layouts and scalable text.
  • Accessible forms, error states, and success feedback where included within scope.

What may still vary

  • Third-party plugins, embedded services, and legacy client systems may have accessibility limitations outside RiverPen's direct control.
  • A full accessibility audit or certification is a separate deliverable unless the contract provides otherwise.
  • If a project requires a specific standard such as WCAG 2.1 AA, that requirement should be stated in the scope from the outset.

Reporting barriers

  • If you identify a barrier on this site or on a RiverPen-built project, please provide the relevant details and the page or screen involved.
  • The issue will be reviewed and, where feasible, corrected or addressed through an alternative measure.
  • For client projects, any remediation approach will depend on the agreed scope, budget, and release stage.

Effective date: August 24, 2025