Accessibility at Wexumi.

Read the work and contact the studio.

The essential tasks on this site are reading about industrial R&D consulting, comparing the services and contacting Wexumi. These tasks should not depend on a hover effect, a moving photograph or a particular screen size. The pages use text headings and ordinary links so the information remains usable without visual effects.

The design approach is informed by the Web Content Accessibility Guidelines, including keyboard operation, visible focus and sufficient contrast. This statement is not an independent audit, a certification or a claim that every browser and assistive technology combination has been verified. A feature described here can still have an issue in a particular setup. Please report the task that failed.

Accessibility feedback is about removing the barrier, not screening the person who reports it. You can ask for the content of a service page by email or explain which inquiry field prevents completion. There is no need to upload proof of a condition or disclose personal health information.

Move through controls without a pointer.

The first keyboard link is “Skip to content.” It bypasses the repeated header and moves to the page's main content. Use Tab to move forward through interactive controls and Shift + Tab to go back. A visible focus outline distinguishes the current control from surrounding text.

The “Our work” menu is a disclosure rather than a hover-only list. Focus its summary and use Enter or Space to open it. On smaller screens the Menu button controls the main navigation when page enhancements are active. Ordinary service links remain the route to each full page.

The sections on this page use native disclosure controls. Their summaries can be opened and closed with the keyboard. The cookie notice uses the same reading pattern. The terms page divides the document into parts; its tab bar uses arrow keys, Home and End, with a stacked layout on smaller screens.

No service description requires dragging an element or following a pointer. If focus becomes trapped or moves to a control you cannot see, please include the page address and the control you used immediately before it happened in your report.

Keep the reading order intact.

Use your browser's zoom or text enlargement controls. The site uses flexible columns that stack on narrow screens, with wrapping headings rather than text locked to a single line. Buttons and labels have padding around their words so a long label can wrap instead of being cut off.

Dark brown and oxblood text sit against light cream or paper backgrounds. Fine gold rules provide emphasis but are not the sole indication of an action or error. Links in reading text have underlines, and form errors use explanatory words rather than relying only on a change of color.

Wide reference tables, where present in the legal pages, sit in their own horizontal scrolling area. The rest of the page should continue to fit the viewport. If zoom makes a field inaccessible or covers an important control, report the approximate zoom level and whether the page was viewed in portrait or landscape orientation.

Browser or operating-system contrast settings can alter the intended palette. That is expected. The styling includes borders and focus indicators for forced-color modes instead of depending on background photography to make an action visible.

The content does not depend on animation.

The homepage headline uses a changing word to indicate the range of work. Editorial photographs can remain in place while the adjacent explanation scrolls. Page transitions connect one ordinary page to another. Those effects are presentation, not steps you have to complete.

With the operating system or browser's reduced-motion preference enabled, word cycling stops on meaningful text, sticky image sequences become normal stacked content and transition animation is removed. Service links continue to work. There is no autoplay video to stop before you can read the page.

The fit checker presents its inputs together. You do not have to finish a timed sequence to get a recommendation. Its decision-window input describes the project's circumstances; it is not a countdown or a promise of delivery.

If movement remains after you enable reduced motion, let Wexumi know the page and effect involved. You can still use the service links in the main navigation or request the relevant information by email.

Use page structure, not the picture, to find the work.

Pages have a main heading followed by section headings. Navigation, main content and the footer use semantic regions. A screen reader's heading or landmark commands can provide a faster route than moving through every link in turn.

Photographs have text alternatives that describe the industrial subject. Captions distinguish illustrative industrial contexts from verified Wexumi facilities or project evidence. A photograph does not carry the only description of a service or contain an instruction you must read to submit an inquiry.

Icons that repeat an adjacent text label are hidden from assistive technology to avoid reading the same action twice. Icon-only controls, such as closing the support chat, have accessible names. Field labels remain visible above their controls rather than disappearing when you begin typing.

If a screen reader announces a control without a useful name, include the surrounding heading or link text in a report. You can name the assistive technology and browser if convenient, but those details are optional. The blocked task is the important part.

Choose email or phone.

The project inquiry form identifies required fields in text. A name and consent to inquiry processing are required. Email and phone are each optional, but at least one must be provided so Wexumi can respond. A precise home address is not needed.

Form controls have associated labels and guidance. Errors should identify the affected field, not just tell you that something went wrong. A successful enhanced submission displays the actual ticket returned by the server. If the connection fails, do not assume that a message was stored just because the submit button was pressed.

Support chat is an additional route for a general question, not a requirement for obtaining service information. It has a labeled close control and a text transcript. A reply may not be immediate. Email and phone remain available if the widget is unavailable or difficult to use.

Do not enter confidential plant records or sensitive personal information while reporting a form issue. A description such as “the consent checkbox cannot be reached after the scope field” is more useful than a screenshot containing private contact details.

Allow and decline are separate, labeled choices.

The consent banner is non-blocking. You can decline advertising and analytics storage and continue to read the industrial innovation consulting pages or make an inquiry. Inquiry-processing consent is a separate choice in the form, not permission for advertising storage.

Google Ads, Microsoft Advertising and Meta Ads send paid traffic here. Their landing links carry the click identifiers gclid, msclkid and fbclid. Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow storage, and returns all four to denied when you decline or withdraw. Denied states do not mean that every network request is blocked.

The footer's Cookie choices control reopens the choice. Essential preference storage is separate from chat continuity storage and from advertising or analytics. Global Privacy Control is honored as an opt-out without asking again. Read the cookie notice for the storage explanation and the Microsoft privacy statement for Microsoft's handling.

If the banner obscures the control you need at your zoom level or with an on-screen keyboard open, describe that state in your report. You can contact the studio directly without resolving the banner interaction first.

Ordinary links are the fallback.

The service pages are HTML documents. A browser that does not support page transitions still follows the same links. Native disclosures on this page can be opened without JavaScript. The layout does not require a plugin or a separate application.

Some functions need scripting, including live chat updates and the fit checker's calculated recommendation. If those functions are unavailable, read the full service pages or send a short inquiry instead. The studio page explains the operating boundaries, and contact details are written as text as well as links.

External privacy statements are controlled by their respective publishers. Wexumi cannot change how those external pages work. If an external reference prevents you from understanding a site disclosure, tell the studio which reference you need help with rather than sharing account credentials or private browsing records.

For a printed copy, open the sections you want to retain before using your browser's print command. This also provides a simple fallback if a browser does not expand closed disclosures in its print view.

A short access report is enough.

Send accessibility feedback to office@wexumi.com or call +1 (832) 555-6719. Use “Website accessibility feedback” as the subject if that helps distinguish the message from a project inquiry. You may also write to the postal address below.

• Identify the page address and the task you were trying to complete.
• Describe what prevented completion. Include the control's visible label if you know it.
• Share browser, device or assistive technology details only if you are comfortable doing so.
• Leave a reply route and say whether you need the information in another format.

Wexumi can use those details to understand the barrier and discuss a workable alternative. A reply may not be immediate. This statement does not promise a fixed repair date for an issue before its cause is understood.

Feedback containing personal information is handled as correspondence under the privacy policy. For a request to access, correct or delete personal information, use the dedicated data request route. Do not send identity documents through a public inquiry or chat.