Accessibility
Built to be used by everyone who designs boards.
This statement describes what we build into the website and portal today, how we test it, and where we still fall short. It covers QodeX PCB on this domain: the public pages, the instant quote, the 3D Studio and the customer portal.
Keyboard
- Every link, button and form control can be reached and used with the keyboard, in a logical order.
- A visible focus ring on every focused element, in both themes.
- A "Skip to content" link is the first thing on every page.
- Escape closes the navigation menus and clears a selection in the 3D viewer.
- File drop zones open the file picker with Enter or Space; on the order form, U opens it too.
Screen readers
- Pages use landmarks (header, navigation, main, footer) and a heading structure.
- Form fields have labels; icon-only buttons have an accessible name.
- Live prices, upload progress and form errors are announced as they change.
- Decorative icons are hidden from assistive technology.
Contrast and themes
- Light, dark or follow your system setting, from the header or your account settings.
- Our automated tests check the colour tokens against WCAG 2.1 AA: 4.5:1 for text and 3:1 for form controls and the focus ring, in the light theme and the dark theme.
- Links inside running text are underlined, not told apart by colour alone.
Motion, zoom and phones
- With "reduce motion" set on your device, animations and transitions are turned off and the 3D hero does not rotate by itself.
- Pages reflow down to phone width without horizontal scrolling of the page, and text can be zoomed by the browser.
- The 3D viewer supports touch gestures on phones and tablets.
Known limitations
- Rotating and exploring a board in the 3D viewer needs a mouse or touch. The facts behind it are also available as text: board statistics, DFM findings, nets and the before / after checks are listed next to the model.
- PDF invoices and credit notes are not tagged PDFs. The same figures are on the receipt page in your portal, which is ordinary HTML.
- We have not had an independent accessibility audit. This statement describes what we build and test ourselves.
Report a problem
If something on the site is hard or impossible to use with your setup, tell us what you were trying to do, which page it was, and the browser and assistive technology you use. We treat accessibility problems as bugs.