Accessibility Statement

1. Our approach

We aim to provide clear structure, readable text, consistent navigation, meaningful labels, keyboard access, sufficient color contrast, responsive layouts, and understandable feedback. The website is designed so core information about services, scope boundaries, pricing ranges, reviews, and contact details can be read without relying only on color, sound, animation, or fine pointer control.

We seek to use recognized web accessibility principles as practical guidance. Because technology, content, browsers, devices, and user needs change, this statement does not represent a guarantee that every page or feature will meet every technical criterion at all times.

2. Measures included in the website

The website design includes semantic headings, labeled navigation, descriptive button text, visible focus styles, keyboard-operable controls, responsive sizing, reduced-motion support, text alternatives for meaningful images, and form labels connected with their controls. Modal content is identified as a dialog, can be closed with the keyboard, and is intended to keep keyboard focus within the open dialog until it is closed.

Review content can be navigated with controls or horizontal scrolling. Text initials are used in place of decorative profile imagery so a missing icon does not remove the identity presented with a testimonial. Images include intrinsic dimensions to reduce layout movement.

3. Visual presentation

The site uses a restrained palette, large headings, readable body text, generous spacing, and layouts that reflow on narrower screens. Important information is not intended to be communicated through color alone. Visitors may use browser zoom and operating-system display settings. The layout is designed to accommodate enlargement, although very high zoom levels and some combinations of browser extensions may produce different wrapping.

Motion is limited and decorative entrance effects are disabled or shortened when a visitor’s device indicates a preference for reduced motion.

4. Keyboard use

Interactive elements are intended to be reachable through the keyboard in a logical order. Links and buttons should show a visible focus indicator. Menus, review controls, project-form fields, modal controls, and the form submission control are intended to operate without a mouse. The Escape key closes the project form dialog, and focus returns to the element that opened it.

If a visitor encounters a keyboard trap, an unreachable control, an unclear focus position, or a control that does not respond to expected keys, the visitor is encouraged to report the page, device, browser, and steps that produced the problem.

5. Forms and validation

The project form identifies required fields with native form requirements. Its submission button remains unavailable until required information is complete and valid. Validation does not replace plain-language field labels. After a valid submission action, the form displays a text confirmation in a status region intended to be announced by compatible assistive technology.

The form does not open an email application. It is configured to display a confirmation on the page. Visitors who cannot use the form may use the plain-text email, address, or phone information at the end of this statement through the communication method of their choice.

6. Images and non-text content

Meaningful editorial images are intended to include concise alternative text describing their operational context. Decorative backgrounds and purely presentational elements may be hidden from assistive technology. Logos should include a useful text alternative. We avoid using essential information only inside an image.

If an image fails to load, core service and contact information remains available as text. The site package also includes embedded image fallbacks to reduce the chance that key section imagery disappears when theme assets have not yet been uploaded.

7. Documents and client materials

Website accessibility does not automatically guarantee that every client-provided or third-party document is accessible. When accessibility of a project deliverable is part of the written scope, the intended format, audience, and reasonable requirements should be discussed before work begins. A client remains responsible for source-document quality, content accuracy, and final testing in its own systems.

8. Third-party platforms

This website may depend on a commerce or content-management platform, hosting provider, browser, embedded feature, or other third-party technology. Some accessibility characteristics of those services are outside our direct control. We aim to select and configure technology responsibly, but we cannot guarantee the accessibility of an independent provider’s interface, outage message, payment page, or browser extension.

9. Known limitations

Potential limitations may include differences in how older browsers interpret newer layout features, the behavior of very long testimonial text in compact viewports, third-party platform controls, and content added after the original design. Users may also experience differences when custom styles, translation tools, or assistive technologies alter the page.

We welcome specific reports rather than assuming that automated testing identifies every barrier. Human feedback is particularly useful for keyboard order, screen-reader phrasing, zoom behavior, and cognitive clarity.

10. Requesting assistance or an accommodation

If a visitor cannot access information or complete an action, the visitor may request the same information or a reasonable alternative format. A useful request identifies the page or content, the barrier encountered, the assistive technology or device used if relevant, and a preferred way to receive the information. A visitor is not required to disclose a diagnosis.

We will review a request in good faith and aim to provide a practical response within a reasonable time. The appropriate response depends on the content, urgency, technical issue, and requested format.

11. Ongoing review

Accessibility review may include keyboard checks, contrast review, responsive testing, heading-order review, alternative-text review, form-label inspection, and testing with available assistive technology. New content or platform updates may introduce issues, so periodic review is appropriate.

12. Feedback process

Accessibility feedback is welcomed. Reports should avoid including sensitive personal information and should provide enough detail to reproduce the issue. We may ask follow-up questions and may coordinate with a platform provider if the barrier arises from third-party technology.