allow user to slow the presentation rate of audio/video/animations

NEW
Unassigned

Status

()

Core
Disability Access APIs
P5
normal
19 years ago
9 months ago

People

(Reporter: xiaotong, Unassigned)

Tracking

(Blocks: 1 bug, {access})

Trunk
access
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
This is opened to address priority 1 item according to W3C accessibility
guildline. Checkpoint 4.5 - Allow user to slow the presentation rate of audio,
video, and animations.
(Reporter)

Updated

19 years ago
Blocks: 24413

Comment 1

19 years ago
same as #24413, reassign it to lake to find proper eng. to reassign. We will 
need to figure out the engineering resource for futuer commitment. UI team can't 
implement anything.
Assignee: shuang → lake

Comment 2

19 years ago
Moving all UE/UI bugs to new component: User Interface: Design Feedback
UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback

Comment 3

18 years ago
QA Assigning non-confidential New/Assigned User Interface: Design Feedback bugs 
to Matthew Thomas (mpt@mailandnews.com).

Matthew Thomas is now the QA owner for the User Interface: Design Feedback 
component. (Bugs that involve UI issues in the Netscape-branded Mozilla browser 
should continue be QA assigned to elig@netscape.com.)
QA Contact: elig → mpt

Updated

18 years ago
Keywords: access

Comment 4

18 years ago
Chaning the qa contact on these bugs to me. MPT will be moving to the 
owner of this component shortly. I would like to thank him for all his hard 
work as he moves roles in mozilla.org...Yada, Yada, Yada...
QA Contact: mpt → zach

Comment 5

18 years ago
updating to new owner. sorry for the spam.
Assignee: lake → mpt

Comment 6

17 years ago
I suppost if the presentation rate could be slowed down, it could be sped up as
well.

Comment 7

17 years ago
Taking, will work with UI team and Pavlov on this one
Assignee: mpt → aaronl

Updated

16 years ago
Component: User Interface Design → Browser-General
OS: Windows NT → All
Hardware: PC → All

Updated

16 years ago
Component: Browser-General → Accessibility APIs

Updated

14 years ago
Priority: P3 → P4

Updated

12 years ago
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED

Comment 8

12 years ago
Since this bug was written in 2000, I feel this bug probably has been resolved,
so I am closing out this bug, if you feel that this has been done in error,
please reopen the bug and explain.
Closing bugs on a whim when you're not the owner of it is NOT the right thing to do. And I'm pretty certain that this bug has not been resolved yet, so I don't know what you're doing.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → NEW

Updated

12 years ago
QA Contact: zach → accessibility-apis
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody

Comment 11

8 years ago
Agree speeding up is equally desirable.

It might require tinkering with the page's experience of time, e.g. if setTimeout(something,20) should now call back in 10ms.

Actually for audio/video triggered purely by setTimeout, it might be possible just to override the setTimeout and Date functions with a userscript.
Priority: P4 → P5
You need to log in before you can comment on or make changes to this bug.