You can ask for help without using a form.

Move through the controls in reading order.

Use Tab to move to the next link or control and Shift + Tab to move back. The first link is “Skip to content”; activate it to pass the repeated header and reach the main page. Ordinary links open with Enter. Buttons and disclosure summaries can be activated with Enter or Space.

On a narrow screen, the Menu button opens the main navigation. Its expanded state indicates whether the links are showing. Search, indexing and maps are followed by catalogue, about and contact in the document order. The same destinations remain available without a pointer.

The sentences on this page are disclosure controls. Activate a sentence to open its explanation, then continue through the content below it. You can open more than one section at a time. The document controls let you open everything for reading or printing; each section also works independently.

A hover preview is not a hidden destination. Service names remain ordinary links when the preview is unavailable. If you are discussing search result filters for your own project, describe the keyboard behaviour you need in that scope; a photograph of a focused result does not establish the accessibility of a commissioned system.

Focus is not just a colour change.

Keyboard focus is marked with a contrasting outline. It tells you which link, field or button will receive the next action. The outline remains available when reduced motion is selected; the decorative focus brackets are not the only indicator.

Selected navigation and form errors use text or structural marks in addition to colour. Form controls carry their own labels, and icons accompany words where their meaning would otherwise be unclear. If a focus outline is obscured by a header or another control in your browser, report the page and the control's visible label.

Some desktop controls move slightly toward a pointer. That treatment is limited to fine pointers and does not change the action or make the target dependent on a hover position. Touch use has no need to trigger it. A keyboard attached to a tablet still receives a static focus outline.

Use your browser's reading controls.

Browser zoom is not disabled. Enlarge the page with the controls provided by your browser or device. Text and control labels are designed to wrap rather than remain on a single long line. At smaller widths, side-by-side sections move into a reading sequence.

A wide data table may need horizontal scrolling inside its own bordered region. That is different from scrolling the entire page sideways. The terms page's date rail also becomes a horizontal metadata strip on small screens; the full terms remain below it in the normal reading order.

The design uses light text against dark surfaces, with visible rules to separate modules. If a browser colour override or high-contrast setting makes an essential label unreadable, tell us which setting was active. You do not need to identify a disability or explain why you use that setting.

Legal information is also available through privacy disclosures, the numbered cookie statement and the terms rail. You can request an explanation of a particular passage by email instead of working through an interface that is not usable for you.

Movement is an enhancement, not an instruction.

The site follows the reduced-motion preference exposed by your operating system and browser. With that preference active, animated page transitions, pointer-follow previews and magnetic movement are disabled. The links still open their destinations.

Without a reduced-motion preference, supported browsers can animate the transition between ordinary pages. Browsers that do not support the transition feature use normal navigation instead. No information depends on seeing an animation finish, and there is no autoplay video to pause before reading.

On touch devices, service photographs remain in the page rather than following a pointer. The planning estimator uses labelled fields and a result message. Its calculation does not require dragging a slider or completing a timed step. For pricing help without the tool, use search project support and describe the work directly.

The service information stays in text.

The interface photographs are illustrative. Their screen lettering is intentionally not presented as readable service content. Nearby prose explains the relevant record structure or behaviour, and image alternatives identify the subject. A visitor does not need to read text inside an image to understand the offer.

Page headings establish a reading structure. The brand image links home, and the main, breadcrumb and footer navigation have separate labels. Decorative sprite icons are hidden from assistive technology when the adjacent text already names the action.

The place data service is explained using text records. There is no map widget to manipulate. The written contact address is also available as text. A company listing inquiry can be made from the catalogue page without selecting a point or interpreting a geographic image.

If an image alternative fails to answer a practical question, name the image or copy its caption into your report. Ask for the information you need, such as the distinction between a source field and an index field, rather than sending personal documents to demonstrate the barrier.

Search project support without a form.

Inquiry forms label each field and identify optional contact information. Provide a phone number or an email address so we can reply; you do not have to provide both. Name and consent are required by the inquiry form. A missing reply route needs correction before a request can be stored.

Validation messages identify the field that needs attention. The form's result area reports whether the submission was saved. A visible inquiry reference confirms storage, not a completed service or a promise of delivery. If a network error interrupts the process, do not assume the message reached us.

The support widget has a labelled close control and a message history. Its messages belong to a support conversation, not a public discussion. Starting chat stores a token in the browser to keep that conversation connected. If the widget is difficult to use, email [email protected] or phone +1 (435) 555-4934.

Optional cookie storage is separate from agreeing to data use for a requested conversation. The cookie banner offers both Decline and Allow storage, and Cookie choices in the footer reopens the decision. See the cookie explanation for the storage signals and the effect of withdrawing permission.

Describe the blocked action, not your personal circumstances.

Email [email protected] with “Access barrier” in the subject, or call +1 (435) 555-4934. Tell us what you were trying to do and the page where it happened. A short description is enough to start. You do not need to provide a diagnosis or disclose any health information.

• Give the page address and the visible name of the control involved.
• Describe the action that failed, such as opening a disclosure or reaching a submit button.
• If you know them, include the browser and device, and any assistive technology relevant to the issue. These details are optional.
• Tell us your preferred reply route and whether you need the affected information in a different text format.

A screenshot is not required. If you choose to send one by email, remove personal information and unrelated browser content first. Please do not send a screen recording that exposes account details or other conversations.

We use the report to understand the obstacle and discuss an alternative route while it is examined. This page does not promise a repair deadline or claim an independently verified conformance level. A service inquiry and an access report are different requests; label the access issue so it can be understood on its own.

Report the behaviour you actually encounter.

This statement applies to yondexy.com. It does not certify a third-party source, a linked website or work that has not been scoped and delivered. No audited conformance certification or blanket compatibility claim is made here.

Browser behaviour and assistive technology can differ. If the described controls do not work as expected in your setup, the useful evidence is the page, action and result. A report can identify a problem even when the same action works through another input method.

Yondexy, trading at yondexy.com, can also be contacted in writing at 174 Mill Street, Apt 3, Austin, Texas 28536, Austin, Texas, United States. Barrier reports are handled as correspondence. Read the privacy statement for the information recorded and the retention periods. If your concern is about access to personal data rather than access to a webpage, use the data request route.

The effective and last-updated date of this statement is October 10, 2026. There are no amendments recorded. The correction boundaries explain how work under Yondexy's control differs from external systems; they do not replace the direct route for reporting an access barrier.