St. Stephen's Daycare
Effective April 15, 2026
Accessibility.
Designed so every parent can use it with confidence.
Accessibility is an operational requirement, not a feature
We prioritize usable, readable, keyboard-operable experiences across core parent journeys.
St. Stephen's Daycare commits to accessible digital access for families, including users of screen readers, keyboard-only navigation, magnification, and reduced-motion settings.
This statement covers our current standard, known gaps, and how to report barriers. We triage accessibility defects as service-quality incidents and track remediation timelines.
1. Conformance Standard
WCAG 2.2 AA TARGET
- Target baseline: WCAG 2.2 Level AA for public pages and authenticated parent flows.
- Current status: Partially conformant while remediation for legacy content and third-party dependencies remains in progress.
- Priority journeys: Admissions inquiry, parent login/authentication, attendance view, and policy pages.
2. Scope of This Statement
WHAT IS INCLUDED
- Included: Main website pages, legal pages, and parent portal pages operated by the school.
- Partially controlled: Third-party embeds, map widgets, and externally hosted resources that may have independent accessibility limitations.
- Out of scope: User-owned devices, browser-specific bugs, or assistive-technology limitations outside web standards compliance.
3. Engineering Controls We Enforce
BUILD-TIME AND RUNTIME PRACTICES
- Semantic structure: Correct heading order, landmarks, and form semantics for assistive technology parsing.
- Keyboard operation: Interactive controls are reachable and usable without a mouse, including modal dismissal and focus return behavior.
- Visible focus: Focus indicators are preserved for all keyboard-reachable components.
- Contrast and readability: Color contrast and typography spacing are maintained to support low-vision readability.
- Motion sensitivity: Animation behavior respects reduced-motion preferences where practical.
- Error clarity: Form errors are explicit, field-linked, and actionable.
4. Known Issues and Active Remediation
TRANSPARENCY
- Legacy documents: Some downloadable PDFs may not be fully tagged for screen-reader navigation.
- Third-party content: External widgets may not always expose complete keyboard and screen-reader semantics.
- Historical media: Older blog assets may require alt-text backfill and heading normalization.
- Remediation approach: We maintain a prioritized accessibility backlog and address high-impact blockers first.
5. Assistive Technology Coverage
TESTED COMBINATIONS
- Screen reader + browser: NVDA/JAWS with Chromium-family browsers on Windows, and VoiceOver with Safari on Apple platforms.
- Keyboard-only checks: Core workflows are tested for tab order, logical focus, and non-pointer operability.
- Mobile checks: Responsive behavior and touch target sizing are validated on common modern devices.
6. Legal and Policy Alignment
INDIA PRIMARY, GLOBAL GOOD PRACTICE
- India alignment: We support equal-access objectives under the Rights of Persons with Disabilities Act, 2016 and applicable digital-service obligations.
- Government guidance: Our approach is informed by Indian accessibility guidance and internationally accepted WCAG controls.
- Privacy intersection: Accessibility feedback that includes personal data is handled under our Privacy Policy and secure support workflow.
7. Feedback, Escalation, and Resolution Timelines
HOW TO REPORT A BARRIER
- What to send: Page URL, task attempted, issue description, device/browser, and assistive technology details.
- Acknowledgment timeline: We aim to acknowledge reports within 2 business days.
- Resolution timeline: We target a workaround or fix plan within 10 business days for standard issues; critical access blockers are expedited.
- Escalation: If unresolved, request escalation through the compliance contact in writing.
Report an Accessibility Barrier
If any part of the website or portal is difficult to access, contact us with reproduction details. We use your report only for support, remediation, and compliance tracking.
Acknowledgment target
within 2 business days
Resolution/workaround target
within 10 business days
Include
URL, issue details, device/browser, and assistive technology used
