(973) 886-3301
ETS.

01 — IDEA

IDEA: translation and interpretation in special education.

The Individuals with Disabilities Education Act sets the highest bar for language access — for infants and toddlers under Part C (IFSP / Early Intervention) and for school-age students under Part B (IEP). Here's what it actually requires.

In 60 seconds

The summary.

IDEA has two parts. Part C covers infants and toddlers under 3 — administered by each state (in New Jersey, through NJEIS), with native-language duties at IFSP meetings and on EI evaluations. Part B covers school-age special education — the same duties apply at IEP team meetings. The interpretation and translation standards are identical in both rooms.

Native-language consent is not a courtesy. It's the gating standard for any change in identification, evaluation, or placement.

The actual citations

What the regulations say.

34 CFR § 300.503 — Prior Written Notice

Notice to parents of a proposed change in identification, evaluation, placement, or FAPE provision must be provided in the parent's native language, unless clearly not feasible.

20 U.S.C. § 1415(d)(2) — Procedural Safeguards Notice

The annual procedural safeguards notice must be written in the parent's native language unless clearly not feasible.

34 CFR § 300.304 — Evaluation Procedures

Assessments and other evaluation materials must be administered in the child's native language or other mode of communication, unless clearly not feasible.

34 CFR § 300.322(e) — Parent Participation in IEP Meetings

The public agency must take whatever action is necessary to ensure that the parent understands the proceedings, including arranging for an interpreter for parents whose native language is not English or who are deaf.

34 CFR § 300.9 — Consent

The parent must be fully informed of all information relevant to the activity for which consent is sought, in the parent's native language or other mode of communication.

What compliance looks like

In practice, in an EI agency or school district.

  • The procedural safeguards notice is translated and provided annually in the parent's native language.
  • PWN is translated in full for any proposed change — not summarized, but translated.
  • Evaluations are administered in the child's native language by trained evaluators — not in English with a sibling translating.
  • An interpreter is at every IFSP and IEP meeting where the parent's native language is not English. Not a bilingual staff member who happened to be available. Not the older sibling.
  • Consent forms are sight-translated at the table and followed with a written translation the family keeps — a signature should never rest on a one-time read-aloud alone.
  • The IFSP or IEP itself is translated when reasonably necessary to ensure parental understanding — a duty that comes from OCR/DOJ Title VI guidance (the January 7, 2015 Dear Colleague Letter) and state practice, not from the IDEA citations above.

Common mistakes

What gets districts in trouble.

  • Using a sibling, friend, or untrained bilingual staff member as interpreter. The OCR/DOJ 2015 Dear Colleague guidance was explicit on this.
  • Running the IFSP or IEP through Google Translate. See Why Google Translate isn't enough.
  • Forgetting to translate Prior Written Notice. PWN is the formal notice that triggers the family's procedural rights — and the most commonly missed translation duty.
  • Treating "clearly not feasible" as a default rather than a narrow exception. If the family's language is reasonably available — and in NJ, most are — feasibility is not the question.

How we help

Compliance-grade interpretation and translation.

Trained interpreters at IFSP and IEP meetings; human-translated documents with attestation; FERPA-aligned data handling; same-day quotes.

Related reading

Where this connects.