Sacred knowledge should be easier to reach.

Target: WCAG 2.2 Level AA · Status: accessibility-aware implementation with automated/static checks completed; manual assistive-technology and real-device verification remains a launch gate.

Accessibility principles built into current production

The website uses semantic headings and landmarks, skip navigation, visible keyboard focus, large touch targets, labeled form controls, inline field errors, live form status regions, meaningful link text, responsive layouts and text alternatives for meaningful images. Decorative brand marks use empty alt text so they are not redundantly announced.

Keyboard and focus

Interactive elements receive an explicit high-contrast :focus-visible outline. The mobile navigation exposes expanded/collapsed state, supports Escape to close and is designed to remain keyboard operable. Focus should never be intentionally hidden.

Motion

Animations and smooth scrolling respond to prefers-reduced-motion. Essential content is not dependent on animation.

Forms and errors

Request and testimonial controls are associated with visible labels. Required fields are indicated in text/semantics rather than color alone. Validation errors are returned by the server as well as surfaced near the corresponding field in the browser. Status messages use live regions and the submission button communicates a meaningful action.

Images and portraits

Important portraits use a dedicated art-directed 4:5 crop that preserves the full face and top of the head instead of relying on a fragile desktop-only object-position. Responsive WebP variants are supplied for other photographs. A final real-browser visual pass at common mobile, tablet and desktop widths remains required.

Contrast and typography

A darker gold text token is used on light surfaces; the brighter decorative gold remains available on dark burgundy surfaces. Text is not intentionally locked against browser zoom. System fonts reduce external dependencies and generally improve rendering resilience.

Panchangam and dynamic content

Calculated results are presented as text, not color-only states. Loading and error messages remain readable. Further screen-reader testing should verify that updates are announced at the right verbosity in the final browser build.

Known manual verification remaining

WCAG conformance cannot be established by source inspection alone. Before launch, test keyboard-only completion, VoiceOver on iOS/Safari, NVDA or JAWS on Windows, zoom/reflow at 200–400%, high-contrast settings, form errors, mobile navigation, Turnstile accessibility, confirmation/calendar actions and portrait framing on representative devices.

Accessibility feedback

Before launch, establish a monitored accessibility contact such as accessibility@yourvedicpriest.com. Visitors should be able to report barriers and request an accessible alternative without being forced into one communication channel.