Accessibility Statement

What's in place

• Semantic HTML5 landmarks (header, nav, main, footer) and a logical heading order on every page.
• A visible 'skip to main content' link for keyboard and screen-reader users.
• Full keyboard navigation, with a visible focus indicator on every interactive element.
• Color contrast checked at 4.5:1 for text and 3:1 for UI elements, in both light and dark themes.
• Descriptive link text and accessible labels — no bare 'click here' links or icon-only buttons without a label.
• Respects prefers-reduced-motion and prefers-color-scheme rather than overriding them.
• Usable at 200% browser zoom with no horizontal scrolling or clipped content.

How it's verified

Automated checks (axe-core and Lighthouse) run in CI on every deploy, and I do a manual pass with a screen reader (VoiceOver/NVDA) and keyboard-only navigation before shipping any new page. Automated tools catch roughly a third of real accessibility issues — the manual pass is what actually matters.

Privacy & analytics

This site counts page views and link clicks with its own cookieless analytics, so I can see which pages are useful. It stores the page, the link clicked, the referring site, your country, and a rough device size — never your IP address, browser fingerprint, or anything that identifies you. A random visit id lives only in your browser tab and disappears when you close it, and raw events are deleted after 90 days.

If your browser sends Do Not Track or Global Privacy Control, nothing is recorded at all. Separately, the visitor map on the home page keeps an aggregate count per approximate city-level location (rounded to about 11 km), again without storing IP addresses.

Questions typed into the "Ask about Ashish" assistant are sent to Cloudflare Workers AI to generate an answer and are not stored; only the fact that a question was asked is counted.

Found a problem?

If something on this site doesn't work well with assistive technology, I want to know — please reach out.