Every front-of-classroom display technology in operational use across the district. Mixed-generation reality is the norm — newer interactive flat-panel displays in renovated buildings, projectors still active in older ones, occasional smart TVs in specialty spaces. Distinct from a district-wide standard (see F2 for that). Empty selection is incomplete data, not a finding.
How uniformly the display technology from F1 is deployed. Patchwork is operational immaturity (no security/safety failure), so there's no hard finding — the discipline question is whether there's a documented refresh strategy moving toward consistency. That refresh strategy itself lives in EUC-LCY, not duplicated here.
Whether classrooms have voice-amplification systems (FrontRow, Audio Enhancement, Lightspeed, similar). Often a Title I or accessibility-driven program rather than a district-wide standard. No hard finding — "no amplification" is a defensible posture at the right scale and budget.
How teachers project content from a tablet or laptop to the front-of-room display. The maturity question is whether there's a district-supported standard (one solution, supported by IT, available everywhere) versus per-classroom solutions teachers cobbled together. No hard finding — hardwired-only is a defensible posture some districts deliberately maintain for reliability.
Scope boundary: this field captures the IT-operational coordination layer for assistive technology — district inventory, deployment process, refresh, IT-to-AT-specialist coordination. It does NOT capture IDEA / IEP compliance, FAPE provision evaluation, or special-education program management. Those are outside Kadera's scope; findings here are operational ("no IT coordination"), not legal or compliance verdicts.
The upstream district-wide process that decides what instructional software is allowed in the first place — privacy review, license tracking, sunset criteria, approved-tools inventory. Not the on-device install-blocking mechanism (that lives in EUC-MGT F6 and EUC-STU F6). Cross-ref STW / Student Data Privacy (when that domain comes online): privacy-review at the policy layer lives there; this field captures the operational inventory and IT-side workflow.
How classroom AV issues get resolved when something breaks. Dedicated AV teams are realistic only for larger districts; for mid-sized TX K-12 districts, general IT helpdesk with documented escalation and campus-tech triage is the achievable mature pattern. Ad-hoc support — issues handled by whoever's available with no documented path — is a hard finding: instructional time is lost on every issue while the district hopes the right person notices.