Accessibility statement

• The public website at haccphyve.com, in all six languages it is published in.
• The signed-in application: the manager dashboard, the fourteen-chapter course, the exams, the certificates and the daily records.
• The venue tablet screens staff sign on to in a kitchen.
• It does not cover material a company uploads for its own staff — its own videos, photographs and documents. Those belong to the company that added them. What that means in practice is set out below.

HACCP Hyve is partially compliant with EN 301 549 V3.2.1, the European accessibility standard, which applies WCAG 2.1 Level AA. Partially compliant means most of the standard is met and the exceptions are named below, each with a date.

We are a private company selling to other businesses, so neither the European law on public sector websites nor the European Accessibility Act obliges us to publish this. We publish it because buyers ask for it, and because the standard those laws use is the right one to be measured against.

Measured on 25 August 2026 from the running code. Contrast figures are calculated from the stylesheet, not judged by eye.

• Every page states which language it is written in, in all six published languages.
• Every image carries a description for screen-reader software, and a release is blocked if one is added without.
• Every form field is tied to its own label, and a release is blocked if one is not.
• Everything can be operated with a keyboard alone. The outline that shows where you are measures 13.8 to 1 against the page in the light theme and 10 to 1 in the dark one, where the standard asks for 3 to 1.
• Text is comfortable to read: body text 15.5 to 1, secondary text 5.2 to 1, error messages 5.7 to 1, against a requirement of 4.5 to 1. Every colour is recalculated on every release, in both the light and the dark theme, and a colour that drops below the line stops the release.
• Temperature, the field kitchen staff use most, can be spun, typed or set with the arrow keys, with the same limits whichever you use.
• Answering a lesson or exam question is announced to screen-reader software, right or wrong, together with the explanation.
• Right and wrong are shown by a tick or a cross as well as by colour, so the answer does not depend on seeing the difference between green and red.
• Wide tables can be scrolled with the keyboard, so no column is out of reach.
• Anyone whose device asks for less movement gets the animation switched off.

Three things. Each is listed with what you can use instead in the meantime.

• Training videos have no captions. A company can upload its own video as extra study material, and our player has no way to carry captions or subtitles for it. Someone who is deaf or hard of hearing gets nothing equivalent to what is said on screen. This fails success criteria 1.2.2 and 1.2.5 of WCAG 2.1.
• Instead, for now: the fourteen-chapter course is written text with written questions in nine languages, and it can be completed in full, exams included, without watching a single video.

• By 31 December 2026, a certificate that screen-reader software reads properly, as a web page alongside the PDF. Making the PDF itself carry a reading order depends on a change in the software we use to draw it, so we are not promising a date for that.
• By 31 December 2026, a skip-to-content link on every page. Screen-reader software can already jump straight to the main part of a page, because the regions are marked up for it, but a keyboard user who does not use that software has to tab past the header on every page.
• By 31 March 2027, captions on video: the player will carry a caption file, and adding a video will ask for one.
• During 2027, an independent accessibility audit. We have never had one, and we will commission one once the items above are closed.

• Prepared on 25 August 2026 by self-assessment: we measured the running code ourselves. No third party assessed it and we hold no accessibility certificate.
• The colour figures are calculated from the stylesheet by an automated test rather than judged by eye. Image descriptions, form labels and keyboard reachability are enforced by rules that fail the release, so this class of problem is caught before it ships rather than found by a customer.
• What we did not do: test with real screen-reader and magnification software on real devices, and be audited by an independent expert. Both are worth doing and neither has been done, so read the list above as a careful measurement rather than as a certificate.
• We review this statement at least once a year, and again after any substantial change to the product.

If anything here is in your way, write to bonsaicoffeebcn@gmail.com and tell us what you were trying to do and what happened. We reply within five working days. If something you need is not accessible to you — a certificate, a chapter, a record — ask, and we will send it in a form you can use.

Accessibility is the responsibility of the founder of HACCP Hyve, who reads that address personally.

• Write again to the same address and say you are not satisfied. It reaches the owner of the company directly, not a queue.
• There is no national enforcement body that supervises this service. The European complaint route for accessibility statements exists for public sector bodies, and we are a private supplier. The European Accessibility Act covers consumer services, and a workplace training tool sold to businesses is not on its list.
• If you are buying on behalf of a public body, your own country's accessibility enforcement body can hold you to this standard as the buyer. Ask us for whatever evidence you need and we will provide it.

This statement follows the model accessibility statement laid down in Commission Implementing Decision (EU) 2018/1523 of 11 October 2018, published in the Official Journal of the European Union, L 256, 12 October 2018, page 103. That is the format European buyers ask for by name. The standard measured against is EN 301 549 V3.2.1, the version currently cited in the Official Journal, which applies WCAG 2.1 Level AA. A newer version applying WCAG 2.2 is expected to be cited during 2026, and we will re-measure against it when it is.

• Security
• Privacy Policy
• Terms of Service