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.
CSS
CSS Development and Co-Ordination
Contents
August 2011: The PFWG is engaging in a comprehensive CSS review.
Resources
- CSS Development Snapshot, November 2008
- Current Work on CSS (CSS WG resource)
- Grid Style Sheets and apparent competitor to some W3C CSS work
Previous PF Work on CSS
- Braille Cascading Style Sheets: A Preliminary Requirement Analysis
- CSS proposal: Add haptic Media Type to tactile Media Group
- additional issue: Should text alternatives be sensitive to specific media types, e.g., should a braille display only take text alternative from the "braille" media type.
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
- Cascading Style Sheets, Level 2.1 (CR Draft)
- Issue 1: Relegation of Aural CSS to an informative appendix & the Deprecation of the aural media type (DRAFT)
- Issue 2: Editorial Change Requested to aural.html#propdef-cue (DRAFT2)
- Issue 3: Inaccessibility of Index to CSS2.1 / Violation of WCAG (DRAFT2)
- Issue 4: Clarification Needed: Default Media Type if None Specified (DRAFT2)
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"
- CSS Ruby (CR Draft, 14 May 2003)
- CSS TV Profile (CR Draft, 14 May 2003)
- CSS Namespaces (CR Draft, 23 May 2003)
- CSS3 Basic User Interface Module (latest draft)
- CSS Basic User Interface (CR Draft, 11 May 2004)
- note: CSS Basic User Interface "describes those user interface related selectors, properties and values that are proposed for CSS level 3 to style HTML and XML (including XHTML and XForms). It includes and extends user interface related features from the selectors, properties and values of CSS level 2 revision 1 and Selectors specifications."
- CSS Basic User Interface (CR Draft, 11 May 2004)
- CSS Mobile Profile (CR Draft, 1 August 2008)
- CSS Marquee
- CSS3 Media Queries (latest draft)
- CSS Background and Borders Module Level 3 (CR Draft, 17 December 2009)
- note: CSS Background & Borders Module Level 3 replaces two earlier drafts: CSS3 Backgrounds and CSS3 Border
- CSS3 Multi-Column Layout (CR draft, 17 December 2009)
CSS3 Documents in Last Call
- CSS3 Template Layout Module (LC ends 18 May 2010)
- CSS Color Module, Level 3 (note: the Last Call draft states that the review period for this spec ended 1 September 2008)
- issue: The System Colors Deprecated in favor of the CSS3 User Interface (UI) module
- test: CSS3 System Colors Test
- issue: The System Colors Deprecated in favor of the CSS3 User Interface (UI) module
- CSS Selectors, Level 3 (Last Call)
- CSS Web Fonts, Level 3 (Last Call)
CSS3 Working Drafts
- CSS3 Writing Modes (formerly Text Layout) public working draft
- CSS3 Writing Modes (formerly Text Layout Module) latest editor's draft
- abstract: "This module specifies the text layout model in CSS and the properties that control it. It covers bidirectionality and vertical text."
- issue: Hyphenation probably enhances readability for some, but probably reduces it for others. Need to encourage appropriate use, determine whether appropriate to have default value to on or off.
- CSS3 User Interface (UI) module
- issue: The System Colors Deprecated in favor of the CSS3 User Interface (UI) module
- Behavioral Extensions to CSS
- describes the "binding" property, an alternative way for XBL UAs to bind XBL to XML elements.
- CSS Animations {latest Working Draft)
- CSS 3D Transforms Module Level 3 (latest Working Draft)
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
- 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.
CSS3 Individual Module Issues
- CSS Color Module, Level 3 (LC ends 1 September 2008)
- issue: The System Colors Deprecated in favor of the CSS3 User Interface (UI) module
- test: CSS3 System Colors Test
- issue: The System Colors Deprecated in favor of the CSS3 User Interface (UI) module
- CSS3 User Interface (UI) module
- issue: The System Colors Deprecated in favor of the CSS3 User Interface (UI) module
- unknown module(s):
- 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.
- issue: Should text alternatives be sensitive to specific media types, e.g., should a braille display only take text alternative from the "braille" media type.