Skip to content

PDA · Project Delivery Assistant

Accessibility Statement

PDA's accessibility goal, its current status, known limitations, how it is evaluated and how to report a barrier.

Last updated: October 11, 2026

Our goal

We aim for PDA to be accessible on different screen sizes and for different needs. Our target standard is WCAG 2.2 level AA. Accessibility is continuing work that must be checked again as the product develops.

Current status and evaluation

This statement is based on an evaluation dated 10 October 2026. There is no formal WCAG audit of PDA by an independent body; we therefore do not declare full conformance, and this page is not a certificate.

Our own methods: the public pages (landing, sign-in, registration, password reset, about, FAQ, the legal information pages, accessibility and licence) are scanned automatically with axe against the WCAG 2.0, 2.1 and 2.2 A/AA rules in three languages, in light and dark themes, at phone and desktop widths (the a11y-public test in the end-to-end suite). Forms, menus, the contact and information pages are also checked with automated tests for keyboard use, focus ring and screen width.

Automated tools catch only part of the problems; manual verification with real screen readers and different browser combinations is an ongoing need.

Keyboard use

You can move between links and controls with Tab and Shift+Tab and activate the focused link or button with Enter. The Skip to content link at the start of the page helps you reach the main content.

You can open and close FAQ questions with Enter or Space. In menus and dialogs you can use the application's existing keyboard controls and close supported windows with Escape.

Appearance and reading preferences

The top of the page has language and theme controls. You can choose a light, dark or system theme and use Turkish, English or German interface text.

You can use your browser's zoom. When the reduced-motion preference on your device is on, application animations are reduced. On narrow screens, content and footer links stack.

Meaningful content and assistive technology

On information pages, headings, main content, tables and navigation areas are structured with meaningful HTML elements. The GitHub links in the footer have an accessible name that includes the person's name; decorative icons are hidden from screen readers. Form errors are associated with their field.

Known limitations

The following areas are not yet fully accessible or have not been verified.

  • The analytics charts and visual summaries in the administration panel have not been verified with a screen reader; this area is open to the administrator only.
  • The Google and GitHub sign-in pages belong to those providers; their accessibility is not under PDA's control.
  • The accessibility tags of the CV PDF files that can be downloaded from the About page have not been verified.
  • The signed-in screens of the application (project boards, drag and drop, the calendar) have not been comprehensively verified with screen readers and different browser combinations.

Report a barrier

If you cannot use a page or a process, tell us through the contact form with the category “Accessibility” or by writing to info@pd-assistant.com. Give the page address, what you wanted to do, your browser/device and, if any, the assistive technology you use.

We reply to reports within 30 days at the latest and, where possible, provide the content in an alternative format. If you share screenshots, cover personal data and secrets. You do not need to explain a medical condition to make a report.

Your cookie choices

PDA uses necessary cookies and browser storage to keep you signed in. You can also allow analytics, which measures how the site is used without identifying you. Analytics is off by default and you can change your choice at any time. Cookie Policy