Outdated Content!

The Protocols and Formats Working Group is no longer chartered to operate. Its work will continue in two new Working Groups:

  • https://www.w3.org/WAI/APA/ Accessible Platform Architectures, to review specifications, develop technical support materials, collaborate with other Working Groups on technology accessibility, and coordinate harmonized accessibility strategies within W3C; and
  • https://www.w3.org/WAI/ARIA/ Accessible Rich Internet Applications, to continue development of the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications when needed to bridge known gaps.

Resources from the PFWG remain available to support long-term institutional memory, but this information is of historical value only.

This Wiki page was edited by participants of the Protocols and Formats Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


From Protocols and Formats Working Group Wiki
Jump to: navigation, search

CSS Development and Co-Ordination

August 2011: The PFWG is engaging in a comprehensive CSS review.


Previous PF Work on CSS

Issues To Be/Being Discussed with the CSS WG

  • CSS Spriting - assuring accessibility and ease of authoring
  • CSS-generated text
    • issue: Generated content is difficult to determine how to handle because it's not in the DOM but user agents may or may not need to expose to users.
  • CSS Media Types
  • Pseudo-classes for ARIA (Rich Schwerdtfeger to work up)
  • Semantic alternatives to display properties (Stefan Schnabel to work up)
  • Separation of content and presentation, or not (a goal, but not realistic for developers, how to we make accessible) (James Nurthen)
  • Navigation order

CSS 2.1 Comments and Follow-Up

CSS3 Modules Being Monitored

CSS3 Candidate Recommendations

Note: drafts are listed in chronological order; please note that MANY of the CSS3 Modules have been in Candidate Recommendation status for a very extended period of time. Note that the abbreviation "CR" means "Candidate Recommendation"

CSS3 Documents in Last Call

CSS3 Working Drafts

The CSS3 Aural Module versus The CSS3 Speech Module

Resuscitation of Deprecated, Yet Needed, CSS3 Modules

  • CSS3-Reader (dropped by Style Activity March 2008)
    • Abstract: The keyword 'reader' is a media type for use in Media Queries (similar to 'screen', 'print', 'projection', etc.). Devices that might choose to apply rules inside '@media reader' are devices like screen readers, that display a page on screen and speak it at the same time, or display the page and simultaneously render it on a dynamic braille device. The properties that apply to this media type are therefore the combination of the properties for screen, speech and braille.
      • Gregory J. Rosmaita is currently seeking live bodies to work on reviving CSS3-Reader -- outreach is being made to the Braille-in-DAISY group, braille standards bodies and other interested parties

CSS3 Individual Module Issues