The number needs a meaning
A seek slider can expose a numeric value that is technically present but difficult to understand. Does 75 mean seconds, minutes or percent? W3C's media seek-slider example demonstrates meaningful time text through aria-valuetext so assistive technology can present a position in minutes and seconds. The point is understandable operation, not adding technical attributes without testing their result.
Begin with the user task: identify the current position and move to an available point in an authorised recording. Confirm that the control has a useful name, an understandable value and a known relationship to the media duration. A slider that says only slider 75 leaves the listener guessing even if it can be moved.
A hypothetical review at one minute fifteen
Suppose a recording is paused at one minute fifteen seconds. A screen reader announces seek, 75. The underlying value may be seconds, but the viewer cannot safely infer that from the number. A meaningful announcement can communicate the same position as time. The reviewer should record the actual announcement and environment rather than assuming every screen reader receives identical output.
Also verify that the announced position matches the picture and player display. A beautifully formatted time that lags behind the real position is still misleading. If the recording is live with a limited available window, the interface needs to communicate that model clearly instead of implying a fixed on-demand duration. The control's semantics must fit the media task.
Check interaction as well as announcement
Use the documented keyboard commands and observe how far each action moves the position. Confirm the start and end behaviour for the available range. Do not assume a custom slider behaves like a native control or that pointer dragging proves keyboard access. The website owner should test the supported combinations described by its accessibility requirements.
Repeated announcements can also become distracting if they include too much information on every small movement. W3C's example illustrates a deliberate approach to communicating the maximum time. Treat that example as a pattern to understand and test, not a certification that copied code will work unchanged with every framework, touch assistive technology or player.
Validate the complete seek task
After a correction, reach the slider, understand its position, move to a known interior point and resume playback. Confirm that focus remains usable and that the selected position is actually reached. A screen-reader announcement changing is only one part of the task; the media operation must also succeed.
The report should distinguish an unclear value from an inaccessible control and from a delivery failure after a valid seek. Give the exact announcement, command and observed outcome. That lets the responsible team improve the right layer while preserving the viewer's privacy and avoiding an unsupported conclusion that the account or network caused the interface problem.
Questions answered
Is a numeric slider value enough for a time control?
It may be ambiguous. Provide and test a meaningful label and time representation appropriate to the actual media task.
Does a working mouse drag prove the slider is accessible?
No. Check the required keyboard and assistive-technology interaction, understandable values and the completed seek result.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.