Accessibility / inclusive access

A usable site for every visitor.

UnitWeave is building this site so people can read, navigate and submit a project brief using different devices, input methods and assistive technologies.

Accessibility

Read the scope before you share or rely on information.

Our target is a practical WCAG 2.2 AA experience for the public pages and lead form. Accessibility is an ongoing responsibility: browsers, content, translated layouts and third-party delivery can change the result, so we review the experience as the site evolves.

Last updated: 31 August 2026

Accessibility

The details that govern this site and its project conversations.

Current foundations

The site includes structural and interaction choices intended to support everyday access.

Semantic headings, landmarks, navigation labels and a skip link
Keyboard-visible focus states and keyboard-operable menus, forms and controls
Text alternatives for meaningful images and empty alt text for decorative images
Responsive layouts, readable line lengths and contrast-aware color choices
Reduced-motion handling for visitors who request it

Forms and error recovery

The project form keeps the initial intake short and gives feedback next to the field that needs attention.

Native required and email validation remains available without JavaScript
Submitted errors are announced and the first invalid field can receive focus
The form prevents duplicate submission while a request is in progress
Success and failure messages use status semantics and provide a retry path
The privacy notice is linked at the point where project information is requested

Language and layout

The site supports localized routes, right-to-left Arabic layout and narrow screens, but translated content can still expose a layout or reading issue.

Use the language menu to choose a published locale
Arabic pages set the document direction for reading and navigation
Tables and dense technical records can scroll horizontally on small screens
Long labels and business terms are tested at mobile widths
A translated page may remain out of search until its technical and legal copy is reviewed

Known limitations

Some limitations need human review across browser, zoom and assistive-technology combinations.

Vendor pages and external references are outside our page-level control
Complex comparison tables may require horizontal scrolling
Machine-assisted translations can be less natural or less concise than English
A screenshot, PDF or browser extension may not inherit the site accessibility behavior
A successful automated check does not prove every screen-reader experience

How to report a barrier

Tell us what prevented you from finding information, completing a form or operating a control. A useful report helps us reproduce the issue.

Page URL and the task you were trying to complete
Browser, operating system, device and zoom level if known
Keyboard, screen reader, voice control or other assistive technology used
The expected outcome and what happened instead
A preferred contact route if you would like a response

Our response

Accessibility reports are treated as product issues, not as an inconvenience. We will assess the impact, look for a practical fix and update the page or content when appropriate.

Use the Contact page and identify the message as an accessibility report
Do not include passwords, payment data or customer production records
Urgent access barriers affecting a live business workflow should include the deployment context
The current page date records when this statement was last reviewed

Accessibility

Found an accessibility barrier?

Use the Contact page and include the URL, task, device or assistive technology and what went wrong. We will use that detail to investigate the experience.

Report an accessibility issue