Thursday, December 2, 2021

W3C Invites Implementations of User Timing and Performance Timeline

 The Web Performance Working Group invites implementations of two Candidate Recommendation Snapshots:

  • User Timing defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
  • Performance Timeline extends the High Resolution Time specification [HR-TIME-3] by providing methods to store and retrieve high resolution performance metric data.

First Public Working Draft: MiniApp Packaging

 The MiniApps Working Group has published a First Public Working Draft of MiniApp Packaging. This specification defines semantics and conformance requirements for a MiniApp package, and the structure of the single file container that holds the resources of a MiniApp, including a manifest file, static page templates, stylesheets, JavaScript documents, media files and other resources. Instances of the MiniApp package are used for MiniApp distribution and execution on runtime environments (MiniApp user agent).

First Public Working Draft: Digital Publishing Accessibility API Mappings 1.1

 he Accessible Rich Internet Applications Working Group has published a First Public Working Draft of Digital Publishing Accessibility API Mappings 1.1. The Digital Publishing Accessibility API Mappings (DPub-AAM) defines how user agents map the Digital Publishing WAI-ARIA Module [dpub-aria-1.1] markup to platform accessibility APIs. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.

The implementation of this specification in user agents enables authors to produce more accessible e-books, by conveying structural book constructs used by the digital publishing industry to assistive technologies. It does this by extending the Core Accessibility API Mappings 1.1 and the Accessible Name and Description: Computation and API Mappings 1.1 specifications for user agents. It provides Accessibility API Mapping guidance for the roles defined in the Digital Publish WAI-ARIA Module.

The DPub-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

Tuesday, November 16, 2021

W3C opens Technical Architecture Group (TAG) election

 

W3C TAG logoThe W3C Advisory Committee, having nominated four individuals, is invited today to vote until 14 December 2021 for three seats in the W3C Technical Architecture Group (TAG) election.

The TAG is a special working group within the W3C, chartered under the W3C Process Document, with stewardship of the Web architecture. Some aspects of its mission include

  • to document and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary;
  • to resolve issues involving general Web architecture brought to the TAG;
  • to help coordinate cross-technology architecture developments inside and outside W3C.

Job: Automotive and Transportation Champion (USA, China, Japan)

 

handshakeWe are excited to announce an open position (possibly part-time) : Automotive & Transportation Champion, based in the USA or China, or Japan.

This is an opportunity for a global leader to drive the overall strategy of applying open web standards to the automotive & transportation ecosystem. The Champion is a thought leader who has a deep understanding of the needs of the automotive industry and a working understanding of web technology. The Champion engages with other automotive thought leaders from W3C Members and with technologists in W3C. By bringing these groups together, the Champion identifies new technology needs for the industry and identifies technical and business approaches to satisfy those needs.

Authorized Translation of WCAG 2.1 in Arabic

 12 November 2021

Screenshot showing the w3c logo and the title of the W3C WCAG 2.1 Web Content Accessibility GuidelinesThe World Wide Web Consortium published the Authorized Arabic Translation of Web Content Accessibility Guidelines (WCAG) 2.1مبادئ النفاذ إلى محتوى الويب (WCAG2.1). The Lead Translation Organization for this Authorized Translation was the Mada Center, Qatar.

Translations in other languages are listed in WCAG 2 Translations. W3C Web Accessibility Initiative (WAI) particularly encourages the development of Authorized Translations of WCAG 2.1 and other technical specifications to facilitate their adoption and implementation internationally. Read about the Policy for W3C Authorized Translations.

Monday, October 18, 2021

W3C TPAC 2021 Exhibition Space opens for registration

 

TPAC 2021W3C’s annual technical meeting, TPAC, has a unique feature this year – an Exhibition Space that is open to the public! If you’re interested in learning about solutions that you can leverage, then register to come visit us. The W3C TPAC Exhibition Hall is open from 18 – 24 October so please stop by and visit our great Sponsors – Coil, Legible, Igalia and Movement for an Open Web.

W3C and Yubico offer first online Web Authentication course for developers

 

W3CYubicoW3C and Yubico announced today the opening of registration for a W3Cx online education course that teaches developers how to build and incorporate modern authentication techniques into their web-based applications using W3C’s Web Authentication (WebAuthn). Both organizations collaborated to design the Massive Open Online Course (MOOC) titled “Introduction to Web Authentication” to equip learners with the knowledge to replace aging password-based credentials with a secure model that incorporates strong authentication. The course to begin 30 November 2021 is free to learners who can opt-into a paid course and earn a certificate of completion. Please, read more in our joint press release.

First Public Working Draft: Accessibility of Remote Meetings

 The Accessible Platform Architectures Working Group has published a First Public Working Draft of Accessibility of Remote Meetings. Remote meeting is an umbrella term used to describe real-time discussions or presentations held between two or more parties online. The issues faced by people with disabilities will vary depending on the implementation of accessibility requirements and current limitations of remote meeting software. While W3C has applicable guidance across several standards and Notes relating to real-time communication and XR, it is this level of complexity that this document endeavours to address.

Comments are welcome through 19th November 2021.

Friday, October 1, 2021

First Public Working Draft: Media Source Extensions™

 The Media Working Group has published a First Public Working Draft of Media Source Extensions™. This specification extends HTMLMediaElement [HTML] to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams.

Call for Review: Payment Request API and Payment Method Identifiers are W3C Proposed Recommendations

 The Web Payments Working Group has just published Proposed Recommendations of Payment Request API and Payment Method Identifiers.

Payment Request standardizes an API to allow merchants (i.e., web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. Browsers facilitate the payment flow between merchant and user. Payment Method Identifiers defines payment method identifiers and how they are validated, and, where applicable, minted and formally registered with the W3C.

Call for Review: ARIA in HTML is a W3C Proposed Recommendation

 The Web Applications Working Group has just published a Proposed Recommendation of ARIA in HTML. This specification defines the authoring rules (author conformance requirements) for the use of Accessible Rich Internet Applications (WAI-ARIA) 1.1 and Digital Publishing WAI-ARIA Module 1.0 attributes on [HTML] elements. This specification’s primary objective is to define requirements for use with conformance checking tools used by authors (i.e., web developers). These requirements will aid authors in their development of web content, including custom interfaces/widgets, that makes use of ARIA to complement or extend the features of the host language [HTML].

Thursday, September 30, 2021

SEO Tips

Google is the most popular search engine by a wide margin. Roughly 70% of all search traffic moves through Google.

Google and other search engines like it when you link to external content, and they really like it when your link text is short, descriptive, and natural.

Create original content that is so good, useful, and interesting that other websites want to share it.

Optimization: There are two ways of optimization

On-Page SEO - It includes providing good content, good keywords selection, putting keywords

on correct places, giving appropriate title to every page, etc.

Off-Page SEO - It includes link building, increasing link popularity by submitting open

directories, search engines, link exchange, etc

SEO techniques

White Hat SEO - Techniques that search engines recommend as part of a good design.

Black Hat SEO - Techniques that search engines do not approve and attempt to minimize the

effect of. These techniques are also known as spamdexing.

Thursday, September 23, 2021

First Public Working Draft: WebRTC Encoded Transform

21 September 2021 The Web Real-Time Communications Working Group has published a First Public Working Draft of WebRTC Encoded Transform. The goal of this work is to define an API for processing encoded media in WebRTC, for example for voice processing, background removal, dynamic control of codec parameters, etc. This document specifies an API surface for manipulating the bits on MediaStreamTracks being sent via an RTCPeerConnection.api

First Public Working Draft: WebXR Lighting Estimation API Level 1

9 September 2021 The Immersive Web Working Group has published a First Public Working Draft of WebXR Lighting Estimation API Level 1. This specification describes support for exposing estimates of environmental lighting conditions to WebXR sessions.

Tuesday, September 7, 2021

First Public Working Draft: Incremental Font Transfer

 7 September 2021

The Web Fonts Working Group has published a First Public Working Draft of Incremental Font Transfer. This specification defines two methods to incrementally transfer fonts from server to client. Incremental transfer allows clients to load only the portions of the font they actually need which speeds up font loads and reduces data transfer needed to load the fonts. A font can be loaded over multiple requests where each request incrementally adds additional data.

Working Group Note: XR Accessibility User Requirements

 1 September 2021

The Accessible Platform Architectures (APA) Working Group has published XR Accessibility User Requirements (XAUR) as a Working Group Note. XR refers to hardware, applications, and techniques used for virtual reality or immersive environments (VR), augmented or mixed reality (AR), and other related technologies. XAUR introduces technical accessibility challenges, such as the need for multi-modal support, synchronization of input and output devices, and customization. It describes accessibility user needs and suggests requirements. XAUR is for designers and developers involved in creating immersive and augmented experiences. It’s also useful for anyone who wants to better understand accessibility in a range of immersive or augmented environments.

Tuesday, August 17, 2021

First Public Working Draft: MathML Core

 The Math Working Group has published the First Public Working Draft of MathML Core.

The MathML Core specification tries to address several issues related to implementing MathML in browsers. The MathML3 specification has been difficult to implement for browsers, because it is big and does not contain very precise rules for rendering math formulas. MathML also has several parts that are not useful in browsers. The MathML Core specification tries to define an appropriate subset of MathML, describe its rendering in detail (using rules from the TeXBook and the Open Font Format as basis) and clarify the interactions of MathML with other parts of HTML and the Open Web Platform.

The Math Working Group is also working on the rest of MathML. It is defining MathML4, the fourth version of MathML. The features included in MathML Core may evolve, or a second version of MathML Core may be defined, depending on how MathML4 develops.

W3C Workshop Report: Smart Cities

 

Illustration showing a night cityscape and connected pictogramsW3C is pleased to announce the report from the W3C Workshop on Smart Cities, held on 25 June 2021.

The main goal of the workshop was to improve and finalize the description of the draft Charter for a potential Smart Cities Interest Group so that we can launch the Interest Group and start further discussions on (1) interoperability for Web-based Smart City services and (2) use cases and requirements that W3C specifications need to meet to support Smart City services.

Workshop discussions:

  • Identified Smart Cities standardization stakeholders to drive the development of Web standards aligned with the real needs of Smart Cities
  • Clarified reasonable applications for Smart Cities technologies
  • Pointed out how to improve the draft Charter for the potential Smart Cities Interest Group

As a concrete next step following the workshop, W3C will finalize the draft Charter hoping to launch a Smart Cities Interest Group and start further discussion within the group.

We thank all the presenters and the participants for making this event a success.

Thursday, July 8, 2021

Authorized Translation of WCAG 2.1 in Norwegian

 

Screenshot showing the w3c logo and the title of the W3C WCAG 2.1 Web Content Accessibility GuidelinesThe World Wide Web Consortium published the Authorized Norwegian Translation of Web Content Accessibility Guidelines (WCAG) 2.1Retningslinjer for universell utforming av nettinnhold (WCAG) 2.1. The Lead Translation Organization for this Authorized Translation was the Digitaliseringsdirektoratet (Norwegian Digitalisation Agency).

Translations in other languages are listed in WCAG 2 Translations. W3C Web Accessibility Initiative (WAI) particularly encourages the development of Authorized Translations of WCAG 2.1 and other technical specifications to facilitate their adoption and implementation internationally. Read about the Policy for W3C Authorized Translations.

Web Audio API is a W3C Recommendation

 

web audio logoThe Audio Working Group has published Web Audio API as a W3C Recommendation. This specification describes a high-level Web API for creating, shaping, and processing audio directly in a Web browser or in web applications.

With the API standardized and deployed as a royalty-free feature in Web browsers and other devices and platforms, both on desktop and mobile, creating sound with the Web Audio API has become a dependable, widely available, built-in capability, eliminating the need to install plugins or download separate applications. You may read more in our Press Release.

Monday, April 5, 2021

W3C re-introduces popular BLINK feature

 

[At the occasion of April Fools’ Day] W3C today re-introduced the popular BLINK feature as part of the open web platform, thus mitigating the community critique about the removal of the early version.

Using state-of-the-art W3C technology, Web authors now can be sure to get the readers’ attention that their important information deserves, and web users to never miss important information again.

The new feature gives back full editing control to web authors while ensuring an inclusive user experience for all. More information is available in the press release.

Monday, March 8, 2021

W3C accepting proposals for Professional Employer Organization (PEO) Services

 Since its founding in 1994 by Web Inventor Tim Berners-Lee, the World Wide Web Consortium has developed the foundational technical standards upon which the Web has flourished. The Web and its place in society have changed dramatically, and the Web Consortium has been at the core of its technical interoperability. Today we need a more dramatic transformation to address the opportunities and threats the Web now faces and to continue to shape its future constructively.

W3C is currently headquartered in Massachusetts, with staff members distributed around the world. Four institutions partner to “host” W3C: MIT (USA), ERCIM (France), Keio University (Japan), and Beihang University (China). We are planning the transition to a USA-based incorporated legal entity, a 501(c)(3) non-profit, as of January 1, 2022, which will continue to work with the distributed staff while consolidating financial and administrative functions. The Web Consortium is accepting proposals for Professional Employer Organization (PEO) Services; please consult our RFP.

If your organization provides these services please submit a proposal by email to W3CLEadmin@w3.org. If you have any questions, you can send them to that same address.

Interested parties must respond by Friday, March 26, 2021, and we expect to make a selection by Friday, April 9, 2021. We look forward to getting some robust responses!

W3C Invites Implementations of WAI-ARIA 1.2

 The Accessible Rich Internet Applications Working Group invites implementations of a Candidate Recommendation of Accessible Rich Internet Applications (WAI-ARIA) 1.2. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML] and [SVG2]. This specification complements both [HTML] and [SVG2].

Please share any implementations or comments by 5 April 2021.

Thursday, February 25, 2021

First Public Working Draft: EPUB Accessibility 1.1

 The EPUB 3 Working Group has published a First Public Working Draft of EPUB Accessibility 1.1. This document specifies content conformance requirements for verifying the accessibility of EPUB Publications. It also specifies accessibility metadata requirements for the discoverability of EPUB Publications. The document takes an abstract approach to the accessibility requirements for EPUB Publications, similar to how WCAG 2 separates its accessibility guidelines from the techniques to achieve them. This approach allows the guidelines to remain stable even as the format evolves.

To facilitate this approach, a companion EPUB Accessibility Techniques 1.1 has also been published today as a W3C Working Group Note, which outlines conformance techniques. These techniques explain how to meet the requirements of this document for different versions of EPUB.

The Working Group welcomes comments via the GitHub repository issues.

W3C Workshop Report: Maps for the Web

 

Maps of Montreal, past, present, and future.W3C is pleased to announce a report from the W3C/OGC Joint Workshop Series on Maps for the Web, held in September & October, 2020.

Through live presentations, panel discussions, and pre-recorded videos, workshop participants discussed requirements and proposals for Web platform maps.

As an outcome of the workshop, participants seek to initiate a cross-community (W3C, OGC among others) working group that will define a roadmap to specify and implement native Web maps. The ongoing work was initiated and has been incubated in the ​W3C Maps for HTML Community Group​ since late 2014. Anyone interested in participating in the Maps for the Web discussions should join the free W3C Community Group.

W3C thanks our sponsor, Natural Resources Canada, the ​Program Committee​, our co-host, the Open Geospatial Consortium, and all the participants for making this event a success. Please read more in the W3C Blog post.

Wednesday, January 13, 2021

First Public Working Drafts: EPUB 3.3

 12 January 2021

The EPUB 3 Working Group has published four First Public Working Drafts today for EPUB 3.3. This technology defines a distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced Web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file container.

The specification represents the third major revision and, in particular, a revision of the EPUB 3.2 document published by the EPUB 3 Community Group. This new version of the specification is now on a W3C Recommendation Track.

The four documents published by the Working Group are:

  • The EPUB 3.3 specification defines the authoring requirements for EPUB Publications and represents the third major revision of the standard.
  • The EPUB 3.3 Reading Systems specification defines the conformance requirements for EPUB 3 Reading Systems — the user agents that render EPUB Publications.
  • The EPUB Multiple-Rendition Publications 1.1 specification defines the creation and rendering of EPUB Publications consisting of more than one Rendition. This document is not on recommendation track.
  • The EPUB 3 Overview gives a high level overview of the EPUB 3.3 specification aimed primarily at non-technical readers. This document is not on recommendation track.

The Working Group welcomes comments via the GitHub repository issues.

W3C Advisory Committee Elects Technical Architecture Group

 

W3C TAG logoThe W3C Advisory Committee has elected the following people to the W3C Technical Architecture Group (TAG): Amy Guy (Digital Bazaar), Sangwhan Moon (W3C Invited Expert), Theresa O’Connor (Apple, Inc.) and Lea Verou (W3C Invited Expert). They join co-Chair Tim Berners-Lee and continuing participants, Daniel Appelquist (Samsung Electronics; co-Chair), Rossen Atanassov (Microsoft Corporation), Hadley Beeman (W3C Invited Expert), Kenneth Rohde Christiansen (Intel Corporation) and Peter Linss (W3C Invited Expert; co-Chair). Yves Lafon continues as staff contact. Many thanks for contributions to the TAG to the departing participants, David Baron (W3C Invited Expert) and Alice Boxhall (Google), whose terms end at the end of this month.

The TAG is a special group within the W3C, chartered under the W3C Process Document, with stewardship of the Web architecture. The mission of the TAG is to build consensus around principles of Web architecture and to interpret and clarify these principles when necessary, to resolve issues involving general Web architecture brought to the TAG, and to help coordinate cross-technology architecture developments inside and outside W3C. The elected Members of the TAG participate as individual contributors, not as representatives of their organizations. TAG participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user. Learn more about the TAG.