D.C. Court Weighs ADA Remote Work Accommodation Duties

If the past few years taught employers anything, it’s this: a laptop can be a workplace, a kitchen table can be a desk,
and sweatpants can be “business casual” if you angle the camera high enough. But as return-to-office policies harden,
a very old legal question is getting a very modern remix: when does the Americans with Disabilities Act (ADA) require
remote work (or hybrid work) as a reasonable accommodationand what exactly must employers do to evaluate it?

A recent decision from a federal court in Washington, D.C., highlights how messy (and fact-heavy) these disputes can be.
The court didn’t declare “remote work is always required” or “remote work is never required.” Instead, it emphasized
what the ADA has demanded all along: individualized assessment, real evidence about job duties, and a thoughtful look
at whether an accommodation actually works in the real worldnot just on paper.

Why this D.C. decision matters right now

Employers are juggling competing pressures: productivity, collaboration, security concerns, office leases that refuse to
stop existing, and employees who discovered they can do excellent work without commuting 90 minutes to attend a meeting
that could have been an email. In that environment, disability-related remote work requests are increasingly common.

Courts, meanwhile, are being asked to referee. The key takeaway from the D.C. litigation trend is not “telework wins”
or “telework loses.” It’s that blanket answers are risky. If the facts show remote work was successful, and if the job’s
truly essential functions can be performed off-site (or mostly off-site with a workable hybrid schedule), an employer may
have a tougher time defending a flat denial.

The ADA framework in plain English (no law school required)

1) You must be “qualified” to do the job

ADA accommodation obligations apply to a “qualified individual” who can perform the job’s essential functionswith or
without accommodation. That puts essential functions at the center of most remote-work cases. The question is not whether
being on-site is “nice,” “traditional,” or “what we’ve always done.” The question is whether being on-site is genuinely
fundamental to performing the job.

2) “Reasonable accommodation” is about effectiveness, not preference

Employees can request a specific accommodation (like full-time telework), but the ADA generally doesn’t guarantee the
employee’s first choice. It requires an effective accommodationone that enables the employee to do the essential parts
of the job. Sometimes remote work is that accommodation. Sometimes it isn’t. Sometimes a hybrid schedule, modified duties,
adjusted work location, or equipment changes get the job done just as well.

3) Employers can say “no” if there’s an undue hardshipbut they have to prove it

“Undue hardship” is more than “this is inconvenient” or “our managers don’t like it.” It generally means significant
difficulty or expense in light of the employer’s operations. The stronger the evidence that remote work is workable (and
that the employee has done it successfully), the harder it can be to defend a hardship argument that’s based mostly on
vibes.

4) The interactive process: the ADA’s unofficial superpower

The ADA doesn’t read like a step-by-step recipe, but EEOC regulations and guidance strongly encourage an interactive,
flexible “give-and-take” process to identify workable accommodations. Courts often evaluate whether both sides engaged
in good faith. Translation: “We said no instantly” is rarely a great look, and “I refused to explain anything” can be
risky toodepending on the context and what information was requested.

What the D.C. court did (and what it was really signaling)

In a case involving a former employee of the Superior Court of the District of Columbia, the plaintiff had been permitted
to telework full time for an extended period during the COVID-19 era due to medical vulnerability following extensive
cancer treatment. As the pandemic waned, she asked to continue full-time remote work as an ADA accommodation. When that
request was denied, she asked for a narrower alternativefewer required in-person days. That was denied too. She later
resigned and sued, alleging failure to accommodate (and retaliation, though she did not contest summary judgment on the
retaliation claim).

The employer moved for summary judgment. The court granted it in part and denied it in partallowing the failure-to-accommodate
claim to survive. The decision turned on a familiar ADA battle: whether the employee could perform the job’s essential
functions with remote work (or a reduced in-person schedule), and whether the employer could genuinely show undue hardship.

Remote success became evidencenot a guarantee, but a problem for a quick denial

The court pointed to record evidence that the employee performed at high levels while teleworking for about two years.
That doesn’t automatically mean full-time telework must continue forever. But it can create a real factual dispute about
whether on-site work is truly essential or whether certain in-person elements are marginal (especially when performance
reviews, supervisor statements, and operational outcomes suggest remote work was effective).

Hybrid realities matter

The court also noted that other employees were operating under a rotational schedule that alternated between on-site and
remote work. When an organization itself treats physical presence as part-time for a role (or a similar role), it may
undermine an argument that “in-office presence is essential, full stop.” Again, not a guaranteed win for the employee
but enough to keep the dispute alive.

Undue hardship needs more than a label

One especially instructive theme: the court scrutinized whether the employer’s hardship arguments were explained with
specifics. Courts tend to look for concrete operational impacts (staffing constraints, service backlogs, required in-person
duties that cannot be reassigned, security limitations, etc.), not conclusory assertions. When the record includes
supportive supervisor feedback and measurable success during remote work, a thin hardship narrative can struggle.

Bottom line: the D.C. court didn’t proclaim a new rule that remote work is always required. It signaled something more
practical (and more dangerous for employers who love one-size-fits-all policies): remote-work accommodation cases often
can’t be decided by sweeping statements. They live and die on facts.

The D.C. Circuit’s companion lesson: Don’t “accommodate” by isolating someone

If the D.C. district court case shows why employers may need to seriously evaluate requests to work from home, a D.C. Circuit
decision shows the flip side: remote work is not automatically a “reasonable” solution if it effectively sidelines the
employee or is offered as a take-it-or-leave-it option without meaningful engagement.

In a Rehabilitation Act case (which generally uses ADA standards for federal employment), the D.C. Circuit addressed a
scenario where an employee with severe allergies sought an in-office accommodation. The employer offered only one option:
100% telework. The employee rejected that as “not a good option,” and the lower court treated his rejection as the cause
of a breakdown in the accommodation process. The D.C. Circuit reversed, emphasizing that the key question was whether the
employer’s sole offer of remote work was reasonable under the circumstancesand that the disputes were fact-intensive
enough for a jury to decide.

The court’s logic is a modern workplace reality check: some employees with disabilities may need remote work; others may
not want it or may be harmed by itprofessionally or practically. If remote work limits advancement opportunities, reduces
access to leadership roles, or segregates the employee from the workplace community, a court may be reluctant to bless it
as the only answer without a deeper look at context.

So when is remote work a reasonable accommodation?

There’s no magic phrase that guarantees a yes or justifies a no. But courts and agencies tend to revolve around a set of
recurring, concrete questions. Think of these as the “adulting checklist” for ADA telework decisions:

• What are the essential functions? Not “what has always been done,” but what truly must be done.
• Can those functions be performed remotely? Fully, partially (hybrid), or with tools and restructuring?
• What does the job description sayand does reality match it? Courts weigh employer judgment, but they also look at actual practice.
• What happened during prior remote work? Performance metrics, quality, errors, turnaround time, customer impact, and supervision needs matter.
• What are the alternatives? Private office, air filtration, schedule changes, relocation away from triggers, reassignment, or equipment changes may be effective.
• What is the operational burden? Documented staffing shortages, required in-person coverage, security constraints, and costs should be specific.

EEOC guidance has long recognized telework as a potential reasonable accommodation in appropriate circumstances. The tricky
part is the phrase “in appropriate circumstances.” Post-pandemic, many more roles have proof-of-concept data showing what
can be done remotely. That data can help employees and employers alikeif they use it honestly.

What employers should do (if they’d like fewer lawsuits and more sleep)

1) Treat the request like a process, not a referendum

When an employee requests telework for disability-related reasons, don’t start with “we don’t do that.” Start with
“tell us what limitations you’re experiencing and what tasks are impacted.” Then explore options. A flat denial without
individualized analysis is exactly the kind of fact pattern that can keep a case alive in court.

2) Ask follow-up questionsand document them

Courts notice when employers fail to ask obvious questions. If remote work is offered and the employee says it won’t work,
ask why. If the employee requests remote work, ask which essential tasks they can perform remotely, what technology they
need, and what a workable schedule looks like. Documentation is not just bureaucracyit’s evidence.

3) Audit “essential functions” before they become courtroom exhibits

Job descriptions should match reality. If an employer claims daily in-person interaction is essential, but the role has
been performed successfully with remote tools for two years, a court may view the “essential” label skeptically. Review:
customer-facing requirements, handling physical materials, on-site safety obligations, secure systems, supervision needs,
and teamwork functions.

4) Consider trial periods and hybrid options

A common mistake is treating accommodation as permanent or nothing. Trial arrangements (with clear metrics and review dates)
can reduce risk and gather real data. Hybrid schedules can also be a practical compromise when some duties are truly on-site
but not daily.

5) If you claim undue hardship, show your work

Undue hardship is not a one-word spell that makes the ADA vanish. Explain the operational impact: coverage gaps, delays,
costs, workload shifts, security limitations, and why alternatives won’t solve the issue. Vague claims often age poorly
under cross-examination.

What employees should do (to make a request stronger and more workable)

1) Connect the dots between disability-related limitations and job tasks

The most persuasive requests don’t say “I like remote work.” They say “because of X limitation, I struggle with Y job
task in the office, and remote/hybrid work would allow me to perform Z essential functions effectively.” Specificity helps.

2) Offer a plan, not just a preference

A strong proposal includes: the schedule requested (remote/hybrid), how communication will work, how deliverables will be
tracked, what equipment is needed, and how on-site tasks will be handled.

3) Be prepared to support the request with appropriate documentation

Employers may request medical information when the disability or need for accommodation isn’t obvious. A brief provider
note explaining functional limitations (not your entire medical history) can move the process forward.

What to watch next: the “evidence era” of remote-work accommodation

The pandemic created a giant, unplanned experiment in remote work. Courts are now dealing with the receipts. When the record
shows remote work was effective, employers may need stronger, more specific reasons for denying it. When the record shows
remote work prevented essential tasks or created real operational strain, employers may be on firmer ground.

The D.C. decisions underscore a bigger trend: remote work isn’t automatically required, but it also isn’t automatically
unreasonable. The ADA asks a fact-based questioncan the employee do the essential job with an effective accommodation
without undue hardship? Courts in D.C. are signaling they want real answers supported by real evidence.

Experiences related to ADA remote-work accommodations (real-world scenarios)

To make this less abstract, here are common workplace “scenes” that mirror what courts end up evaluating. These are not
one-off unicorn storiesthese patterns show up again and again when organizations try to navigate disability accommodations
in a post-pandemic workplace.

Scenario 1: The “It worked for two years… so why not now?” moment

An employee has strong performance reviews during a long period of remote work. When leadership announces a return-to-office
policy, the employee requests continued telework (or a hybrid schedule) due to a health condition that makes commuting,
crowded spaces, or environmental triggers riskier. The manager’s first instinct is to say, “Policy is policy.”

What changes outcomes is whether anyone pauses to ask: Which parts of the job truly require physical presence? Did remote
work cause measurable problems, or did it actually improve output? In organizations that respond well, HR sits down with
the employee and the manager, reviews actual job tasks, and identifies what must happen on-site (if anything). Often the
solution ends up being hybridspecific days for essential in-person tasks, with remote work for everything else. The
conversation is not “special treatment,” but “how do we keep a qualified employee productive without creating avoidable risk?”

Scenario 2: The “remote work as exile” problem

Sometimes the accommodation debate flips. An employee asks for an in-office adjustmentmaybe a private workspace away from
triggers, different seating, modified ventilation, or a schedule that avoids peak crowds. The employer, trying to be helpful
(or trying to be done with the conversation), offers only remote work.

The catch is that remote work can limit mentorship, visibility, and growthespecially in roles where leadership selection
is informal and proximity-based. In healthier workplaces, the employer treats remote work as one option among many, not a
“go be somewhere else” solution. The best practice is to discuss tradeoffs openly: “Here’s what we can do on-site, here’s
what remote work solves, and here’s how we prevent career harm if remote work is chosen.”

Scenario 3: The documentation gap that turns into a legal gap

A manager denies a request quickly and sends a short email: “Not an ADA matter,” or “Undue hardship.” Months later, a
lawyer asks, “What analysis did you do? What alternatives did you consider? What data supports hardship?”

If the organization didn’t document the interactive processquestions asked, options reviewed, why certain choices were
rejectedit’s stuck trying to recreate reasoning after the fact. That’s like writing your final exam answers after the
teacher collected the test: bold strategy, questionable results. The organizations that avoid escalation are the ones that
treat accommodation decisions like decisionscomplete with factual support, measured reasoning, and a record of good-faith
engagement.

Scenario 4: The “trial period” that saves the day

A remote-work request feels risky because the role includes some time-sensitive, in-person tasks. Instead of defaulting to
no, the employer offers a structured trial: 60 days of hybrid work, specific performance metrics, weekly check-ins, and a
plan for handling the on-site duties. At the end of the trial, the organization uses evidenceturnaround time, service
levels, collaboration outcomesto decide whether to extend, modify, or end the arrangement.

Employees tend to appreciate the seriousness of the approach (they’re being evaluated fairly, not dismissed), and employers
gain data they can defend. Even if the result is “remote work isn’t workable for this role,” the employer can show it tried
to find a solution rather than hiding behind a policy wall.

These experiences point to a single, unglamorous truth: ADA remote-work disputes are often won or lost in the middle steps.
The interactive process, the evidence, the documentation, and the willingness to consider practical alternatives are what
turn a tense request into a workable arrangementor into a lawsuit.

Conclusion

The D.C. court’s approach reflects where ADA law is heading in the remote-work era: away from slogans and toward proof.
If an employee can point to a track record of effective remote performance and the employer can’t explainspecifically
why in-person work is essential or why remote work creates undue hardship, the dispute may be headed for a jury. On the
other hand, when employers can show that critical tasks require physical presence and that alternatives were genuinely
considered, courts are more likely to view a denial as lawful.

The smart move for both sides is the same: treat remote work as a serious accommodation option, evaluate it with real facts,
and document the process like you might one day have to explain it to someone who wears a robe for a living.

SEO Tags