Morning Announcement Upload and Accessibility
At a high school, a student video team produces a weekly 12-minute morning announcement. They export 1080p at 8 Mbps. The school's upload link is 5 Mbps, and the learning management system has a 500 MB per-file limit. Remote students often watch on phones with limited data. The team also posts a PDF script, but several students who are deaf or hard of hearing report that the videos lack accurate captions. The faculty advisor wants to know why uploads take so long and how to make the announcements usable for all students without buying new equipment. The team has one laptop, a camcorder, access to free editing software, 40 minutes of class time per week, and no dedicated server. The first upload attempt timed out twice.
1. Calculate the approximate file size and ideal upload time. Show your work and explain any discrepancy with the team's experience.
Read the worked answer
The video is 12 minutes, or 720 seconds. At 8 Mbps, the data volume is 8 megabits per second times 720 seconds, which equals 5,760 megabits. Divide by 8 to convert to megabytes: 5,760 / 8 = 720 MB. That already exceeds the LMS 500 MB per-file limit, so the export cannot be uploaded as-is even before considering network overhead.
The ideal upload time at 5 Mbps is 5,760 megabits divided by 5 megabits per second, or 1,152 seconds. That is 19.2 minutes. Real uploads are slower because of protocol overhead, Wi-Fi interference, competing traffic, and LMS processing. A 20 to 30 percent overhead would put the transfer near 23 to 25 minutes. The timeouts make sense: the file is over the size limit, the connection is shared, and a long single transfer is fragile. The team should not interpret the delay as a broken camcorder or a need for new equipment.
2. Recommend an export and delivery plan that keeps quality acceptable and meets the 500 MB limit without new equipment.
Read the worked answer
Produce a distribution master rather than one large file. Export the weekly announcement at 720p and about 2 to 2.5 Mbps using H.264 MP4 with AAC audio. At 2.2 Mbps for 720 seconds, the file is about 198 MB; at 2.5 Mbps it is about 225 MB. Both fit under 500 MB and should upload in roughly 5 to 6 minutes at 5 Mbps before overhead. This is adequate for spoken announcements, graphics, and a talking head.
Keep a higher-quality 1080p archive locally only if storage allows, or split it into segments if it must be posted. Use free editing software to normalize audio, keep text large, and avoid long static shots. Upload during a quiet period and confirm processing before release. If the LMS still struggles, post the video in two chapters under the limit and provide the PDF script as a backup. The key is matching bitrate to viewing conditions, not simply lowering resolution and hoping for the best.
3. Address the accessibility complaint and identify one workflow or policy change that would prevent recurrence.
Read the worked answer
The PDF script is not equivalent to captions because it is separate from the timed video and may not match what is actually said. The team should add synchronized captions and a transcript. Auto-captions can be a starting point, but they must be reviewed by a student or staff member for names, numbers, and technical terms. Captions should be high contrast and not cover important text. The team should also test the video on a phone with sound off and with captions on, because remote students may be watching in noisy or data-limited conditions.
A workable policy is a caption-review checkpoint before publishing: no announcement goes live until captions and a transcript are checked against the final audio. Assign two student roles, one for caption review and one for mobile playback testing, and keep a short checklist. This fits within the 40 minutes of weekly class time better than re-editing after complaints. The policy also gives the advisor evidence that accessibility is part of the production process, not an optional add-on.