Configurix
Buyer guide

Can buyers complete your configurator using a keyboard?

Evaluate keyboard access across product choices, dimensions, 3D alternatives, validation, saved projects and the enquiry form before buying.

Configurix2 min read
Table of contents
  1. Define the outcome rather than a visual shortcut
  2. Test an invalid configuration, not only a successful one
  3. Include translated and mobile journeys
  4. Put accessibility evidence into the Configurix scope
  5. Is adding keyboard shortcuts enough?
  6. Does accessibility only concern customers who use screen readers?

A keyboard buying test should cover the complete product journey, not just whether the first button can receive focus. Customers need to select options, understand restrictions, correct input and reach the next useful action. Agree the required accessibility scope and ask for evidence using representative configurations.

Define the outcome rather than a visual shortcut

A customer may need to choose a roof, enter a width and request an offer. The implementation should provide operable controls and understandable feedback for those tasks. Some visual interactions may need an alternative way to reach the same product decision.

W3C's keyboard criterion addresses operation through a keyboard interface. W3C keyboard guidance. A project still needs review against the complete accessibility scope your business requires.

Journey stepCheck during evaluation
Choose an optionVisible focus and understandable selected state
Enter a measurementAssociated label, unit and error explanation
Encounter a restrictionReachable information and useful next action
Explore a modelAppropriate control or equivalent alternative
Request an offerOperable fields, consent choices and confirmation

Test an invalid configuration, not only a successful one

Enter a dimension outside the permitted range. Confirm that the problem is identified and the customer can reach the relevant field or explanation. Then correct the value and continue without losing earlier selections.

Also open and close overlays, product menus and image dialogs. A customer should be able to leave an interaction and return to the journey without an unexplained focus change or trapped navigation.

Include translated and mobile journeys

Longer labels, different measurement instructions and responsive layouts can expose issues absent from the initial demonstration. Test the languages and device conditions relevant to your customers. A single English desktop review does not establish every edition's behaviour.

Record the tested configurations, assistive methods and remaining issues. Avoid treating one keyboard walkthrough as a blanket certificate of accessibility compliance.

Put accessibility evidence into the Configurix scope

Use the Configurix accessibility guide to define acceptance responsibilities for a custom project. Ask how product controls, errors, documents and embedded forms will be reviewed, and which independent assessments your organization requires.

Is adding keyboard shortcuts enough?

No. The normal controls, focus order and feedback must support the required tasks. Shortcuts can supplement a coherent journey but should not conceal inaccessible controls.

Does accessibility only concern customers who use screen readers?

No. Keyboard operation, understandable errors and clear labels can matter to several users and input methods. Evaluate the actual tasks your buyers need to complete.

Book a private Configurix demo

Bring your product range, price list and a representative quote. We can define the configuration and sales workflow around your business.

Book a private Configurix demo →

Related articles