Accessibility

Diplace is built for school and university students, and we believe everyone should be able to use it: with a keyboard and no mouse, with a screen reader, with low vision, and with the page zoomed in.

We target WCAG 2.2, level AA. As of the review date above, the site partially conforms. What works and what does not is listed below without omissions.

Verified on the date above.

• The whole site can be operated by keyboard. The first Tab on any page reveals a "Skip to content" link that bypasses the menu.
• Every control has a visible focus indicator with a contrast ratio of at least 4.5:1.
• Dialogs and slide-over panels close with Escape, keep focus inside, and return focus to the control that opened them.
• Body text contrast is at least 4.5:1 everywhere; input field borders are at least 3:1.
• The page language is declared and changes with the interface language, so a screen reader switches pronunciation.
• Form errors are announced to screen readers, and an empty required field is marked by text next to it, not by colour alone.
• The page can be zoomed to 200% without loss of content and without horizontal scrolling.
• If reduced motion is enabled in the system, all motion and transitions are switched off.
• Buttons and links are at least 44 pixels tall on phones.
• Decorative images are hidden from screen readers; meaningful ones are labelled.

We know about these and do not present them as done.

• Hover tooltips. Some explanations appear on mouse hover and do not appear on touch screens or by keyboard. We are removing them in favour of plain text; where one remains, the button label is written to make sense without it.
• Catalog card. The whole card is clickable with a mouse. By keyboard, the card title and the buttons inside it work, but the card as a single element does not.
• Opportunity texts. Titles and descriptions are collected automatically from organizers' sites. We normalise them, but we cannot be responsible for the wording or structure of the source text.
• External pages. The apply button leads to the organizer's own site. Their accessibility is not under our control.
• Evaluation method. This is a self-assessment: code review, a keyboard walkthrough and contrast computed by formula. We have not commissioned an independent audit or testing with screen reader users.

Write to us and we will fix it. This is not a formality: reports of inaccessibility go first, because a person who cannot use the site cannot wait either.

Email: akm.work.acc@gmail.com. Please help us reproduce it: which page, what you were trying to do, and what you use (keyboard, screen reader, magnification).

We reply within 5 working days and name a fix date in the reply. If a quick fix is not possible, we offer another way to get the same result.

Part of the accessibility requirements is checked automatically on every code change: label-to-field association, handlers on non-interactive elements, roles without names. The build fails when a rule is broken.

This statement is updated with every change that affects accessibility, and at least once a year.