This is the list of proposed Community and Business Groups. To express support for a group, you must have a W3C account. Once a group has sufficient support (5 supporters), W3C announces its creation, lists it on the current groups page, and people can join it to begin work.
Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
People reach more and more of the world's information — reading, learning, medical and scientific imagery, public services, transit and travel guidance, signage, connected devices and control surfaces — through software built on a web rendering engine running as a native application, rather than inside a traditional browser. How well that engine is used directly shapes whether information is readable, usable, and accessible to everyone.
The mission of this group is to improve how rendering engines are used by bringing together people across every field that builds on rendering engines, including: publishing systems, government and civic services, transportation and transit, architecture and construction, broadcasting and media, embedded devices and the Web of Things, games, and assistive technology. Across these fields, the group shares practical patterns and surfaces the parts of the web platform that are under-specified or awkward when an engine is embedded outside the traditional browser.
Concretely, the group looks at how to give people: text that is readable in any language (including Japanese vertical writing, ruby and CJK typography); content that is accessible to assistive technology (bridging the web accessibility tree to platform APIs such as AT-SPI / UIA); rich visuals such as 3D models in education, medicine, and architecture and construction (GPU / EGL rendering paths); captioned and synchronized media for broadcasting and accessible publications (Media Overlays); secure access to licensed material for libraries (e.g. Readium LCP); and responsive, real-time interfaces for control surfaces, devices and interactive applications — together with the application lifecycle, native integration and performance characteristics that make these dependable.
This group will not publish Specifications. It incubates findings — best-practice guides, gap analyses, sample code and test cases — that may inform relevant W3C Working Groups (for example CSS, Internationalization, Accessibility (APA/ARIA), Web Performance, Web of Things, and EPUB/Publishing), handing off concrete proposals where useful.
