On this page
The public site is designed around practical access.
The aim is to keep core routes understandable and operable across common input methods, screen sizes and motion preferences.
Keyboard & focusCore interactive controls are designed to be keyboard operable with visible focus.
Semantic structureHeadings, landmarks, labels and control relationships are used to communicate page structure.
Responsive reflowDense content is designed to stack or reflow rather than becoming an unreadable desktop layout on a small screen.
Reduced motionReduced-motion preferences are respected where motion is used.
Forms & errorsForms use labels, instructions and clear error states so a problem can be identified and corrected.
Readable hierarchyTypography, spacing, contrast and hierarchy are designed to support scanning and sustained reading.
If something prevents you using the site, tell us what happened.
Email hello@winintel.co.uk. If you can, include the page or task involved, what went wrong, and the browser, device or assistive technology you were using. You do not need to provide a technical diagnosis.
Report a barrier
Page, task and problem.
Tell us which page or interaction caused the problem and what you were trying to do. A short description or screenshot can help where you are comfortable providing one.
Reasonable adjustment
Tell us what would help you access the service.
If an ordinary website or service route is not accessible to you, explain the adjustment you need. You do not need to provide a detailed medical history.
Keep the request proportionateShare only the information needed to explain the barrier and the adjustment you are asking for. If another accessible route can reasonably be provided, WinIntel can discuss that with you directly.