index.html 26.6 KB
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
		<title>Protocols and Formats Working Group Public Page</title>
		<link rel="stylesheet" href="../wai-main.css" type="text/css" />
		<!--[if IE 7]><link rel="stylesheet" href="/WAI/ie-old.css" type="text/css" media="all"/><![endif]-->
	</head>
	<body> <div id="controls"><ul>
      <li><a href="#skip" shape="rect"><img src="/Icons/downinpage.png" alt="" /> Skip to Content </a></li>
      <li><a href="/WAI/changedesign.html" shape="rect"> | Change 
         text size or colors </a> </li>
   </ul></div> <div id="masthead"><p id="logos"><a href="http://www.w3.org/" title="W3C Home" shape="rect"><img alt="W3C logo" src="/Icons/w3c_home" /></a><a href="http://www.w3.org/WAI/" title="WAI Home" shape="rect"><img alt="Web Accessibility initiative" src="/WAI/images/wai-temp" /></a></p></div> <div id="tagline"><p>WAI: Strategies, guidelines, resources to make the
      Web accessible to people with disabilities</p></div>
		<div id="nav"><h2>Site Navigation</h2><p id="w3cnav"><a href="http://www.w3.org/">W3C Home</a></p><p id="subhomenav"><a href="/WAI/">Web Accessibility Initiative (WAI) Home</a></p><ol id="nav1" type="A"><li><a href="../gettingstarted/Overview.html" shape="rect">Getting Started</a></li><li><a href="../users/Overview.html" shape="rect">Designing for Inclusion</a></li><li><a href="../guid-tech.html" shape="rect">Guidelines &amp; 
            Techniques</a></li><li><a href="../managing.html" shape="rect">Planning &amp; Implementing</a></li><li><a href="../eval/Overview.html" shape="rect">Evaluating Accessibility</a></li><li><a href="../train.html" shape="rect">Presentations &amp; Tutorials</a></li><li class="current-nav "><a href="../about-links.html" shape="rect">Getting Involved with WAI</a><ol type="1"><li><a href="../participation.html" shape="rect">Participating</a></li><li><a href="../about.html" shape="rect">About WAI</a></li><li><a href="../about/usingWAImaterial.html" shape="rect">Using WAI Material</a></li><li><a href="../about/announcements.php" shape="rect">Getting WAI Announcements</a></li><li class="current-nav "><a href="../groups.html" shape="rect">WAI Groups</a><ol type="1" class="anno"><li><a href="../AU/Overview.html" shape="rect">Authoring Tool (AUWG) </a></li><li><a href="../EO/Overview.html" shape="rect">Education &amp; Outreach (EOWG)</a></li><li><a href="../ER/Overview.html" shape="rect">Evaluation Tools (ERT WG) </a></li><li id="current-node" class="current-nav "><span class="label"><span id="current-icon">»</span>Protocols &amp; Formats (PFWG) </span><ol type="i"><li><a href="participation.html" shape="rect">How to Join (Participation)</a></li><li class="external"><a href="/WAI/PF/charter201006" shape="rect">Charter <img src="/Icons/tr.png" alt="different format" /></a></li><li><a href="comments/Overview.php" shape="rect">Comments</a></li><li class="external"><a href="http://lists.w3.org/Archives/Public/wai-xtech/" shape="rect">XTECH E-mail Archives <img src="/Icons/tr.png" alt="archive format" /></a></li><li class="external"><a href="http://lists.w3.org/Archives/Member/w3c-wai-pf/" shape="rect">PFWG E-mail Archives, Member <img src="/Icons/tr.png" alt="archive format" /></a></li><li class="external"><a href="/WAI/PF/Group/" shape="rect">PFWG Members Area <img src="/Icons/tr.png" alt="different format" /></a></li></ol></li><li><a href="../RD/Overview.html" shape="rect">Research (RDWG)</a></li><li><a href="../UA/Overview.html" shape="rect">User Agent (UAWG) </a></li><li><a href="../IG/Overview.html" shape="rect">WAI Interest Group (WAI IG) </a></li><li><a href="../GL/Overview.html" shape="rect">Web Content (WCAG WG)</a></li></ol></li></ol></li></ol><div id="nav-static"><div class="nav-discover">
      <p><a href="http://www.w3.org/WAI/yourWAI" shape="rect"><strong><u>Discover new resources</u></strong> for people with disabilities, policy makers, managers, and you!</a></p>
   </div><p class="translations"><a href="http://www.w3.org/WAI/wai-translations" shape="rect"><img src="http://www.w3.org/WAI/images/translations-med-1" alt="characters from different languages" /> Translations</a></p></div></div>
		<!--Make DW lay out --> <div id="main"><div id="skipwrapper"><a id="skip" shape="rect">-</a></div>
			<h1>Protocols and Formats Working Group (<acronym>PFWG</acronym>) Public
			Page</h1> <div id="contents">
			<h2>Page Contents</h2>
			<ul>
				<li><a href="#announcements" shape="rect">Announcements and
					Meetings</a></li>
				<li><a href="#current" shape="rect">Current Work</a></li>
				<li><a href="#pubs" shape="rect">Publications</a></li>
				<li><a href="#about" shape="rect">About the PFWG</a></li>
			</ul>
			<!-- end (page) contents (list)-->
			</div> <h2><a name="announcements" id="announcements" shape="rect"
			></a>Announcements and Meetings</h2> <p>3 January 2012: Published <a
			href="http://www.w3.org/TR/2012/WD-media-accessibility-reqs-20120103/"
			>Media Accessibility User Requirements</a> First Public Working Draft.
			Please <a href="http://www.w3.org/WAI/PF/comments/instructions"
			shape="rect">comment</a> by 10 February 2012.</p> <p>18 January 2011:
			Published <a href="http://www.w3.org/TR/2011/CR-wai-aria-20110118/"
			shape="rect">WAI-ARIA 1.0 Candidate Recommendation</a>. Read the <a
			href="http://www.w3.org/QA/2011/01/wai-aria-cr.html" shape="rect">WAI-ARIA
			publication announcement</a>. Please <a
			href="http://www.w3.org/WAI/PF/comments/instructions" shape="rect"
			>comment</a> by 25 February 2011.</p> <p>13 January 2011: Published <a
			href="http://www.w3.org/TR/2011/WD-role-attribute-20110113/" shape="rect"
			>Last Call Working Draft of Role Attribute 1.0</a>. Please <a
			href="http://www.w3.org/WAI/PF/comments/instructions" shape="rect"
			>comment</a> by 25 February 2011.</p> <p><a href="Group/meetings/f2fmar12"
			>Face to face meeting 5 - 7 March 2012 in Austin, TX</a></p> <h2><a
			name="current" id="current" shape="rect">Current Work</a></h2> <h3><a
			name="review" id="review" shape="rect"></a>Public Working Drafts under
			review</h3> <p>The Protocols and Formats Working Group invites public
			comment on the 3 January 2012 Working Draft of <a
			href="http://www.w3.org/TR/2012/WD-media-accessibility-reqs-20120103/"
			>Media Accessibility User Requirements</a>. Follow the <a
			href="http://www.w3.org/WAI/PF/comments/instructions" shape="rect"
			>instructions for commenting</a> page to submit comments. <a
			href="http://www.w3.org/WAI/PF/comments/submit?document_version_id=6"
			shape="rect">Submit comments online</a> (preferred) or by email to to <a
			href="mailto:public-pfwg-comments@w3.org" shape="rect"
			>public-pfwg-comments@w3.org</a> (<a
			href="http://lists.w3.org/Archives/Public/public-pfwg-comments/"
			title="PFWG public comments list archive" shape="rect">Archive</a>).
			Comments should be made by <strong>25 February 2011</strong>.</p> <h3><a
			name="specreview" id="specreview" shape="rect"></a>Technology Review</h3>
			<p>W3C invites public comment on the <a
			href="http://www.w3.org/TR/tr-status-all.html#tr_LCWD" shape="rect"
			>Working Drafts in Last Call</a>. The WAI and the Protocols and Formats
			Working Group invite anyone who perceives an access problem with these
			drafts to comment. Submit your comments as directed in the individual
			drafts; the email addresses vary from document to document.</p><h3>
			Technical Specifications</h3> <p>Please note that Editors' Drafts:</p> <ul>
			<li> May not be up-to-date with recent Working Group decisions</li>
			<li> Do not necessarily represent Working Group consensus, that is, the
				drafts may include proposals that the Working Group has not agreed
				on</li>
			<li> May change frequently without public notification </li>
			<li> Include "Editorial notes" that are intended for public review and
				comment </li>
			<li> Include internal "Todo" notes and areas that are not ready for review
			</li>
			</ul> <p>Edits to documents are posted regularly to the publicly visible
			editors' draft. People interested in following the work can subscribe to
			the public-pfwg-cvs mailing list to receive notification when changes are
			checked in. Techniques and examples of how to apply these technologies to
			create rich internet applications are discussed on the <a
			href="http://lists.w3.org/Archives/Public/wai-xtech/latest" shape="rect"
			>wai-xtech</a> mailing list. See <a href="#participation" shape="rect"
			>participation</a> for how to follow or get involved in this work.</p>
			<h4><a name="aria" id="aria" shape="rect"></a>Accessible Rich Internet
			Applications (WAI-ARIA)</h4><p>WAI-ARIA, the Accessible Rich Internet
			Applications Suite, defines a way to make Web content and Web applications
			more accessible to people with disabilities. It especially helps with
			dynamic content and advanced user interface controls developed with Ajax,
			HTML, JavaScript, and related technologies.</p> <p>The work has been
			divided into five documents.  The current editor's working drafts of these
			are: </p> <dl>
			<dt><a href="aria-roadmap/" shape="rect">Roadmap for Accessible Rich
				Internet Applications (WAI-ARIA Roadmap) (public editor's draft)
				</a></dt>
			<dd>This roadmap that describes the problem, what W3C specifications will
				be used to correct the problem, and the timeline for the new
				specifications. See also the <a href="/TR/wai-aria-roadmap/"
				shape="rect">Public Working Draft of the WAI-ARIA Roadmap</a>. </dd>
			<dt><a href="aria/" shape="rect">Accessible Rich Internet Applications
				(WAI-ARIA) (public editor's draft) </a><a
				href="http://www.w3.org/WAI/PF/GUI/" shape="rect"></a></dt>
			<dd>This specification provides an ontology of roles, states, and
				properties that set out an abstract model for accessible interfaces and
				can be used to improve the accessibility and interoperability of Web
				Content and Applications. This information can be mapped to
				accessibility frameworks that use this information to provide
				alternative access solutions. Similarly, this information can be used to
				change the rendering of content dynamically using different style sheet
				properties. The result is an interoperable method for associating
				behaviors with document-level markup. See also the <a
				href="/TR/wai-aria/" shape="rect">Public version of WAI-ARIA</a>.</dd>
			<dt><a href="aria-primer/" shape="rect">WAI-ARIA Primer (public editor's
				draft) </a></dt>
			<dd>Explains the accessibility problems posed by hybrid technologies such
				as DHTML and AJAX and introduces the technologies to map controls, AJAX
				live regions, and events to accessibility APIs. Also describes new
				navigation techniques to mark common Web elements such as menus, primary
				content, secondary content, banner information and other types of Web
				structures. See also the <a href="/TR/wai-aria-primer/" shape="rect"
				>Public Working Draft of the WAI-ARIA Primer </a>.</dd>
			<dt><a href="aria-practices/" shape="rect">WAI-ARIA Authoring Practices
				(public editor's draft) </a></dt>
			<dd>Provides recommended approaches to create accessible Web content using
				WAI-ARIA roles, states, and properties to make widgets, navigation, and
				behaviors accessible. Also describes considerations that might not be
				evident to most implementors from the WAI-ARIA specification alone. See
				also the <a href="/TR/wai-aria-practices/" shape="rect">Public Working
				Draft of the WAI-ARIA Authoring Practices</a>.</dd>
			<dt><a href="aria-implementation/" shape="rect">WAI-ARIA User Agent
				Implementation Guide (public editor's draft)</a></dt>
			<dd>Describes how user agents should map WAI-ARIA features to platform
				accessibility APIs. See also the <a href="/TR/wai-aria-implementation/"
				shape="rect">Public Working Draft of the WAI-ARIA User Agent
				Implementation Guide</a>.</dd>
			</dl> <p>Formal Public Working Drafts of these documents can be found from
			the <a href="/WAI/intro/aria" shape="rect">WAI-ARIA Overview Page</a>.
			</p> <h4><a name="role-attribute" id="role-attribute" shape="rect"
			></a>Role Attribute</h4> <p>The <a href="role-attribute/" shape="rect"
			>Role Attribute (public editor's draft)</a> allows the author to annotate
			markup languages with machine-extractable semantic information about the
			purpose of an element. Use cases include accessibility, device adaptation,
			server-side processing, and complex data description. This attribute can
			be integrated into any markup language. The role attribute is necessary to
			support WAI-ARIA to define roles in XML-based languages, when the
			languages do not define their own role attribute. See also the <a
			href="/TR/role-attribute/" shape="rect">Public Working Draft of the Role
			Attribute</a>.</p> <h4><a name="media-a11y-reqs" id="media-a11y-reqs"
			shape="rect"></a>Media Accessibility User Requirements</h4> <p><a
			href="media-a11y-reqs/" shape="rect">Media Accessibility User Requiremenst
			(public editors' draft)</a> aggregates the requirements of an
			accessibility user that the W3C HTML5 Accessibility Task Force has
			collected with respect to audio and video on the Web.  See also the <a
			href="http://www.w3.org/TR/media-accessibility-reqs/">Public Working Draft
			of Media Accessibility User Requirements</a>.</p> <h3><a name="taskforces"
			id="taskforces" shape="rect"></a>Task Forces</h3> <h4><a name="tf-aria"
			id="tf-aria" shape="rect"></a>WAI-ARIA Task Force</h4> <p>This task force
			develops the WAI-ARIA technology. Currently we are processing comments
			received on the latest ARIA Working Draft. ARIA issues are tracked in the
			<a href="comments/" shape="rect">PFWG public comments tracker</a>. The <a
			href="#aria" shape="rect">section on WAI-ARIA</a> has further information
			about how to follow this work.</p> <h4><a name="tf-aria-uaig"
			id="tf-aria-uaig" shape="rect"></a>WAI-ARIA User Agent Implementation Task
			Force</h4> <p>The publicly visible <a href="/WAI/PF/aria-ua-task-force"
			shape="rect">User Agent Implementation Task Force</a> is a joint task
			force of the PFWG and the <a href="http://www.w3.org/html/wg/"
			shape="rect">HTML Working Group (HTML WG)</a>. The objective of UAI TF is
			to develop guidelines for interoperable user agent implementation of the
			WAI-ARIA specification. Discussion and meeting information is posted to
			the WAI-XTech mailing list with the subject prefix "aapi". The <a
			href="#aria" shape="rect">section on WAI-ARIA</a> has further information
			about how to follow this work.</p> <h4><a name="tf-html-a11y"
			id="tf-html-a11y" shape="rect"></a>HTML Accessibility Task Force</h4>
			<p>The <a href="/WAI/PF/html-task-force" shape="rect">HTML Accessibility
			Task Force</a> is a joint task force of the PFWG and the <a
			href="http://www.w3.org/html/wg/" shape="rect">HTML Working Group (HTML
			WG)</a>. The objective of this task force is to review accessibility
			considerations for HTML 5. The work of this task force is mainly tracked
			in the <a href="http://www.w3.org/WAI/PF/HTML/wiki/" shape="rect">HTML
			Accessibility Task Force wiki</a>. The task force currently has a number
			of sub-groups focusing on <a
			href="http://www.w3.org/WAI/PF/HTML/wiki/Media_Sub-Group" shape="rect"
			>media</a>, <a href="http://www.w3.org/WAI/PF/HTML/wiki/Canvas"
			shape="rect">canvas</a>, <a
			href="http://www.w3.org/WAI/PF/HTML/wiki/ARIA_Integration" shape="rect"
			>ARIA integration</a>, and <a
			href="http://www.w3.org/WAI/PF/HTML/wiki/Bug_Triage" shape="rect">bug
			triage</a>.</p> <h4>Specification Accessibility Task Force</h4> <p><a
			name="tf-spec-review" id="tf-spec-review" shape="rect"></a>The <a
			href="/WAI/PF/Group/spec-review-tf" shape="rect">Specification
			Accessibility Task Force</a> assists the Working Group with accessibility
			review of W3C specifications. Currently this work is done by the working
			group as a whole.</p> <h2><a id="pubs" name="pubs" shape="rect"
			>Publications</a></h2> <p>In addition to the <a href="#aria" shape="rect"
			>WAI-ARIA documents</a> and the Role Attribute, the PFWG has been
			responsible in the past for the incorporation of a number of the
			accessibility improvements introduced into W3C formats from HTML 4.0
			onward including CSS, SMIL, SVG and VoiceXML. Some specific publications
			developed in service of this work:</p> <dl>
			<dt><a href="http://www.w3.org/TR/turingtest" shape="rect">Inaccessibility
				of Visually-Oriented Anti-Robot Tests: Problems and
				Alternatives</a></dt>
			<dd>This paper evaluates the accessibility problems with <a
				href="http://www.captcha.net/" shape="rect"><acronym
				title="Completely Automated Public Turing test to tell Computers and Humans Apart"
				>CAPTCHA</acronym></a>, a visual verification system popular on many Web
				sites, and evaluates a number of more-accessible alternatives to the
				same problems CAPTCHA claims to solve.</dd>
			<dt><a href="http://www.w3.org/WAI/PF/natural-lang-20030326.html"
				shape="rect">Natural Language Usage -- Issues and Strategies for
				Universal Access to Information</a></dt>
			<dd>This paper suggests a possible implementation of a language annotation
				system to clarify meaning in potentially ambiguous terms.</dd>
			<dt><a href="http://www.w3.org/WAI/PF/XML/about" shape="rect">XML
				Accessibility Guidelines</a></dt>
			<dd>The discussions for XAG take place on the public <a
				href="http://lists.w3.org/Archives/Public/wai-xtech/" shape="rect"
				>wai-xtech list</a>. This specification is developed by the Working
				Group.</dd>
			</dl> Some of these are are discussed in the following education notes: <ul>
			<li><a href="/WAI/References/HTML4-access" shape="rect">HTML4
				accessibility improvements</a></li>
			<li><a href="/WAI/EO/NOTE-css-access-19990309" shape="rect">CSS2
				accessibility improvements</a></li>
			<li><a href="/WAI/EO/SMIL-access.html" shape="rect">SMIL accessibility
				improvements</a></li>
			<li><a href="/TR/SVG-access/" shape="rect">SVG accessibility Note</a></li>
			</ul> <h2><a id="about" name="about" shape="rect">About the PFWG</a></h2>
			<h3><a name="contacts" id="contacts" shape="rect"></a>Contacts</h3> <ul>
			<li>PFWG Chair: Janina Sajka &lt;<a href="mailto:janina@rednote.net"
				shape="rect">janina@rednote.net</a>&gt;</li>
			<li>PFWG W3C Staff Contact: Michael Cooper &lt;<a
				href="mailto:cooper@w3.org" shape="rect">cooper@w3.org</a>&gt;</li>
			</ul> <h3><a name="activities" id="activities" shape="rect"
			></a>Activities</h3> <p>The PFWG looks at the formal Web technologies
			(protocols, formats, etc.) from an accessibility perspective. Best
			practices for using these technologies are addressed by <a
			href="#wai-groups" shape="rect">other WAI groups</a>, producing guidelines
			explaining how to use the technologies.</p> <p>The principal output of
			this working group is feedback to other W3C working groups developing
			specification, on how to ensure that their work can allow for
			accessibility. This does not generally create deliverables in the form of
			W3C publications.</p> <p>In particular, the group tries to review at least
			every <a href="/TR/#last-call" shape="rect">Last Call working
			draft</a>.</p> <p>The PFWG also works on the <a href="/TR/xag"
			shape="rect">XML Accessibility Guidelines (XAG)</a>.</p> <h3><a
			name="charter" id="charter" shape="rect"></a>Charter</h3> <p>The <a
			href="charter201006" shape="rect">charter of the working group</a>
			outlines the goals, work methods, and requirements for participation. It
			also explains why the working drafts and email archives of this group are
			in the <a href="Group/" shape="rect">members-only</a> area. This activity
			is conducted by the <a href="/" shape="rect">W3C</a> as part of its <a
			href="/WAI/" shape="rect">Web Accessibility Initiative</a></p> <h3><a
			name="participation" id="participation" shape="rect"
			></a>Participation</h3> <p>The participation page provides details about
			<a href="participation" shape="rect">how to join the group</a>. </p> <p>To
			follow the work of the WG without joining, the following resources are
			available:</p> <ul>
			<li>Subscribe to public <a href="#lists" shape="rect">mailing
				lists</a>;</li>
			<li>Review formal and editors' drafts of <a href="#aria" shape="rect"
				>publications</a>;</li>
			<li>Submit <a href="comments/" shape="rect">public comments</a> on current
				work and review existing comments;</li>
			<li>Join <a href="#taskforces" shape="rect">task forces</a> where
				participation requirements allow.</li>
			</ul> <h3><a name="lists" id="lists" shape="rect"></a>Mailing Lists</h3> <ul>
			<li><a href="http://lists.w3.org/Archives/Public/wai-xtech/" shape="rect"
				>wai-xtech@w3.org</a> is a public list for discussion of items within
				PFWG's scope, where W3C Member-confidentiality is not required;</li>
			<li>public-pfwg-cvs@w3.org is a public non-archived announcement list to
				alert followers when edits to documents are committed;</li>
			<li><a href="http://lists.w3.org/Archives/Member/w3c-wai-pf" shape="rect"
				>w3c-wai-pf@w3.org</a> is a W3C member-confidential list for working
				group business, and for discussions of PFWG work where
				Member-confidentiality is required.</li>
			</ul> <p>Anyone can join the wai-xtech and public-pfwg-cvs mailing lists.
			Follow Instructions for <a href="participation.html#mail" shape="rect"
			>subscribing to the PFWG mailing lists</a>; in short, send email to <a
			href="mailto:wai-pf-call@w3.org?Subject=Request%20to%20join%20PF%20mailing%20list"
			shape="rect">wai-pf-call@w3.org</a> indicating which list you would like
			to join.</p> <h3><a id="neighborhood" name="neighborhood" shape="rect"
			>Some areas of related work</a></h3> <h4><a id="protols-formats"
			name="protols-formats" shape="rect">Protocols and Formats</a></h4> <p>On
			the growing edge of the Web we find Protocols and Formats such as:</p> <ul>
			<li>The <a href="/XML/" shape="rect">Extensible Markup Language (XML)</a>
				provides for continuous enhancement of the hypertext medium.</li>
			<li>The <a href="/Graphics/" shape="rect">Scalable Vector Graphics
				(SVG)</a> which introduces symbolic representation of graphics.</li>
			<li>The <a href="/Metadata/" shape="rect">Resource Description Framework
				(RDF)</a> introduces knowledge about resources to the Web.</li>
			<li>The <a href="/AudioVideo/" shape="rect">Synchronized Multimedia
				Integration Language (SMIL)</a> offers a means to exchange multimedia
				content across the breadth of the Web.</li>
			<li>The <a href="/DOM/" shape="rect">Document Object Model (DOM)</a>
				offers a neutral API for accessing the document tree.</li>
			</ul> <h4><a id="wai-groups" name="wai-groups" shape="rect">Other WAI
			Groups</a></h4> <p>Most accessibility issues involve cooperative work
			between the PFWG and its sister groups within the WAI, particularly</p> <ul>
			<li><a href="/WAI/ER/" shape="rect">Evaluation and Repair Tools (ERT)</a>
				which deals with assessing and correcting accessibility in Web
				pages</li>
			<li><a href="/WAI/GL/" shape="rect">Web Content Accessibility Guidelines
				(WCAG)</a> on the use of document formats to build resource webs of
				universal accessibility.</li>
			<li><a href="/WAI/UA/" shape="rect">User Agent Accessibility Guidelines
				(UAAG)</a> analyzes user interface dialogs and requirements, and what
				browsers and access agents that form part of the adapted client can do
				to optimize access.</li>
			<li><a href="/WAI/AU/" shape="rect">Authoring Tools Accessibility
				Guidelines (ATAG)</a> deals with the automation of accessible resource
				development and the accessibility of resource development
				automation.</li>
			<li><a href="/WAI/AU/" shape="rect">Education and Outreach (EOWG)</a>
				carries the message to various segments of the Web community.</li>
			</ul> <h3><a name="patent" id="patent" shape="rect"></a>Patent Disclosures
			</h3> <p>W3C maintains a <a rel="disclosure"
			href="http://www.w3.org/2004/01/pp-impl/32212/status" shape="rect">public
			list of any patent disclosures</a> made in connection with the
			deliverables of the group; that page also includes instructions for
			disclosing a patent.</p> <p>Janina Sajka &lt;<a
			href="mailto:janina@rednote.net" shape="rect">janina@rednote.net</a>&gt; -
			Chair, PFWG <br clear="none" /> Michael Cooper &lt;<a
			href="mailto:cooper@w3.org" shape="rect">cooper@w3.org</a>&gt; - Staff
			Contact <!-- end main --> </p> <div id="footer">
			<h2>Document Information</h2>
			<p>[<a href="/WAI/contacts" shape="rect">Contacting WAI</a>]</p>
			<div class="footer-nav">
				<p>[<a href="http://www.w3.org/WAI/sitemap.html" shape="rect">WAI Site
					Map</a>] [<a href="http://www.w3.org/WAI/sitehelp.html" shape="rect"
					>Help with WAI Website</a>] [<a
					href="http://www.w3.org/WAI/search.php" shape="rect">Search</a>] [<a
					href="/WAI/contacts" shape="rect">Contacting WAI</a>]<br clear="none"
					 /> <strong>Feedback welcome to <a href="mailto:wai-eo-editors@w3.org"
					shape="rect">wai-eo-editors@w3.org</a></strong> (a publicly archived
					list) or <a href="mailto:wai@w3.org" shape="rect">wai@w3.org</a> (a
					WAI staff-only list).</p>
			</div>
			<div class="copyright">
				<p><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright"
					shape="rect">Copyright</a> © 1994-2011 <a href="/" shape="rect"
					><acronym title="World Wide Web Consortium"
					>W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"
					shape="rect"><acronym title="Massachusetts Institute of Technology"
					>MIT</acronym></a>, <a href="http://www.ercim.org/" shape="rect"
					><acronym
					title="European Research Consortium for Informatics and Mathematics"
					>ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect"
					>Keio</a>), All Rights Reserved. W3C <a
					href="/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect"
					>liability</a>, <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks"
					shape="rect">trademark</a>, <a rel="Copyright"
					href="/Consortium/Legal/copyright-documents" shape="rect">document
					use</a> and <a rel="Copyright"
					href="/Consortium/Legal/copyright-software" shape="rect">software
					licensing</a> rules apply. Your interactions with this site are in
					accordance with our <a
					href="/Consortium/Legal/privacy-statement#Public" shape="rect"
					>public</a> and <a href="/Consortium/Legal/privacy-statement#Members"
					shape="rect">Member</a> privacy statements.</p>
			</div>
			<p>File (not content) last updated on $Date: 2012/01/05 20:22:13 $ by
				$Author shawn $</p>
			<!-- end footer -->
			</div> </div> </body>
</html>