Officially less than a month until #AccessU2019! Three days, seven tracks of hands-on digital #accessibility training. Optional pre-conference workshops. @IAAPOrg certification. Accessibility #hackathon of @mozilla dev tools. Don't miss it - register now! bit.ly/2GqRsyz
This comes in complement to more settled work, such as the one enabled by the Speech Synthesis and Speech Recognition browser APIs developed in the Speech API Community Group w3.org/community/speech-api/
The Voice Interaction Community Group follows up on the VoiceXML family of specifications standardized in W3C some years ago to watch and see what new standards might be relevant w3.org/community/voiceintera…
By "conversational interfaces", we mean a bunch of exploratory work happening around how to make the Web work better with voice-based interactions, including voice assistants.
Hey @w3cdevs, in your "Pipeline" diagram, you include "Conversational Interfaces" but I couldn't find any information about what that means. Is there a different page describing the goals of this segment?
w3.org/2019/04/w3c-highlight…
Check out for more #Web technologies developed in @w3c that increase the capabilities of #Webapps, how they apply more specifically to the mobile context and what are their current implementations: w3.org/Mobile/roadmap/
Finally, the @csswg has started to work on the Resize Observer specification which describes an #API for observing changes to Element’s size. This helps solve the Element Queries problem in a responsive context
w3.org/2019/04/web-roadmaps/…
Then, in order to strengthen #security, Trusted Types allows applications to lock down DOM-based XSS injection sinks (e.g. Element.innerHTML, or Location.href setters) to only accept non-spoofable, typed values in place of strings w3.org/2019/04/web-roadmaps/…
Deadline for expressions of interest is today! "Expressions of interest should briefly explain the participant's interest in the workshop in a few sentences". See more on how to participate: w3.org/WoT/ws-2019/participa…
These pages were expected to be redirected to MDN @MozDevNet but apparently only were so with uppercase HTML in the URL. Now fixed - thanks for the report!