w3.org_blog.rss.xml - sfeed_tests - sfeed tests and RSS and Atom files
(HTM) git clone git://git.codemadness.org/sfeed_tests
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) README
(DIR) LICENSE
---
w3.org_blog.rss.xml (131505B)
---
1 <?xml version="1.0" encoding="UTF-8"?>
2 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
3 <channel>
4 <language>en</language>
5 <title>W3C - Blog</title>
6 <description>The W3C blog is for discussions within W3C and the Web community at large.</description>
7 <pubDate>Tue, 15 Aug 2023 16:12:20 +0000</pubDate>
8 <generator>Laminas_Feed_Writer 2 (https://getlaminas.org)</generator>
9 <link>https://www.w3.org/blog/</link>
10 <atom:link rel="self" type="application/rss+xml" href="https://www.w3.org/blog/feed/"/>
11 <item>
12 <title>Web Environment Integrity has no standing at W3C; understanding new W3C work</title>
13 <description><![CDATA[This article addresses that Web Environment Integrity is not being worked on at W3C, and proceeds to explaining how work is brought to W3C and the processes that foster the development of Web standards and guidelines that ensure the long-term growth of the Web.]]></description>
14 <pubDate>Fri, 11 Aug 2023 19:54:00 +0000</pubDate>
15 <link>https://www.w3.org/blog/2023/web-environment-integrity-has-no-standing-at-w3c/</link>
16 <guid>https://www.w3.org/blog/2023/web-environment-integrity-has-no-standing-at-w3c/</guid>
17 <author>Philippe Le Hégaret</author>
18 <comments>https://www.w3.org/blog/2023/web-environment-integrity-has-no-standing-at-w3c/#comments</comments>
19 <category><![CDATA[corporate]]></category>
20 <category><![CDATA[blogs]]></category>
21 <dc:creator>Philippe Le Hégaret</dc:creator>
22 <content:encoded><![CDATA[ <div class="component component--text">
23 <p>For a few weeks now we have been hearing concern in the Web community in regard to <a href="https://github.com/RupertBenWiser/Web-Environment-Integrity">Web Environment Integrity</a>, and are asked more and more about it. Our silence is due to the fact that the Web Environment Integrity API is not being worked on in W3C, nor has there been any submission to W3C for <a href="/groups/other/tag/">W3C Technical Architecture Group</a> (TAG) review.</p><p>In the rest of this article, I want to take the opportunity to explain generally <a href="/standards/about/#funnel">how new work is brought</a> to the World Wide Web Consortium, and how several W3C work groups coordinate what we call "<a href="/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a>". This review and other safeguards we have in place, transcends a particular technology by focusing on aspects that impact people and the Web: Web accessibility, architecture, internationalization, privacy, and security.</p><h2>Bringing new work to W3C</h2><p>Candidate W3C work arises from <a href="/Consortium/Process/#GAEvents">W3C Workshops</a> or <a href="/Submission/">Member Submissions</a>, or tracking the activity in public <a href="/community/groups/">W3C Community Groups</a>. New work starts at W3C by <a href="/Consortium/Process/#WGCharterDevelopment">initiating new working groups</a> based on interest from W3C Members and Team, or landing in <a href="/groups/">existing working groups</a> (in which case, the groups' charters are updated.) New charters and revised charters both require Member consensus.</p><h2>Passing W3C "horizontal review"</h2><p>The W3C Process Document enshrines <a href="/Consortium/Process/#doc-reviews">"horizontal review" as a requirement</a>. For a new working group, the review is done internally before any proposed charter is brought to W3C Members for approval. For new technology or specifications, the review must be done as part of publication on the W3C Recommendation track (i.e., the progression stages from an idea to a Web Standard.)</p>
24 </div>
25 <figure class="component component--quote">
26 <blockquote>
27 <p>
28 "The objective is to ensure that the entire set of stakeholders of the Web community, including the general public, have had adequate notice of the progress of the Working Group and were able to actually perform reviews of and provide comments on the specification. A second objective is to encourage groups to request reviews early enough that comments and suggested changes can still be reasonably incorporated in response to the review."
29 </p>
30 </blockquote>
31 <figcaption>Excerpt from the requirement for wide review (Section 6.2.2.1, W3C Process)</figcaption>
32 </figure>
33 <div class="component component--text">
34 <h2>Self-review for Web platform designers</h2><p>As a starting point and as part of web developer advocacy, most W3C horizontal review groups have created guides and self-review documents so that key aspects can be resolved autonomously:</p><ul><li>The Technical Architecture Group exists to help ensure that the Web makes sense as a platform, and that the design is coherent. Among the criteria of any<a href="https://tag.w3.org/workmode/"> TAG review</a> is evaluation against the <a href="/TR/design-principles/">Design Principles</a> (which includes the priority of constituencies), the <a href="/TR/privacy-principles/">Privacy Principles</a>, and the <a href="/TR/ethical-web-principles/">Ethical Web Principles</a>.</li><li>The Framework for Accessibility in the Specification of Technologies (<a href="https://w3c.github.io/apa/fast/checklist.html">FAST</a>) explains by types of features how to ensure that a technology is accessible to users with disabilities.</li><li>A <a href="https://w3c.github.io/i18n-drafts/techniques/shortchecklist">short i18n review</a> flags areas to pay particular attention to in the Internationalization (i18n) quality approach taken early to avoid costly and sometimes prohibitive obstacles when rolling out products or a technology to meet the needs of people in different cultures, or who use different languages or writing systems.</li><li>The <a href="/TR/security-privacy-questionnaire/">Security and Privacy self-review questionnaire</a> helps specification authors as they think through the security and privacy implications of their work designing new features for the Web platform.</li></ul><h2>From an idea to a Web standard</h2><p>If there is interest in describing more the various steps new work takes at W3C, we can start a series of articles. In the meantime, I thought I would leave you with a final note on how any specification becomes a "standard" in W3C: it needs to show multiple, interoperable <a href="/Consortium/Process/#implementation-experience">implementations</a>.</p><p>Let us know if you have questions or what you would like to hear more about.</p>
35 </div>
36 ]]></content:encoded>
37 <slash:comments>0</slash:comments>
38 </item>
39 <item>
40 <title>Securing the Web forward: Addressing developer concerns in web security</title>
41 <description><![CDATA[A recent survey affirms the need to drive developer awareness and adoption of Web security standards & practices.]]></description>
42 <pubDate>Mon, 24 Jul 2023 10:18:00 +0000</pubDate>
43 <link>https://www.w3.org/blog/2023/securing-the-web-forward-addressing-developer-concerns-in-web-security/</link>
44 <guid>https://www.w3.org/blog/2023/securing-the-web-forward-addressing-developer-concerns-in-web-security/</guid>
45 <author>Daniel Appelquist</author>
46 <comments>https://www.w3.org/blog/2023/securing-the-web-forward-addressing-developer-concerns-in-web-security/#comments</comments>
47 <category><![CDATA[privacy-and-security]]></category>
48 <category><![CDATA[blogs]]></category>
49 <dc:creator>Daniel Appelquist</dc:creator>
50 <content:encoded><![CDATA[ <div class="component component--text">
51 <p><a href="https://www.w3.org/2023/03/secure-the-web-forward/"><img src="https://www.w3.org/2023/03/secure-the-web-forward/banner.png" alt="black and white photo of padlocks on a metallic fence"></a></p><p>In the ever-evolving landscape of web development, security remains a key concern for developers. A <a href="https://github.com/web-platform-dx/developer-research/blob/main/mdn-short-surveys/2023-05-15-security-dx/interpretation.md">recent survey</a> gathered responses from 297 developers visiting MDN, asking them to rate the challenge they face with various security aspects in their development workflows. These responses offer a clear indication of the complexities and challenges encountered in daily development tasks.</p><p>60% of developers find the addressed security aspects 'Somewhat challenging' or 'Very challenging'. It's evident from this that we have a problem. There is a substantial need for enhanced education, tools, and best practices to assist developers with security issues across the board.</p><p>Delving deeper into the individual security aspects:</p><ul><li>Detecting security vulnerabilities was highlighted as the most challenging aspect, with 71% of developers marking it as 'Somewhat challenging' or 'Very challenging'. An area with clear scope for improvement, it further emphasizes the need for better tools and education.</li><li>Understanding security threats followed closely, gathering 69% of 'Somewhat challenging' or 'Very challenging' responses. As threats evolve continuously, this response underscores the crucial requirement for up-to-date education and efficient tools.</li><li>The intricacy of understanding the web browser's security model came third, seen as challenging by 66% of developers. The ongoing evolution of web technologies may contribute to the difficulty in understanding the security model.</li><li>Safely integrating third-party services received mixed responses. While 55% found it challenging, 27% felt neutral about it. This perhaps reflects the trust developers place in identified companies offering these services.</li><li>Keeping frameworks and libraries up-to-date was another mixed bag, with 54% finding it challenging but 20% considering it easy. This suggests that while the actual updating of dependencies remains challenging, the tools alerting developers about new dependency releases have become mainstream.</li><li>HTTPS Configuration was rated the least challenging aspect, with 45% finding it challenging and 31% considering it easy. It indicates that either server configuration is seen as a well-known task, or hosting services may be assisting developers with these issues.</li></ul><p>The survey also highlighted the challenges of staying updated with new security threats, integrating third-party code securely, the lack of cybersecurity content in formal education, and other issues such as regulatory compliance.</p><p>One thing is clear: if we want to address these challenges we need to do so holistically. <strong>That means we need to get people talking to each other across silos</strong>.</p><p>To further address these concerns and foster an open dialogue, we're inviting you to participate in the W3C, OpenSSF, OpenJSF, and OWASP workshop: “<a href="https://www.w3.org/2023/03/secure-the-web-forward/">Secure the Web Forward</a>.” If you would like to participate in this groundbreaking workshop you have one week left to submit position statements. It’s clear that the ecosystem needs to come together to address these challenges. We hope that this workshop can be a step along the road to building a secure future for web development.</p>
52 </div>
53 ]]></content:encoded>
54 <slash:comments>0</slash:comments>
55 </item>
56 <item>
57 <title>New W3C website deployed</title>
58 <description><![CDATA[The redesign provides a more modern, inclusive, usable website.]]></description>
59 <pubDate>Tue, 20 Jun 2023 12:07:00 +0000</pubDate>
60 <link>https://www.w3.org/blog/2023/new-w3c-website-deployed/</link>
61 <guid>https://www.w3.org/blog/2023/new-w3c-website-deployed/</guid>
62 <author>Coralie Mercier</author>
63 <comments>https://www.w3.org/blog/2023/new-w3c-website-deployed/#comments</comments>
64 <category><![CDATA[corporate]]></category>
65 <category><![CDATA[blogs]]></category>
66 <dc:creator>Coralie Mercier</dc:creator>
67 <content:encoded><![CDATA[ <div class="component component--text">
68 <figure class="image"><img src="https://www.w3.org/cms-uploads/redesign-2023.png"></figure><p>The redesigned <a href="https://www.w3.org/">W3C website</a> is now live! </p><p>There is more to do, but this deployment concludes the four months the site was available in <a href="https://www.w3.org/blog/2023/02/w3c-launches-beta-of-its-new-website/">Beta</a>, which followed a year of internal preparation, and two years of work with UK-based digital agency Studio 24, to whom we <a href="https://www.w3.org/press-releases/2020/studio-24-w3c-website-redesign/">awarded</a> the website redesign project in early 2020. For me personally, this is a milestone of the “action item” I took over 4 years ago to communicate more effectively what our organization does with a more modern, inclusive, usable website. </p><p>Redesigning a website and content that has been building up since 1994 is a massive undertaking, so we chose to break it down into phases and focus first on a subset of the public-facing pages most useful to key audiences: </p><ul><li>W3C homepage </li><li>/Standards, /Participate, /Membership, /Consortium </li><li>W3C Blog & Blog article </li><li>Business ecosystem landing pages </li><li>Work Groups 'profile' pages (new) </li><li>/TR homepage </li><li>Account pages </li><li>Others as determined by Information Architecture </li></ul><p>This as well as goals and other related elements are documented in a <a href="https://www.w3.org/Press/slides/202002-website-redesign/#rfp">slide deck</a> I created at the start of the project. </p><p>On the surface, the new site implements current web best practices and technologies, donned a cleaner and elegant visual design, and provides information (in many cases rewritten and consolidated) in a more user-friendly fashion. </p><p>Under the hood, everything changed. From the complete information architecture to the CMS and the tools that make all of our sub-sites work together. </p><p>Feedback on the site itself and the content is expected as issues on our <a href="https://github.com/w3c/w3c-website">GitHub repository</a>. </p><p>We will gradually work to address existing non-blocking issues (in association with Studio 24 who now help us with support and maintenance), and to include the rest of the site as part of this design, starting with deploying the Chinese and Japanese localized sites for which we have seeded a lot of the work already. </p><p>Finally, I want to acknowledge the considerable help I got along this captivating project from the entire <a href="https://www.w3.org/staff/systeam/">W3C Systems Team</a>, in particular this project could not have happened without the contributions from Vivien Lacourba, Jean-Guilhem Rouel, Gerald Oskoboiny, Laurent Carcone, Denis Ah-Kang. Thank you. </p><h3>More information on the W3C Website redesign: </h3><p>The goals of the redesign were to achieve a cleaner and modern look and greater usability, better accessibility, as well as ultimately simplifying how the site is managed. We also want to offer integrated Japanese and Chinese versions. </p><p>Studio 24 documented the collaboration and process on the redesign of our website in a “work in the open” site, notably today's <a href="https://w3c.studio24.net/updates/live-website-launch">update</a>. You can read more about today’s milestone from Studio 24’s <a href="https://www.studio24.net/blog/w3c-launch-their-new-website/">blog post</a>. </p>
69 </div>
70 ]]></content:encoded>
71 <slash:comments>5</slash:comments>
72 </item>
73 <item>
74 <title>Web technologies for applications: workshop and coding contest in Paris, 13 June 2023</title>
75 <description><![CDATA[Web technologies for applications: workshop and coding contest in Paris, 13 June 2023]]></description>
76 <pubDate>Mon, 05 Jun 2023 16:07:00 +0000</pubDate>
77 <link>https://www.w3.org/blog/2023/web-technologies-for-applications-workshop-and-coding-contest-in-paris-13-june-2023/</link>
78 <guid>https://www.w3.org/blog/2023/web-technologies-for-applications-workshop-and-coding-contest-in-paris-13-june-2023/</guid>
79 <author>Marie-Claire Forgue</author>
80 <comments>https://www.w3.org/blog/2023/web-technologies-for-applications-workshop-and-coding-contest-in-paris-13-june-2023/#comments</comments>
81 <category><![CDATA[developers]]></category>
82 <category><![CDATA[blogs]]></category>
83 <dc:creator>Marie-Claire Forgue</dc:creator>
84 <content:encoded><![CDATA[ <div class="component component--text">
85 <p>The convergence of web innovation, light app technologies, and mobile devices is transforming the digital landscape. The “Web Technologies for Applications” workshop and coding contest, organized the <a href="https://systematic-paris-region.org/?lang=en" rel="noopener" target="_blank">Systematic Paris-Region cluster</a> and the Open-Source Software for Information Systems (<a href="https://www.ow2.org/">OW2</a>) in coordination with W3C, brings together industry professionals, web developers, researchers, programmers, and technology enthusiasts to explore the latest trends and advancements in web applications in a mobile context.</p><p><strong>Take part in this exciting day and </strong><a href="https://systematic-paris-region.org/evenement/web-technologies-for-applications-workshop-and-coding-contest/"><strong>register free of charge </strong></a><strong>for June 13, 2023, in Paris <img style="vertical-align:sub;width:15px;" src="https://s.w.org/images/core/emoji/14.0.0/svg/1f1eb-1f1f7.svg" alt="🇫🇷"> !</strong></p><p><a href="https://systematic-paris-region.org/evenement/web-technologies-for-applications-workshop-and-coding-contest/"><img class="aligncenter size-medium" src="https://systematic-paris-region.org/wp-content/uploads/2023/06/1685707300_image_event_c.png" alt="W3C, OW2 and Systematic organize a workshop and coding contest in Paris, on 13 June 2023. The event is entitled: " decoding="async"></a></p><p>Starting from the mid-2000s, web access through mobile devices experienced a remarkable surge, driven by the popularity of smartphones and the availability of affordable, high-speed mobile data networks. At that time, W3C launched the <a href="https://www.w3.org/2005/05/mwi-pressrelease.html.en" rel="noopener" target="_blank">Mobile Web Initiative</a> to make browsing the Web from mobile devices a reality. In parallel, mobile native apps were adapting to user expectations, including seamless connectivity, smooth interactivity, etc. To orient developers and content providers who wanted to create the same or even a better experience on mobile, W3C maintained and published <a href="https://www.w3.org/Mobile/roadmap/" rel="noopener" target="_blank">roadmaps of Web Applications for Mobile</a> collecting information about standardization and implementation status of features described in W3C specifications and others.</p><p>As society embraces an “always on, always connected” real-time paradigm, coupled with the emergence of smart homes, smart cities, AR/VR, AI bots, etc., new challenges have arisen. These challenges prompt us to evolve existing global standards and forge new ones, while addressing concerns such as data privacy, cyber security, online harassment, and more. Simultaneously, we must strive to maintain an accessible and user-friendly development process.</p><p>At the event (9h00 – 14h00), renowned experts will deliver engaging sessions:</p><ul><li>Dominique Hazaël-Massieux (Head of DevRel, W3C) will review and compare how Web technologies are used across ecosystems, and highlight opportunities for greater convergence among them.</li><li>Martin Alvarez-Espinar (Head of Web Standards, Huawei) will present the background and current status of the W3C MiniApp specifications, developed collaboratively by industry leaders and stakeholders within the <a href="https://www.w3.org/2021/miniapps/" rel="noopener" target="_blank">W3C MiniApps Working Group</a>.</li><li>Alex Bourlier (Co-founder, Startin’blox) will explore how Data Interoperability and Data Sovereignty can be enhanced among the MiniApps ecosystem by making use of initiatives like the Solid Project, International Data Spaces (IDS) or Gaia-X.</li><li>Simon Phipps (Standards & Policy Director, OSI) will suggest some definitions and principles over what open source and open standards have in common, and what distinguishes them.</li><li>Fabien Benetou (Prototypist, consultant in WebXR for the European Parliament innovation team) will demonstrate how an immersive experience can take place directly in the browser we are already so familiar with.</li><li>Romain Vailleux (Partnership & Ecosystem Manager, Apizee) will explore the possibilities offered by WebRTC, with a particular focus on use cases and applications.</li></ul><p>With an informative workshop, a challenging coding contest, and opportunities for networking and recognition, this event is a must-attend for those looking to expand their knowledge, showcase their skills, and take their web development career to new heights.</p><p><a href="https://systematic-paris-region.org/evenement/web-technologies-for-applications-workshop-and-coding-contest/" rel="noopener" target="_blank">Join us</a> to shape the future of web and mobile experiences, ensuring inclusivity, security, and accessibility for all. The event is located at 16-18 Rue Vulpian, 75013 Paris.</p><p>The afternoon will be devoted to a code contest for students, who will have to develop and test a lightweight application (PWA, Quick App) to promote a city’s resources. The 3 best projects will win cool prizes! <a href="https://my.weezevent.com/coding-contest-1306?_gl=1*nj3hlw*_ga*NDI0ODY4MzYzLjE2ODMyMDI4NjQ.*_ga_39H9VBFX7G*MTY4MzIwMjg2My4xLjEuMTY4MzIwMjkxNy4wLjAuMA..">Register here</a>.</p>
86 </div>
87 ]]></content:encoded>
88 <slash:comments>0</slash:comments>
89 </item>
90 <item>
91 <title>W3C WAI Updates for GAAD 2023</title>
92 <description><![CDATA[Relevant resources from the W3C Web Accessibility Initiative (WAI) for Global Accessibility Awareness Day (GAAD).]]></description>
93 <pubDate>Wed, 17 May 2023 17:32:00 +0000</pubDate>
94 <link>https://www.w3.org/blog/2023/w3c-wai-updates-for-gaad-2023/</link>
95 <guid>https://www.w3.org/blog/2023/w3c-wai-updates-for-gaad-2023/</guid>
96 <author>Shawn Lawton Henry</author>
97 <comments>https://www.w3.org/blog/2023/w3c-wai-updates-for-gaad-2023/#comments</comments>
98 <category><![CDATA[accessibility]]></category>
99 <category><![CDATA[blogs]]></category>
100 <dc:creator>Shawn Lawton Henry</dc:creator>
101 <content:encoded><![CDATA[ <div class="component component--text">
102 <p>In your materials for Global Accessibility Awareness Day (GAAD), we encourage you to include relevant resources from the W3C Web Accessibility Initiative (WAI).</p>
103
104 <h2>WAI Resources for GAAD</h2>
105
106 <p>For a list of free online resources to support digital accessibility, see <a href="https://www.w3.org/WAI/resources/">WAI Resources</a>.</p>
107
108 <p>Resources particularly relevant for GAAD include:</p>
109
110 <ul>
111 <li><a href="https://www.w3.org/WAI/teach-advocate/accessible-presentations/">Making Events Accessible – Checklist for meetings, conferences, training, and presentations that are remote/virtual, in-person, or hybrid</a></li>
112 <li><a href="https://www.w3.org/WAI/fundamentals/accessibility-intro/">Introduction to Web Accessibility</a></li>
113 <li><a href="https://www.w3.org/WAI/courses/">Digital Accessibility Courses</a></li>
114 </ul>
115
116 <h2>WAI Updates</h2>
117
118 <p>For monthly updates on current WAI work, see <a href="https://www.w3.org/WAI/update/">What We’re Working On – Accessibility Activities and Publications</a>.</p>
119
120 <p>For those interested in Web Content Accessibility Guidelines (WCAG):</p>
121
122 <ul>
123 <li>An updated draft of WCAG 2.2 was published on 17 May 2023. See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">WCAG 2 Overview</a> and <a href="https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/">What’s New in WCAG 2.2 Draft</a>.</li>
124 <li>WCAG 3.0 is exploring a different approach. It is years away from being completed. See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3 Introduction</a>.</li>
125 <li>You can get announcements of WCAG updates via e-mail. See <a href="https://www.w3.org/WAI/news/subscribe/">Get WAI News</a>.</li>
126 </ul>
127
128 <h2>WAI Leadership</h2>
129
130 <p>W3C accessibility work is led by:</p>
131
132 <ul>
133 <li><a href="https://www.w3.org/People/kevin/">Kevin White</a>, Development and Operations Lead</li>
134 <li><a href="https://www.w3.org/People/cooper/">Michael Cooper</a>, Strategy and Technical Lead</li>
135 <li><a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>, Education and Communications Lead</li>
136 </ul>
137
138 <p>WAI staff also includes <a href="https://www.w3.org/People#ran">Ruoxi Ran</a> and <a href="https://www.w3.org/People#dmontalvo">Daniel Montalvo</a>.</p>
139
140 <p>To reach WAI staff, you can e-mail <a href="mailto:wai@w3.org">wai@w3.org</a>.</p>
141 </div>
142 ]]></content:encoded>
143 <slash:comments>0</slash:comments>
144 </item>
145 <item>
146 <title>30th anniversary of licensing the Web for general use and at no cost</title>
147 <description><![CDATA[The post illustrates why selected W3C standards made the Web the premier information commons it is today; and features a graphical timeline that puts W3C standards in perspective with Internet adoption figures, and important websites or services launched.]]></description>
148 <pubDate>Sun, 30 Apr 2023 16:55:00 +0000</pubDate>
149 <link>https://www.w3.org/blog/2023/30th-anniversary-of-licensing-the-web-for-general-use-and-at-no-cost/</link>
150 <guid>https://www.w3.org/blog/2023/30th-anniversary-of-licensing-the-web-for-general-use-and-at-no-cost/</guid>
151 <author>Coralie Mercier</author>
152 <comments>https://www.w3.org/blog/2023/30th-anniversary-of-licensing-the-web-for-general-use-and-at-no-cost/#comments</comments>
153 <category><![CDATA[corporate]]></category>
154 <category><![CDATA[blogs]]></category>
155 <dc:creator>Coralie Mercier</dc:creator>
156 <content:encoded><![CDATA[ <div class="component component--text">
157 <p><small><a href="https://www.chinaw3c.org/30th-anniversary-of-licensing-the-web-for-general-use-and-at-no-cost.html" hreflang="zh-hans">本帖也有简体中文版本</a> (This post also exists in <a href="https://www.chinaw3c.org/30th-anniversary-of-licensing-the-web-for-general-use-and-at-no-cost.html" hreflang="zh-hans">Simplified Chinese</a>)</small></p>
158
159 <hr />
160 </div>
161 <div class="component component--text">
162 <p>Today marks the 30th anniversary of the <a href="https://home.cern/science/computing/birth-web/licensing-web">release of the World Wide Web into the public domain, for general use, and at no cost</a>, on 30 April 1993 by <abbr title="Conseil Européen pour la Recherche Nucléaire">CERN</abbr>.</p>
163
164 <p>This quiet gesture, advocated by Web inventor <a href="https://www.w3.org/People/Berners-Lee/">Sir Tim Berners-Lee</a>, has had implications beyond what he or anyone imagined at that time: the Web, free for everyone, has changed our lives.</p>
165
166 <p>Please, join me in taking a moment to appreciate the impact and the sheer magnitude of the revolution that started just two years prior. “Try it”, Sir Tim noted in his August 1991 email introducing the World Wide Web – and since then, billions of people have.</p>
167
168 <p><img alt="graphic showing a historical photo of Sir Tim Berners-Lee at his desk, next to the text 'try it'" class="alignnone size-medium" decoding="async" src="https://www.w3.org/comm/assets/graphics/try-it-v3.png" /></p>
169
170 <p><a href="https://www.statista.com/statistics/273018/number-of-internet-users-worldwide/">Two thirds of the world are online</a> today (66% of the global population, or 5.3 billion people), and although access may vary greatly between parts of the world, there was a noticeable surge in the steady increase as a result of the Coronavirus pandemic, when suddenly <strong>people become reliant on the Web</strong> for communication, work, education, democracy, online shopping and business, connecting with family and friends, and entertainment, among myriad reasons to use the world’s truest social network.</p>
171
172 <p><strong>The Web has been life-changing for people</strong>. I ran a short <a href="https://w3c.social/@koalie/110140401080412458">poll</a> on social media a few weeks ago, asking people in what way(s) the Web changed their life. <a href="https://w3c.social/@xuf@geraffel.social/110141023455582285">One response</a>, of the many I got, stayed with me:</p>
173
174 <blockquote>
175 <p>“I think there are two type of persons, the ones that the web changed their lives, and the ones that they are not aware that it changed their lives.”</p>
176 </blockquote>
177
178 <p>It warmed my heart and reinforced the sense of purpose I get from working at W3C how people overwhelmingly and enthusiastically lauded the Web. Its positive impact can be broken into three main categories:</p>
179
180 <ol>
181 <li><strong>Vital family and social interactions.</strong> Also, it’s astounding the number of people who met the love of their life thanks to the Web!</li>
182 <li><strong>Earning a living.</strong> Many found jobs as web developers, many conduct business online, many work from home thanks to the Internet and the Web.</li>
183 <li><strong>Empowerment and personal growth.</strong> From enabling people with disabilities or ill people to lead better lives, to breaking world frontiers and expanding horizons to learn, play and discover.</li>
184 </ol>
185
186 <p>Sir Tim Berners-Lee founded the World Wide Web Consortium in 1994 as an <strong>international multi-stakeholder consortium to advance a consistent architecture accommodating progress in web standards</strong>, where member organizations, a full-time staff, and the public develop open web standards.</p>
187
188 <p>CERN’s decision to provide unencumbered access to the basic Web protocols and software developed there was instrumental to the success of the technical work done at the World Wide Web Consortium. The decision to base the Web on royalty-free standards from the beginning has been vital to its success. The open platform of royalty-free standards enabled software companies to profit by selling new products with powerful features, enabled e-commerce companies to profit from services that grew on this foundation, and brought social benefits in the non-commercial realm beyond simple economic valuation.</p>
189
190 <p>In May 2003, coinciding almost exactly with the tenth anniversary of CERN’s decision, W3C <a href="https://www.w3.org/2003/05/patentpolicy-pressrelease.html.en">adopted a Patent Policy</a> to enable continued innovation and widespread adoption of Web standards developed by the World Wide Web Consortium. The W3C Patent Policy governs the handling of patents in the process of producing Web Standards. The goal of this policy is to assure that Recommendations produced under this policy can be implemented on a Royalty-Free (RF) basis. By adopting this Patent Policy with its commitment to royalty-free standards, W3C laid the foundation for future decades of technical innovation, economic growth, and social advancement.</p>
191
192 <p>To date, W3C has published more than <a href="https://www.w3.org/2002/01/tr-automation/tr-stats?form[startdate]=1994-10-01&form[enddate]=2023-04-30">11,000 specifications</a>, of which 470 are web standards.</p>
193
194 <p><a href="https://www.w3.org/comm/assets/graphics/2023-04-30_timeline-1994-2023/2023-04-30_timeline-1994-2023.pdf"><img alt="timeline showing W3C technologies that have had particular impact on the Web, showing websites and product launches that put the web into perspective, showing the number of websites and internet users every 5 years" class="alignnone size-medium" decoding="async" loading="lazy" longdesc="https://www.w3.org/comm/assets/graphics/2023-04-30_timeline-1994-2023/2023-04-30_timeline-1994-2023.html" src="https://www.w3.org/comm/assets/graphics/2023-04-30_timeline-1994-2023/2023-04-30_timeline-1994-2023.png" /></a></p>
195
196 <p>Among the many achievements originating from W3C that influenced the Web for the better, those that made it the premier information commons that it has become are:</p>
197
198 <ul>
199 <li><abbr title="hypertext markup language">HTML</abbr>, <abbr title="cascading style sheets">CSS</abbr>, <abbr title="portable network graphics">PNG</abbr> (1995), the foundational technologies to display content on the web.</li>
200 <li><abbr title="extensible markup language">XML</abbr> (1996), enabling structured data on the web.</li>
201 <li><a href="https://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a> (1997), for planning content and sites that are accessible to all, including disabled people.</li>
202 <li>Patent Policy Working Group formed (1999), to reduce the threat of blocking patents on key components of Web infrastructure, and ultimately allow W3C to deliver royalty-free standards for the Web.</li>
203 <li><abbr title="document object model">DOM</abbr> (1997), for giving logical structure allowing online documents to be accessed and manipulated.</li>
204 <li><a href="https://www.w3.org/International/">Internationalization</a> (1998), for making the World Wide Web truly world-wide, adapted for people from any culture, region, or language, and ensuring text layout and typographic needs of scripts and languages around the world are built in Web technology.</li>
205 <li>Ecommerce/Micropayment (1998), to make it possible to buy and sell goods and services online reliably and securely, and which led to a series of Web Payments work.</li>
206 <li><abbr title="resource description framework">RDF</abbr> (1999), to model data interchange, and enable structured data to be mixed, exposed, and shared.</li>
207 <li><abbr title="scalable vector graphics">SVG</abbr> (2001), to enable two-dimensional graphics, allowing shapes, text and embedded graphics to be displayed on the web and integrated with HTML and CSS.</li>
208 <li><a href="https://www.w3.org/2003/05/patentpolicy-pressrelease.html.en">W3C Patent Policy</a> (2003), to assure that specifications can be implemented on a Royalty-Free (RF) basis and used at no cost, thus boosting adoption and usage.</li>
209 <li>Mobile Web Initiative (2005), which made web access from a mobile device simple, easy, and convenient. As of August 2021, <a href="https://www.statista.com/topics/1145/internet-usage-worldwide/#topicOverview">mobile devices accounted for 57% of web page views worldwide</a>.</li>
210 <li>W3C in China (2006), where the online presence has been leading for a long time, gave way notably to ongoing standardization of MiniApps to enhance the interoperability, accessibility, internationalization, privacy and security between different MiniApp platforms and the web.</li>
211 <li><a href="https://www.w3.org/2008/12/wcag20-pressrelease.html.en"><abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.0</a>, to make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photo sensitivity and combinations of these. Following these guidelines often makes content more usable to users in general.</li>
212 <li><a href="https://www.w3.org/2021/01/pressrelease-webrtc-rec.html.en">Web<abbr title="real-time communications">RTC</abbr></a> (2011), for bringing audio and video communications anywhere on the web, from any connected device.</li>
213 <li><abbr title="web open font format">WOFF</abbr> (2012), for providing downloadable fonts easily licensed and reliably used in any browser on laptops, mobile and TV. W3C received its <a href="https://www.w3.org/2022/04/pressrelease-woff-emmyaward.html.en">third Technology & Engineering Emmy® Award</a> in 2022 for standardizing font technology for custom downloadable fonts and typography for web and TV devices.</li>
214 <li>JSON-LD (2014), for making Linked Data and RDF much easier to adopt by developers. Its most resounding success is its use in schema.org, allowing people to simply include machine readable data in their web pages, to help search engine better index them, and other web agents to better understand them.</li>
215 <li>Web Payments (2014) for making web payments easier and more secure.</li>
216 <li>ActivityPub (2018), for powering the world’s greatest decentralized network. The protocol enables creating, updating and deleting content across several federated servers.</li>
217 <li><a href="https://www.w3.org/2019/12/pressrelease-wasm-rec.html.en">WebAssembly</a> (2019), for enabling high-performance applications relying on a low-level infrastructure, and enhancing web performance and power consumption.</li>
218 <li><a href="https://www.w3.org/2019/03/pressrelease-webauthn-rec.html.en"><abbr title="web authentication">WebAuthn</abbr></a> (2019), for making the web more secure and usable, by building support for easy and secure logins via biometrics, mobile devices and other implements.</li>
219 <li><a href="https://www.w3.org/2022/07/pressrelease-did-rec.html.en"><abbr title="decentralized identifiers">DIDs</abbr></a> (2022), to empower everyone on the web with privacy-respecting online identity and consent-based data sharing.</li>
220 </ul>
221
222 <p>Our <a href="https://www.w3.org/Consortium/mission#vision">vision</a> for the future is a Web that is truly a force for good. A World Wide Web that is international and inclusive, respectful of its users. A Web that supports truth better than falsehood, people more than profits, humanity rather than hate. A Web that works for everyone, because of everyone.</p>
223 </div>
224 ]]></content:encoded>
225 <slash:comments>3</slash:comments>
226 </item>
227 <item>
228 <title>Answering “What ARIA can I use?”</title>
229 <description><![CDATA[Announcing the launch of “Assistive Technology Support” tables in the ARIA Authoring Practices Guide (APG).]]></description>
230 <pubDate>Mon, 17 Apr 2023 17:20:00 +0000</pubDate>
231 <link>https://www.w3.org/blog/2023/answering-what-aria-can-i-use/</link>
232 <guid>https://www.w3.org/blog/2023/answering-what-aria-can-i-use/</guid>
233 <author>Matthew King</author>
234 <comments>https://www.w3.org/blog/2023/answering-what-aria-can-i-use/#comments</comments>
235 <category><![CDATA[accessibility]]></category>
236 <category><![CDATA[blogs]]></category>
237 <dc:creator>Matthew King</dc:creator>
238 <content:encoded><![CDATA[ <div class="component component--text">
239 <h2>New! AT support tables in the Authoring Practices Guide (APG)</h2>
240
241 <p>The <a href="https://www.w3.org/groups/cg/aria-at">ARIA and Assistive Technologies Community Group</a> (ARIA-AT CG) and <a href="https://www.w3.org/groups/tf/aria-practices">ARIA Authoring Practices Task Force</a> (APG TF) are excited to announce the launch of “Assistive Technology Support” tables in the ARIA Authoring Practices Guide (APG). This initial release includes tables showing JAWS, NVDA, and VoiceOver support levels on four pages that demonstrate pattern implementations, including <a href="https://www.w3.org/WAI/ARIA/apg/patterns/button/examples/button/#assistivetechnologysupport">Button Examples</a>, <a href="https://www.w3.org/WAI/ARIA/apg/patterns/link/examples/link/#assistivetechnologysupport">Link Examples</a>, <a href="https://www.w3.org/WAI/ARIA/apg/patterns/radio/examples/radio-activedescendant/#assistivetechnologysupport">Radio Group Example Using aria-activedescendant</a>, and <a href="https://www.w3.org/WAI/ARIA/apg/patterns/alert/examples/alert/#assistivetechnologysupport">Alert Example</a>. More are coming soon.</p>
242
243 <p>This “Can I Use…” like data showing how three screen readers support four UI pattern implementations represents a sea change in accessibility engineering. The data are the first taste of the fruits of nearly five years of collaboration, learning, community building, and process and infrastructure development.</p>
244
245 <p><strong>That fruit makes predictable screen reader behavior possible.</strong> That possibility portends a world where any web developer can build rich web experiences that work well with any assistive technology as readily as they can create experiences that work in any browser for people who do not rely on assistive technology.</p>
246
247 <h2>The problem of the “accessibility supported” puzzle</h2>
248
249 <p>It has always been a struggle, often a monumental and expensive one, for web developers to find ways of coding experiences that are understandable by users of any assistive technology (AT). You get your site working with one AT and it ends up not working as well with another. Then the experience of your site with an important AT degrades because the latest version of that AT includes changes to better support a popular site that has encoded a similar experience in a different way. Of course, the degradation was unintentional. As is often the case, accessibility experts frequently have conflicting understandings of how to satisfy relevant specifications. Consequently, unintentional negative side effects are difficult if not impossible to avoid.</p>
250
251 <p>Web, browser, operating system, and AT developers are all attempting to cut pieces of a puzzle. Everyone hopes that, when assembled, the puzzle will picture a usable web built from accessibility supported experiences. Unfortunately, while browser and operating system developers get pretty clear and stable maps showing where to draw their cutting lines from specifications for ARIA, HTML, and various accessibility APIs, web and AT developers do not. They do their best, but the act of drawing moves the puzzle board, messing up the lines being drawn by others. What’s worse is they occasionally discover ink has randomly disappeared. So, the way the picture is divided constantly changes. Sometimes pieces fit together, giving users a good experience, but far too often, they don’t.</p>
252
253 <p><a href="https://www.w3.org/WAI/WCAG22/Understanding/conformance#accessibility-support">Understanding WCAG conformance</a> defines what we need for a new technology, like an ARIA-enabled UI pattern, to be accessibility supported:</p>
254
255 <blockquote>
256 <p>“When new technologies are introduced, two things must happen in order for people using assistive technologies to be able to access them. First, the technologies must be designed in a way that user agents including assistive technologies could access all the information they need to present the content to the user. Secondly, the user agents and assistive technologies may need to be redesigned or modified to be able to actually work with these new technologies.”</p>
257 </blockquote>
258
259 <p>So, even when browsers and accessibility APIs are perfectly implementing their specs, we don’t yet have everything necessary to design and build web UI patterns that are “accessibility supported.” For that, we also need:</p>
260
261 <ol>
262 <li>Consistent understanding across web development communities of “all the information assistive technologies need to present” a given pattern, which accessibility semantics best represent that information, and which ways of coding the pattern accurately express those semantics.</li>
263 <li>Consistent interpretation and rendering of accessibility semantics across the AT industry, such that there are shared expectations for acceptable AT responses to a given semantic in a given pattern.</li>
264 <li>All stakeholders having sufficiently similar understanding of the meaning of “actually works” for any given pattern.</li>
265 </ol>
266
267 <p>In other words, web developers and AT developers need to be on the same page, and that page must not only synthesize information from a wide variety of specifications but also include information about what “actually works” for AT users that has not been available anywhere.</p>
268
269 <h2>Helping map the rest of the “accessibility supported” puzzle</h2>
270
271 <p>The ARIA-AT CG and APG TF have been jointly working to align the web development and AT developer communities. They are building missing pieces of the foundational infrastructure needed to generate the information and consensus that can make “accessibility supported” web UI patterns available to any web developer and users of any AT.</p>
272
273 <p>First, to foster harmonization of how accessibility semantics are used in practice by web developers, the APG TF has been transforming the Authoring Practices Guide into a platform that supports the multiple facets of that goal. To start, it provides <a href="https://www.w3.org/WAI/ARIA/apg/patterns/">thirty patterns for using ARIA semantics</a>. To demonstrate how to apply those patterns in practice, it also includes more than 60 <a href="https://www.w3.org/WAI/ARIA/apg/example-index/">example implementations of the patterns</a>. As of the time of this announcement, the APG also provides the equivalent of “can I use …” data, i.e., AT support tables, for four of the reference implementations.</p>
274
275 <p>That “can I use …” type of data comes from the <a href="https://aria-at.w3.org/">ARIA-AT project</a>. The objective of ARIA-AT stated in terms of “WCAG accessibility supported” is to build consensus for definitions of “actually works” that are specific to every accessibility semantic defined within a specification related to ARIA. It is starting with semantics employed in APG patterns.</p>
276
277 <h2>The challenge of defining and testing AT behavior that “actually works”</h2>
278
279 <p>Figuring out how to define, develop consensus for, and test baseline expectations for AT behaviors has proven to be as fantastically challenging as anyone might have imagined. In 2018, the ARIA-AT CG set a five-year goal of testing 60 APG examples with three desktop screen readers and two mobile screen readers. Even with the scope limited to a select few screen readers, the goal was more ambitious than we anticipated. Last year, we had to dial back our end of 2023 target to testing 30 examples with three desktop screen readers. The good news is that progress is solid, and the community group is proving that 1) AT interoperability is a realistic industry goal, and 2) if we can keep the work funded, universally available accessibility supported web sites can one day be a reality.</p>
280
281 <p>At a high level, the major elements of the APG TF and ARIA-AT CG AT interoperability work are:</p>
282
283 <ol>
284 <li>Build the supply of sufficient, robust, and stable test cases that represent real-world usage of accessibility semantics. The initial source is the APG. There could be many more in the future.</li>
285 <li>Craft statements of expected AT behaviors in the form of test plans. This is very difficult work that is executed by community group members from Prime Access Consulting, which you can read about on the <a href="https://www.pac.bz/blog/pac-and-aria-at-helping-to-define-and-evaluate-screen-reader-support-expectations">PAC blog</a>.</li>
286 <li>Develop systems for managing the stakeholder consensus process, manually running tests, and serving reports. These systems are being delivered by community group members who work at Bocoup, and you can learn more about that work in <a href="https://bocoup.com/blog/can-i-use-but-for-aria">this post on their blog</a>.</li>
287 <li>Develop and implement an AT automation standard that enables tests to be re-run within continuous integration systems for every new version of an assistive technology or browser. As described in the two previously referenced posts, Bocoup is leading development of the <a href="https://w3c.github.io/at-driver/">AT Driver standard</a>, and PAC is developing the <a href="https://github.com/Prime-Access-Consulting/nvda-at-automation/">NVDA implementation</a>.</li>
288 </ol>
289
290 <p>All that is enablement. The deliverables from those workstreams make it possible for community group members and stakeholders to run tests, gather feedback on test plans, define issues, negotiate consensus solutions, incorporate resolutions into test plans, and finally raise and resolve AT bugs.</p>
291
292 <h2>Screen reader partnership</h2>
293
294 <p>Given that the community group is kickstarting AT interoperability with an initial focus on the three most popular desktop screen readers, progress depends on effective collaboration with the developers of those screen readers. One of the critical enablers of today’s launch has been the involvement and responsiveness of Vispero and Apple.</p>
295
296 <p>Negotiating the details of how to test interoperability and adjusting screen reader behaviors to align with the expectations defined by the tests is substantive work. The community group is seeking ways of helping NVAccess (developer of NVDA) build the capacity it would need to support it as well.</p>
297
298 <h2>What’s next</h2>
299
300 <p>In coming months, AT support tables will be added to more APG example pages. The ARIA-AT CG is developing a quarterly schedule for covering the rest of the APG, and we plan to make it publicly available soon. Over the course of 2023, as we integrate automation into the process, the tables will include data for more screen reader and browser combinations.</p>
301
302 <p>In 2024, as we complete the first round of test plans for desktop screen readers, we plan to start adding test plans for mobile screen readers. Assuming continued success and funding, the project will expand to support more types of assistive technologies and test more accessibility semantics.</p>
303
304 <h2>Get involved</h2>
305
306 <p>To learn more about how you or your organization can participate or support the project, visit our <a href="https://github.com/w3c/aria-at/wiki/Contributing-to-the-ARIA-and-Assistive-Technologies-Project">wiki page about contributing to the project</a>.</p>
307 </div>
308 ]]></content:encoded>
309 <slash:comments>1</slash:comments>
310 </item>
311 <item>
312 <title>Privacy Principles for the Web</title>
313 <description><![CDATA[The W3C Technical Architecture Group (TAG) is seeking public comments by the end of April on a set of privacy principles for the web.]]></description>
314 <pubDate>Wed, 22 Mar 2023 09:04:00 +0000</pubDate>
315 <link>https://www.w3.org/blog/2023/privacy-principles-for-the-web/</link>
316 <guid>https://www.w3.org/blog/2023/privacy-principles-for-the-web/</guid>
317 <author>Samuel Weiler</author>
318 <comments>https://www.w3.org/blog/2023/privacy-principles-for-the-web/#comments</comments>
319 <category><![CDATA[privacy-and-security]]></category>
320 <category><![CDATA[blogs]]></category>
321 <dc:creator>Samuel Weiler</dc:creator>
322 <content:encoded><![CDATA[ <div class="component component--text">
323 <p>The World Wide Web Consortium’s <a href="https://www.w3.org/groups/other/tag">Technical Architecture Group (TAG)</a> has recently established a task force to create a set of <a href="https://www.w3.org/TR/privacy-principles/">privacy principles for the web</a>. This initiative is part of the W3C’s ongoing efforts to promote and protect privacy on the web. The Privacy Principles document lays out a set of principles that aim to guide the development of new specifications for the web platform, with the goal of eventually publishing it as a <a href="https://www.w3.org/2021/Process-20211102/#statement">W3C Statement</a>. This effort builds on previous work by the W3C’s Privacy Interest Group and the TAG’s Security & Privacy Questionnaire and Ethical Web Principles, which underscore the importance of respecting users’ privacy in web design and development.</p>
324
325 <p>We welcome your feedback on the document. We encourage you to <a href="https://github.com/w3ctag/privacy-principles">leave that feedback in the document’s Github repository</a>. We would like comments before the end of April.</p>
326 </div>
327 ]]></content:encoded>
328 <slash:comments>0</slash:comments>
329 </item>
330 <item>
331 <title>W3C launches beta of its new website</title>
332 <description><![CDATA[W3C welcomes feedback on the beta of its new website.]]></description>
333 <pubDate>Mon, 27 Feb 2023 07:31:00 +0000</pubDate>
334 <link>https://www.w3.org/blog/2023/w3c-launches-beta-of-its-new-website/</link>
335 <guid>https://www.w3.org/blog/2023/w3c-launches-beta-of-its-new-website/</guid>
336 <author>Coralie Mercier</author>
337 <comments>https://www.w3.org/blog/2023/w3c-launches-beta-of-its-new-website/#comments</comments>
338 <category><![CDATA[corporate]]></category>
339 <category><![CDATA[blogs]]></category>
340 <dc:creator>Coralie Mercier</dc:creator>
341 <content:encoded><![CDATA[ <figure class="component component--image">
342 <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-center_none/betasite-2023-02-27.png" extension="png" sizes="100vw"
343 loading="lazy"
344 alt=""
345 />
346 <figcaption>
347 <p>Screenshot of the beta homepage of the redesigned W3C website</p>
348 </figcaption>
349 </figure>
350 <div class="component component--text">
351 <p>Today we launched a<a href="https://www.w3.org/" style="text-decoration:none"> <u>beta version</u></a> of the redesign of our website.</p>
352
353 <p>The goals of the redesign are to achieve a cleaner and modern look and greater usability, better accessibility, as well as ultimately simplifying how the site is managed. We also want to offer integrated Japanese and Chinese versions, which we will roll out after the beta of the English site has concluded.</p>
354
355 <p>For several years, W3C has worked in close partnership with <a href="https://w3c.studio24.net" style="text-decoration:none"><u>Studio 24</u></a> to redesign our website. This is, as many in our community know, an enormous undertaking and one which has been of great importance to us. You can read more from <a href="https://www.studio24.net/blog/w3c-beta-site-launch/" style="text-decoration:none"><u>Studio 24’s blog post</u></a> about our collaboration (“the journey!”) and process.</p>
356
357 <p>The scope of the redesign is limited to most of our public pages, but we will gradually work to include the rest of the site.</p>
358
359 <p>We invite your feedback on the beta site, on website or content issues, we're using <a href="https://github.com/w3c/w3c-website" style="text-decoration:none"><u>GitHub</u></a> to manage comments.</p>
360
361 <p>My heartfelt thanks to the W3C Systems Team for its tremendous work for several years as well as to the many people in the WAI and i18n teams and to everyone so far and in the near future who’ve worked with Studio 24 and us on this project. We are grateful to Studio 24 for their incredible work, dedication and technical skills - our new site would not exist without them.</p>
362
363 <p>We’re not done, but we’ve reached a significant milestone!</p>
364
365 <p>Please let us know what you think. </p>
366 </div>
367 ]]></content:encoded>
368 <slash:comments>7</slash:comments>
369 </item>
370 <item>
371 <title>Farewell Karen Myers, W3C Business Development Leader Extraordinaire</title>
372 <description><![CDATA[Farewell Karen Myers, W3C Business Development Leader Extraordinaire]]></description>
373 <pubDate>Wed, 18 Jan 2023 11:05:00 +0000</pubDate>
374 <link>https://www.w3.org/blog/2023/farewell-karen-myers-w3c-business-development-leader-extraordinaire/</link>
375 <guid>https://www.w3.org/blog/2023/farewell-karen-myers-w3c-business-development-leader-extraordinaire/</guid>
376 <author>J. Alan Bird</author>
377 <comments>https://www.w3.org/blog/2023/farewell-karen-myers-w3c-business-development-leader-extraordinaire/#comments</comments>
378 <category><![CDATA[corporate]]></category>
379 <category><![CDATA[blogs]]></category>
380 <dc:creator>J. Alan Bird</dc:creator>
381 <content:encoded><![CDATA[ <div class="component component--text">
382 <p><img alt="group picture at the Emmy Awards ceremony" src="https://www.w3.org/2016/01/MDB_5533-TTWG-Emmy-1-small.jpg" /></p>
383
384 <p>It is with bittersweet emotions, that I share that Karen Myers’ time as W3C Business Development Leader for the Americas and Australia is ending.</p>
385
386 <p>After 18 years, Karen has chosen to retire from the World Wide Web Consortium to pursue personal endeavors. We want to take this opportunity to thank Karen and to reflect upon her contributions to W3C over her many years of service.</p>
387
388 <p>We welcomed Karen Myers in 2004 to assume the role of Acting Director of Communications, and we were fortunate to later gain her help with marketing and business development for memberships. In both areas, Karen’s technology marketing experience, her positive energy and love of learning were strengths which enabled her to accomplish the challenge to create business value propositions that made clear both the power of the Web and the value of Membership so that organizations would consider joining W3C.</p>
389
390 <p>Karen’s achievements over the years, allocating her time between marketing, media coordination, and business development were numerous. To name only a few:</p>
391
392 <ul>
393 <li>coordinating the communications of our Director Tim Berners-Lee’s knighthood by Her Majesty Queen Elizabeth in 2004.</li>
394 <li>planning the W3C ten-year anniversary events and gala.</li>
395 <li>working with Tim on some of his speeches —including his first TED talk.</li>
396 <li>putting together international W3C events at the Consumer Electronics Show (CES) in Las Vegas (USA) and Mobile World Congress (MWC) in Barcelona (Spain), the first Web and TV W3C Workshop in Hollywood (USA) where we began the work to “make video a first-class citizen of the web”, which in turn led a few years after to W3C receiving one of 3 National Academy of Television Arts and Sciences (NATAS) technical Emmy® Awards.</li>
397 <li>coordinating with W3C Evangelists and Chapters in publishing, media and entertainment, automotive and accessibility, and supporting global outreach and educational events.</li>
398 <li>recruiting and onboarding hundreds of new members to participate in W3C standards activities and more.</li>
399 </ul>
400
401 <p>Going forward, I, <a href="https://www.w3.org/People/AlanBird/">Alan Bird</a>, Global W3C Business Development Lead, will resume Karen’s day-to-day responsibilities immediately. <a href="https://www.w3.org/People#Y">Naomi Yoshizawa</a>, Global W3C Member Relations Lead, will handle member relationship and other administrative questions. And <a href="https://www.w3.org/People/LeHegaret/">Philippe Le Hégaret</a>, W3C Project Management Lead is the contact for operational questions regarding W3C groups charters, W3C process, and participation in work groups.</p>
402
403 <p>Farewell and best wishes to Karen in whatever new adventures she chooses to pursue next!</p>
404 </div>
405 ]]></content:encoded>
406 <slash:comments>1</slash:comments>
407 </item>
408 <item>
409 <title>2023; a new era for W3C</title>
410 <pubDate>Mon, 09 Jan 2023 12:27:00 +0000</pubDate>
411 <link>https://www.w3.org/blog/2023/2023-a-new-era-for-w3c/</link>
412 <guid>https://www.w3.org/blog/2023/2023-a-new-era-for-w3c/</guid>
413 <author>Ralph Swick</author>
414 <comments>https://www.w3.org/blog/2023/2023-a-new-era-for-w3c/#comments</comments>
415 <category><![CDATA[corporate]]></category>
416 <category><![CDATA[blogs]]></category>
417 <dc:creator>Ralph Swick</dc:creator>
418 <content:encoded><![CDATA[<div class="component component--text">
419 <p>With the start of the year 2023 we pass a <a href="/news/2022/w3c-board-of-directors-successfully-brokered-mit-asset-transfer-agreement/">milestone</a> in the evolution of the global collaboration project that is the World Wide Web Consortium: In our 29th year of operation, we are <a href="https://www.w3.org/2022/09/w3c-inc-faq">operating</a> now as World Wide Web Consortium Inc, continuing with Beihang University (China), <abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr> (France), and Keio University (Japan) as partners.</p>
420
421 <p>At the broadest level our <a href="https://www.w3.org/Consortium/mission">mission</a> continues unchanged, with the W3C Advisory Board leading a project to <a href="https://github.com/w3c/AB-public/tree/main/Vision">renew the expression of that mission</a>.</p>
422
423 <p>Our community – our <a href="https://www.w3.org/Consortium/Member/List">Members</a>, non-Member contributors, <a href="https://www.w3.org/People">Team</a>, and all who use the results of our collective work – will continue to refine their expectations of this project and we will continue to adapt to those expectations.</p>
424
425 <p>Our strength derives from the diversity of our global inclusion. This should be our guide as we continue to refine the best arrangement of the elements of this project.</p>
426
427 <p>Thank you for your continued engagement in this global effort to maintain <strong>one world wide web with equitable access for all</strong> its users.</p>
428
429 <p>–Ralph Swick, W3C Interim CEO</p>
430 </div>]]></content:encoded>
431 <slash:comments>1</slash:comments>
432 </item>
433 <item>
434 <title>Latest EPUBCheck 5.0.0 Preview</title>
435 <pubDate>Mon, 28 Nov 2022 18:36:00 +0000</pubDate>
436 <link>https://www.w3.org/blog/2022/latest-epubcheck-5-0-0-preview/</link>
437 <guid>https://www.w3.org/blog/2022/latest-epubcheck-5-0-0-preview/</guid>
438 <author>Tzviya Siegman</author>
439 <comments>https://www.w3.org/blog/2022/latest-epubcheck-5-0-0-preview/#comments</comments>
440 <category><![CDATA[developers]]></category>
441 <category><![CDATA[blogs]]></category>
442 <dc:creator>Tzviya Siegman</dc:creator>
443 <content:encoded><![CDATA[<div class="component component--text">
444 <h2>Latest EPUBCheck 5.0.0 preview is available!</h2>
445
446 <p>We are pleased to announce the latest <strong>preview release</strong> of the next major version of EPUBCheck, v5.0.0. For the first time, this version <strong>fully implements</strong> the new rules in <a href="https://www.w3.org/TR/epub-33">EPUB 3.3</a> (W3C Candidate Recommendation Draft).</p>
447
448 <p>We encourage users to effectively test this version of EPUBCheck in their production workflows to get ready for EPUB 3.3!</p>
449
450 <p>The full change log is available on the EPUBCheck <a href="https://github.com/w3c/epubcheck/releases/tag/preview">preview release page</a>.</p>
451
452 <p>Please file comments, bug reports, and feature request to our <a href="https://github.com/w3c/epubcheck/issues">issue tracker</a>. Or, come <a href="https://www.w3.org/publishing/epubcheck/docs/translating">help with the translation</a> of EPUBCheck into your favorite language!</p>
453 </div>]]></content:encoded>
454 <slash:comments>0</slash:comments>
455 </item>
456 <item>
457 <title>WebDX: Improving the experience for web developers</title>
458 <pubDate>Tue, 08 Nov 2022 14:29:00 +0000</pubDate>
459 <link>https://www.w3.org/blog/2022/webdx-improving-the-experience-for-web-developers/</link>
460 <guid>https://www.w3.org/blog/2022/webdx-improving-the-experience-for-web-developers/</guid>
461 <author>Dominique Hazaël-Massieux</author>
462 <comments>https://www.w3.org/blog/2022/webdx-improving-the-experience-for-web-developers/#comments</comments>
463 <category><![CDATA[developers]]></category>
464 <category><![CDATA[blogs]]></category>
465 <dc:creator>Dominique Hazaël-Massieux</dc:creator>
466 <content:encoded><![CDATA[<div class="component component--text">
467 <p>When surveyed, 38% of developers in general seem to dread using Web technologies (<a href="https://survey.stackoverflow.co/2022/#most-loved-dreaded-and-wanted-language-love-dread">HTML & CSS, JS in StackOverflow 2022 survey</a>); and when asking Web developers and designers more specifically, 23% aren't satisfied with the Web platform (<a href="https://insights.developer.mozilla.org/reports/mdn-web-developer-needs-assessment-2020.html#overall-satisfaction-with-the-web-overview">MDN DNA 2020 survey</a>). This could be worse - but how can we make it better?</p>
468
469 <p>As a development platform, the Web platform is fairly unique in being provided through competing browsers which implement a shared set of standardized technologies. This combination of cooperation in defining the technologies and competition in implementing them has long been recognized as an important driver of improvements for the platform as a whole, as implementers innovate on new user facing features and protections, improved developer tools, and increased performance.</p>
470
471 <p>While competing implementations are a great driver of innovation, it also creates <strong>fragmentation</strong>, a regular top pain point that developers report (e.g. <a href="https://insights.developer.mozilla.org/reports/mdn-web-developer-needs-assessment-2020.html#overall-satisfaction-with-the-web-satisfaction-by-subcategory">browser compatibility pain point in MDN DNA survey 2020</a>). What feature can developers rely on to ensure that their app will work on the combination of devices, operating systems and browsers that they need to serve?</p>
472
473 <p>Understanding and monitoring what constitutes the interoperable surface of the Web platform is a non-trivial task, especially as browsers now get updated on a very regular basis.</p>
474
475 <p>The <a href="https://github.com/web-platform-tests/interop">Interop project</a> is an ongoing effort to bring cooperation not just about the definition of technologies, but also about their deployment, with the clear goal of reducing fragmentation developers most suffer from.</p>
476
477 <p>Similarly, <a href="https://openwebdocs.org/">Open Web Docs</a> provides home for cooperation in developing another key part of the developer experience, documentation, through contributions to <a href="https://developer.mozilla.org/en-US/docs/Web">MDN Web Docs</a>.</p>
478
479 <p>To build on these positive patterns, the <a href="https://www.w3.org/community/webdx/">WebDX Community Group</a> was launched a couple of weeks ago with a mission to facilitate coordinated approaches to improve the overall experience of developing for the Web platform. The group will initially <a href="https://github.com/web-platform-dx/admin/blob/main/charter.md">focus on two key areas</a>.</p>
480
481 <p>First, it will <b>enable shared research on the pain points that developer face</b>. Previous shared research efforts include the <a href="https://insights.developer.mozilla.org/">MDN Web Developer Need Assessment surveys</a> that ran in 2019 and 2020. Their results unambiguously highlighted the cost of fragmentation for developers, and with additional complementary research, were key drivers of improvements in this space, in particular via the <a href="https://github.com/web-platform-tests/interop">Interop project</a>. The WebDX Community Group intends to provide a home to discuss topics and infrastructures for shared research on developer needs and wants. Our efforts start with a collaboration on short surveys that will run on a regular basis on <a href="https://developer.mozilla.org/en-US/docs/Web">MDN</a> (with our deep gratitude to Mozilla and the MDN team). During <a href="https://www.w3.org/2022/09/TPAC/breakouts.html">W3C TPAC unconference in September</a>, we also <a href="https://www.w3.org/2022/09/14-webdx-minutes.html">collected a number of other suggestions</a> about how shared and curated research could help us take better decisions for the platform.</p>
482
483 <p>In complement to that, we want to provide structural improvements in how developers can understand and manage fragmentation: reducing fragmentation (as proposed by the <a href="https://github.com/web-platform-tests/interop">Interop</a> project) is the preferred approach, but some fragmentation is unavoidable (e.g. because hardware capabilities may differ across devices), and some of it is probably a necessary consequence of the competitive model of the platform.</p>
484
485 <p>We want to <b>make it easier for developers to track the list of features that are widely available and those that are under development</b>. My colleague and WebDX Community Group co-chair François Daoust developed an <a href="https://github.com/web-platform-dx/feature-set/blob/main/towards-features.md">analysis of how features get described and their implementation tracked</a> across a variety of tools and systems, including <a href="https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Page_structures/Compatibility_tables">MDN Browser Compatibility Data</a> and <a href="https://caniuse.com/">Can I Use</a> that many developers already call upon to answer these questions. We believe that we can improve our approaches towards reducing fragmentation and making sure that developers know about it, provided that we can describe and agree on features that compose the Web platform.</p>
486
487 <p>It's still early days! If you want to contribute and improve the developer experience of the most popular platform, please join the <a href="https://www.w3.org/community/webdx/">WebDX Community Group</a> or bring your input to our <a href="https://github.com/web-platform-dx">GitHub repositories</a>.</p>
488 </div>]]></content:encoded>
489 <slash:comments>1</slash:comments>
490 </item>
491 <item>
492 <title>Stepping forward on WAI management</title>
493 <pubDate>Wed, 19 Oct 2022 12:18:00 +0000</pubDate>
494 <link>https://www.w3.org/blog/2022/stepping-forward-on-wai-management/</link>
495 <guid>https://www.w3.org/blog/2022/stepping-forward-on-wai-management/</guid>
496 <author>Michael Cooper</author>
497 <comments>https://www.w3.org/blog/2022/stepping-forward-on-wai-management/#comments</comments>
498 <category><![CDATA[accessibility]]></category>
499 <category><![CDATA[blogs]]></category>
500 <dc:creator>Michael Cooper</dc:creator>
501 <content:encoded><![CDATA[<div class="component component--text">
502 <p>Associated with <a href="https://www.w3.org/blog/2022/10/w3c-wai-updates-october-2022/">several WAI transitions</a>, it has been announced that I will take over some aspects of Judy Brewer's role, in order to ensure continuity of the WAI program after her departure in January. I want to share with everyone what I know so far about what this means for WAI. This is an interim assignment for now, for which I feel well-positioned to bring my experience in W3C to help WAI and W3C evolve through the current transitions.</p>
503
504 <p>My priority is to keep the work moving forwards, including working groups and projects associated with WAI, as well as the behind-the-scenes activities that enable the staff to support that work. I will need to make time for this work, and am glad my colleagues Shawn Henry, Daniel Montalvo, and Roy Ran will expand their responsibilities as well. For those of you who know how embedded I am in the <a href="https://www.w3.org/WAI/GL/">Accessibility Guidelines</a> work, be reassured that I plan to continue active involvement in that group so I can continue to provide institutional memory, and my characteristic approach at understanding issues, to this challenging work.</p>
505
506 <p>Another transition is that Kevin White rejoined WAI this week, bringing a great deal of experience in program management and digital accessibility. Our respective strengths and experience will help us ensure the work progresses smoothly. We will also work with WAI staff and W3C to determine what roles the program needs going forwards, and how we might fill those with current and future staff. My own role after the transition will be addressed in those discussions as well.</p>
507
508 <p>Many of you know me mostly in my role as staff contact to the Accessibility Guidelines Working Group, as well as to the APA and ARIA groups. I've been involved in this work for over 20 years, and have vision for how to move WAI forward through the staff and W3C transitions. I look forward to engaging with a broader set of stakeholders than I have so far, and to helping lead WAI into its next phase!</p>
509 </div>]]></content:encoded>
510 <slash:comments>0</slash:comments>
511 </item>
512 <item>
513 <title>W3C WAI Updates, October 2022</title>
514 <pubDate>Wed, 19 Oct 2022 12:12:00 +0000</pubDate>
515 <link>https://www.w3.org/blog/2022/w3c-wai-updates-october-2022/</link>
516 <guid>https://www.w3.org/blog/2022/w3c-wai-updates-october-2022/</guid>
517 <author>Shawn Lawton Henry</author>
518 <comments>https://www.w3.org/blog/2022/w3c-wai-updates-october-2022/#comments</comments>
519 <category><![CDATA[accessibility]]></category>
520 <category><![CDATA[blogs]]></category>
521 <dc:creator>Shawn Lawton Henry</dc:creator>
522 <content:encoded><![CDATA[<div class="component component--text">
523 <p>Several changes are in progress at the <a href="https://www.w3.org/WAI/">W3C Web Accessibility Initiative (WAI)</a>, each exciting in different ways. W3C and WAI staff are supporting our accessibility work on the current path during this transition.</p>
524
525 <h2>WAI Staff and Roles</h2>
526
527 <p><strong>Judy Brewer</strong> will be leaving WAI for a new opportunity. She shared more in a <a href="https://lists.w3.org/Archives/Public/public-wai-announce/2022OctDec/0002.html">WAI Transitions message</a>. From 24 October 2022 to 13 January 2023, Judy will be available part-time to help the transition for stability and continuity of WAI at W3C.</p>
528
529 <p><strong>Kevin White</strong> rejoined the WAI Team in October as Accessibility Development and Operations Lead. Kevin will contribute his accessibility, technical, and program management experience to WAI's work in Europe and internationally.</p>
530
531 <p><strong><a href="https://www.w3.org/People/cooper/">Michael Cooper</a></strong> has taken up some interim leadership responsibilities to ensure smooth transition of the WAI program. He will also remain the primary team contact for the Accessibility Guidelines Working Group, to help guide that challenging work. Michael shared more in <a href="/blog/2022/stepping-forward-on-wai-management/">Stepping Forward on WAI Management</a>.</p>
532
533 <p><strong><a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a></strong>, <strong><a href="https://www.w3.org/People/Roy/">Roy Ran</a></strong>, and <strong><a href="https://www.w3.org/People#dmontalvo">Daniel Montalvo</a></strong> are also taking up additional responsibilities in the interim.</p>
534
535 <p>Over the next few months, WAI will refine roles and responsibilities for W3C accessibility work, and explore coverage by current and future staff.</p>
536
537 <h2>W3C Supports WAI Going Forward</h2>
538
539 <p>"W3C is proud of WAI's successes under Judy's leadership," said <strong><a href="https://www.w3.org/People#rswick">Ralph Swick, W3C COO</a></strong>. "W3C is committed to continuing the important accessibility work of WAI to advance the <a href="https://www.w3.org/Consortium/mission.html#principles">Web for All</a>."</p>
540
541 <p>WAI staff will work on WAI vision and strategic plan in early 2023, with input from the WAI community and the broader W3C community. Core accessibility work will continue, and we look forward to defining the focus and priorities for 2023 and beyond.</p>
542
543 <h2>Current WAI Work and Updates</h2>
544
545 <p><strong>To get up-to-date information on active projects, upcoming publications, and more, see:<br />
546 <a href="https://www.w3.org/WAI/update/">What We’re Working On – Accessibility Activities and Publications</a></strong><br />
547 To get future updates, see: <a href="https://www.w3.org/WAI/news/subscribe/">Get WAI News</a><br />
548 To learn about existing accessibility standards and supporting material, see: <a href="https://www.w3.org/WAI/resources/">WAI Resources</a></p>
549
550 <p>Please feel free to reach out to any of us directly with questions and suggestions. (and please be patient if we are slow to respond:) To send e-mail to all W3C WAI Team, you can use: <a href="mailto:wai@w3.org">wai@w3.org</a></p>
551
552 <p><strong>We look forward to working together with the community to advance digital accessibility through WAI at W3C.</strong></p>
553 </div>]]></content:encoded>
554 <slash:comments>0</slash:comments>
555 </item>
556 <item>
557 <title>Looking back at TPAC 2022</title>
558 <pubDate>Mon, 17 Oct 2022 08:29:00 +0000</pubDate>
559 <link>https://www.w3.org/blog/2022/looking-back-at-tpac-2022/</link>
560 <guid>https://www.w3.org/blog/2022/looking-back-at-tpac-2022/</guid>
561 <author>Xueyuan Jia</author>
562 <comments>https://www.w3.org/blog/2022/looking-back-at-tpac-2022/#comments</comments>
563 <category><![CDATA[events]]></category>
564 <category><![CDATA[blogs]]></category>
565 <dc:creator>Xueyuan Jia</dc:creator>
566 <content:encoded><![CDATA[<div class="component component--text">
567 <p><a href="https://www.w3.org/2022/09/TPAC/"><img alt="TPAC 2022" src="https://www.w3.org/2022/09/TPAC/images/TPAC-2022-cover.svg" /></a></p>
568
569 <p>W3C's annual conference <a href="https://www.w3.org/2022/09/TPAC/Overview.html">TPAC 2022</a> concluded in September when our Community was able to meet in person for the first time in three years.</p>
570
571 <p>The conference was in hybrid format. The main in-person hub was in Vancouver, Canada, with over 360 on-site participants. Meanwhile, TPAC 2022 fully included the remote participants in our meetings and offered them the possibility to be participate actively in the discussion.</p>
572
573 <p><strong>What attendees said - How TPAC 2022 went</strong></p>
574
575 <p><i>“TPAC is taking Covid measures extremely seriously.” </i><br />
576 Our Events Planning team always puts the safety and experience of attendees at the very first place. They worked hard to set up appropriate health rules, carefully taking into account various requirements such as the evolution on the health situation and its impact on the attendees.</p>
577
578 <p>"<em>Just really nice to see everyone again and have somewhat organic conversations over some coffee or a lunch, or during a walk</em>." - Though hallway and informal conversations are the main TPAC assets, this year we gave higher priority to making sure TPAC was a safe place and therefore had to limit the contacts among participants. To support attendees' social demands to the biggest extent, lunches and breaks were more staggered than usual and attendees were given the option to have their breaks and meals outdoors.</p>
579
580 <p><em>"Also the organizers did an awesome job ensuring people could participate in every meeting remotely."</em> - Provided by our technical support team, audio and video equipment was available in each meeting room ensuring a good experience both for onsite and remote participants. The remote participants were also able to attend the plenary sessions which have been video-broadcasted.</p>
581
582 <p><em>"It’s great to see so many important players gather around the same table..."</em> - The event brought together W3C technical groups, the W3C Advisory Board, TAG, Advisory Committee, and the public, to network and work to resolve challenging technical and social issues. During TPAC 2022, the Working Groups, Interest Groups, and Community Groups held 90 meetings gathering a global community of web developers, architects, and product teams to advance standards development on emerging web technologies, to make the web work for everyone.</p>
583
584 <p>The technical plenary day, consisting of <a href="https://www.w3.org/2022/09/TPAC/breakouts.html">45 breakout sessions</a>, offered a great opportunity for everyone to meet and liaise, brainstorm ideas, and coordinate on a wide variety of topics relating to W3C activities, ranging from Web Components, Privacy, Accessibility, WoT, Open UI, Web Monetization, Digital Twins, WebViews, Trusted Web, Multicast, Web3, Sustainability, W3Cx Online Courses, Web Developer Experience, W3C Member Support, just to name a few.</p>
585
586 <p>During the AC open session, W3C CEO Jeff Jaffe presented “W3C Strategy, past, present, and future” on the <a href="/press-releases/2022/w3c-le/">W3C launch as a new legal entity</a> in January 2023, and the AB proactively communicated with members about the transition plan and progress.</p>
587
588 <p>The Developer Meetup gathered the global Web community to coordinate the development of Web standards, and delivered four talks during the event, which illustrated how W3C community paves the path of creating solid Web standards, from incubating an idea to a deployed standard that people can reliably use and adopt. See more in <a href="/blog/2022/w3c-devmeetup-2022-vancouver-report/">W3C DevMeetup report – Vancouver, 2022</a>.</p>
589
590 <p>Given the travel restrictions and time differences, W3C/Beihang Host organized a <a href="https://tpac2022-china-hub.netlify.app/#/">TPAC China Hub</a> in Hangzhou to provide an in-person gathering place to support sessions that are particularly relevant to the Chinese community, covering topics around metaverse & Web 3.0, multimedia & WebTransport, Web Editing, MiniApps and Accessibility. The Chinese Member meeting also debriefed about the W3C Legal Entity transition plan and its potential impact.</p>
591
592 <p><strong>Next meetings</strong></p>
593
594 <p>We are looking forward to the next annual conference, which will be held in Europe. More information coming soon.</p>
595 </div>]]></content:encoded>
596 <slash:comments>0</slash:comments>
597 </item>
598 <item>
599 <title>W3C DevMeetup report - Vancouver, 2022</title>
600 <pubDate>Thu, 06 Oct 2022 17:37:00 +0000</pubDate>
601 <link>https://www.w3.org/blog/2022/w3c-devmeetup-2022-vancouver-report/</link>
602 <guid>https://www.w3.org/blog/2022/w3c-devmeetup-2022-vancouver-report/</guid>
603 <author>Marie-Claire Forgue</author>
604 <comments>https://www.w3.org/blog/2022/w3c-devmeetup-2022-vancouver-report/#comments</comments>
605 <category><![CDATA[developers]]></category>
606 <category><![CDATA[blogs]]></category>
607 <dc:creator>Marie-Claire Forgue</dc:creator>
608 <content:encoded><![CDATA[<div class="component component--text">
609 <p><a href="https://www.w3.org/2022/09/meetup/"><img alt="Visual for the W3C Developer meetup, organized by W3C Developer Relations team, on 13 Sept. 2022, in Vancouver, Canada. The graphics represents Vancouver's skyline at twilight" loading="lazy" src="https://www.w3.org/2022/09/meetup/images/twitter-card-homepage.jpg" width="500" /></a></p>
610
611 <p>On September 13, 2022, in Vancouver BC, Canada, the W3C developer relations team organized a <a href="https://www.w3.org/2022/09/meetup/" rel="noopener noreferrer" target="_blank">developer meetup</a> as part of the annual <a href="https://www.w3.org/2022/09/TPAC/" rel="noopener noreferrer" target="_blank">W3C TPAC2022</a> (Technical Plenary / Advisory Committee) week for the global Web community to coordinate the development of Web standards.</p>
612
613 <p>Today, we are pleased to share the recorded videos of the four talks that were delivered during the event. They illustrate how W3C community paves the path of creating solid Web standards, from incubating an idea to a deployed standard that people can reliably use and adopt. Each of these videos come accompanied by their transcripts and the set of slides the speakers used:</p>
614
615 <ul>
616 <li><strong>Greg Whitworth</strong> (SalesForce) related the research and incubation work happening in the <a href="https://www.w3.org/community/open-ui/" rel="noopener" target="_blank">W3C Open UI Community Group</a> [<a href="https://www.w3.org/2022/09/meetup/speaker-greg.html" rel="noopener" target="_blank"><img alt="Icon of a video camera" src="https://upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Video_Camera_Icon.svg/256px-Video_Camera_Icon.svg.png" width="20" /> video</a>, <a href="https://www.w3.org/2022/09/meetup/speaker-greg.html#transcript" rel="noopener" target="_blank">transcript</a>, <a href="https://www.w3.org/2022/09/meetup/Greg-Whitworth-Open-UI.pdf" rel="noopener" target="_blank">slides</a>].</li>
617 <li><strong>Aram Zucker-Scharff</strong> (The Washington Post) gave an overview of the work done in the Private Advertising Technology Community Group, as it is transitioning into a more formal part of the standardization process [<a href="https://www.w3.org/2022/09/meetup/speaker-aram.html" rel="noopener" target="_blank"><img alt="Icon of a video camera" src="https://upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Video_Camera_Icon.svg/256px-Video_Camera_Icon.svg.png" width="20" /> video</a>, <a href="https://www.w3.org/2022/09/meetup/speaker-aram.html#transcript" rel="noopener" target="_blank">transcript</a>, <a href="https://www.w3.org/2022/09/meetup/aram.pdf" rel="noopener" target="_blank">slides</a>].</li>
618 <li>Within the standardization track, new CSS features are emerging from the <a href="https://www.w3.org/groups/wg/css" rel="noopener" target="_blank">W3C CSS Working Group</a> and <strong>Miriam Suzanne</strong> (W3C Invited Expert) demonstrated what intrinsic Web design allows as an evolution of responsive Web design and where container queries & units play an important role [<a href="https://www.w3.org/2022/09/meetup/speaker-miriam.html" rel="noopener" target="_blank"><img alt="Icon of a video camera" class="alignnone " src="https://upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Video_Camera_Icon.svg/256px-Video_Camera_Icon.svg.png" width="20" /> video </a>, <a href="https://www.w3.org/2022/09/meetup/speaker-miriam.html#transcript" rel="noopener" target="_blank">transcript</a>, <a href="https://slides.oddbird.net/queries-units/tpac22/" rel="noopener" target="_blank">slides</a>].</li>
619 <li>Finally, illustrating the work that remains to be done once Web standards are well developed, <strong>Rachel Andrew</strong> (Google) presented the <a href="https://web.dev/interop-2022/" rel="noopener" target="_blank">Interop 2022 initiative</a> which aims to make specified web platform features work exactly the same across browsers, a key requirement Web developers have before they can adopt new features [<a href="https://www.w3.org/2022/09/meetup/speaker-rachel.html" rel="noopener" target="_blank"><img alt="Icon of a video camera" class="alignnone " src="https://upload.wikimedia.org/wikipedia/commons/thumb/b/b4/Video_Camera_Icon.svg/256px-Video_Camera_Icon.svg.png" width="20" /> video</a>, <a href="https://www.w3.org/2022/09/meetup/speaker-rachel.html#transcript" rel="noopener" target="_blank">transcript</a>, <a href="https://noti.st/rachelandrew/ycqiM9/interop-2022" rel="noopener" target="_blank">slides</a>].</li>
620 </ul>
621
622 <p>This event was made possible thanks to the support of our sponsors, to which we want to express again our gratitude: <a href="https://www.yubico.com/" rel="noopener" target="_blank">Yubico</a>, <a href="https://www.igalia.com/" rel="noopener" target="_blank">Igalia</a>, <a href="https://developer.samsung.com/internet" rel="noopener" target="_blank">Samsung Internet</a>, <a href="https://fortunetimesgroup.com/" rel="noopener" target="_blank">FTG</a>, <a href="https://withyou.fr/" rel="noopener" target="_blank">WithYou</a> and <a href="https://legible.com/" rel="noopener" target="_blank">Legible</a>.</p>
623
624 <p><img alt="Thank you to the W3C DevMeetup in Vancouver sponsors: Igalia, Samsung Internet, Yubico, FTG, Legible and WithYou" src="https://www.w3.org/2022/09/meetup/images/twitter-card-sponsors.jpg" /></p>
625
626 <p><em>Follow us on <a href="https://twitter.com/w3cdevs" rel="noopener noreferrer" target="_blank">@w3cdevs</a> and subscribe to our <a href="https://www.youtube.com/W3COfficial" rel="noopener" target="_blank">YouTube channel</a> to track new Web technology development, and to learn of opportunities to contribute to W3C work!</em></p>
627 </div>]]></content:encoded>
628 <slash:comments>0</slash:comments>
629 </item>
630 <item>
631 <title>TPAC Recap (2022 Edition)</title>
632 <pubDate>Thu, 06 Oct 2022 13:45:18 +0000</pubDate>
633 <link>https://www.w3.org/blog/2022/tpac-recap-2022-edition/</link>
634 <guid>https://www.w3.org/blog/2022/tpac-recap-2022-edition/</guid>
635 <author>Ian Jacobs</author>
636 <comments>https://www.w3.org/blog/2022/tpac-recap-2022-edition/#comments</comments>
637 <category><![CDATA[events]]></category>
638 <category><![CDATA[blogs]]></category>
639 <dc:creator>Ian Jacobs</dc:creator>
640 <content:encoded><![CDATA[<div class="component component--text">
641 <p>After a three-year hiatus, W3C held TPAC 2022 in person in Vancouver. It was really great to be back in person, and I heard that sentiment from just about everyone. More than 360 people registered to attend TPAC in person and another 250 joined remotely.
642 </p><p>
643 Below I summarize discussions of the meetings I attended: the Web Payments Working Group, the Web Payment Security Interest Group, and joint meetings with the Web Authentication Working Group and the Antifraud Community Group.
644 </p><p>
645 <h3>Web Payments Working Group</h3>
646 <p>
647 The Web Payments Working Group agenda opened with a focus on Secure Payment Confirmation (<a href="https://www.w3.org/2022/09/12-wpwg-minutes.html">12 September minutes</a>):
648 </p>
649 <ul>
650 <li>Adyen and Airbnb shared some information about their SPC pilot. The discussion led us to topics such as the importance of user education (for the new user experience), some ideas for the timing of user registration (post-transaction), and the potential value of sharing a FIDO attestation when using SPC in a delegated authentication flow.</li>
651 <li>Google presented their current work to bring SPC to Chrome on Android. That led to discussion about (and strong interest in) SPC availability beyond browsers in native Android apps.</li>
652 <li>FIS shared thoughts on three topics of interest: shops making the transition from brick and mortar to digital-first, online stores looking to create a seamless shopping experience, and merchants that prefer strong control over the user experience. Across these topics there were three main themes:
653 <ul>
654 <li>Merchants want to know who their customers are prior to authorization. On this point we discussed the impact of tokenization and potential benefits of ensuring that the Payment Account Reference (PAR) can be communicated during an EMV® 3-D Secure transaction that involves SPC.</li>
655 <li>Data is not always available based on payment types or implementations.</li>
656 <li>Cart abandonment is a problem due to extra friction and payment problems.</li>
657 </ul>
658 </li>
659 <li>Microsoft shared some perspectives as a merchant that adopted strong customer authentication in Europe. They emphasized the important of frictionless authentication and indicated (as FIS also indicated) that stronger authentication can lead to cart abandonment; see the <a href="http://www.w3.org/2022/Talks/dean-jordaan-20220912.pdf">Microsoft slides</a> for details. Key takeaways were thus that a great SCA user experience is very important (hence our emphasis on SPC) but that frictionless risk assessment is still very important. Microsoft reiterated during the talk that merchants do not like to hand over the authentication experience to banks, which, to me, reinforced the value proposition of SPC where merchant controls the authentication ceremony, and the bank can still validate the results.</li>
660 <li>We then revisited some EMVCo observations about SPC and some changes that the EMVCo 3-D Secure Working Group has requested, including support for non-payments use cases, recurring payments, and more alignment with user experience requirements defined in the EMV® 3-D Secure specification.</li>
661 </ul>
662 <p>
663 We opened the second day of the WPWG meeting (<a href="https://www.w3.org/2022/09/13-wpwg-minutes">13 September minutes</a>) with discussion about the Payment Request API, which advanced to Recommendation just before the start of TPAC. Both Apple and Google expressed interest in restoring some capabilities related to address collection that are implemented in their respective browsers, but that were removed from version 1 of the specification for privacy-related reasons. I expect the features will be re-introduced so that interoperable implementations are documented, even if not recommended in their current form. The Working Group is likely to try to evolve the feature to address the previously registered privacy concerns.
664 </p><p>
665 After that:
666 </p>
667 <ul>
668 <li>Apple then described some changes to ApplePay.js over the past couple of years that could be integrated into Payment Request. This was useful for helping the group develop a potential roadmap for new work on the API.</li>
669 <li>We then discussed some upcoming changes to browsers related to "<a href="https://github.com/wanderview/bounce-tracking-mitigations/blob/main/explainer.md">Bounce Tracking Mitigations</a>." Bounce tracking refers to very quick redirects from one site to another and back, usually without the user knowing that the redirect has happened. As with previous discussions about privacy-related changes to browsers (e.g., IP address masking, user agent string masking, removal of third party cookies) we discussed the likely impact on user recognition and fraud prevention.</li>
670 <li>In the same vein, we then heard about changes that the Chrome team plans to make to their Payment Handler implementation based on other changes on the Web related to privacy. The theme of data collection and risk mitigation continued into the Thursday joint meeting (below).</li>
671 </ul>
672 <p>
673 <h3>Tuesday Joint Meeting</h3>
674 <p>
675 On Tuesday afternoon, four groups met: the Web Payments WG, the Web Payment Security IG, the Web Authentication WG, and the Antifraud CG (<a href="https://docs.google.com/document/d/1W6uCLSI5ZEJf35_mnUrc-PgLViLHv7ajetyiU_zXFlM/edit">13 September joint meeting minutes</a>):
676 </p>
677 <ul>
678 <li>The <a href="https://www.w3.org/community/antifraud/">Antifraud CG, launched in early 2022</a>, has developed as set of <a href="https://github.com/antifraudcg/use-cases/blob/main/USE-CASES.md">use cases</a>; these include both payments and advertising use cases. <a href="https://github.com/antifraudcg/proposals/issues">Proposals</a> to address these use cases are emerging, and we heard about several of them during the joint meeting, in particular about <a href="https://github.com/antifraudcg/proposals/issues/8">device integrity attestations</a>. We also discussed <a href="https://github.com/antifraudcg/proposals/issues/7">trust tokens</a>, currently in development in the Web Incubator CG.</li>
679 <li>The Web Authentication Working Group summarized the state of specification and deployment of passkeys (cross-device FIDO credentials) and device public keys. I have the impression that device public keys —not yet implemented— could play an important role in payments use cases so that a Relying Party make make risk decisions based on previously seen devices. Those decisions may also rely on attestation availability, and it was pointed out that attestations are optional with Device Public Keys and may not always be available. We then discussed technology developments around a user experience question that we've heard before: if, for privacy reasons, a party cannot query the browser to determine whether the user has already enrolled credentials, how does that party know when to offer the user a registration experience?</li>
680 <li>In the final session of the joint meeting, we discussed the status of SPC and broached several topics of ongoing coordination with the Web Authentication WG. We heard that our proposed "cross-origin bit" is now part of FIDO CTAP (and will be made public soon). The Web Payments Working Group next needs to register the extension with IANA. The WPWG re-raised the topic of <a href="https://github.com/w3c/webauthn/issues/1656#issuecomment-1219682589">cross-origin credential creation</a>, which is permitted in SPC but not in Web Authentication. While there is some support within the Web Authentication WG to reconsider this capability in Web Authentication Level 3, there is not yet consensus.</li>
681 </ul>
682 <p>
683 Antifraud discussion, in particular about Device Public Keys used for fraud prevention, continued during a <a href="https://docs.google.com/document/d/1W6uCLSI5ZEJf35_mnUrc-PgLViLHv7ajetyiU_zXFlM/edit">Wednesday breakout on Antifraud</a>.
684 </p>
685 <h3>Thursday Joint Meeting</h3>
686 <p>
687 On Thursday, both the Web Payment Security Interest Group and the Antifraud Community Group held individual meetings as well as a 90-minute joint session on patterns of payment fraud (<a href="https://www.w3.org/2022/09/15-wpsig-public-minutes.html">15 September WPSIG/Antifraud minutes</a>):
688 </p>
689 <ul>
690 <li>Entersekt presented some payment fraud patterns (e.g., account takeover through phishing, SIM swap, or social engineering; chargeback fraud, and card skimming attacks). We discussed current mitigation techniques (e.g., IP address monitoring) with attention to how those might be affected by privacy-related changes to browsers. As it was put in the meeting, "Browser fingerprinting is not good enough anymore." Our colleagues from Entersekt evaluated some of the <a href="https://github.com/antifraudcg/proposals/issues">Antifraud CG Proposals</a> in development to see which might help with payments fraud use cases. I anticipate we will soon discuss a proposed new risk signal based on the joint discussion.</li>
691 <li>Our colleague from the University of Illinois Chicago presented findings from research <a href="https://www.usenix.org/conference/usenixsecurity22/presentation/lin-xu">Phish in Sheep's Clothing: Exploring the Authentication Pitfalls of Browser Fingerprinting</a>. One interpretation of the research is that it illustrates the limits of current approaches data collection used for payment fraud mitigation.</li>
692 </ul>
693 <p>
694 We made good progress at TPAC in understanding use cases, formulating the value proposition of SPC, and emphasizing the need for more fraud prevention tools (with some useful whiteboarding in the mix). I anticipate the groups will want to meet again in person well before TPAC 2023.
695 </p>
696 </div>]]></content:encoded>
697 <slash:comments>0</slash:comments>
698 </item>
699 <item>
700 <title>Preparing for TPAC 2022</title>
701 <pubDate>Fri, 09 Sep 2022 20:38:01 +0000</pubDate>
702 <link>https://www.w3.org/blog/2022/preparing-for-tpac-2022/</link>
703 <guid>https://www.w3.org/blog/2022/preparing-for-tpac-2022/</guid>
704 <author>Ian Jacobs</author>
705 <comments>https://www.w3.org/blog/2022/preparing-for-tpac-2022/#comments</comments>
706 <category><![CDATA[events]]></category>
707 <category><![CDATA[blogs]]></category>
708 <dc:creator>Ian Jacobs</dc:creator>
709 <content:encoded><![CDATA[<div class="component component--text">
710 <p>
711 <a href="https://www.w3.org/2022/09/TPAC/">TPAC 2022</a> will be a hybrid event: in-person in Vancouver, with remote participation. I believe more than 600 people have registered, and it looks like more than 350 people will attend in person. This will be my first in-person meeting in about 3 years.
712 </p>
713 <p>
714 I have been working with multiple groups on a coordinated agenda about payments, authentication, and fraud prevention:
715 </p>
716 <ul>
717 <li>
718 Monday and Tuesday morning: <a href="https://github.com/w3c/webpayments/wiki/Agenda-TPAC2022">Web Payments Working Group</a>
719 </li>
720 <li>
721 Tuesday afternoon: <a href="https://docs.google.com/document/d/1Bxm7_gc-Wi7ZjWlgOMPbq3Kdv0L3lgvkkcVaQIFgPx8/edit#heading=h.dvz4zyoilau4">joint meeting</a> of WPWG, Web Payment Security Interest Group, Web Authentication WG, and Antifraud CG
722 </li>
723 <li>
724 Wednesday afternoon: <a href="https://www.w3.org/2022/09/TPAC/breakouts.html">Breakout sessions</a>
725 </li>
726 <li>
727 Thursday: <a href="https://www.w3.org/securepay/wiki/Meeting/Sep2022">Web Payment Security IG</a>, with joint discussion about payment fraud patterns with the Antifraud CG. That agenda link requires W3C Member access.
728 </li>
729 </ul>
730 <p>
731 I'm looking forward to discussion about Secure Payment Confirmation (SPC). We expect to hear about a pilot from Airbnb/Adyen, emerging support for SPC on Android, and other industry perspectives about the current version as well as next use cases.
732 </p>
733 <p>
734 I'll summarize the meetings in a few weeks!
735 </p>
736 </div>]]></content:encoded>
737 <slash:comments>0</slash:comments>
738 </item>
739 <item>
740 <title>W3C Accessibility Maturity Model</title>
741 <pubDate>Fri, 09 Sep 2022 06:23:00 +0000</pubDate>
742 <link>https://www.w3.org/blog/2022/w3c-accessibility-maturity-model/</link>
743 <guid>https://www.w3.org/blog/2022/w3c-accessibility-maturity-model/</guid>
744 <author>Ruoxi Ran</author>
745 <comments>https://www.w3.org/blog/2022/w3c-accessibility-maturity-model/#comments</comments>
746 <category><![CDATA[accessibility]]></category>
747 <category><![CDATA[blogs]]></category>
748 <dc:creator>Ruoxi Ran</dc:creator>
749 <content:encoded><![CDATA[<div class="component component--text">
750 <p>Why Does Accessibility Need a <a href="https://www.w3.org/TR/maturity-model/">Maturity Model</a>?</p>
751
752 <p>It’s not enough to get a product accessible. The entire product experience should be accessible, and organizations need to implement processes and systems that can objectively measure whether the correct steps have been taken to keep the product experience accessible. This maturity model additionally includes employee-facing communications, training, documentation, and tools. Incorporating Information and Communications Technology (ICT) accessibility into an organization’s workflow and quality governance can be a complex process. While some organizations have individuals or departments that support accessibility, many do not yet recognize the importance of ICT accessibility as a requirement or the need for accessibility governance systems. This can limit these organizations’ ability to produce accessible products and services and their associated training and documentation on an ongoing basis.</p>
753
754 <p>In an organization of moderate or large size, no one department can be responsible for accessibility. It takes a collaborative effort from numerous departments to establish and implement accessibility governance systems throughout the organization. These systems integrate ICT accessibility criteria into policies, key business processes, organizational culture, and management structures in a consistent, repeatable, and measurable fashion. Only then can organizations address the complexities related to enabling ICT accessibility on an ongoing basis.</p>
755
756 <p>Maturity models have been around since the 80s. They generally contain a number of levels with increasing levels of maturity. Each level contains a definition, controls, a list of processes, and proof points that can be produced for an organization to legitimately claim that they are at a particular level of maturity.</p>
757
758 <p>This proposed <a href="https://www.w3.org/TR/maturity-model/">W3C Accessibility Maturity Model</a> describes an overall framework for establishing a robust, repeatable ICT accessibility program and identifying areas for organizational improvement. The W3C Accessibility Maturity Model is a tool that:</p>
759
760 <ul>
761 <li>helps people, groups, or organizations assess their accessibility practices</li>
762 <li>identifies gaps between the current capabilities and the next level of accessibility maturity</li>
763 <li>encourages improving overall accessibility performance over time</li>
764 </ul>
765
766 <p>Accessibility Conformance Reports / Voluntary Product Accessibility Templates (ACR/VPATs) look at a snapshot of single version of a product frozen in a point of time. There are no guarantees about the accessibility of that product later in the product release timeline because ACR/VPATs don’t assess whether accessibility can be repeated.</p>
767
768 <p>Organizations know when they are doing well (or poorly) with product accessibility using audit reports and bug counts. However, these metrics don’t indicate how the organization is doing operationally to continue to produce accessible products. Examining key corporate processes is critical to making this determination, and ACR/VPATs, audits, and defects don’t do that. The W3C Accessibility Maturity Model is a big part of a “shift-left” methodology of preventing problems from recurring, not fixing them after they have happened.</p>
769
770 <p>Accessibility maturity modeling is very different than accessibility conformance testing</p>
771
772 <ul>
773 <li>Conformance testing provides information about the level of accessibility conformance of a particular product at a particular time. The results of a conformance test provide a picture of a particular version of a product (or a subcomponent of a product).</li>
774 <li>Maturity modeling provides information about the ability of an organization to produce accessible products over the long term. The results of a maturity modeling assessment provide a holistic picture of an organization’s accessibility initiatives; where the organization is doing accessibility well and where improvements can be made to remove barriers.</li>
775 </ul>
776
777 <p>We encourage people and organizations who could benefit from implementing the <a href="https://www.w3.org/TR/maturity-model/">W3C Accessibility Maturity Model</a> to review the Group Note and provide comments back to help us refine and improve the document.</p>
778 </div>]]></content:encoded>
779 <slash:comments>5</slash:comments>
780 </item>
781 <item>
782 <title>W3C Developer meetup in Vancouver, Canada, 13 September</title>
783 <pubDate>Tue, 30 Aug 2022 15:40:00 +0000</pubDate>
784 <link>https://www.w3.org/blog/2022/w3c-developer-meetup-in-vancouver-canada-13-september/</link>
785 <guid>https://www.w3.org/blog/2022/w3c-developer-meetup-in-vancouver-canada-13-september/</guid>
786 <author>Marie-Claire Forgue</author>
787 <comments>https://www.w3.org/blog/2022/w3c-developer-meetup-in-vancouver-canada-13-september/#comments</comments>
788 <category><![CDATA[developers]]></category>
789 <category><![CDATA[blogs]]></category>
790 <dc:creator>Marie-Claire Forgue</dc:creator>
791 <content:encoded><![CDATA[<div class="component component--text">
792 <p><a href="https://www.w3.org/2022/09/meetup/"><img alt="Stylized skyline of Vancouver, Canada, at night to announce the W3C Developer meetup to happen on 13 September 2022 from 6pm to 8:45 pm Pacific Time." loading="lazy" src="https://www.w3.org/2022/09/meetup/images/twitter-card-homepage.jpg" width="500" /></a></p>
793
794 <p>W3C invites the vibrant Vancouver-based tech community to its <a href="https://www.w3.org/2022/09/meetup/" rel="noopener" target="_blank">Developer meetup</a>, on <strong>Tuesday 13 September 2022 (6:00 -8:45pm PT)</strong>. This event is <strong>free of charge</strong> but <a href="https://ti.to/w3c/w3c-developer-meetup-vancouver-2022" rel="noopener" target="_blank">registration</a> is mandatory and operates under <a href="https://www.w3.org/2022/09/meetup/venue.html#covid" rel="noopener" target="_blank">COVID-19 health rules</a>.</p>
795
796 <p>We are very much looking forward to connecting with local developers, designers, product and project managers, etc., who are interested to learn about Web standards under development, as well new initiatives put forward to shape the future of an even better Web.</p>
797
798 <h3>A great line-up of speakers</h3>
799
800 <p>As an opportunity to discover and learn what is making the Web an exciting development platform, we are proud to introduce this year’s <a href="https://www.w3.org/2022/09/meetup/speakers.html" target="_blank">devmeetup speakers</a>:</p>
801
802 <ul>
803 <li><b>Rachel Andrew</b>, technical writer at Google, will explain how the <a href="https://www.w3.org/2022/09/meetup/speaker-rachel.html" rel="noopener" target="_blank">Interop 2022 effort</a> will improve the experience of developing for the web in key areas.</li>
804 <li><b>Aram Zucker-Scharff</b>, The Washington Post, will explain the ambition of the proposed <a href="https://lists.w3.org/Archives/Public/public-new-work/2022Aug/0003.html" rel="noopener" target="_blank">Private Advertising Technology Working Group</a> to specify web features and APIs that support advertising while acting in the interests of users, in particular providing strong privacy assurances.</li>
805 <li><b>Miriam Suzanne</b>, W3C Invited Expert, will show how CSS Container Queries have a lot to offer, how to start using them in production, and what to look forward to as <a href="https://www.w3.org/2022/09/meetup/speaker-miriam.html" rel="noopener" target="_blank">Container Queries continue to evolve</a>.</li>
806 <li>In “Open UI: unlocking creativity”, <b>Greg Whitworth</b>, Sr. Director of Product on the Web and Mobile Platform team at Salesforce, will present the <a href="https://www.w3.org/2022/09/meetup/speaker-greg.html" rel="noopener" target="_blank">Open UI initiative</a> under the auspices of the <a href="https://www.w3.org/community/open-ui/" rel="noopener" target="_blank">W3C Open UI community group</a> to allow web developers to style and extend built-in web UI controls.</li>
807 </ul>
808
809 <h3>Thanks to our sponsors!</h3>
810
811 <p><img alt="Thank you to the 2022 Developer meetup in Vancouver 2022: Igalia, Samsung Internet, Yubico, Legible, FTG and WithYou." class="aligncenter" loading="lazy" src="https://www.w3.org/2022/09/meetup/images/twitter-card-sponsors.jpg" /></p>
812
813 <p>Follow us on <a href="https://twitter.com/w3cdevs"><strong>@w3cdevs</strong> </a> to read more about our speakers and discover <a href="https://www.w3.org/2022/09/meetup/demos.html" rel="noopener" target="_blank">sponsors’ demos</a> between now and the <a href="https://twitter.com/search?q=%23w3cdevs2022" rel="noopener noreferrer" target="_blank">#w3cdevs2022</a> meetup.</p>
814 </div>]]></content:encoded>
815 <slash:comments>0</slash:comments>
816 </item>
817 <item>
818 <title>Observations from our initial https redirection tests</title>
819 <pubDate>Mon, 22 Aug 2022 18:56:00 +0000</pubDate>
820 <link>https://www.w3.org/blog/2022/https-redirection-observations/</link>
821 <guid>https://www.w3.org/blog/2022/https-redirection-observations/</guid>
822 <author>Gerald Oskoboiny</author>
823 <comments>https://www.w3.org/blog/2022/https-redirection-observations/#comments</comments>
824 <category><![CDATA[systems]]></category>
825 <category><![CDATA[blogs]]></category>
826 <dc:creator>Gerald Oskoboiny</dc:creator>
827 <content:encoded><![CDATA[<div class="component component--text">
828 <p>We recently announced that we are <a href="https://www.w3.org/blog/2022/07/redirecting-to-https-on-www-w3-org/">planning to start redirecting all of www.w3.org to https</a>, as is commonly done elsewhere.</p>
829
830 <p>To get an understanding of whether this change is feasible for our site and what issues might arise, we conducted some limited tests of this configuration change, on <a href="https://status.w3.org/incidents/mhn7p58hbfwc">August 1</a> and <a href="https://status.w3.org/incidents/dhv59mm7kdw6">August 18-19</a>.</p>
831
832 <p>Here are some notes on what we have learned so far, and answers to some questions we have received.</p>
833
834 <p>We receive a lot of automated requests for machine-readable resources on our site and have for many years, see for example <a href="https://www.w3.org/blog/2008/02/w3c_s_excessive_dtd_traffic/">this blog post from 2008</a>. Due to the huge amount of traffic (hundreds of millions of requests per day) and the generic user-agent headers that are commonly in use (for example <code>Java/xx</code>), it’s hard to identify the source of most of this traffic. Also the generic user-agent strings make it difficult to do targeted outreach to the developers of the software making these requests.</p>
835
836 <p>Therefore we decided to do some limited tests of redirecting our entire site to https so any issues could be discovered and understood. We weren’t sure if this would only impact a handful of people who could easily adapt with some simple configuration changes, or if it had the possibility of being more disruptive.</p>
837
838 <p>During our initial tests we heard from a few people that this was causing issues with their systems that make automated requests to our site, for example when doing XML Schema validation. We are hoping these systems can be reworked to either follow the redirects to https, or use an XML catalog to keep local copies of any files needed to avoid making unnecessary requests to our site.</p>
839
840 <p>Questions we have received include: what action are we expecting from Web developers? Is it necessary to update all references starting with <code>http://www.w3.org/</code> to <code>https</code>?</p>
841
842 <p>In general that is not necessary, and in fact in many cases those references to our site starting with <code>http://www.w3.org/</code> must be preserved exactly as is, for example in a reference to an XML namespace that must be an exact match for a given string.</p>
843
844 <p>If you maintain a software system that retrieves resources from www.w3.org, please check whether it has the ability to handle redirects and https and update the software if needed. Also consider carefully whether you want to keep this dependency on our site or if it would be worthwhile to rework your systems to remove it, for example using an XML catalog. We do our best to keep our systems available and performant but we have occasional service outages like any other site. We expect most people would not want their production systems to be impacted by issues with our site.</p>
845
846 <p>We plan to continue limited tests of this change to our site over the coming weeks and months to gather more feedback in order to understand its impact before deploying it more permanently. Depending on the results of these tests we may decide to defer this change until more software can be updated, or deploy it with specific exceptions for example continuing to serve .xsd files via HTTP while redirecting the rest of the site.</p>
847
848 <p>To stay informed of future tests and other updates to our systems please stay tuned to our <a href="https://status.w3.org/">systems status page</a>.</p>
849 </div>]]></content:encoded>
850 <slash:comments>10</slash:comments>
851 </item>
852 <item>
853 <title>Redirecting to https on all of www.w3.org</title>
854 <pubDate>Mon, 25 Jul 2022 19:54:00 +0000</pubDate>
855 <link>https://www.w3.org/blog/2022/redirecting-to-https-on-www-w3-org/</link>
856 <guid>https://www.w3.org/blog/2022/redirecting-to-https-on-www-w3-org/</guid>
857 <author>Gerald Oskoboiny</author>
858 <comments>https://www.w3.org/blog/2022/redirecting-to-https-on-www-w3-org/#comments</comments>
859 <category><![CDATA[systems]]></category>
860 <category><![CDATA[blogs]]></category>
861 <dc:creator>Gerald Oskoboiny</dc:creator>
862 <content:encoded><![CDATA[<div class="component component--text">
863 <p>W3C's main web site <code><a href="https://www.w3.org/">www.w3.org</a></code> has been available via <code>https</code> for over a decade, but until now we have not been redirecting all requests to <code>https</code> as is commonly done on most other sites.</p>
864
865 <p>The primary reason for this is that we wanted to avoid causing issues for software requesting machine-readable resources from <code><a href="https://www.w3.org/">www.w3.org</a></code> such as HTML DTDs, XML Schemas, and namespace documents.</p>
866
867 <p>We believe enough time has passed for most such software to have been updated to handle redirects and https, so we are planning to start redirecting all requests received over <code>http</code> to <code>https</code> within a month or two.</p>
868
869 <p>In order to discover any potential remaining issues and to give some advance notice in case there are software systems that still have issues with redirects and https, we plan to conduct some limited tests before fully deploying this change to our site, where we redirect all http traffic to https for a few hours at a time.</p>
870
871 <p>The first such test is planned for Monday August 1, for 8 hours starting at 14:00 UTC (14:00 UTC to 22:00 UTC)</p>
872
873 <p>Update 16 Aug 2022: The second test is planned to run from Thursday August 18 to Sunday August 21, for 72 hours starting at 14:00 UTC on Thursday.</p>
874
875 <p>Update 19 Aug 2022: We ended the second test early, at 17:30 UTC today due to several complaints that this change was impacting production services. We plan to conduct another test in two weeks, for 48 hours starting at 17:00 UTC on Sep 1, ending at 17:00 UTC Sep 3. If you have dependencies on our web site in your production services please work to remove them, or update them to handle redirections and https.</p>
876
877 <p>If you have any questions or comments about this planned change, please post a comment here or contact us by email at <a href="mailto:sysreq@w3.org">sysreq@w3.org</a></p>
878 </div>]]></content:encoded>
879 <slash:comments>32</slash:comments>
880 </item>
881 <item>
882 <title>Accessibility of Remote Meetings Published as W3C Group Note</title>
883 <pubDate>Fri, 22 Jul 2022 07:07:00 +0000</pubDate>
884 <link>https://www.w3.org/blog/2022/accessibility-of-remote-meetings-published-as-w3c-group-note/</link>
885 <guid>https://www.w3.org/blog/2022/accessibility-of-remote-meetings-published-as-w3c-group-note/</guid>
886 <author>Ruoxi Ran</author>
887 <comments>https://www.w3.org/blog/2022/accessibility-of-remote-meetings-published-as-w3c-group-note/#comments</comments>
888 <category><![CDATA[accessibility]]></category>
889 <category><![CDATA[blogs]]></category>
890 <dc:creator>Ruoxi Ran</dc:creator>
891 <content:encoded><![CDATA[<div class="component component--text">
892 <p>W3C WAI announces publication of the Group Note <strong><a href="https://www.w3.org/TR/remote-meetings/">Accessibility of Remote Meetings</a></strong>. It is a companion to the more succinct W3C resource: <strong><a href="https://www.w3.org/WAI/teach-advocate/accessible-presentations/">How to Make Your Presentations and Meetings Accessible to All</a></strong>.</p>
893
894 <p>The impact of COVID-19 has seen a substantial increase in usage of remote meeting platforms. Before 2020, software-based remote meeting applications were available, but not necessarily viewed as critical. The shift to remote meetings from a complementary tool to a replacement for face-to-face contact, has driven significant innovation in this space, including improvements in the provision of accessibility for people with disabilities. More recently, hybrid meetings, combining in-person attendance with remote participation, have become more common.</p>
895
896 <p>Yet despite the rapid growth of remote meeting platforms and innovation, there has been little formalized guidance to date on how to ensure remote meetings are accessible. Part of the issue lies with determining who is ultimately responsible for ensuring accessibility. To take the provision of captions as an example, it is necessary for a remote meeting platform to support captions, a process to be put in place to create them, and for the meeting host and participants to know not only that captions are available, but also how to ensure the they are included. This demonstrates the shared responsibility, across different audiences, for remote meetings to be accessible. It is with this in mind, that this guidance has been created to gather important accessibility considerations in the one publication.</p>
897
898 <p>This W3C Group Note is sectioned into different audience groups and includes, guidance on vendor procurement planning. It is critical for organizations to make informed decisions about the accessibility of remote meeting platforms they choose to use. The document covers the need for remote meeting platforms to adhere to accessibility standards in their development, and the need to ensure content used in a remote meeting is accessible to all participants. There is also guidance for hosts and participants regarding how to make all accessibility features of the platform available during an online or hybrid meeting.</p>
899
900 <p>The <a href="https://www.w3.org/WAI/APA/task-forces/research-questions/">Research Questions Task Force (RQTF)</a> of the <a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures (APA) Working Group</a> considered how best to support these different audiences, while also linking guidance back to relevant W3C standards where applicable. Accessibility of Remote Meetings captures knowledge and experience gained in the last several years on how to support the diverse needs of people with disabilities in the software, organizations and activities through which remote and hybrid meetings take place. Thus, by encompassing the entire process of delivering accessible meetings (not just the technical aspects of Web standards and software implementation), this work builds on and complements the earlier <a href="https://www.w3.org/TR/RAUR/">RTC Accessibility User Requirements</a>.</p>
901
902 <p>Accessibility of Remote Meetings is expected to be of broad interest to a variety of audiences, including meeting platform developers, meeting organizers, and participants with disabilities. In addition, it has the potential to influence subsequent work of W3C Web Accessibility Initiative including future formal accessibility guidance.</p>
903 </div>]]></content:encoded>
904 <slash:comments>1</slash:comments>
905 </item>
906 <item>
907 <title>Diversity and Inclusion at W3C: 2022 figures</title>
908 <pubDate>Wed, 13 Jul 2022 09:55:00 +0000</pubDate>
909 <link>https://www.w3.org/blog/2022/diversity-and-inclusion-at-w3c-2022-figures/</link>
910 <guid>https://www.w3.org/blog/2022/diversity-and-inclusion-at-w3c-2022-figures/</guid>
911 <author>Jeff Jaffe</author>
912 <comments>https://www.w3.org/blog/2022/diversity-and-inclusion-at-w3c-2022-figures/#comments</comments>
913 <category><![CDATA[corporate]]></category>
914 <category><![CDATA[blogs]]></category>
915 <dc:creator>Jeff Jaffe</dc:creator>
916 <content:encoded><![CDATA[<div class="component component--text">
917
918 <p>As part of our commitment and continued focus on diversity and inclusion here is the annual report for our most senior bodies.</p>
919
920 <p>Over a several year period we have substantially improved our geographic and gender diversity in these groups. But we still have much more to go. More broadly in the consortium we still have many under-represented groups.</p>
921
922 <p>As you can see in the graphs, since <a href="https://www.w3.org/blog/2021/06/diversity-and-inclusion-at-w3c-inclusion-fund-and-fellowships-for-tpac-2021/#diversity">last year</a> (and yearly since 2018) we continue to make incremental improvements.</p>
923
924 <p>The <a href="https://www.w3.org/2022/07/diversity/descriptions.html">W3C Diversity bar charts and figures for 2022</a> are also available in a standalone public document.</p>
925
926 <h2 id="diversity">Diversity data for W3C</h2>
927
928 <p>Notes on the graphs and information collection: Because we <a href="https://www.w3.org/Consortium/Legal/privacy-statement">do not collect participants’ data, to preserve privacy</a>, it is difficult to gather data for different characterizations of diversity. We are able to focus on gender identity and geography for several of our representative bodies: W3C Advisory Board (AB), W3C Technical Architecture Group (TAG), W3C Management (W3M).</p>
929
930 <h3 id="ab">W3C Advisory Board</h3>
931 <p>The <a href="https://www.w3.org/2002/ab/">W3C Advisory Board</a> provides ongoing guidance to W3C on issues of strategy, management, legal matters, process, and conflict resolution. Created in March 1998, the AB has now for several years conducted its work in a <a href="https://www.w3.org/wiki/AB">public wiki</a>. The elected Members of the Advisory Board participate as individual contributors and not as representatives of their organizations; the AB use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user.</p>
932
933 <p>The 11 Advisory Board positions are member-elected. The gender diversity of the AB has not changed this year. After the last <a href="https://www.w3.org/blog/news/archives/9568">election</a> last month, the board has 4 women and 7 men for the fourth consecutive year.</p>
934
935 <p><a href="https://www.w3.org/2022/07/diversity/ab-gender.png"><img src="https://www.w3.org/2022/07/diversity/ab-gender-small.png" alt="diagram of AB gender identity spanning 1998-2022" longdesc="https://www.w3.org/2022/07/diversity/descriptions.html#ab-gender" /></a><br>
936 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#ab-gender">Tabular version</a> of AB by gender identity.</p>
937
938 <p>Looking at the Advisory Board by geography, we see that the geographical diversity which was heavily tilted toward North America between 1998 and 2009 steadily improved and reached in 2018 an equal number of participants in each region. The Asian representation has expanded without regressing since 2016 and this year it reached its highest number, surpassing the North American representation. The European representation which was more or less consistently about 1/5<sup>th</sup> since 2004 and peaked around 1/3<sup>rd</sup> in 2017 and 2018, has continued to shrink after this and has been at its lowest for the third year in a row.</p>
939
940 <p><a href="https://www.w3.org/2022/07/diversity/ab-geo.png"><img src="https://www.w3.org/2022/07/diversity/ab-geo-small.png" alt="diagram of AB by geography spanning 1998-2022" longdesc="https://www.w3.org/2022/07/diversity/descriptions.html#ab-geo" /></a><br>
941 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#ab-geo">Tabular version</a> of AB by geography.</p>
942
943 <h3 id="tag">W3C Technical Architecture Group</h3>
944 <p>The <a href="http://www.w3.org/2001/tag/">W3C Technical Architecture Group</a> (TAG) is a special working group within W3C, chartered to steward web architecture, document and build consensus around principles of web architecture, resolve issues involving general web architecture brought to the TAG, and to help coordinate cross-technology architecture developments inside and outside W3C.</p>
945
946 <p>The 9 Technical Architecture Group positions are a mix of member election and appointment by the W3C Director. The group was composed only of men during its first nine years until 2011 when the TAG counted a woman during the next eight years except in 2015 where there were 2 of them. In 2019 and 2020, a third of the TAG were women. After the last <a href="https://www.w3.org/blog/news/archives/9377">election</a> earlier this year, the composition of the TAG remained the same: a non-binary member, 3 women and 5 men.</p>
947
948 <p><a href="https://www.w3.org/2022/07/diversity/tag-gender.png"><img src="https://www.w3.org/2022/07/diversity/tag-gender-small.png" alt="diagram of TAG gender identity spanning 2002-2022" longdesc="https://www.w3.org/2022/07/diversity/descriptions.html#tag-gender" /><br>
949 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#tag-gender">Tabular version</a> of TAG by gender identity.</p>
950
951 <p>Looking at the TAG by geography, we returned to the same representation as in 2020: the North America contingent is the most represented again, followed by Europe, and Asia/Pacific.</p>
952
953 <p><a href="https://www.w3.org/2022/07/diversity/tag-geo.png"><img src="https://www.w3.org/2022/07/diversity/tag-geo-small.png" alt="diagram of TAG by geography spanning 2002-2022" longdesc="https://www.w3.org/2022/07/diversity/descriptions.html#tag-geo" /></a><br>
954 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#tag-geo">Tabular version</a> of TAG by geography.</p>
955
956 <h3 id="w3m">W3C Management</h3>
957 <p>The <a href="https://www.w3.org/People/functions/w3m">W3C management team</a> is responsible for the day to day coordination of and decisions for the team, resource allocation, and strategic planning.</p>
958
959 <p>Note: The diagrams use percentages because the number of persons on W3M has changed over the years.</p>
960
961 <p>Gender diversity of W3C management continues to be heavily tilted toward male representation. The trend toward an increase in female representation has started in 2012. It has been rather stable between 2016 and 2021. In 2022 we have reached for the first time 1/3<sup>rd</sup> of women in W3C management. There are 12 men and 6 women in W3C management today.</p>
962
963 <p><a href="https://www.w3.org/2022/07/diversity/w3m-gender.png"><img src="https://www.w3.org/2022/07/diversity/w3m-gender-small.png" alt="diagram of W3M by gender identity spanning 1999-2022" longdesc="https://www.w3.org/2022/07/diversity/descriptions.html#w3m-gender" /><br>
964 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#w3m-gender">Tabular version</a> of W3M by gender identity.</p>
965
966 <p>The geographical distribution in W3M is relatively good and has been trending steadily toward more balance since 2012. The Northern America contingent is still the most represented, but it is at its lowest and for the second year in a row. Asian representation which surpassed the European's in 2021 has increased a bit. For the 5<sup>th</sup> year in a row, the European and Asian representatives amount to slightly over 50% of the W3C management.</p>
967
968 <p><a href="https://www.w3.org/2022/07/diversity/w3m-geo.png"><img src="https://www.w3.org/2022/07/diversity/w3m-geo-small.png" alt="diagram of W3M by geography spanning 1999-2022" longdesc="https://www.w3.org/2022/07/diversity/descriptions.html#w3m-geo" /><br>
969 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#w3m-geo">Tabular version</a> of W3M by geography.</p>
970 </div>]]></content:encoded>
971 <slash:comments>0</slash:comments>
972 </item>
973 </channel>
974 </rss>