Get involved in @w3c and give input on all of our specs. See also youtube.com/@W3COfficial and @w3cdevs@w3c.social. By @dontcallmeDOM and @marieforgue
Joined October 2014
- Tweets 4,375
- Following 608
- Followers 11,339
- Likes 2,472
Fear not - this is a minor update to the existing Recommendation:
“Allow the Structural pseudo-classes to match the root element ”
w3.org/TR/2018/CR-selectors-… - look, you've just gained a new topic of conversation for your next meetup!
1
“What's happening? Is all my extended knowledge about #CSS selectors good for the bin? How will I chit-chat at my next meetup? 😱" I hear you worry
1
“But Selectors Level 3 was published as a Recommendation a bazillion years ago? 😲” I hear you ask w3.org/TR/2011/REC-css3-sele…
This tweet is unavailable
1
To learn the basics about why #accessibility matters and how #WebStandard can help, see the video released last month featuring our very own @sabouzah
This tweet is unavailable
4
2
If you have feedback, find bugs or issues with the current document, please file them at github.com/w3c/wcag21/issues
1
And the details about the expectations around implementation feedback and schedule are given by @awkawk in his blog post published today w3.org/blog/2018/01/wcag21-c…
1
There is more background and context on this document in @joshueoconnor blog post from a year ago w3.org/blog/2017/02/wcag21-f…
1
WCAG 2.1 primary focus is #accessibility requirements for people with low vision and cognitive and learning disabilities, and #mobile accessibility w3.org/WAI/WCAG20/wcag2faq#v…
1
1
#WCAG 2.1 proposes an update to the Web Content Accessibility Guidelines w3.org/TR/WCAG21/ - having reached Candidate Recommendation status, the Accessibility Guidelines Working Group is seeking implementation feedback from #webdeveloper #timetoimplement @w3c_wai
This tweet is unavailable
1
2
There are already a number of new features that have been requested for that API github.com/w3c/IndexedDB/iss… - is yours already there?
Browser support is already quite good caniuse.com/#feat=indexeddb2 - main exception is @MicrosoftEdge wpdev.uservoice.com/forums/2…
1
IndexedDB 2 provides an upgrade to everyone's favorite client-side database #IndexedDB w3.org/TR/2018/REC-IndexedDB…
@bevistseng provided a very nice overview of the new features in a @mozhacks article some months ago hacks.mozilla.org/2016/10/wh…
This tweet is unavailable
3
2
And being based on Web technologies doesn't imply lower quality or performance - see
When people ask if 3D or #VR on the web can really be "pretty" I'll also start to share @sketchfab #glTF page sketchfab.com/features/gltf in addition to @PlayCanvas #WebGL2 "After the flood" demo playcanv.as/e/p/44MRmJRU/ and @thespite cru·ci·form clicktorelease.com/code/cruc…
1
2
But since that API is not implemented yet, the best way to get started with VR on the Web is the existing WebVR 1.1 API webvr.info/
1
To get a grasp of what the API looks like, the explainer is the best place to start github.com/immersive-web/web…
1
The main API , #WebXR Device API is developed at github.com/immersive-web/web… - it enables browsers to interact with VR/AR/MR headsets and their many capabilities.
Compared to the existing WebVR 1.1 API, it provides a much smoother integration with the browser render loop.
1
3
If you want to get involved in the work around #WebXR, the relevant Github repos are at github.com/immersive-web , the mailing list is lists.w3.org/Archives/Public… and they are now organizing regular teleconferences open to all the CG participants - join at w3.org/community/webvr/
This tweet is unavailable
1
2
This #W3Cworkshop comes in the context of the new European directive on privacy rights, #GDPR, and will look at how to manage #LinkedData to preserve privacy properties through their lifecycle
1
Want to explore interoperability in #privacy using #LinkedData? You have until 26 February to submit your interest to the @specialprivacy #W3Cworkshop kwz.me/hbC #dataprivacy18
1
4
1
6