TervuqWebsite accessibilityWebsite accessibility. A clear route to report a barrier.
Use the keyboard to follow links or open the menu. Set reduced motion in your device preferences to turn off decorative movement. If a control stops you from reading about business website development or sending a website technical support inquiry, report it by email or phone.
This is an account of current design and testing scope. It is not a certification, a statement of universal compliance or a promise that every assistive technology and browser combination behaves identically.
Keyboard use has a visible route.
A visitor can move through the page, open the menu and reach the inquiry links without relying on a pointer.
Focus is not hidden
Interactive links, buttons, form fields and the support control receive a visible orange focus outline. The outline is separated from the control so it does not disappear into a border or a dark image. Press Tab to move forward through controls and Shift+Tab to move back. Use Enter to follow a link; buttons also respond to Space. While the menu is open, focus stays within it until you close it.
The menu has a named dialog, a close control and Escape handling when the site scripts are available. A keyboard user can close it and return to the Menu control. With scripts disabled, the page still exposes the footer navigation and the page links as ordinary HTML.
Controls say what they do
Controls carry their own words. “Discuss a request” describes the destination, while “Close menu” describes the action. The stamp, line rules and orange state are decoration or emphasis; instructions are not conveyed by color alone.
Long labels wrap inside padded controls. There is no hover-only information needed to understand a service, and the service photographs are illustrative context rather than a required explanation.
- Skip linkA direct link moves keyboard focus to the main content.
- Menu stateThe overlay exposes expanded and dialog state and offers a labelled close action.
- Form labelsInputs have persistent visible labels, optional contact routes and adjacent error text.
- Reading orderSections, headings and links retain a sensible order when the layout becomes one column.
Motion has an off switch.
The interface does not require movement, cursor effects or a canvas field to reveal content or complete an inquiry.
Reduced motion
When a visitor selects reduced motion in the operating system, page transitions, stamp settling, magnetic controls, hover-follow previews and the generative depth layer are suppressed or reduced to their static state. The canvas is not initialized on narrow viewports or under reduced motion. The grid texture remains quiet background texture, not moving content.
Fine-pointer enhancements are limited to pointer devices that can use them. Touch visitors receive the inline layout. Keyboard visitors receive the visible figure and the same service text without needing to hover.
Readable contrast and scale
Carbon surfaces carry cream text. Secondary text is kept distinct from rules, and the orange signal is used for focus and state rather than long passages. Text uses fluid sizes and wraps naturally from 320px upward. Browser zoom and text enlargement may change the composition; they should not turn a control into clipped text.
Photographs carry alternative text that states the subject without pretending to document a delivered client project. Decorative maker's marks use empty alternative text.
Testing scope is not a certification.
Review focuses on the page structure, keyboard route, responsive breakpoints and the main inquiry interaction.
Scope and evidence
The review scope is keyboard-only movement through the menu and forms, with visible focus and readable errors. It also covers touch use and text reflow at narrow widths. The layout targets 320, 360, 414, 768, 1024, 1440 and 1920 pixels; those targets are not a record of completed device tests.
No independent accessibility audit or browser and assistive-technology test report is published here. The provisions described on this page are design and implementation choices, not verified results for every visitor. A browser update or a changed setting can expose a barrier that the layout alone does not reveal.
What is not claimed
Tervuq does not claim universal compliance, a conformance level, or testing against every browser, screen reader, operating system, plug-in and user setting. Vendor interfaces reached through external links have their own accessibility controls. The support chat is asynchronous and is not presented as an always-staffed accessible help desk.
If a browser, keyboard, screen reader or zoom setting produces a problem, the reporting route below is the fastest useful next step.
Report a barrier with enough detail to reproduce it.
Send the page address, the action that failed and the setting that changed the result. Do not send passwords or private records.
Useful report details
A short report can include the page URL, the control or heading you were trying to reach, the steps immediately before the problem, what you expected and what happened instead. Add the browser and operating system, keyboard or assistive technology used, zoom level or reduced-motion setting when relevant. A screenshot is optional and should be cropped to remove names, account numbers and confidential content.
Do not include credentials, customer records, medical information, financial details or a full private conversation. A description is enough to start. If the issue concerns a project or a live website, say so without pasting its secret access details.
Accessible reporting route
Email [email protected] with the subject “Accessibility barrier”. You can also call +1 (638) 555-4623. Tervuq is based at 19 Oak Lane, Apt 3, Austin, Texas 49198, United States. Use email or phone to arrange a different way to communicate; the address is not an invitation to visit.
A barrier report is handled as an inquiry. A reply route is useful, but do not send more personal information than is needed to respond.