346
edits
Accessibility/Captioning Work Plan: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
# Determine which subset of that format is the most crucial. This can save the Mozilla developers a good deal of work, because captioning formats are complex. Some of the complexity is necessary and some is not necessary for Mozilla suppoort | # Determine which subset of that format is the most crucial. This can save the Mozilla developers a good deal of work, because captioning formats are complex. Some of the complexity is necessary and some is not necessary for Mozilla suppoort | ||
# Work with HTML 5, web browser development and captioning communities to ensure that the solution will be accepted. We don't want different solutions in each browser. That would either mean one browser would need to redo their work, or that caption developers would have to deal with incompatible solutions in different browsers. | # Work with HTML 5, web browser development and captioning communities to ensure that the solution will be accepted. We don't want different solutions in each browser. That would either mean one browser would need to redo their work, or that caption developers would have to deal with incompatible solutions in different browsers. | ||
# Ensure solution will support the following features: social caption creation, multiple languages, semantics and style, etc. | |||
# Ensure captioning solution is compatible with current authoring and if possible, video conversion tools, so that current and future content can easily use the solution | # Ensure captioning solution is compatible with current authoring and if possible, video conversion tools, so that current and future content can easily use the solution | ||
# Build test cases -- we need x testcases with y features | # Build test cases -- we need x testcases with y features | ||