4th Thursday ADA Talk: ADA Title I: Employment Protections

Telework Tensions in Employment Protections

ADA Title I prohibits discrimination against qualified individuals with disabilities in employment and requires employers with 15 or more employees to provide reasonable accommodations unless it causes undue hardship. This includes modifications like telework for those whose disabilities make in-office work difficult or impossible.

In early 2026, the landscape shifted when the EEOC released detailed guidance addressing telework as a reasonable accommodation, specifically in response to federal government directives pushing for full-time in-person work. Though aimed at federal agencies under the parallel Rehabilitation Act, the principles mirror ADA Title I obligations for private employers: requests must be evaluated case-by-case through an interactive process, considering essential job functions and alternatives if full-time remote work poses hardship.

This timing matters because many private companies have implemented or tightened return-to-office policies post-pandemic, prompting a surge in accommodation requests. Denials without thorough analysis expose employers to claims, especially as courts and the EEOC increasingly view mental health impairments—such as PTSD or depression—as disabilities warranting protection.

The stakes are tangible. Non-compliance can trigger EEOC investigations, back pay awards, compensatory damages up to statutory caps (ranging from $50,000 to $300,000 depending on employer size), and attorney fees. Larger cases often settle in six or seven figures to avoid trial. Smaller employers, while not immune, face proportional risks amplified by limited resources for compliance.

A non-obvious tension lies in balancing business needs for in-person collaboration against accommodation duties. Employers may argue undue hardship from reduced productivity or team dynamics, but the EEOC stresses that such claims require evidence, not assumptions. Meanwhile, employees risk retaliation claims if requests are poorly handled, creating a fraught dynamic for both sides.