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
Filter
Exclude
Time range
-
Near
Implementation experience with Semantic Sensor Network Ontology #WebStandard to trigger proposal to extend it with an ObservationCollection class and an hasUltimateFeatureOfInterest property github.com/w3c/sdw/projects/… w3.org/TR/vocab-ssn/
The Linked Building Data @w3c #CommunityGroup will tell the group about its work on Building Information Modeling (#BIM) w3.org/community/lbd/
1
1
Preparing a #roadmap for #SpatialData. Current analysis at github.com/w3c/sdw/blob/gh-p…. See anything missing? Have an idea to group features? Input welcome at github.com/w3c/sdw/issues/10…
1
1
The group will review the @opengeospatial technology trends to identify areas for coordination that would make spatial-data more Web-friendly github.com/opengeospatial/OG…
1
1
See more support materials to help you understand and implement #accessibility #a11y at the @w3c_wai redesigned Web site: w3.org/WAI/
2
The success criteria were tested in implementations across different types of #websites and Web content. Check out the #WCAG21 implementation report: w3.org/WAI/WCAG21/implementa…
1
#WCAG21 provides 17 additional success criteria to address mobile accessibility, people with low vision, people with cognitive and learning disabilities. Read more: w3.org/WAI/standards-guideli…
1
1
#WCAG21 is backward compatible with WCAG 2.0, and the three levels of success criteria (A, AA, AAA) still apply.
1
The initial work dates back from 1997 with the release of WCAG1.0 and its popular WAI quick tips to make accessible #websites. WCAG2.0 was published in December 2008 and later became an #ISO standard (#ISO40500) in 2012.
1
Congrats to editors @awkawk (@Adobe), @joshueoconnor (#InvitedExpert), @alastc (@we_are_nomensa) (who are also chairs of the @w3c_wai Accessibility Guidelines #WorkingGroup - w3.org/WAI/about/groups/agwg…), @cooper_w3c (@w3c) and all #WorkingGroup participants: kwz.me/htk
1
1
"Having a standard way to automate interaction with a browser is a big win for #WebDevelopers in helping ensure their #WebApplications work in the best way they should for their users", concludes Michael[tm] Smith from @w3c. Read his full post at w3.org/blog/2018/06/webdrive…
#WebDriver is widely supported, with implementations shipping for all four major browser engines: github.com/w3c/webdriver/blo…
1
1
It defines the #WebDriver #API, a platform and language-neutral interface that enables the use of different programs or scripts to introspect into, and control the behaviour of, a #WebBrowser. Supported programming languages are: #Java #PHP #Python #Perl #Ruby etc.
1
#WebDriver is a cross-browser set of protocol and #APIs that allows #Web authors and #developers to write and execute tests against different browsers.
1
Congrats to editors @AutomatedTester and @shs96c for advancing #WebDriver to #WebStandard status! w3.org/TR/webdriver/ #timetoadopt
This tweet is unavailable
1
1
1
5
It notably led to the creation of a new Data Privacy Vocabularies and Controls @w3c #CommunityGroup w3.org/community/dpvcg/. Join and contribute!
1