Accessibility

Invena Labs Limited (trading as invena)
167-169 Great Portland Street, 5th Floor, London W1W 5PF, United Kingdom
Company number 17237229
Registered in England and Wales

Last updated: 28 July 2026

We are building invena to be usable by as many people as possible, including older adults, caregivers, and people managing household continuity under stress. Accessibility is an ongoing commitment, not a one-time checkbox.

We aim to identify barriers early, fix them where feasible, and improve the experience as the product develops.

Our commitment

We aim to design clear, readable experiences that work well with assistive technologies and respect your device settings. During private beta, some parts of the product are still evolving.

If you encounter a barrier, please use our Accessibility contact form. It helps if you tell us which page or feature caused the problem and what assistive technology you were using, if any.

We review this page as the product evolves. A formal accessibility audit is not yet completed.

Standards we work toward

Web Content Accessibility Guidelines (WCAG)

We align our public website and customer-facing surfaces with the Web Content Accessibility Guidelines (WCAG) 2.2 published by the W3C.

Target: Level AA before general availability.

WCAG is organised around four principles: content must be perceivable, operable, understandable, and robust for people using assistive technologies or different devices. During private beta we apply these principles where we control the experience and document platform limits honestly (see the beta app section below).

Plain language

We write for households, caregivers, and people under stress — not for specialists first.

We follow plain-language practice consistent with:

• ISO 24495-1 (international plain-language principles: relevant, findable, understandable, usable)
• The Plain Language Commission (UK) Clear English approach to grammar, clarity, and layout
• Our own canonical product language (Space, Entry, Document, Invite)

Trust pages, FAQs, and UI labels use short sentences, active voice, and defined terms. Legal pages remain legally precise but use clear headings and structure. We may seek formal Clear English accreditation for selected customer documents before general availability.

Website (invena.app)

Our marketing and legal pages on www.invena.app use:

• Clear headings, labels, links, and keyboard-friendly navigation
• Readable contrast on a light background
• FAQ accordions with native expand/collapse (keyboard accessible)
• Responsive layout for mobile and desktop

We aspire to WCAG 2.2 Level AA over time. We have not yet completed a formal audit of the public website.

Beta app (app.invena.app)

The beta application runs on Next.js (hosted on Vercel). We continue to improve labelling, focus order, and layout for assistive technology.

What works today:

• You can use your browser’s zoom and your operating system’s text size settings on most pages
• Standard browser navigation and tab order apply to many controls

Known limitations during beta:

• We do not yet offer in-app font-size or high-contrast toggles
• Screen reader support is partial — we are improving labelling and flows over time
• Some dense dashboard layouts may be harder to navigate on smaller screens

We intend to invest in stronger in-app accessibility controls before general availability.

Tips while using the beta app

Larger text (iOS)

Settings → Accessibility → Display & Text Size → Larger Text

Larger text (Android)

Settings → Display → Font size or Display size

VoiceOver / TalkBack

You can use your device’s screen reader with the beta app in the browser. Some controls may not yet have ideal labels. If something is unclear, tell us via Accessibility contact.

What we are working toward

• Clearer labels and focus order in the beta app
• Formal WCAG review before general availability
• In-app accessibility settings in the product app

Contact

For accessibility feedback or general help: Contact hub

If you do not receive a response within a reasonable time, reply to the same thread or contact us again with Accessibility in the subject line.