Accessibility statement for oPortfolio

How accessible this service is

We want as many people as possible to be able to use this service. You should be able to:

• use every feature with a keyboard alone, including writing an entry, mapping objectives, attaching files and downloading your archive;
• navigate using a skip link, landmarks and one clear heading per page;
• zoom to 400% or view at 320 CSS pixels wide without two-dimensional scrolling;
• read text at a contrast of at least 4.5:1, with focus indicators of at least 3:1;
• choose a sans-serif reading font for long text from your account page;
• use a password manager or paste into the email field — there are no passwords, puzzles or memory tests to sign in;
• understand every status, error and coverage count from text alone, never from colour or icon alone.

Compliance status

The service is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 level AA. It has not yet been independently audited, so we do not claim full conformance. Every release is checked automatically with axe-core against WCAG 2.0, 2.1 and 2.2 A/AA rules on each page, plus manual keyboard-only and 400% zoom checks; serious or critical findings block release. Automated tools find only part of the problems that matter, so we treat this service as partially compliant until an audit with real assistive technology has been completed.

Known issues

• Rich-text editor. The entry editor (toolbar, headings, lists, links) has not yet been tested with screen readers such as NVDA, JAWS or VoiceOver. Plain text works throughout and no formatting control is required to write or save an entry.
• Objective picker. The combined search-and-browse control has been tested with a keyboard but not yet with assistive technology.
• PDF archives. The PDF inside your downloaded archive is not a tagged PDF, so heading structure and reading order may not be exposed to screen readers. The same content is included in the archive as structured JSON, and every entry remains readable in the service itself.
• Session timeout. You are signed out after 60 minutes without activity. The service does not yet warn you before this happens; unsaved text is kept by autosave, which runs while you type.
• Uploaded files. We cannot make documents or images you upload accessible for you. You can add a description to each file.

We intend to fix these as the project develops and to update this list when we do. If any of them stops you using the service, tell us and we will help you another way.

Feedback and contact information

If you find something we have missed, need part of the service in a different format, or have difficulty with any step, email 0xchromatin@proton.me. Please do not include any diary content, patient details or other people's personal data in your message. We aim to reply within 10 working days.

Enforcement procedure

Because this is an independent service and not a public sector body, the Equality and Human Rights Commission's enforcement route for the 2018 Regulations does not apply. The Equality Act 2010 still applies to us. If you are not satisfied with how we respond to your feedback, write to the contact address above marked “accessibility complaint” and it will be reviewed by the service operator personally.

Technical information and testing

The service is built with semantic HTML first, uses ARIA only where native elements cannot express a control, keeps all controls at least 44 by 44 CSS pixels, and uses no third-party scripts, fonts or trackers. The accessibility checks described above run in the automated test suite for every change (see tests/e2e/accessibility.spec.ts in the source repository).

This statement was prepared on 29 August 2026 and will be reviewed by 29 August 2027, or sooner if the interface changes materially or an audit is completed.