How to Request an IEP or Section 504 Review for Digital Learning Access

Describe the task before proposing a tool

For Zuri, the digital learning access review begins with the science task: opening the simulation, finding instructions, entering an answer, hearing feedback, and submitting work. Record the device, browser, version, accessibility settings, assistive technology, prompt, expected action, observed barrier, and effect. A broad statement such as “the website is hard” gives the team too little to test.

Route the request to the right team

Ask whether the concern belongs in an IEP Team review, a Section 504 process, an accessibility repair, an assistive-technology discussion, or several coordinated tracks. The Education Department's current FAQ says disability law applies to online and other digital content and technology. The qualified school team makes the student-specific educational decision.

Write implementation that staff can follow

If the responsible team adopts a support, name the task, tool or method, settings, locations, responsible staff, training, start date, backup, and evidence of use. Under 34 CFR 300.323(d), staff responsible for an IEP must have access to it and know their implementation responsibilities and the supports required for the child.

Retest the real assignment

A demonstration on a blank practice page may miss the barrier in Zuri's actual class. Reopen the assigned simulation with the same account, assistive technology, time limit, and submission path. Record whether Zuri can perceive the content, operate controls, understand instructions, communicate, complete the task, and obtain help. Return any failed step to its owner.

Prepare Zuri's digital-access review

Bring Zuri's digital-access plan-review record, the exact device and account, current accessibility settings, assistive technology and AAC, representative school content, relevant IEP or Section 504 records, privacy notices, support tickets, deadlines, and a short decision list. Ask each school, accessibility, technology, vendor, clinical, ABA, privacy, payer, and legal role to act within its authority. End with owners, dates, accessible interim routes, and a scheduled real-task check.

Build Zuri's source-attributed record

Create a restricted digital-access plan-review record for Zuri's request, platform, task, barrier, functional impact, immediate route, evaluation, assistive technology, accommodation, service, training, implementation, and retest. Give every field a source, system or content version, device, user role, author, time, effective period, status, owner, next action, due date, correction, and closure evidence. Attribute student communication, family report, teacher observation, accessibility test, system log, vendor statement, and professional conclusion separately.

Keep educational decisions, clinical recommendations, accessibility findings, technology administration, privacy authority, payer states, and student experience distinct.

Protect Zuri's communication and choice

Give Zuri accessible instructions, privacy, enough response time, and a reliable way to ask questions, disagree, correct a message, accept, decline, pause, and request help. Keep AAC, interpreters, captions, hearing and vision tools, mobility, food, water, bathroom access, rest, prescribed care, and emergency help available.

Avoid requiring speech, eye contact, a caregiver's device, or public disclosure before honoring a recognizable message. A partner may support access while leaving Zuri's authorship intact.

Ask eight digital-access questions for Zuri

Use these questions in the digital-access plan-review record:

• Which student, course, task, content, platform, account role, device, setting, and deadline apply?
• Which disability-related barrier and functional effect did Zuri experience?
• Which accessibility setting, assistive technology, AAC, caption, alternative format, or support is due?
• Which school, vendor, accessibility, clinical, privacy, and family role owns each decision or action?
• Which immediate route preserves instruction, communication, safety, privacy, and the deadline?
• Which data does the tool collect, use, disclose, retain, correct, and delete under which route?
• Which evidence will show readiness, successful use, failure, educational effect, repair, and student experience?
• How will the actual journey be retested after a change?

Classify fields as complete, failed, pending, declined, disputed, or inapplicable with a reason.

A fictional digital-access example for Zuri

In this fictional example, Zuri takes a seventh-grade science course that uses a learning platform, interactive simulations, videos, and timed quizzes. Reviewers freeze 42 student-specific barrier, decision, support, implementation, and retest fields and complete 31 of 42 by the checkpoint. A missing platform, task, content version, account, device, setting, assistive-technology, AAC, privacy, support, outage, deadline, repair, or retest field remains in Zuri's denominator with an owner, age, and next action.

The digital-access plan-review record reports evidence completion separately from legal compliance, technical conformance, educational access, IEP or Section 504 implementation, clinical quality, learning, participation, privacy, and satisfaction. Concurrent changes limit causal conclusions.

Use compatible denominators for Zuri

For Zuri's digital-access plan-review record, report accessible tasks completed divided by tasks due; working access configurations divided by configurations due; files validated divided by files due; captioned media delivered on time divided by media due; usable AAC pathways divided by pathways due; privacy decisions documented divided by tools reviewed; support responses completed by target divided by requests due; and corrections validated divided by corrections due.

Publish raw counts with percentages and age every open item. Keep procurement review, technical conformance, student readiness, successful task use, educational effect, family burden, repair, and satisfaction as separate measures.

Apply the current digital-access source boundaries for Zuri

For Zuri, the Education Department's technology-accessibility page and current disability FAQ address equal access to digital educational opportunities. The 2024 IDEA assistive-technology guidance explains that IEP Teams consider AT whenever an IEP is developed, reviewed, or revised, and that services, training, coordination, and documented implementation can matter along with a device. 34 CFR 300.105 and 300.320(a)(4) govern their stated IDEA questions.

The current DOJ guide supplies the Title II technical rule and extended dates. WCAG 2.1 supplies the incorporated technical criteria. Verify the school type, population method, current federal rule, Section 504, IDEA, state, district, contract, and student-specific decision for Zuri.

Apply privacy and professional boundaries for Zuri

The Education Department's online-services guidance and classroom-tool FAQ address FERPA-related school and vendor questions. The joint FERPA-HIPAA guidance explains why the record and holder matter. ASHA addresses AAC access. The BACB Ethics Code applies to its covered people, and the CASP overview gives broad organizational context for page 1.

These sources do not assign school, accessibility, vendor, privacy, payer, legal, or emergency authority to a private ABA provider. Verify each role and route before sharing data or changing a plan.

Close Zuri's loop with a real-task check

Ask Zuri and the relevant family member to review the accessible outcome through their usual language and communication methods. Test the repaired login, platform journey, file, media item, AAC pathway, privacy setting, backup, or handoff suited to the question. Log every mismatch, interim route, owner, due date, dependent school task, and later verification. Close only fields that meet the predefined access condition and give any missed educational opportunity an accountable disposition.