Accessibility Statement

1. Our Commitment to Digital Inclusion

At Acadyn Labs, accessibility is not a cosmetic checklist or a post-launch remediation effort — it is a foundational architectural principle. Whether an educator is managing student coursework, a finance officer is running institutional payroll, or a candidate is reviewing open positions, our software is engineered to work reliably across diverse devices, assistive technologies, and physical abilities.

We design software to work for the way people actually interact with the web — with keyboards, screen readers, switch devices, screen magnifiers, and voice controls.

2. Conformance Standards & Regulatory Alignment

We benchmark all interface development against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, with selective adoption of Level AAA criteria where technically feasible (such as high-contrast color pairings and explicit focus styling).

WCAG 2.1 Level AA: Primary benchmark governing perceivability, operability, understandability, and robustness.
Section 508 (US Rehabilitation Act): Technical standards for electronic and information technology accessibility.
EN 301 549 (European Standard): European accessibility requirements for ICT products and services.
GIGW & RPwD Act (India): Guidelines for web accessibility under the Rights of Persons with Disabilities legislation.

3. Technical Measures & Architectural Implementation

We employ proactive engineering techniques across our UI layer to ensure seamless usability:

Complete Keyboard Navigation: Every interactive element — links, buttons, form controls, tabs, and modal triggers — is fully operable via standard keyboard commands (Tab, Shift+Tab, Enter, Space, Escape, Arrow keys). Logical tab sequences are maintained without arbitrary positive tabindex overrides.
Visible Focus Rings (:focus-visible): High-contrast, non-intrusive focus rings indicate active focus points for keyboard navigators without intrusive browser default outlines on mouse clicks.
Skip to Main Content: Direct skip links are embedded at the top of every page layout, allowing keyboard users to bypass repetitive header navigation and jump straight to primary content.
Semantic HTML5 Hierarchy: Strict landmark markup (<header>, <nav>, <main>, <aside>, <section>, <footer>) and structured heading trees (one <h1> per page with descending <h2> to <h4>) provide screen reader users with effortless page scanning.
Dynamic ARIA Implementation: ARIA live regions (aria-live="polite") announce dynamic status changes without shifting focus. Complex SVG diagrams carry full textual summaries via aria-label on parent <figure role="img"> containers.
Color Contrast & Scalable Typography: Contrast ratios strictly meet or exceed WCAG AA thresholds (minimum 4.5:1 for normal text and 3:1 for large text/UI components). Layouts and typography scale smoothly up to 200% zoom without horizontal scrolling or text clipping.
Reduced Motion Respect: Full support for OS-level prefers-reduced-motion preferences. When enabled, non-essential animations, parallax effects, and animated vector transitions immediately resolve to their static resting states.
Form Usability & Error Routing: Form fields are explicitly bound to programmatic <label> elements. When validation errors occur, focus is automatically directed to the first invalid field, accompanied by descriptive aria-invalid and aria-describedby error messages.

4. Assistive Technology & Browser Compatibility

Our platforms and corporate website are tested and engineered for compatibility with modern operating systems, web browsers, and screen readers:

Screen Readers: NVDA, JAWS (Windows), VoiceOver (macOS, iOS), TalkBack (Android).
Web Browsers: Latest versions of Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge.
Alternative Inputs: Switch control hardware, head pointers, voice recognition software, and screen magnification tools.

5. Ongoing Testing & Engineering Practices

Accessibility is embedded directly into our continuous integration (CI/CD) and design review workflows:

Automated linting and test suites (axe-core, Lighthouse) run against every code change to catch markup regressions early.
Manual keyboard-only walkthroughs and screen reader smoke tests are conducted before major production deployments.
Design token palettes are systematically tested for contrast under diverse display calibrations and ambient lighting conditions.

6. Known Considerations & Future Roadmap

While we strive for complete accessibility across all touchpoints, complex interactive dashboards and dense data tables require ongoing refinement. We are actively developing enhanced keyboard shortcuts for high-depth table navigation and custom high-contrast mode toggles for power users.

7. Feedback, Alternative Formats & Contact

We welcome feedback from users on how we can improve the accessibility of our website and platforms. If you encounter any barriers or require information in an alternative format:

Email our Accessibility Team directly at accessibility@acadyn.in or contact our Data Protection & Compliance Officer at berdin.jasper@acadyn.in. We commit to acknowledging all accessibility feedback within 2 business days and providing a concrete timeline for resolution.

Need something specific?

Our Data Protection Officer can answer questions about data handling, retention and regional compliance.

Contact DPO →

1. Our Commitment to Digital Inclusion

We design software to work for the way people actually interact with the web — with keyboards, screen readers, switch devices, screen magnifiers, and voice controls.

2. Conformance Standards & Regulatory Alignment

WCAG 2.1 Level AA: Primary benchmark governing perceivability, operability, understandability, and robustness.

Section 508 (US Rehabilitation Act): Technical standards for electronic and information technology accessibility.

EN 301 549 (European Standard): European accessibility requirements for ICT products and services.

GIGW & RPwD Act (India): Guidelines for web accessibility under the Rights of Persons with Disabilities legislation.

3. Technical Measures & Architectural Implementation

We employ proactive engineering techniques across our UI layer to ensure seamless usability:

Complete Keyboard Navigation: Every interactive element — links, buttons, form controls, tabs, and modal triggers — is fully operable via standard keyboard commands (Tab, Shift+Tab, Enter, Space, Escape, Arrow keys). Logical tab sequences are maintained without arbitrary positive tabindex overrides.

Visible Focus Rings (:focus-visible): High-contrast, non-intrusive focus rings indicate active focus points for keyboard navigators without intrusive browser default outlines on mouse clicks.

Skip to Main Content: Direct skip links are embedded at the top of every page layout, allowing keyboard users to bypass repetitive header navigation and jump straight to primary content.

Semantic HTML5 Hierarchy: Strict landmark markup (<header>, <nav>, <main>, <aside>, <section>, <footer>) and structured heading trees (one <h1> per page with descending <h2> to <h4>) provide screen reader users with effortless page scanning.

Dynamic ARIA Implementation: ARIA live regions (aria-live="polite") announce dynamic status changes without shifting focus. Complex SVG diagrams carry full textual summaries via aria-label on parent <figure role="img"> containers.

Color Contrast & Scalable Typography: Contrast ratios strictly meet or exceed WCAG AA thresholds (minimum 4.5:1 for normal text and 3:1 for large text/UI components). Layouts and typography scale smoothly up to 200% zoom without horizontal scrolling or text clipping.

Reduced Motion Respect: Full support for OS-level prefers-reduced-motion preferences. When enabled, non-essential animations, parallax effects, and animated vector transitions immediately resolve to their static resting states.

Form Usability & Error Routing: Form fields are explicitly bound to programmatic <label> elements. When validation errors occur, focus is automatically directed to the first invalid field, accompanied by descriptive aria-invalid and aria-describedby error messages.

4. Assistive Technology & Browser Compatibility

Our platforms and corporate website are tested and engineered for compatibility with modern operating systems, web browsers, and screen readers:

Screen Readers: NVDA, JAWS (Windows), VoiceOver (macOS, iOS), TalkBack (Android).

Web Browsers: Latest versions of Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge.

Alternative Inputs: Switch control hardware, head pointers, voice recognition software, and screen magnification tools.

5. Ongoing Testing & Engineering Practices

Accessibility is embedded directly into our continuous integration (CI/CD) and design review workflows:

Automated linting and test suites (axe-core, Lighthouse) run against every code change to catch markup regressions early.

Manual keyboard-only walkthroughs and screen reader smoke tests are conducted before major production deployments.

Design token palettes are systematically tested for contrast under diverse display calibrations and ambient lighting conditions.

7. Feedback, Alternative Formats & Contact

We welcome feedback from users on how we can improve the accessibility of our website and platforms. If you encounter any barriers or require information in an alternative format: