Accessibility Statement

1. Commitment

We believe digital experiences should be understandable, operable, and perceivable across different devices, input methods, and user needs. We work to improve semantic structure, keyboard usability, contrast, responsive behavior, readable typography, focus states, labels, and motion preferences.

2. Measures We Use

Reasonable measures may include semantic HTML, descriptive headings, form labels, keyboard-accessible controls, visible focus treatment, sufficient color contrast, alternative text for meaningful images, responsive layouts, reduced-motion support, and review of common interaction barriers.

Accessibility is an ongoing process. Website content, platform themes, apps, embedded services, browsers, and assistive technologies change over time.

3. Compatibility

The website is intended to function with current versions of major browsers and commonly used assistive technology configurations. Compatibility may be reduced with obsolete browsers, unsupported operating systems, unusual browser extensions, or third-party content outside our control.

4. Known Limitations

Some third-party components, embedded media, externally hosted documents, or platform-generated interfaces may not fully conform to every accessibility expectation. We do not control the code or update cycle of all such services.

Highly visual effects may be simplified or disabled through reduced-motion preferences or responsive layouts. Users can also use browser zoom, text scaling, and operating-system accessibility settings.

5. Feedback and Assistance

Visitors who encounter an accessibility barrier may contact us using the information below. A useful report includes the page, feature, browser, device, assistive technology, and a description of the issue.

We will review good-faith reports and make reasonable efforts to provide information in an alternative format or improve the affected experience.

6. Accessibility in Client Projects

For client projects, accessibility work is limited to the approved scope. A standard website project may include baseline best practices but does not constitute a formal audit, certification, legal opinion, or guarantee of compliance with every jurisdictional standard.

Formal conformance testing, assistive-technology testing, remediation of third-party systems, document accessibility, captioning, transcription, or ongoing monitoring must be separately scoped.

7. Client Responsibilities

Clients remain responsible for the accessibility of content, documents, videos, product data, policies, images, apps, future edits, and third-party integrations they supply or add after delivery.

8. Continuing Improvement

We may update design patterns, code, content, and testing practices as technology and standards evolve. Feedback is used to prioritize practical improvements.