Statute of Limitations for Employment Discrimination — ADA (federal) in Wisconsin

5 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

Employment discrimination claims can implicate multiple federal statutes, including the Americans with Disabilities Act (ADA). One practical challenge in ADA employment cases is the statute of limitations (SOL)—the deadline for filing your claim after an alleged discriminatory act.

In Wisconsin, DocketMath focuses on the federal-law SOL as applied through Wisconsin’s general limitations framework. For the ADA employment-discrimination SOL discussed here, the applicable general/default period is 6 years, as reflected in Wis. Stat. § 939.74(1). No claim-type-specific sub-rule was identified for this scenario, so the general rule is the rule you start with.

Note: This page is about timelines (SOL). It does not determine whether a specific event qualifies as an ADA-covered employment discrimination incident, nor does it address administrative prerequisites like agency charge filing.

If you’re building a case calendar, treat the SOL deadline as one of several moving parts:

the date of the alleged discriminatory act (or, in some situations, the date it was discovered)
any internal deadlines (company policies)
any federal procedural steps that may affect timing

Limitation period

Default SOL for ADA employment discrimination in Wisconsin (federal framework using Wis. general rule)

General SOL period: 6 years
General statute supplying the period: **Wis. Stat. § 939.74(1)
How it’s used here: You start with the general/default limitations period because no claim-type-specific sub-rule was found for this ADA employment-discrimination timing question.

What the “clock” usually depends on

While you should not assume every ADA case turns on the same date, SOL analysis typically anchors on one of the following:

the date the employer made the challenged decision (e.g., denial of an accommodation, termination date, failure to hire)
the date the employee experienced the adverse employment action
sometimes, a date tied to when the employee knew or should have known about the discriminatory conduct

DocketMath’s approach is designed to help you model deadlines from a chosen “start date” without guessing the outcome of legal nuances. Use the calculator with the best-supported date you have.

Common deadline planning scenarios

Below is a practical way to think about how the SOL deadline lands:

Scenario	Start date you use in DocketMath	Resulting deadline behavior
Termination decision made on a known date	Termination date	Deadline = start date + 6 years (subject to any specific procedural rules beyond this SOL)
Accommodation denial you remember from a specific email	Date of denial email	Deadline tracks that remembered denial date rather than later events
You’re unsure of the first discriminatory act date	Earliest documented act date	You minimize risk by using the earliest plausible date (so you don’t accidentally “push” the deadline)

How to interpret “6 years” in practice

A six-year period often means:

the filing deadline is not measured in months, and
the date you select as the “start” can materially change the deadline.

That’s why DocketMath’s input choices matter. If you shift the start date by even 30–90 days, your end date shifts by the same amount.

Warning: SOL is only one timing deadline. Filing or agency steps in federal ADA litigation can add additional timing constraints that are separate from the limitations period described here.

Key exceptions

Because this page uses the general/default period (and no claim-type-specific sub-rule was identified), the main “exceptions” to plan for are procedural and timing rules that may operate alongside the SOL.

Use this checklist to surface issues that can affect deadlines beyond the raw “6 years” number:

If you want to be disciplined about deadlines, treat 6 years as the baseline and then layer on:

the earliest likely act date you can document, and
any separate procedural timeline requirements that apply to the forum and method of filing.

Pitfall: Do not assume that every later employment event automatically resets the SOL. A later consequence of an earlier decision can still be governed by the earlier date in many timing frameworks.

Statute citation

The general/default limitations period used here is sourced from:

Wis. Stat. § 939.74(1) — General SOL period: 6 years
Source: https://codes.findlaw.com/wi/crimes-ch-938-to-951/wi-st-939-74/

Per the information available for this topic, no claim-type-specific sub-rule was found. Accordingly:

You apply the general 6-year period as the default for the ADA employment discrimination SOL analysis described in this page.

Use the calculator

DocketMath’s statute-of-limitations tool helps you compute a deadline from a chosen date basis—useful for case calendaring and internal review.

Primary CTA: **/tools/statute-of-limitations

Inputs to consider (and how they change outputs)

When you use the calculator, you’ll typically provide something like:

Start date (the date you believe the clock begins)
Jurisdiction (set to US-WI for Wisconsin)
Limitations period (the tool should reflect the applicable general/default period discussed on this page)

Given the default rule here, the key variable is the start date:

If you enter an earlier start date, your deadline becomes earlier.
If you enter a later start date, your deadline becomes later.

Practical workflow

Pick the earliest documented act date that supports the alleged discrimination (email date, decision date, written notice, or event date).
Enter that date into /tools/statute-of-limitations (see CTA above).
Review the output deadline against your internal milestones (drafting, evidence gathering, filing window).
If you have multiple plausible act dates, compute multiple deadlines and compare them—then decide which one best matches the factual record you can document.

If you’re tracking multiple events, run the calculator more than once—each distinct act may be associated with a different start date.