Skip to content
Bhavesh Works

Accessibility Statement

We build interfaces for everyone who has to use them. This statement sets out what we have done on works.bhavvesh.in, what we are still working on, and how to tell us when we have got something wrong.

Last updated
6 August 2026
Reading time
2 min
Sections
5
Applies to
works.bhavvesh.in

Our commitment

Accessibility is part of the engineering work, not a review step at the end. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across this website.

What we have implemented

  • Semantic HTML landmarks, a logical heading order, and a skip-to-content link as the first focusable element.
  • Full keyboard operability, including the navigation dropdown, the services accordion and the contact form.
  • Visible focus indicators on every interactive element, at a contrast that survives both themes.
  • Text and interface contrast meeting or exceeding the 4.5:1 and 3:1 thresholds in both light and dark appearance.
  • Form fields with persistent labels, programmatic error association, and errors announced to assistive technology.
  • Meaningful alternative text on informative images; decorative drawings marked as such and hidden from screen readers.
  • Full support for prefers-reduced-motion — smooth scrolling, parallax and reveal animations are disabled, not merely shortened.
  • Layout, spacing and type that reflow cleanly to 400% zoom without loss of content or horizontal scrolling.

Known limitations

We would rather name these than let you discover them:

  • Portfolio thumbnails are synchronised from bhavvesh.in. Their alternative text is generated from the project title and summary, which is descriptive but less specific than hand-written text for each image.
  • Case studies linked from the portfolio are hosted on a separate site that is outside the scope of this statement.
  • Some hover-revealed project detail is supplementary and is not surfaced on touch devices; the same information appears in the text beneath each project.

How we assess

We test with keyboard-only navigation, with VoiceOver and NVDA, with automated auditing in the build pipeline, and with the operating system’s reduced-motion, increased-contrast and text-scaling settings enabled. Self-assessment has its limits, and we treat reports from real users as more authoritative than any audit tool.

Feedback

If any part of this site is difficult or impossible for you to use, email bhavubhoi806@gmail.com and describe what happened, the page, and the assistive technology you were using. We aim to acknowledge within two business days and to fix confirmed barriers in the next deployment.

If you need information from this site in an alternative format, ask and we will provide it.

Other documents