Accessibility

§1The target

Pinaka targets WCAG 2.1 level AA conformance across the marketing site, the student app, and the admin app. The exam shell ships at AA on first launch, with ongoing audits as the surface grows.

§2What we build for

Keyboard navigation through every interactive surface, with a visible focus state on every focusable element. Skip-to-content links on every public page. Logical heading hierarchy and landmark regions.

Screen-reader labels on icon-only buttons. ARIA roles applied only where they add information not already conveyed by the underlying HTML.

Color contrast above the WCAG AA threshold for all text. Information is never conveyed by color alone.

Touch targets of at least 44 by 44 CSS pixels on mobile. Form fields are labeled and described, with inline error messages associated with their inputs.

Motion respects the operating-system reduced-motion preference. Auto-playing animation is avoided.

§3Known gaps

The exam timer has an audio cue at five minutes remaining. There is no haptic equivalent on mobile yet.

The skill map wave chart will ship with a tabular alternative view for screen readers; the alternative view is in progress.

Some long-form analysis posts include data visualizations whose alt-text and table fallbacks are being added retroactively.

§4Reporting an accessibility problem

Email support@mypinaka.com with the URL of the page, the device and browser you used, the assistive technology you use (screen reader, voice control, switch device, magnifier, etc.), and a description of what failed.

We respond within five working days and prioritize fixes that block use of the service. If a specific page blocks you from completing a critical task (signing up, taking a mock, requesting a refund), tell us in the email and we will work with you directly until you can complete it.

§5Standards we follow

WCAG 2.1 level AA, with selected level AAA practices where they are inexpensive to maintain. ARIA Authoring Practices for component patterns. EN 301 549 where it converges with WCAG 2.1 AA.

For users in jurisdictions with statutory accessibility requirements, this commitment is intended to satisfy Section 508 of the US Rehabilitation Act (where applicable), the Americans with Disabilities Act, the Accessibility for Ontarians with Disabilities Act (AODA), and the Accessible Canada Act.