Accessibility

Last updated: 31 October 2026

We want everyone to be able to use Perdura, including with a keyboard, a screen reader, larger text or reduced motion. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Perdura does not yet fully meet it everywhere; this page says what is in place and what is not.

What is in place

  • Every page can be used with a keyboard, with a visible focus ring.
  • Every form field has a label, and errors are announced and tied to their field.
  • Each chart has a summary for screen readers and a "Show as a table" option that lists every point.
  • The gym screen moves focus to what comes next and announces each saved set and the end of each rest.
  • Motion is reduced or removed when your device asks for less motion, and moving content can be paused.
  • Every control is at least 24 by 24 pixels, apart from links inside a sentence. On a phone, about half of the buttons and fields are 44 pixels or more; most of the others are icon buttons of 36 to 40 pixels, and some links in lists and tables are 24.
  • Perdura has light and dark appearances.

How we check it

On 31 October 2026 we measured the public pages and the signed-in pages, the signed-in ones in a development copy of Perdura with sample data:

  • An automated rules scan (axe-core 4.13, WCAG 2.2 A and AA) on 15 signed-in pages and 9 public pages, at phone, tablet and desktop widths, and on every section in both appearances. It found no serious or critical problems.
  • The size of every control on those pages. Before the fixes below, four controls failed the WCAG 2.2 target size test, and many more were under 24 pixels and passed it only because of the space around them. After the fixes, no control on those pages is under 24 pixels.
  • The contrast of text over photographs, colour gradients and see-through surfaces, which the rules scan cannot judge: measured from pictures of the pages in both appearances, pixel by pixel behind each piece of text. Seven places were under 4.5:1 and are fixed; two remaining readings are a line drawn through the words on purpose and a chart line under one label.
  • An automated walk through setting up a plan, a workout, adding food, cancelling Premium and deleting an account, recording what a screen reader is given at each step: where focus is, the name and role of each control, and what is announced. This is not the same as testing with a screen reader.

The rules scan, the size check and the walk now run every night, and a smaller rules scan runs on every change. The earlier scan, with WCAG 2.1 rules, ran on 28 September 2026 with no serious problems found.

What we fixed on 31 October 2026

  • Small controls are now at least 24 pixels: Sign in in the header, Forgot password, the RSS feed link, the consent box, Rotate in 3D, the days in the calendar's list, the foods in the Diary, links on Goals, Progress and Today, and the logo and Community button at tablet width.
  • The account menu button no longer points to a menu that is not on the page.
  • In the Diary's table, every column has a header, and each meal's buttons belong to that meal.
  • The save status stays in place for screen readers, so a change to it can be announced.
  • Text over photographs and charts now reaches 4.5:1: the plans' free-trial line, the home page's photo sections and its opening on phones, the reading suggestion on Today, and the labels on line charts.
  • In setting up a plan, each new step takes focus to its heading, and each field's name is said with its unit.
  • The account deletion question opens on Cancel, so Enter cannot delete by accident.

What is not done yet

  • Perdura has not yet been tested with a screen reader by a person. A VoiceOver pass (Mac) and an NVDA pass (Windows) on setting up a plan, a workout, adding food, cancelling and deleting an account are scheduled and have not been run. Automated checks cannot judge everything, such as whether an announcement comes at the right time.
  • The signed-in pages were checked with sample data, not with a real account.
  • Many controls are smaller than 44 pixels, the size we aim for on touch screens.

Tell us about a problem

If something in Perdura is hard or impossible for you to use, write to support@perdura.fit with the page and what happened. We reply within 5 business days and, while we fix it, help you do what you were trying to do another way.