Adjustable contrast
A high-contrast mode makes text and interface elements easier to distinguish, independent of the colour theme.
An honest assessment rather than a badge: what is implemented, what was checked and what is missing.
In short
Door James 2.0 was designed against the relevant criteria of the German BITV and WCAG 2.0 during development. No independent certification or external audit has been completed; we phrase it that way in tenders too. This page describes the current state, the measures implemented and the route for feedback.
A high-contrast mode makes text and interface elements easier to distinguish, independent of the colour theme.
The theme follows the device setting or is chosen explicitly. Both directions are part of the accessibility settings, not a design gimmick.
Animations can be reduced for people who prefer minimal motion or experience motion sickness – and the system setting is respected by default.
Several colour themes with a live sample, so the choice can be made against real text rather than a swatch.
On mobile, the floor plan can show explicit zoom buttons – pinch gestures are not an option for everyone.
Semantic structure, keyboard operability, a visible focus indicator and a skip link to the main content.
Desks and rooms carry attributes such as step-free access or a height-adjustable desk, so they can be filtered for rather than asked about.
This website delivers its full content in the HTML. Anything that only appears after scripts have run is unavailable to some assistive setups.
Accessibility statements tend to come in two shapes. One is a logo and the word "compliant". The other is a description of what was built, what was checked, and what is still open. The first is easier to produce and worth less, because the moment somebody tests it, the difference shows.
Door James 2.0 was designed against the relevant criteria of BITV and WCAG 2.0 during development, and the app carries real settings that people can change themselves: contrast, theme, reduced motion, colour themes, zoom buttons on the map. That is a substantive starting point. It is not a conformity statement, and we do not present it as one.
Three areas, in our own estimation. The interactive floor plan is the hardest: a spatial interface is genuinely difficult to convey through a screen reader, and the honest answer today is that the list view is the accessible path to a booking. Complex reports – occupancy tables and charts – need their data available in a form that does not depend on reading a picture. And dynamically generated content in the native apps needs its labelling checked on the actual devices rather than in a simulator.
Naming these in advance is deliberate. They are the questions an auditor asks, and an organization deciding on workplace software deserves them before the contract rather than after.
For public-sector buyers this is rarely about goodwill; it is a criterion with points attached. The useful thing we can offer is precision: what is implemented, what is unverified, and what would be needed to close the gap. If your tender requires a conformity statement against EN 301 549, that means an external audit, and that has a lead time. Raise it at the start and it becomes a scheduled step; raise it at the end and it becomes a reason to lose.
If you hit a barrier, write to doorjames.support@cgi.com with the page or view, the device, the browser and the assistive technology you use. Confirmed barriers are treated as defects rather than feature requests, and they appear in the release notes when they are fixed.
Send the page or view, the device, the browser and the assistive technology to the support address. A screenshot or a short recording helps more than a description.
Barriers are reproduced against the same combination of device and assistive technology before anything is changed – otherwise a fix is guesswork.
Confirmed barriers are treated as defects, not as feature requests, and appear in the release notes when they are resolved.
For the public sector
A written statement of the current state, the criteria used and the gaps – the form a procurement review can actually work with.
For works councils and inclusion officers
Named settings that individuals can change themselves, rather than a central configuration everyone has to live with.
For IT and procurement
A clear answer on what is verified and what is not, so no conformity is entered into a matrix that we have not claimed.
Door James 2.0 was designed against relevant BITV/WCAG 2.0 criteria. Without an independent audit we cannot make a conformity statement in the sense of a verified confirmation, and therefore do not.
An external audit is a sensible next step but currently has no dated entry on the roadmap. We do not communicate a date we have not committed to.
By email to doorjames.support@cgi.com, stating the page or view, the device used and the assistive technology. Reports feed into product prioritization.
Yes. This website was built with semantic HTML, keyboard operability, visible focus, contrast checking and complete content without JavaScript.
Whether the BFSG applies depends on who you are and how the product is used. It addresses products and services offered to consumers; workplace software procured by an employer for its own staff is usually assessed against different obligations – public-sector accessibility rules, the Workplace Ordinance, and increasingly a contractual requirement in tenders. We do not claim the BFSG is satisfied. What we do is describe the state accurately enough that your own legal assessment can use it.
EN 301 549 is the European standard that public procurement usually refers to, and a VPAT is the common way to document conformity claim by claim. Neither exists for Door James today. If a tender requires one, say so early – producing it properly means an external audit, and that is a project with a lead time, not a document we can write over a weekend.
The core flows are built with semantic structure and keyboard operability in mind, and everyday use with a screen reader works in our own testing. The area we would not promise is the interactive floor plan: a map is a hard problem for a screen reader, and it is the first thing an external audit would look at. Booking through the list view rather than the map is the accessible route today.
Per person. Contrast, theme, reduced motion and the map zoom buttons sit in each user's own settings, which is the point – a central setting cannot know who needs what.
It is built for it: semantic HTML, a meaningful heading hierarchy, keyboard operability, a visible focus indicator, a skip link, text alternatives, contrast checking, correct language markup per page, respect for reduced motion, and full content without JavaScript. It has not been independently audited either.
Bring the exact wording of the requirement. We will say what is implemented, what is unverified, and what an audit would take – in that order.