Website accessibility. Report a barrier.

The site uses ordinary links and labelled controls. The skip link at the start of each page moves past the repeated header to the main content. Keyboard focus has a visible outline so you can see which link, button or field will receive your next action.

These are access choices built into this destination, not a certification. A responsive web page build needs to accommodate changing content and input methods; this statement explains the choices here and how to tell us when one fails.

Policy parts stay addressable

On wider screens this statement uses a tab bar. With a tab focused, the arrow keys move between parts; Home and End move to the first and last part. The selected part is reflected in the page address, so a link to reporting a barrier opens that part directly.

On phones the same parts become stacked accordion controls. Each control states whether its content is expanded. Without JavaScript, all the policy text remains in the document rather than being locked behind a control that cannot work.

Forms explain what they need

Inquiry fields have visible labels. Your name and permission to use the message for a reply are required. Phone and email are individually optional, but at least one is needed so the studio has a way to respond. A postal address is not needed to report a problem.

A failed submission is not a sent request. Read the error message before trying again, and keep a copy of a long message if your connection is unreliable. You can use the email route below instead of troubleshooting a form. Permission to reply is separate from optional advertising storage.

We do not claim that every browser and assistive-technology combination has been tested, or that this site meets every requirement of an accessibility standard. This statement does not certify the website. A control can still fail in a particular reading mode even when its intended keyboard behaviour is clear.

There is no verified defect register published here. That is not a claim that there are no defects. Reports about a hidden focus indicator, an unclear error or a reading order that makes an action hard to find are useful because they point to something that can be inspected.

Some features need scripts or a connection

The enhanced menu, storage-choice controls and support conversation rely on JavaScript. With scripts unavailable, the policy text and ordinary contact links remain readable, and the inquiry form retains its server submission route. The animated colour field is decorative; missing graphics support should not remove information.

A support conversation also needs a working connection. Its conversation token uses localStorage after a visitor starts chat. Browser restrictions on storage can interrupt conversation continuity. If chat does not connect or does not retain a conversation, email the studio rather than repeatedly sending the same private details.

External pages have their own interfaces

Platform privacy links leave vexbun.com. Their page layouts and access controls are managed by their respective providers. If you cannot read one of those pages, tell us which information you need about this site's handling of your visit. Do not send account credentials so we can inspect it for you.

Targeted website fixes are not an audit certificate

The precision pass service can address an agreed issue on an existing page. That offer is not a complete accessibility audit or a legal compliance guarantee. A narrow correction, such as stopping a button from clipping at a phone width, cannot establish that every route in a larger site is accessible.

Reports about access to vexbun.com are separate from paid project inquiries. You do not have to commission targeted website fixes to tell us about a barrier here. If you are looking for project work, the service comparison explains the scope before you make an inquiry.

Email [email protected] with the subject “Website access barrier”, or call +1 (784) 555-7475. Either route can be used without completing a web form. If you prefer a particular way of receiving a reply, say so in your message.

Where it happened

Give the page address or its title. If you arrived from a search or advertisement, the page title is enough; you can omit the tracking parameters from its address.

What you were doing

Explain the action you intended, such as opening the menu, reading a policy part or sending an inquiry. Say what happened instead.

Useful context

If you know it, include the browser and the input method or assistive technology involved. These details help reproduce the problem but are not a condition for reporting it.

The information you need

If a barrier hides a service description or contact detail, identify that content. Ask for it in the body of an email or another practical text format.

How the report is used

The studio uses the report to understand the barrier, communicate with you and consider a correction or an alternative route to the information. We may ask for the step just before the failure. We do not promise a fixed response time or a repair deadline in this statement.

If your message concerns personal information rather than a page interaction, use the data request route. It covers access to records, correction and deletion requests, as well as consent help. The privacy statement explains how correspondence is handled.

Storage choices must not block access

You can decline optional advertising and analytics storage and continue to read the site or contact the studio. Google Ads and Microsoft Advertising send paid traffic here; Meta Ads is included in the site's advertising and consent coverage. Landing links can contain gclid, msclkid or fbclid. Their presence does not grant permission to save them in optional storage.

Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow the relevant storage categories, and sets them back to denied when you decline or withdraw permission. Microsoft and Meta optional storage follow the advertising choice too. Denied storage does not mean that every network request or form of measurement stops.

Use Cookie settings in the footer to change a choice. If that control presents a barrier, tell us; do not assume a message alone changes the preference saved in your browser. The cookie statement gives the full explanation. Platform information includes the Microsoft privacy statement.