Accessibility Statement

1. Our commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We believe accessibility is not a feature but a baseline expectation — every release should be navigable by keyboard, readable by assistive technology, and respectful of user preferences for reduced motion, larger text, and high-contrast colour schemes.

2. What we've done

• Semantic HTML and ARIA landmarks on every page (header, main, footer, nav).
• Visible focus indicators on every interactive element.
• Form fields with explicit labels and helper text; error messages tied to fields viaaria-describedby.
• Status changes announced through aria-live regions where appropriate (matched count in the project wizard, success / error toasts).
• Sufficient colour contrast for body copy and primary buttons against the background. Status pills use both colour and text so colour-blind users aren't disadvantaged.
• Mobile breakpoints down to a 360 px viewport so the service works on small phones.
• Email templates that fall back gracefully without remote images and respect the user's prefers-color-scheme setting.

3. Known gaps

We track accessibility issues openly. As of the date above, known gaps include:

• Some long-form data tables in admin tools do not yet have row-header relationships announced via scope="row".
• Certain inline icons in the wizard use emoji characters; we are reviewing whether additional aria-hidden wrappers are needed for specific screen-reader combinations.
• Drag-and-drop file upload does not yet expose an explicit keyboard-first flow.

We commit to closing these in our next quarterly accessibility review.

4. Standards we follow

• WCAG 2.1 Level AA, with selective adoption of 2.2 success criteria where they fit our patterns.
• California Unruh Civil Rights Act and California Disabled Persons Act — we treat digital accessibility as part of our public-accommodation obligations.
• Section 508 and ADA Title III principles where applicable to a private commercial service.

5. Browsers and assistive tech

We test the service with the latest two versions of:

• Chrome, Firefox, Safari, and Edge on desktop.
• Safari on iOS and Chrome on Android.
• VoiceOver on macOS and iOS, and NVDA on Windows.

If you use a different combination and run into issues, let us know — we want to fix it.

6. Reporting an issue

Email accessibility@officeconnectsolution.com with a description of the issue, the URL where you encountered it, and the assistive technology and browser you were using. We aim to respond within five business days.

7. Alternative contact

If the service is not accessible to you for any reason, you can also call the craftsman assistant line during business hours and we will help you complete any task you would otherwise do online — submitting a project, viewing an estimate, paying an invoice.