GopherProxy

	w3.org_blog.rss.xml - sfeed_tests - sfeed tests and RSS and Atom files
	git clone git://git.codemadness.org/sfeed_tests
	Log
	Files
	Refs
	README
	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="ht…
	3 <channel>
	4 <language>en</language>
	5 <title>W3C - Blog</title>
	6 <description>The W3C blog is for discussions within W3C and the Web …
	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.w…
	11 <item>
	12 <title>Web Environment Integrity has no standing at W3C; understan…
	13 <description><![CDATA[This article addresses that Web Environment …
	14 <pubDate>Fri, 11 Aug 2023 19:54:00 +0000</pubDate>
	15 <link>https://www.w3.org/blog/2023/web-environment-integrity-has-n…
	16 <guid>https://www.w3.org/blog/2023/web-environment-integrity-has-n…
	17 <author>Philippe Le Hégaret</author>
	18 <comments>https://www.w3.org/blog/2023/web-environment-integrity-h…
	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 compon…
	23 <p>For a few weeks now we have been hearing concern …
	24 </div>
	25 <figure class="component component--quote">
	26 <blockquote>
	27 <p>
	28 "The objective is to ensure that the en…
	29 </p>
	30 </blockquote>
	31 <figcaption>Excerpt from the requirement for wide review (Se…
	32 </figure>
	33 <div class="component component--text">
	34 <h2>Self-review for Web platform designers</h2><p>As…
	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 …
	41 <description><![CDATA[A recent survey affirms the need to drive de…
	42 <pubDate>Mon, 24 Jul 2023 10:18:00 +0000</pubDate>
	43 <link>https://www.w3.org/blog/2023/securing-the-web-forward-addres…
	44 <guid>https://www.w3.org/blog/2023/securing-the-web-forward-addres…
	45 <author>Daniel Appelquist</author>
	46 <comments>https://www.w3.org/blog/2023/securing-the-web-forward-ad…
	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 compon…
	51 <p><a href="https://www.w3.org/2023/03/secure-the-we…
	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, inclusi…
	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/#c…
	64 <category><![CDATA[corporate]]></category>
	65 <category><![CDATA[blogs]]></category>
	66 <dc:creator>Coralie Mercier</dc:creator>
	67 <content:encoded><![CDATA[ <div class="component compon…
	68 <figure class="image"><img src="https://www.w3.org/c…
	69 </div>
	70 ]]></content:encoded>
	71 <slash:comments>5</slash:comments>
	72 </item>
	73 <item>
	74 <title>Web technologies for applications: workshop and coding cont…
	75 <description><![CDATA[Web technologies for applications: workshop …
	76 <pubDate>Mon, 05 Jun 2023 16:07:00 +0000</pubDate>
	77 <link>https://www.w3.org/blog/2023/web-technologies-for-applicatio…
	78 <guid>https://www.w3.org/blog/2023/web-technologies-for-applicatio…
	79 <author>Marie-Claire Forgue</author>
	80 <comments>https://www.w3.org/blog/2023/web-technologies-for-applic…
	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 compon…
	85 <p>The convergence of web innovation, light app tech…
	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 Accessib…
	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/<…
	95 <guid>https://www.w3.org/blog/2023/w3c-wai-updates-for-gaad-2023/<…
	96 <author>Shawn Lawton Henry</author>
	97 <comments>https://www.w3.org/blog/2023/w3c-wai-updates-for-gaad-20…
	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 compon…
	102 <p>In your materials for Global Accessibility Awaren…
	103
	104 <h2>WAI Resources for GAAD</h2>
	105
	106 <p>For a list of free online resources to support digital accessibility,…
	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-pr…
	112 <li><a href="https://www.w3.org/WAI/fundamentals/accessibility-i…
	113 <li><a href="https://www.w3.org/WAI/courses/">Digital Accessibil…
	114 </ul>
	115
	116 <h2>WAI Updates</h2>
	117
	118 <p>For monthly updates on current WAI work, see <a href="https://www.w3.…
	119
	120 <p>For those interested in Web Content Accessibility Guidelines (WCAG):<…
	121
	122 <ul>
	123 <li>An updated draft of WCAG 2.2 was published on 17 May 2023. S…
	124 <li>WCAG 3.0 is exploring a different approach. It is years away…
	125 <li>You can get announcements of WCAG updates via e-mail. See <a…
	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>, …
	134 <li><a href="https://www.w3.org/People/cooper/">Michael Cooper</…
	135 <li><a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henr…
	136 </ul>
	137
	138 <p>WAI staff also includes <a href="https://www.w3.org/People#ran">Ruoxi…
	139
	140 <p>To reach WAI staff, you can e-mail <a href="mailto:[email protected]">wai@w3…
	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 a…
	147 <description><![CDATA[The post illustrates why selected W3C standa…
	148 <pubDate>Sun, 30 Apr 2023 16:55:00 +0000</pubDate>
	149 <link>https://www.w3.org/blog/2023/30th-anniversary-of-licensing-t…
	150 <guid>https://www.w3.org/blog/2023/30th-anniversary-of-licensing-t…
	151 <author>Coralie Mercier</author>
	152 <comments>https://www.w3.org/blog/2023/30th-anniversary-of-licensi…
	153 <category><![CDATA[corporate]]></category>
	154 <category><![CDATA[blogs]]></category>
	155 <dc:creator>Coralie Mercier</dc:creator>
	156 <content:encoded><![CDATA[ <div class="component compon…
	157 <p><small><a href="https://www.chinaw3c.org/30th-ann…
	158
	159 <hr />
	160 </div>
	161 <div class="component component--text">
	162 <p>Today marks the 30th anniversary of the <a href="…
	163
	164 <p>This quiet gesture, advocated by Web inventor <a href="https://www.w3…
	165
	166 <p>Please, join me in taking a moment to appreciate the impact and the s…
	167
	168 <p><img alt="graphic showing a historical photo of Sir Tim Berners-Lee a…
	169
	170 <p><a href="https://www.statista.com/statistics/273018/number-of-interne…
	171
	172 <p><strong>The Web has been life-changing for people</strong>. I ran a s…
	173
	174 <blockquote>
	175 <p>“I think there are two type of persons, the ones that the web c…
	176 </blockquote>
	177
	178 <p>It warmed my heart and reinforced the sense of purpose I get from wor…
	179
	180 <ol>
	181 <li><strong>Vital family and social interactions.</strong> Also,…
	182 <li><strong>Earning a living.</strong> Many found jobs as web de…
	183 <li><strong>Empowerment and personal growth.</strong> From enabl…
	184 </ol>
	185
	186 <p>Sir Tim Berners-Lee founded the World Wide Web Consortium in 1994 as …
	187
	188 <p>CERN’s decision to provide unencumbered access to the basic Web…
	189
	190 <p>In May 2003, coinciding almost exactly with the tenth anniversary of …
	191
	192 <p>To date, W3C has published more than <a href="https://www.w3.org/2002…
	193
	194 <p><a href="https://www.w3.org/comm/assets/graphics/2023-04-30_timeline-…
	195
	196 <p>Among the many achievements originating from W3C that influenced the …
	197
	198 <ul>
	199 <li><abbr title="hypertext markup language">HTML</abbr>, <abbr t…
	200 <li><abbr title="extensible markup language">XML</abbr> (1996), …
	201 <li><a href="https://www.w3.org/WAI/">Web Accessibility Initiati…
	202 <li>Patent Policy Working Group formed (1999), to reduce the thr…
	203 <li><abbr title="document object model">DOM</abbr> (1997), for g…
	204 <li><a href="https://www.w3.org/International/">Internationaliza…
	205 <li>Ecommerce/Micropayment (1998), to make it possible to buy an…
	206 <li><abbr title="resource description framework">RDF</abbr> (199…
	207 <li><abbr title="scalable vector graphics">SVG</abbr> (2001), to…
	208 <li><a href="https://www.w3.org/2003/05/patentpolicy-pressreleas…
	209 <li>Mobile Web Initiative (2005), which made web access from a m…
	210 <li>W3C in China (2006), where the online presence has been lead…
	211 <li><a href="https://www.w3.org/2008/12/wcag20-pressrelease.html…
	212 <li><a href="https://www.w3.org/2021/01/pressrelease-webrtc-rec.…
	213 <li><abbr title="web open font format">WOFF</abbr> (2012), for p…
	214 <li>JSON-LD (2014), for making Linked Data and RDF much easier t…
	215 <li>Web Payments (2014) for making web payments easier and more …
	216 <li>ActivityPub (2018), for powering the world’s greatest …
	217 <li><a href="https://www.w3.org/2019/12/pressrelease-wasm-rec.ht…
	218 <li><a href="https://www.w3.org/2019/03/pressrelease-webauthn-re…
	219 <li><a href="https://www.w3.org/2022/07/pressrelease-did-rec.htm…
	220 </ul>
	221
	222 <p>Our <a href="https://www.w3.org/Consortium/mission#vision">vision</a>…
	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 Techno…
	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/<…
	232 <guid>https://www.w3.org/blog/2023/answering-what-aria-can-i-use/<…
	233 <author>Matthew King</author>
	234 <comments>https://www.w3.org/blog/2023/answering-what-aria-can-i-u…
	235 <category><![CDATA[accessibility]]></category>
	236 <category><![CDATA[blogs]]></category>
	237 <dc:creator>Matthew King</dc:creator>
	238 <content:encoded><![CDATA[ <div class="component compon…
	239 <h2>New! AT support tables in the Authoring Practice…
	240
	241 <p>The <a href="https://www.w3.org/groups/cg/aria-at">ARIA and Assistive…
	242
	243 <p>This “Can I Use…” like data showing how three scre…
	244
	245 <p><strong>That fruit makes predictable screen reader behavior possible.…
	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, …
	250
	251 <p>Web, browser, operating system, and AT developers are all attempting …
	252
	253 <p><a href="https://www.w3.org/WAI/WCAG22/Understanding/conformance#acce…
	254
	255 <blockquote>
	256 <p>“When new technologies are introduced, two things must happen i…
	257 </blockquote>
	258
	259 <p>So, even when browsers and accessibility APIs are perfectly implement…
	260
	261 <ol>
	262 <li>Consistent understanding across web development communities …
	263 <li>Consistent interpretation and rendering of accessibility sem…
	264 <li>All stakeholders having sufficiently similar understanding o…
	265 </ol>
	266
	267 <p>In other words, web developers and AT developers need to be on the sa…
	268
	269 <h2>Helping map the rest of the “accessibility supported” pu…
	270
	271 <p>The ARIA-AT CG and APG TF have been jointly working to align the web …
	272
	273 <p>First, to foster harmonization of how accessibility semantics are use…
	274
	275 <p>That “can I use …” type of data comes from the <a …
	276
	277 <h2>The challenge of defining and testing AT behavior that “actual…
	278
	279 <p>Figuring out how to define, develop consensus for, and test baseline …
	280
	281 <p>At a high level, the major elements of the APG TF and ARIA-AT CG AT i…
	282
	283 <ol>
	284 <li>Build the supply of sufficient, robust, and stable test case…
	285 <li>Craft statements of expected AT behaviors in the form of tes…
	286 <li>Develop systems for managing the stakeholder consensus proce…
	287 <li>Develop and implement an AT automation standard that enables…
	288 </ol>
	289
	290 <p>All that is enablement. The deliverables from those workstreams make …
	291
	292 <h2>Screen reader partnership</h2>
	293
	294 <p>Given that the community group is kickstarting AT interoperability wi…
	295
	296 <p>Negotiating the details of how to test interoperability and adjusting…
	297
	298 <h2>What’s next</h2>
	299
	300 <p>In coming months, AT support tables will be added to more APG example…
	301
	302 <p>In 2024, as we complete the first round of test plans for desktop scr…
	303
	304 <h2>Get involved</h2>
	305
	306 <p>To learn more about how you or your organization can participate or s…
	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) i…
	314 <pubDate>Wed, 22 Mar 2023 09:04:00 +0000</pubDate>
	315 <link>https://www.w3.org/blog/2023/privacy-principles-for-the-web/…
	316 <guid>https://www.w3.org/blog/2023/privacy-principles-for-the-web/…
	317 <author>Samuel Weiler</author>
	318 <comments>https://www.w3.org/blog/2023/privacy-principles-for-the-…
	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 compon…
	323 <p>The World Wide Web Consortium’s <a href="ht…
	324
	325 <p>We welcome your feedback on the document. We encourage you to <a href…
	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…
	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-we…
	335 <guid>https://www.w3.org/blog/2023/w3c-launches-beta-of-its-new-we…
	336 <author>Coralie Mercier</author>
	337 <comments>https://www.w3.org/blog/2023/w3c-launches-beta-of-its-ne…
	338 <category><![CDATA[corporate]]></category>
	339 <category><![CDATA[blogs]]></category>
	340 <dc:creator>Coralie Mercier</dc:creator>
	341 <content:encoded><![CDATA[ <figure class="component com…
	342 <img src="https://www.w3.org/cms-uploads/_580xAUTO_crop_center-c…
	343 loading="lazy"
	344 alt=""
	345 />
	346 <figcaption>
	347 <p>Screenshot of the beta homepage of the redesigned W3C web…
	348 </figcaption>
	349 </figure>
	350 <div class="component component--text">
	351 <p>Today we launched a<a href="https://www.w3.org/" …
	352
	353 <p>The goals of the redesign are to achieve a cleaner and modern look an…
	354
	355 <p>For several years, W3C has worked in close partnership with <a href="…
	356
	357 <p>The scope of the redesign is limited to most of our public pages, but…
	358
	359 <p>We invite your feedback on the beta site, on website or content issue…
	360
	361 <p>My heartfelt thanks to the W3C Systems Team for its tremendous work f…
	362
	363 <p>We’re not done, but we’ve reached a significant milestone…
	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 Extra…
	372 <description><![CDATA[Farewell Karen Myers, W3C Business Developme…
	373 <pubDate>Wed, 18 Jan 2023 11:05:00 +0000</pubDate>
	374 <link>https://www.w3.org/blog/2023/farewell-karen-myers-w3c-busine…
	375 <guid>https://www.w3.org/blog/2023/farewell-karen-myers-w3c-busine…
	376 <author>J. Alan Bird</author>
	377 <comments>https://www.w3.org/blog/2023/farewell-karen-myers-w3c-bu…
	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 compon…
	382 <p><img alt="group picture at the Emmy Awards ceremo…
	383
	384 <p>It is with bittersweet emotions, that I share that Karen Myers’…
	385
	386 <p>After 18 years, Karen has chosen to retire from the World Wide Web Co…
	387
	388 <p>We welcomed Karen Myers in 2004 to assume the role of Acting Director…
	389
	390 <p>Karen’s achievements over the years, allocating her time betwee…
	391
	392 <ul>
	393 <li>coordinating the communications of our Director Tim Berners-…
	394 <li>planning the W3C ten-year anniversary events and gala.</li>
	395 <li>working with Tim on some of his speeches —including hi…
	396 <li>putting together international W3C events at the Consumer El…
	397 <li>coordinating with W3C Evangelists and Chapters in publishing…
	398 <li>recruiting and onboarding hundreds of new members to partici…
	399 </ul>
	400
	401 <p>Going forward, I, <a href="https://www.w3.org/People/AlanBird/">Alan …
	402
	403 <p>Farewell and best wishes to Karen in whatever new adventures she choo…
	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/#com…
	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-boa…
	420
	421 <p>At the broadest level our <a href="https://www.w3.org/Consortium/miss…
	422
	423 <p>Our community – our <a href="https://www.w3.org/Consortium/Memb…
	424
	425 <p>Our strength derives from the diversity of our global inclusion. This…
	426
	427 <p>Thank you for your continued engagement in this global effort to main…
	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/…
	437 <guid>https://www.w3.org/blog/2022/latest-epubcheck-5-0-0-preview/…
	438 <author>Tzviya Siegman</author>
	439 <comments>https://www.w3.org/blog/2022/latest-epubcheck-5-0-0-prev…
	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…
	447
	448 <p>We encourage users to effectively test this version of EPUBCheck in t…
	449
	450 <p>The full change log is available on the EPUBCheck <a href="https://gi…
	451
	452 <p>Please file comments, bug reports, and feature request to our <a href…
	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-…
	460 <guid>https://www.w3.org/blog/2022/webdx-improving-the-experience-…
	461 <author>Dominique Hazaël-Massieux</author>
	462 <comments>https://www.w3.org/blog/2022/webdx-improving-the-experie…
	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 t…
	468
	469 <p>As a development platform, the Web platform is fairly unique in being…
	470
	471 <p>While competing implementations are a great driver of innovation, it …
	472
	473 <p>Understanding and monitoring what constitutes the interoperable surfa…
	474
	475 <p>The <a href="https://github.com/web-platform-tests/interop">Interop p…
	476
	477 <p>Similarly, <a href="https://openwebdocs.org/">Open Web Docs</a> provi…
	478
	479 <p>To build on these positive patterns, the <a href="https://www.w3.org/…
	480
	481 <p>First, it will <b>enable shared research on the pain points that deve…
	482
	483 <p>In complement to that, we want to provide structural improvements in …
	484
	485 <p>We want to <b>make it easier for developers to track the list of feat…
	486
	487 <p>It's still early days! If you want to contribute and improve the …
	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-managem…
	495 <guid>https://www.w3.org/blog/2022/stepping-forward-on-wai-managem…
	496 <author>Michael Cooper</author>
	497 <comments>https://www.w3.org/blog/2022/stepping-forward-on-wai-man…
	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-upda…
	503
	504 <p>My priority is to keep the work moving forwards, including working gr…
	505
	506 <p>Another transition is that Kevin White rejoined WAI this week, bringi…
	507
	508 <p>Many of you know me mostly in my role as staff contact to the Accessi…
	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/</…
	516 <guid>https://www.w3.org/blog/2022/w3c-wai-updates-october-2022/</…
	517 <author>Shawn Lawton Henry</author>
	518 <comments>https://www.w3.org/blog/2022/w3c-wai-updates-october-202…
	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/WA…
	524
	525 <h2>WAI Staff and Roles</h2>
	526
	527 <p><strong>Judy Brewer</strong> will be leaving WAI for a new opportunit…
	528
	529 <p><strong>Kevin White</strong> rejoined the WAI Team in October as Acce…
	530
	531 <p><strong><a href="https://www.w3.org/People/cooper/">Michael Cooper</a…
	532
	533 <p><strong><a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry…
	534
	535 <p>Over the next few months, WAI will refine roles and responsibilities …
	536
	537 <h2>W3C Supports WAI Going Forward</h2>
	538
	539 <p>"W3C is proud of WAI's successes under Judy's leadership…
	540
	541 <p>WAI staff will work on WAI vision and strategic plan in early 2023, w…
	542
	543 <h2>Current WAI Work and Updates</h2>
	544
	545 <p><strong>To get up-to-date information on active projects, upcoming pu…
	546 <a href="https://www.w3.org/WAI/update/">What We’re Working On &nd…
	547 To get future updates, see: <a href="https://www.w3.org/WAI/news/subscri…
	548 To learn about existing accessibility standards and supporting material,…
	549
	550 <p>Please feel free to reach out to any of us directly with questions an…
	551
	552 <p><strong>We look forward to working together with the community to adv…
	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/</lin…
	560 <guid>https://www.w3.org/blog/2022/looking-back-at-tpac-2022/</gui…
	561 <author>Xueyuan Jia</author>
	562 <comments>https://www.w3.org/blog/2022/looking-back-at-tpac-2022/#…
	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="…
	568
	569 <p>W3C's annual conference <a href="https://www.w3.org/2022/09/TPAC/…
	570
	571 <p>The conference was in hybrid format. The main in-person hub was in Va…
	572
	573 <p><strong>What attendees said - How TPAC 2022 went</strong></p>
	574
	575 <p><i>“TPAC is taking Covid measures extremely seriously.” <…
	576 Our Events Planning team always puts the safety and experience of attend…
	577
	578 <p>"<em>Just really nice to see everyone again and have somewhat or…
	579
	580 <p><em>"Also the organizers did an awesome job ensuring people coul…
	581
	582 <p><em>"It’s great to see so many important players gather ar…
	583
	584 <p>The technical plenary day, consisting of <a href="https://www.w3.org/…
	585
	586 <p>During the AC open session, W3C CEO Jeff Jaffe presented “W3C S…
	587
	588 <p>The Developer Meetup gathered the global Web community to coordinate …
	589
	590 <p>Given the travel restrictions and time differences, W3C/Beihang Host …
	591
	592 <p><strong>Next meetings</strong></p>
	593
	594 <p>We are looking forward to the next annual conference, which will be h…
	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-re…
	602 <guid>https://www.w3.org/blog/2022/w3c-devmeetup-2022-vancouver-re…
	603 <author>Marie-Claire Forgue</author>
	604 <comments>https://www.w3.org/blog/2022/w3c-devmeetup-2022-vancouve…
	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…
	610
	611 <p>On September 13, 2022, in Vancouver BC, Canada, the W3C developer rel…
	612
	613 <p>Today, we are pleased to share the recorded videos of the four talks …
	614
	615 <ul>
	616 <li><strong>Greg Whitworth</strong> (SalesForce) related the res…
	617 <li><strong>Aram Zucker-Scharff</strong> (The Washington Post) g…
	618 <li>Within the standardization track, new CSS features are emerg…
	619 <li>Finally, illustrating the work that remains to be done once …
	620 </ul>
	621
	622 <p>This event was made possible thanks to the support of our sponsors, t…
	623
	624 <p><img alt="Thank you to the W3C DevMeetup in Vancouver sponsors: Igali…
	625
	626 <p><em>Follow us on <a href="https://twitter.com/w3cdevs" rel="noopener …
	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/#co…
	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.…
	642 </p><p>
	643 Below I summarize discussions of the meetings I attended: the Web Paymen…
	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 Paym…
	648 </p>
	649 <ul>
	650 <li>Adyen and Airbnb shared some information about their SPC pilot. The …
	651 <li>Google presented their current work to bring SPC to Chrome on Androi…
	652 <li>FIS shared thoughts on three topics of interest: shops making the tr…
	653 <ul>
	654 <li>Merchants want to know who their customers are prior to authorizatio…
	655 <li>Data is not always available based on payment types or implementatio…
	656 <li>Cart abandonment is a problem due to extra friction and payment prob…
	657 </ul>
	658 </li>
	659 <li>Microsoft shared some perspectives as a merchant that adopted strong…
	660 <li>We then revisited some EMVCo observations about SPC and some changes…
	661 </ul>
	662 <p>
	663 We opened the second day of the WPWG meeting (<a href="https://www.w3.or…
	664 </p><p>
	665 After that:
	666 </p>
	667 <ul>
	668 <li>Apple then described some changes to ApplePay.js over the past coupl…
	669 <li>We then discussed some upcoming changes to browsers related to "<a h…
	670 <li>In the same vein, we then heard about changes that the Chrome team p…
	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 Paym…
	676 </p>
	677 <ul>
	678 <li>The <a href="https://www.w3.org/community/antifraud/">Antifraud CG, …
	679 <li>The Web Authentication Working Group summarized the state of specifi…
	680 <li>In the final session of the joint meeting, we discussed the status o…
	681 </ul>
	682 <p>
	683 Antifraud discussion, in particular about Device Public Keys used for fr…
	684 </p>
	685 <h3>Thursday Joint Meeting</h3>
	686 <p>
	687 On Thursday, both the Web Payment Security Interest Group and the Antifr…
	688 </p>
	689 <ul>
	690 <li>Entersekt presented some payment fraud patterns (e.g., account takeo…
	691 <li>Our colleague from the University of Illinois Chicago presented find…
	692 </ul>
	693 <p>
	694 We made good progress at TPAC in understanding use cases, formulating th…
	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/#co…
	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…
	712 </p>
	713 <p>
	714 I have been working with multiple groups on a coordinated agenda…
	715 </p>
	716 <ul>
	717 <li>
	718 Monday and Tuesday morning: <a href="https://github.com/w3c/…
	719 </li>
	720 <li>
	721 Tuesday afternoon: <a href="https://docs.google.com/document…
	722 </li>
	723 <li>
	724 Wednesday afternoon: <a href="https://www.w3.org/2022/09/TPA…
	725 </li>
	726 <li>
	727 Thursday: <a href="https://www.w3.org/securepay/wiki/Meeting…
	728 </li>
	729 </ul>
	730 <p>
	731 I'm looking forward to discussion about Secure Payment Confirmat…
	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-mode…
	743 <guid>https://www.w3.org/blog/2022/w3c-accessibility-maturity-mode…
	744 <author>Ruoxi Ran</author>
	745 <comments>https://www.w3.org/blog/2022/w3c-accessibility-maturity-…
	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…
	751
	752 <p>It’s not enough to get a product accessible. The entire product…
	753
	754 <p>In an organization of moderate or large size, no one department can b…
	755
	756 <p>Maturity models have been around since the 80s. They generally contai…
	757
	758 <p>This proposed <a href="https://www.w3.org/TR/maturity-model/">W3C Acc…
	759
	760 <ul>
	761 <li>helps people, groups, or organizations assess their accessib…
	762 <li>identifies gaps between the current capabilities and the nex…
	763 <li>encourages improving overall accessibility performance over …
	764 </ul>
	765
	766 <p>Accessibility Conformance Reports / Voluntary Product Accessibility T…
	767
	768 <p>Organizations know when they are doing well (or poorly) with product …
	769
	770 <p>Accessibility maturity modeling is very different than accessibility …
	771
	772 <ul>
	773 <li>Conformance testing provides information about the level of …
	774 <li>Maturity modeling provides information about the ability of …
	775 </ul>
	776
	777 <p>We encourage people and organizations who could benefit from implemen…
	778 </div>]]></content:encoded>
	779 <slash:comments>5</slash:comments>
	780 </item>
	781 <item>
	782 <title>W3C Developer meetup in Vancouver, Canada, 13 September</ti…
	783 <pubDate>Tue, 30 Aug 2022 15:40:00 +0000</pubDate>
	784 <link>https://www.w3.org/blog/2022/w3c-developer-meetup-in-vancouv…
	785 <guid>https://www.w3.org/blog/2022/w3c-developer-meetup-in-vancouv…
	786 <author>Marie-Claire Forgue</author>
	787 <comments>https://www.w3.org/blog/2022/w3c-developer-meetup-in-van…
	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 skyli…
	793
	794 <p>W3C invites the vibrant Vancouver-based tech community to its <a href…
	795
	796 <p>We are very much looking forward to connecting with local developers,…
	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 exc…
	801
	802 <ul>
	803 <li><b>Rachel Andrew</b>, technical writer at Google, will expla…
	804 <li><b>Aram Zucker-Scharff</b>, The Washington Post, will explai…
	805 <li><b>Miriam Suzanne</b>, W3C Invited Expert, will show how CSS…
	806 <li>In “Open UI: unlocking creativity”, <b>Greg Whit…
	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: I…
	812
	813 <p>Follow us on <a href="https://twitter.com/w3cdevs"><strong>@w3cdevs</…
	814 </div>]]></content:encoded>
	815 <slash:comments>0</slash:comments>
	816 </item>
	817 <item>
	818 <title>Observations from our initial https redirection tests</titl…
	819 <pubDate>Mon, 22 Aug 2022 18:56:00 +0000</pubDate>
	820 <link>https://www.w3.org/blog/2022/https-redirection-observations/…
	821 <guid>https://www.w3.org/blog/2022/https-redirection-observations/…
	822 <author>Gerald Oskoboiny</author>
	823 <comments>https://www.w3.org/blog/2022/https-redirection-observati…
	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/20…
	829
	830 <p>To get an understanding of whether this change is feasible for our si…
	831
	832 <p>Here are some notes on what we have learned so far, and answers to so…
	833
	834 <p>We receive a lot of automated requests for machine-readable resources…
	835
	836 <p>Therefore we decided to do some limited tests of redirecting our enti…
	837
	838 <p>During our initial tests we heard from a few people that this was cau…
	839
	840 <p>Questions we have received include: what action are we expecting from…
	841
	842 <p>In general that is not necessary, and in fact in many cases those ref…
	843
	844 <p>If you maintain a software system that retrieves resources from www.w…
	845
	846 <p>We plan to continue limited tests of this change to our site over the…
	847
	848 <p>To stay informed of future tests and other updates to our systems ple…
	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-…
	856 <guid>https://www.w3.org/blog/2022/redirecting-to-https-on-www-w3-…
	857 <author>Gerald Oskoboiny</author>
	858 <comments>https://www.w3.org/blog/2022/redirecting-to-https-on-www…
	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.or…
	864
	865 <p>The primary reason for this is that we wanted to avoid causing issues…
	866
	867 <p>We believe enough time has passed for most such software to have been…
	868
	869 <p>In order to discover any potential remaining issues and to give some …
	870
	871 <p>The first such test is planned for Monday August 1, for 8 hours start…
	872
	873 <p>Update 16 Aug 2022: The second test is planned to run from Thursday A…
	874
	875 <p>Update 19 Aug 2022: We ended the second test early, at 17:30 UTC toda…
	876
	877 <p>If you have any questions or comments about this planned change, plea…
	878 </div>]]></content:encoded>
	879 <slash:comments>32</slash:comments>
	880 </item>
	881 <item>
	882 <title>Accessibility of Remote Meetings Published as W3C Group Not…
	883 <pubDate>Fri, 22 Jul 2022 07:07:00 +0000</pubDate>
	884 <link>https://www.w3.org/blog/2022/accessibility-of-remote-meeting…
	885 <guid>https://www.w3.org/blog/2022/accessibility-of-remote-meeting…
	886 <author>Ruoxi Ran</author>
	887 <comments>https://www.w3.org/blog/2022/accessibility-of-remote-mee…
	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="http…
	893
	894 <p>The impact of COVID-19 has seen a substantial increase in usage of re…
	895
	896 <p>Yet despite the rapid growth of remote meeting platforms and innovati…
	897
	898 <p>This W3C Group Note is sectioned into different audience groups and i…
	899
	900 <p>The <a href="https://www.w3.org/WAI/APA/task-forces/research-question…
	901
	902 <p>Accessibility of Remote Meetings is expected to be of broad interest …
	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-…
	910 <guid>https://www.w3.org/blog/2022/diversity-and-inclusion-at-w3c-…
	911 <author>Jeff Jaffe</author>
	912 <comments>https://www.w3.org/blog/2022/diversity-and-inclusion-at-…
	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 inclus…
	919
	920 <p>Over a several year period we have substantially improved our geograp…
	921
	922 <p>As you can see in the graphs, since <a href="https://www.w3.org/blog/…
	923
	924 <p>The <a href="https://www.w3.org/2022/07/diversity/descriptions.html">…
	925
	926 <h2 id="diversity">Diversity data for W3C</h2>
	927
	928 <p>Notes on the graphs and information collection: Because we <a href="h…
	929
	930 <h3 id="ab">W3C Advisory Board</h3>
	931 <p>The <a href="https://www.w3.org/2002/ab/">W3C Advisory Board</a> prov…
	932
	933 <p>The 11 Advisory Board positions are member-elected. The gender divers…
	934
	935 <p><a href="https://www.w3.org/2022/07/diversity/ab-gender.png"><img src…
	936 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#ab-gende…
	937
	938 <p>Looking at the Advisory Board by geography, we see that the geographi…
	939
	940 <p><a href="https://www.w3.org/2022/07/diversity/ab-geo.png"><img src="h…
	941 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#ab-geo">…
	942
	943 <h3 id="tag">W3C Technical Architecture Group</h3>
	944 <p>The <a href="http://www.w3.org/2001/tag/">W3C Technical Architecture …
	945
	946 <p>The 9 Technical Architecture Group positions are a mix of member elec…
	947
	948 <p><a href="https://www.w3.org/2022/07/diversity/tag-gender.png"><img sr…
	949 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#tag-gend…
	950
	951 <p>Looking at the TAG by geography, we returned to the same representati…
	952
	953 <p><a href="https://www.w3.org/2022/07/diversity/tag-geo.png"><img src="…
	954 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#tag-geo"…
	955
	956 <h3 id="w3m">W3C Management</h3>
	957 <p>The <a href="https://www.w3.org/People/functions/w3m">W3C management …
	958
	959 <p>Note: The diagrams use percentages because the number of persons on W…
	960
	961 <p>Gender diversity of W3C management continues to be heavily tilted tow…
	962
	963 <p><a href="https://www.w3.org/2022/07/diversity/w3m-gender.png"><img sr…
	964 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#w3m-gend…
	965
	966 <p>The geographical distribution in W3M is relatively good and has been …
	967
	968 <p><a href="https://www.w3.org/2022/07/diversity/w3m-geo.png"><img src="…
	969 <a href="https://www.w3.org/2022/07/diversity/descriptions.html#w3m-geo"…
	970 </div>]]></content:encoded>
	971 <slash:comments>0</slash:comments>
	972 </item>
	973 </channel>
	974 </rss>