How to Plan Accessible Computer-Based Testing and Assistive Technology

Test the whole assessment journey

Accessible computer-based testing and assistive technology for Darius begin with login and end with a confirmed submission. Test directions, sample items, navigation, selection, constructed responses, review screens, flags, calculator or tool panels, breaks, save and resume behavior, and exit. A screen reader announcing the welcome page does not establish access to interactive items.

Check compatibility with the secure environment

A locked browser can disable extensions, external devices, clipboard functions, network services, speech tools, or AAC integrations. Confirm which embedded and external tools are permitted for Darius under the current assessment manual and team decision. Use the approved device image and security settings. Document any conflict before the administration date.

Use technical criteria and student testing together

For public-school web and mobile content within the current rule's scope, the DOJ Title II guide incorporates WCAG 2.1 Level AA and current compliance dates. WCAG 2.1 offers technical criteria such as keyboard operation, focus, text alternatives, captions, and reflow. Student-specific assessment rules and individual access still require separate verification.

Prepare an approved accessible backup

Identify the authorized response when Darius's device, account, network, assistive technology, or platform fails. A paper form helps only if Darius can use it and the test permits it. Define who pauses the test, protects security, records the interruption, contacts support, decides resumption, and confirms that no response was lost or duplicated.

Prepare Darius's assessment-access review

Bring Darius's computer-based assessment access record, current IEP or Section 504 records, the exact assessment name and manual, representative nonsecure materials, device and account details, accessibility settings, assistive technology and AAC, staff confirmations, deadlines, incident records, and a short decision list. Ask each school, assessment, accessibility, technology, clinical, ABA, privacy, payer, and legal role to act within its authority. End with owners, dates, current score states, and a scheduled access check.

Build Darius's source-attributed record

Create a restricted computer-based assessment access record for Darius's account, device, secure application, network, keyboard, switch, screen reader, magnification, text-to-speech, caption, zoom, focus, response, timing, break, save, resume, help, security, and backup. Give every field a source, assessment and rule version, author, user role, date, status, owner, next action, due date, correction, and closure evidence. Attribute student communication, family report, teacher observation, proctor record, system log, testing-coordinator decision, vendor statement, and professional conclusion separately.

Keep accommodation authorization, setup readiness, actual delivery, score validity, educational interpretation, privacy authority, clinical recommendation, payer state, and student experience distinct.

Protect Darius's communication and wellbeing

Give Darius accessible directions, privacy, appropriate response time, and a reliable way to ask for help, report a problem, correct a message, accept, decline, pause, and request a break. Keep AAC, interpreters, captions, hearing and vision tools, mobility, food, water, bathroom access, prescribed care, and emergency help available under the applicable testing and safety rules.

Avoid treating distress, silence, compliance, speech, eye contact, or a partner's prediction as proof of consent, understanding, or skill.

Ask eight assessment-access questions for Darius

Use these questions in the computer-based assessment access record:

• Which student, assessment, purpose, construct, grade, subject, format, date, and rule version apply?
• Which disability-related access barrier and ordinary support are documented for Darius?
• Which IEP, Section 504, assessment, or other authorized role decides each support and score state?
• Which presentation, response, setting, timing, schedule, technology, AAC, and break supports are due?
• Which configuration, staff preparation, practice check, backup, and escalation must be complete before testing?
• What actually occurred during administration, including interruptions and student communication?
• Which privacy, access, disclosure, correction, test-security, and retention routes govern each record?
• Which evidence will show readiness, delivery, validity disposition, repair, and student experience?

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

A fictional assessment-access example for Darius

Darius is fictional and involved in a locked testing application used with keyboard navigation, screen magnification, text-to-speech, and an alternate response device. Reviewers freeze 46 platform, device, security, assistive-technology, response, and backup checks and complete 34 of 46, or 73.9%, by the checkpoint. A missing assessment, rule version, plan decision, support, configuration, staff, practice, administration, incident, score, privacy, communication, correction, or retest field remains in Darius's denominator with an owner, age, and next action.

The computer-based assessment access record reports evidence completion separately from legal compliance, assessment validity, student skill, educational quality, IEP or Section 504 implementation, clinical quality, learning, privacy, and satisfaction. Concurrent changes limit causal conclusions.

Use compatible denominators for Darius

For Darius's computer-based assessment access record, report approved supports with current assessment-rule mapping divided by supports due; correctly configured student-assessment episodes divided by episodes due; prepared staff assignments divided by assignments due; accommodations delivered as authorized divided by completed administrations requiring them; incidents with a documented disposition divided by incidents due for review; and corrections passing retest divided by corrections due.

Publish raw counts with percentages and report how long every open item has remained unresolved. Keep decision, mapping, readiness, delivery, incident, score validity, interpretation, repair, and student experience as separate measures.

Apply the assessment source boundaries for Darius

For Darius, 34 CFR 300.320(a)(6) addresses IEP statements for state and district-wide assessment accommodations and an alternate-assessment decision. 34 CFR 300.160 addresses inclusion, valid accommodation guidelines, alternate assessments for the stated population, parent explanation, and public reporting. 34 CFR 300.323(d) addresses staff access to and knowledge of IEP implementation responsibilities.

The IDEA AT rule and 2024 federal AT guidance address needed devices and services. The OCR FAQ supplies Section 504 and digital-access context. Verify the current state and district testing manual, test-security rule, local plan, and student-specific decision.

Apply privacy and professional boundaries for Darius

For Darius, the FERPA regulations govern covered education-record access, amendment, and disclosure questions. The Education Department's report-card and transcript FAQ provides disability and privacy context for reporting. The current DOJ guide and WCAG 2.1 apply within their stated technical scope. ASHA addresses AAC.

The BACB Ethics Code applies to covered people, and the CASP overview gives broad organizational context only. Neither source assigns a private ABA provider authority over school testing, score validity, privacy, payer, or legal decisions.

Close Darius's loop with an access check

Ask Darius and the relevant family member to review the outcome through their usual language and communication methods. Test the approved presentation, response, setting, timing, technology, AAC, break, backup, or reporting route in an authorized practice environment or representative nonsecure task. Log every mismatch, immediate safeguard, owner, due date, score or decision dependency, and later verification. Close only fields that meet the predefined condition and give any affected assessment result an accountable disposition.