Viranova

Accessibility Statement

What Viranova commits to, what it currently meets, what it does not yet meet, and how to tell us when something blocks you.

Last updated: 12 August 2026

Standard: WCAG 2.2 Level AA

Viranova is a reading product. If a page is hard to read, hard to operate, or impossible to navigate with assistive technology, that is a defect in the product, not an inconvenience for the reader.

What Viranova commits to

  • Body text on every article defaults to at least 17px with a 1.68 line height, and no text on a public page renders below 12.5px.
  • Every text and interface colour pairing is checked against WCAG 2.2 AA contrast, automatically on every release and manually over photography.
  • Every interactive control that stands on its own carries a target of at least 44 by 44 CSS pixels. Links inside a sentence use the WCAG 2.5.8 inline exception.
  • Article bodies use real heading elements, so assistive technology can navigate a long read by section.
  • Images carry alt text that describes their purpose. An image whose caption already describes it is marked decorative rather than repeating the caption.
  • Motion never gates legibility. Content is at full opacity from the first frame, entrances are capped at roughly a fifth of a second, and reduced-motion preferences switch movement off site-wide.
  • Every page can be operated by keyboard alone, with a visible focus indicator and a skip link to the main content.

What is checked, and how often

Automated accessibility checks and a colour-contrast register run on every release. Neither is treated as sufficient: automated tools cannot judge whether alt text is meaningful, whether a heading structure matches the argument of a piece, or whether a page still works at 200% zoom. Those are reviewed by a person, per template.

What Viranova does not yet meet

We publish the gaps rather than claim a clean sheet.

  • Media hosted by third-party platforms (video players, social embeds) is delivered by those platforms, and their captioning and controls are outside Viranova's direct control. Viranova checks daily that published media still resolves and replaces broken players with a described fallback.
  • The Viranova media kit PDF is not tagged. Its title, author and language metadata are correct, but it carries no structure tree, so a screen reader cannot navigate it by heading or read its tables in a reliable order. We will not add the tagging markers without building the real structure behind them, because a PDF that advertises itself as tagged and is not is worse for an assistive-technology user than one that is honestly untagged. Every figure in the kit — rates, formats, audience data and terms — is published as ordinary HTML on this site, and that version is the accessible one.
  • Viranova has not yet commissioned an independent third-party accessibility audit. That is a stated intention, not a completed step, and this page will name the auditor and date when it happens.

Tell us when something blocks you

If any part of Viranova is difficult or impossible to use, email accessibility@viranova.co.za. We aim to acknowledge within two working days and to give a fix or a workaround within ten working days. Tell us the page, what you were trying to do, and the browser or assistive technology you were using — it makes the fix much faster.

Accessibility reports are treated with the same seriousness as corrections: they are logged, owned by a named person, and closed only when the reader who reported the problem can complete the task.