.@igalia is proposing a crowd-funding program to bring their expertise in browser development across all the major engines to add well-identified features based on developer's pledges - we will be
watching the results of that experiment with high interest!
But as anyone who has tried patching browsers will know, being open source doesn't mean it's straightforward to contribute changes to browser engines, which are based on huge and complex code bases
The Web platform is arguably already one of the most open platform for developers: its technologies are developed in the open, gathering input and feedback from anyone; and all the major browser rendering engines are developed as open source projects
In parallel, one of the group's task forces, the Silver Task Force, is actively working towards WCAG 3.0, improving usability and measurability of the #a11y guidelines and providing harmonized guidance to help wider adoption:
w3.org/WAI/GL/task-forces/si…
The group's main work has been to focus on WCAG 2.2, with the addition of around 8 new success criteria which expand support for individuals with disabilities, particularly around cognitive and learning
#disabilities: w3.org/blog/2020/02/wcag-22-…
The mission of the AGWG is to develop specifications to support making implementations of web technologies accessible for people with disabilities, and to develop and maintain implementation support
materials: w3.org/WAI/GL/#a11y
Today is the day where a new @w3c process comes into action - the well-titled “Feb 1 2018 Process Document” w3.org/2018/Process-20180201…
This document sets the rules and expectations around how W3C develops its standards and interacts with its stakeholders.
The main motivations behind the adoption of this new process were to avoid out-of-date and unmaintained specifications and/or to have active versions published outside @w3c, and thus eliminate confusion among implementers and reviewers, as well as #interoperability problems.
This document guides the development of well thought-out, implementable, and relevant specs. Process 2020 represents some of the biggest changes in many years, while ensuring that @w3c values remain: wide review, implementation experience, consensus, and royalty-free licensing.
W3C Process and Patent Policy 2020 revisions have been submitted to a vote by the AC! If you work for a Member company, please strongly encourage them to vote yes!
More about this major revision:
fantasai.inkedblade.net/webl…
The group is also working on supporting docs, such as WebRTC-Stats (telemetry for #WebRTC apps), specs for audio output and media recording and the acquisition of media from #devices, screens, #DOM elements, etc. All the work happens in the open on #GitHubgithub.com/search?q=org%3Aw3…
The group is developing requirements on "WebRTC-Next Version Use Cases" that require new #APIs and protocols, thus paving the way for WebRTC's future: w3.org/TR/webrtc-nv-use-case…