This distinction of type of media streams enable a number of optimization in how the streams are encoded and pre-processed - typically, it's more important to keep text legible on a video streams coming from slide, and noise-suppression is probably inadequate for music recording.
MediaStreamTrack Content Hints allows to annotate media streams (obtained from e.g. a mic, a camera or a screen capture) with the type of content, to distinguish e.g. speech from music for audio, or slides from real-world videos.
w3.org/TR/2018/WD-mst-conten…
Are there concerns for certain categories of persons with disabilities that remain unaddressed or insufficiently addressed in this document?
Are you aware of relevant research in this area we missed?
“while some #CAPTCHA solutions are better than others, there is currently no ideal solution. It is important then to exercise care that any implemented CAPTCHA technology correctly identify people with disabilities as human.”
The previous version of “Inaccessibility of CAPTCHA” had been published 13 years ago, during which a lot has changed, but #CAPTCHA are still there, and still an #accessibility challenge.
#CAPTCHA stands for "Completely Automated Public Turing Test to tell Computers and Humans Apart” - these challenges often embedded in Web sites to prevent bot-based abuses.
And that level of control will also enable to test to a higher degree of confidence the level of interoperability for #WebRTC Stats metrics.
@callstatsio (a great consumer of these metrics) have already started exploring this webrtc-stats.callstats.io/ve…
KITE can be used to test #WebRTC implementations, but also #WebRTC services and applications in controlled conditions, across OS, browsers, devices, etc.
Because of this and other #WebRTC specificities, an open source #WebRTC-specific test framework, KITE, has been developed to complement the usual Web Platform Tests github.com/webrtc/KITE
For WebRTC Stats, evaluating and verifying interoperability for its defined metrics is hard: they reflect ever changing network and system conditions, e.g. round-trip time between 2 remote browsers w3.org/TR/webrtc-stats/#dom-…
.@w3c Working Groups need to demonstrate during #CandidateRecommendation that their specifications have interoperable implementations.
Usually, for browser techs, they do this by developing and running tests in Web Platform Tests github.com/web-platform-test…
All the features that are defined in @w3c specifications to be shipped in browsers are accompanied by a test suite, to help assess how well and how broadly they are implemented by actual browsers.
#WebRTC allows real-time audio/video connections in browsers, either in #P2P mode or mediated by server components.
This first Candidate Recommendation of WebRTC Stats define a set of metrics to monitor and debug these connections #timetoimplement