Accessibility Statement
Laborate Pharmaceuticals is committed to providing a website that is accessible to the widest possible audience. This statement explains how we approach accessibility, what we have implemented, and how you can reach us if you experience any barriers.
Introduction
This Accessibility Statement applies to the Laborate Pharmaceuticals India Ltd. website at laborate.com, including all pages, product information, downloadable resources, and interactive features. It describes our approach to digital accessibility, the standards we aim to align with, and the steps we take to make our website usable by the widest possible audience.
Accessibility is not a project deliverable — it is an ongoing practice. We design and build our website with inclusive intent, test against recognised standards, and actively seek feedback from users who encounter barriers. We acknowledge that accessibility is a continuous journey and commit to improving over time.
Accessibility at Laborate
We believe that access to pharmaceutical and healthcare information should not be restricted by disability or technology. Our website is designed to be usable with a keyboard, compatible with screen readers, readable at increased text sizes, and navigable without a mouse. If you find a part of our website difficult to use, we want to know — your feedback directly improves what we build.
Our Commitment
Laborate Pharmaceuticals is committed to ensuring that its website is accessible to all users, including people with disabilities, users of assistive technologies, older users, and those on low-bandwidth or older devices. We treat accessibility as an integral part of our web development process — not an afterthought.
Our accessibility commitment extends across the full lifecycle of the website:
- Design phase — Colour contrast, typographic hierarchy, focus states, and interaction patterns are reviewed against accessibility criteria before development begins.
- Development phase — Semantic HTML, ARIA landmarks, and accessible component patterns are applied as standard practice. No presentational markup is used where semantic equivalents exist.
- Testing phase — Pages are tested for keyboard operability, focus management, screen reader compatibility, and responsive behaviour across screen sizes.
- Content phase — Editorial guidance encourages meaningful alt text, accessible link text, clear heading structures, and plain language throughout.
- Improvement phase — We review this statement annually and address reported issues progressively. Every accessibility report we receive is acknowledged and investigated.
Accessibility Standards
The laborate.com website is designed to align with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. These guidelines, published by the World Wide Web Consortium (W3C), are the internationally recognised benchmark for web accessibility and are referenced in accessibility legislation across multiple jurisdictions.
We use the following technical frameworks and principles in our implementation:
<header>, <main>, <nav>, <aside>, <footer>, <section>, <article>) provide machine-readable document structure that assistive technologies can navigate. Our implementation uses semantic HTML as the foundation for all accessibility features.Alignment, Not Certification
We design and build laborate.com to align with WCAG 2.2 Level AA success criteria. This statement describes genuine implementation effort and ongoing commitment — it does not constitute a formal third-party conformance certification. Where gaps are identified through user feedback or internal review, we address them progressively. If you encounter a specific accessibility barrier, please report it using the contact details in Section 10.
Accessibility Features
The following accessibility features are implemented across laborate.com. These represent the baseline accessibility layer present in the website's HTML, CSS, and JavaScript as built.
Navigation & Keyboard Access
- Skip to Content link — A visible "Skip to main content" link appears at the top of every page, allowing keyboard users to bypass the navigation menu and jump directly to the main content area.
- Keyboard-navigable menu — The primary navigation is fully operable using only a keyboard. Tab, Enter, Escape, and arrow keys work as expected for opening menus and activating links.
- Visible focus indicators — All interactive elements (links, buttons, form fields, TOC links) display a clear visible focus ring when they receive keyboard focus. Focus states are not suppressed with
outline: noneunless a custom focus style is provided. - Logical tab order — Tab order follows a natural reading sequence (left-to-right, top-to-bottom) consistent with the visual layout.
- Escape key support — Modals, mobile navigation, and expanded accordions can be dismissed with the Escape key.
Visual Design
- Colour contrast — Body text achieves a minimum contrast ratio of 4.5:1 against background colours (WCAG 2.2 AA criterion 1.4.3). Primary blue (#114E96) text on white exceeds 7:1.
- Text resizing — All text is specified in relative units (
rem) and scales proportionally when browser font size is increased up to 200% without loss of content or functionality. - Responsive layout — The website adapts to all screen widths from 320px upwards, eliminating the need for horizontal scrolling on small screens.
- No reliance on colour alone — Status indicators, callouts, and interactive states use icons and text labels alongside colour to convey meaning.
- Reduced motion — Scroll-triggered animations and transitions are suppressed when the operating system's "Reduce Motion" preference is active, via
@media (prefers-reduced-motion: reduce).
Content & Structure
- Logical heading hierarchy — Every page uses a single H1, followed by H2 section headings, H3 subsections, and H4 where needed. Heading levels are not skipped for visual styling purposes.
- Semantic landmarks — HTML5 landmark elements (
<header>,<main>,<nav>,<aside>,<footer>) are present on every page and correctly labelled witharia-labelwhere disambiguation is needed. - Alternative text — All informational images carry descriptive
alttext. Decorative images use empty alt attributes (alt="") androle="presentation"so screen readers skip them. - Accessible tables — Data tables use
<thead>,scope="col"on header cells,role="region", andtabindex="0"for keyboard-scrollable overflow containers. - Descriptive link text — Links use meaningful text that describes the destination without requiring surrounding context. "Read more" links include visually hidden text clarifying the destination.
- Plain language — We write in clear, direct English at a level accessible to a broad audience, including users who rely on plain language for comprehension.
Forms & Interactions
- Labelled form fields — All form inputs have programmatically associated labels using
<label for="...">oraria-labelwhere visual labels are not present. - Error identification — Validation errors are communicated both visually and programmatically, including descriptive error messages associated with the relevant fields via
aria-describedby. - Role and state announcements — Interactive components (accordions, toggles, modals) use appropriate ARIA roles and states (
aria-expanded,aria-controls,aria-current) to communicate their state to assistive technologies. - Sufficient click/touch target size — Interactive elements are sized to provide adequate touch and click targets for users with motor impairments.
Accessibility Roadmap
The following table shows the current accessibility status of key website areas and the improvements we have planned or are actively working towards. This roadmap is reviewed annually and updated as improvements are completed.
| Area | Current Status | Planned Improvements |
|---|---|---|
| Keyboard navigation | Implemented — all interactive elements keyboard-accessible; Escape key support across interactive components | Ongoing review with each new page or feature added |
| Focus indicators | Implemented — visible focus ring on all interactive elements | Enhanced focus styling for high-contrast operating system modes |
| Skip to Content link | Implemented — present on every page | N/A — already implemented globally |
| Heading hierarchy | Implemented — single H1, logical H2–H4 structure on all current pages | Content audit as new pages are published to maintain consistency |
| Colour contrast | Implemented — primary text meets 4.5:1 minimum; blue on white exceeds 7:1 | Audit of interactive state contrast (hover, active, disabled) using APCA methodology |
| Responsive layout | Implemented — fully responsive from 320px upwards; tested across device classes | Ongoing optimisation as new content and page types are added |
| Images & alt text | Implemented — informational images carry descriptive alt text; decorative images are marked presentational | Full editorial review as the product catalogue and media library grow |
| Accessible forms | Implemented — programmatic labels, error identification, ARIA states on all current contact forms | Expanded inline guidance and field grouping for complex multi-step forms |
| Downloadable documents | Partial — HTML pages meet current standards; PDF documents are in progress for accessibility tagging | Remediation of existing PDF library; all new documents published to accessibility standards |
| Embedded content | Partial — Google Maps iframe on Contact page; GA4 analytics (consent-gated). Third-party content accessibility varies. | Accessible fallbacks and text alternatives for all future embedded content; consent-gated loading preserves user control |
| Video & multimedia | Not yet deployed — no video content currently on the public website | When video is introduced: captions (auto-generated + reviewed), transcripts, and audio descriptions where needed |
| Reduced motion | Implemented — prefers-reduced-motion media query suppresses all CSS animations and transitions for users who opt in |
N/A — already implemented globally at the design system level |
Browser & Device Compatibility
Laborate.com is designed to work correctly with modern, standards-compliant web browsers. We test across the following environments and provide best-effort support for the most recent two major versions of each browser:
- Google Chrome — Desktop (Windows, macOS) and Android mobile
- Microsoft Edge — Desktop (Windows, macOS) and Windows mobile
- Mozilla Firefox — Desktop (Windows, macOS, Linux)
- Apple Safari — Desktop (macOS) and iOS mobile
- Samsung Internet — Android mobile (best-effort)
The website is fully responsive and has been tested across the following device classes:
- Desktop — Wide viewports (1280px–1920px+); multi-column layout
- Tablet — Portrait and landscape orientations (768px–1024px); adaptive grid layout
- Mobile — Small screens (320px–767px); single-column layout; touch-optimised navigation
We do not actively support Internet Explorer or browsers more than two major versions behind their current release. Users on older browsers are encouraged to upgrade for the best experience and for security reasons.
Assistive Technology Compatibility
Laborate.com is built with assistive technology compatibility in mind. Our implementation of semantic HTML5, ARIA roles and states, and keyboard navigation patterns is designed to work correctly with the following assistive technology categories:
- Screen readers — The website is designed to be operable with screen reader software. Landmark navigation, heading structure, alternative text, ARIA labels, and live-region announcements are implemented to support screen reader users. We design against the behaviour of commonly used screen readers but have not conducted formal screen reader testing with paid participants at this stage — this is planned as part of our continuous improvement programme.
- Keyboard-only navigation — All functionality available via mouse is also available via keyboard. Users can navigate the entire website, use all interactive components, submit forms, and access all downloads using only a keyboard.
- Screen magnification — The website supports text resizing up to 200% via browser settings without loss of content or function. Responsive layout ensures that content reflows to a single column at high magnification levels rather than overflowing horizontally.
- Voice recognition software — Interactive elements (links, buttons, form fields) carry visible, meaningful text labels that can be activated by voice command. Unlabelled icon-only buttons include accessible names via
aria-labelfor voice navigation compatibility. - High contrast modes — The website is designed to remain usable in Windows High Contrast Mode and equivalent operating system display modes. Focus indicators and interactive states are visible in high contrast mode. We plan to conduct dedicated high-contrast testing as part of our next accessibility review cycle.
Accessibility in Development
Accessibility is embedded in our development methodology from the start. The laborate.com website is built using vanilla HTML5, CSS, and vanilla JavaScript — no page builder frameworks, no generic third-party component libraries, and no auto-generated markup. Every interactive component is written purposefully to meet accessibility criteria.
Our development approach incorporates the following accessibility practices:
- Semantic HTML5 is used for all structural and content elements; presentational
<div>containers do not replace semantic equivalents - ARIA roles and states are applied where native HTML semantics are insufficient — and are not applied where they would conflict with implicit native semantics
- All new components are reviewed against their relevant WCAG 2.2 success criteria before being merged into the main codebase
- Components are reused across the website rather than re-implemented, ensuring that accessibility fixes propagate consistently to all instances
- Keyboard operability is treated as a first-class requirement for every interactive element, not a post-development addition
- Focus management is explicitly handled for dynamic UI patterns (modal dialogs, expandable menus, accordions) to ensure screen readers track state changes correctly
- Responsive testing covers touch, pointer, and keyboard interaction modes at all supported viewport sizes
Accessible by Construction
The laborate.com website is built using a fully custom, hand-coded design system with no auto-generated presentational markup. Every component — from the navigation bar to the legal document TOC — is written in semantic HTML with explicit accessibility attributes. This architecture means accessibility improvements to shared components propagate automatically to every page that uses them, without needing individual page-by-page fixes.
Known Limitations
We are transparent about areas where laborate.com does not yet fully meet our accessibility goals. The following limitations are known and are being addressed progressively:
- PDF documents — Downloadable PDF brochures, technical data sheets, and product catalogues may not meet the same accessibility standards as our HTML web pages. PDFs generated from legacy templates may lack proper tagging, logical reading order, or alternative text. We are working to remediate our PDF library progressively, and all new documents will be published to accessibility standards.
- Third-party embedded content — Some website areas (notably the Contact page map, and any future embedded video) load content from third-party platforms over which Laborate has limited control. The accessibility of embedded third-party content depends on the platform provider's own implementation. We commit to providing accessible alternatives or fallback content wherever third-party embeds are used.
- Formal screen reader testing — While the website is designed and built to be screen reader compatible, we have not yet completed formal usability testing with disabled participants using assistive technology. We plan to conduct structured assistive technology testing as part of our continuous improvement programme.
- Complex product data — As the product catalogue grows, some complex product data tables or specification pages may present accessibility challenges at scale. We will address these on a case-by-case basis as content is published.
- Historic content — Some content published at or near the website launch may require progressive improvements to meet our current standards as editorial resources allow.
Help Us Identify Issues
If you encounter a barrier not listed here — or if a listed limitation is preventing you from accessing important content — please contact us using the details in Section 10. We investigate every accessibility report and prioritise fixes based on the severity of the barrier and the number of users affected. You will receive a response within 10 business days.
Feedback & Reporting Issues
We actively welcome accessibility feedback. If you experience difficulty accessing any part of laborate.com — whether a page is difficult to navigate, a screen reader is not reading content correctly, a form is not keyboard-accessible, or any other barrier — please contact our Digital & Technology team.
To help us investigate your report efficiently, please try to include:
- The URL of the page or section where you experienced the barrier
- A description of what you were trying to do and what happened instead
- The browser and version you were using (if known)
- The assistive technology you were using, if applicable (e.g. screen reader name, keyboard-only navigation)
- The operating system and device type (e.g. Windows desktop, iPhone, Android tablet)
We aim to respond to all accessibility reports within 10 business days. If you require information in an alternative format (for example, large print, audio, or a plain-text version of a document), please request this when you contact us.
Your Feedback Improves Our Website
Every accessibility report we receive is read, logged, and investigated. Reports from users who experience barriers in the real world are among the most valuable inputs we receive — they identify gaps that automated testing and internal review may miss. Please reach out to us at accessibility@laborate.com or via our Contact Us page. We will acknowledge your report and keep you informed of progress.
Continuous Improvement
Accessibility is a continuous practice. As the website grows, as web standards evolve, and as we learn from user feedback, we will identify and address new accessibility requirements. The following activities form part of our ongoing accessibility programme:
- Annual statement review — This Accessibility Statement is reviewed at least once per year and updated to reflect the current state of the website. Material changes to accessibility features or known limitations will be noted in the Revision History.
- Component-level reviews — When new UI components or page types are introduced to the website, they are reviewed for WCAG 2.2 AA alignment before launch.
- PDF remediation — We are working progressively to tag and remediate our downloadable PDF library to meet PDF/UA accessibility standards.
- Formal assistive technology testing — We plan to conduct structured usability testing with disabled participants using assistive technology during the next major website development cycle.
- User feedback integration — Reports from users who encounter barriers are triaged and addressed according to severity. Systemic or high-severity barriers are prioritised for immediate attention.
- Team training — Our digital team maintains awareness of current accessibility standards and best practices, and applies this knowledge to all new development work.
Next Scheduled Review
This statement is next scheduled for review in January 2027. If significant new website features, content types, or third-party integrations are introduced before that date, an interim review will be conducted. Completed improvements since the last review are documented in the Revision History at the end of this page.
Changes to This Statement
This Accessibility Statement will be updated to reflect changes in our accessibility implementation, the addition of new website features or content types, the resolution of known limitations, and any changes in applicable accessibility standards or guidance.
Material changes — including the identification of new limitations, the completion of planned improvements, or a change in our target standards — are recorded in the Revision History in Section 14. The "Last Updated" date in the metadata panel at the top of this page reflects the most recent revision.
Always Current
The latest version of this Accessibility Statement is always available at laborate.com/legal/accessibility-statement/. If you are a regular user who relies on the accessibility features described here, we recommend checking this page after any major website update or at least once per year.
Contact Information
For accessibility feedback, to report a barrier, to request content in an alternative format, or to enquire about our accessibility programme, please contact:
Digital & Technology Team
Laborate Pharmaceuticals India Ltd.E-11, Industrial Area
Panipat – 132103
Haryana, IndiaAccessibility Email: accessibility@laborate.com
General Enquiries: info@laborate.com
Phone: +91-180-3508200We aim to respond to all accessibility enquiries within 10 business days. For general website enquiries, medical information requests, or product questions, please use our Contact Us page.
Revision History
A record of material changes to this Accessibility Statement is maintained below. Changes to the accessibility roadmap, the resolution of known limitations, or updates to our target standards will be noted here.
-
Version 1.0
Initial publication of the Laborate Pharmaceuticals Accessibility Statement. Fourteen sections covering: Introduction (accessibility-at-Laborate Info callout), Our Commitment (5-point lifecycle commitment), Accessibility Standards (WCAG 2.2 AA alignment; POUR principles; ARIA WAI-ARIA 1.2; Semantic HTML5; Progressive Enhancement — definition block; Standards alignment Notice callout), Accessibility Features (H3 subsections — Navigation & Keyboard, Visual Design, Content & Structure, Forms & Interactions — 19 features), Accessibility Roadmap (12-row × 3-column table: keyboard, focus, skip link, headings, contrast, responsive, alt text, forms, PDFs, embedded content, video, reduced motion), Browser & Device Compatibility (5 browsers; 3 device classes), Assistive Technology (5 categories: screen readers, keyboard, magnification, voice, high contrast), Accessibility in Development (7-point development philosophy; Success callout: Accessible by Construction), Known Limitations (5 limitations: PDFs, third-party, formal testing, product data, historic content; Warning callout: Help Us Identify Issues), Feedback & Reporting (what to include; 10-day response; Success callout: Feedback Welcome), Continuous Improvement (6-point programme; Neutral callout: Next Scheduled Review Jan 2027), Changes to This Statement, Contact (accessibility@laborate.com; 10-day response), Revision History. 7 callouts (all 4 variants). 1 table. Built on the LEGAL-001 Enterprise Legal Documentation Framework (C-121–C-126). Published concurrent with the launch of the new laborate.com corporate website.
Experiencing an Accessibility Barrier?
If part of our website is difficult to use, please tell us. We investigate every report, prioritise fixes by severity, and respond within 10 business days. Contact us at accessibility@laborate.com.