![]() ![]() Yes ( ) This was instructed by Greg Krause, one of the key accessibility advisors for Moodle. Maintainability of the links between the player and Moodle - how much work will we need to do every time we upgrade?.Embedding support - so users could post media content outside Moodle, if permitted.Plugins support - can we use or develop community plugins easily?.Streaming media support (including adaptive-bitrate delivery) - can player handle RTMP, Apple HLS, Adobe HDS, Microsoft HSS?.Mobile platforms support - does player also work on iOS and Android?.Audio support - can player handle HTML5 tag?.Consistency among browsers - does player look the same?.Appearance of the player - can its interface be modified, themes support, RTL?.Accessibility of the player - possibility of keyboard navigation, subtitles, support?.Usability of the player - is it easy to use it and intuitively understand how to use controls?.Another aim is to improve accessibility and usability, enhance customisation. The aim of this change is to reach a consistent look of the player among different platforms and browsers, as well as making sure that player starts using flash if html5 is not supported by browser for the given format. The purpose of this document is to choose HTML5 player with flash fallback for integration in Moodle and plan its implementation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |