Commitment

Accessibility Statement

Last updated: October 24, 2026. Applies to shahvatsal.com.

Our commitment

Vatsal Shah is committed to making shahvatsal.com usable by as many people as possible. We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

Conformance status

Partially conformant. Most public pages support keyboard navigation, visible focus indicators, semantic landmarks, and text alternatives for key images. Some interactive tools, dense diagrams, and legacy embeds may not yet fully meet AA.

Measures we take

  • Semantic HTML and labeled form controls on contact, newsletter, and tools flows.
  • Viewport that allows zoom (width=device-width, initial-scale=1) — we do not lock maximum scale to 1.
  • :focus-visible outlines on interactive controls.
  • Skip link to main content where the site chrome provides it.
  • Ongoing audits against our internal A11Y checklist.

Known limitations

  • Some technical diagrams and code samples may rely on visual layout; captions improve over time.
  • Third-party widgets (e.g. scheduling, CAPTCHA) follow their vendors’ accessibility.
  • Older cached pages may lag until cache purge after a deploy.

Feedback and accommodations

If you encounter a barrier or need content in an alternative format, contact us via the contact form or email listed in site settings. Please include the page URL and a short description of the issue. We aim to respond within 5 business days.

Technical specifications

This site is built with HTML, CSS, and JavaScript and depends on modern evergreen browsers. Accessibility relies on compatibility with assistive technologies that support those standards.

Privacy Policy Request an accommodation

Accessibility: FAQ

Standards, known limits and how to ask for help.

WCAG 2.2 AA target
Which accessibility standard does the site follow?

It aims for WCAG 2.2 Level AA. The current status is partially conformant: most public pages support keyboard navigation, visible focus, semantic landmarks and text alternatives, while some tools, diagrams and legacy embeds do not fully meet AA yet.

What accessibility features are in place?

Semantic HTML, labelled form controls, visible focus outlines, a skip link to main content and viewports that allow zoom. Internal audits against an accessibility checklist continue as pages change.

What are the known limitations?

Some technical diagrams and code samples rely on visual layout, and third-party widgets such as scheduling and CAPTCHA follow their vendors’ accessibility. Captions and text alternatives are being improved over time.

How do I report a barrier or ask for another format?

Use the contact form or the email on the site, and include the page address and a short description of the problem. You will get a response within 5 business days, and content can be provided in an alternative format.

Which browsers and assistive technologies are supported?

Modern evergreen browsers and assistive technologies that support current HTML, CSS and JavaScript standards. Reports from specific screen reader and browser combinations help prioritize fixes.

WhatsApp