Re: Question regarding browser-specific issues

Hi, Rajiv:

My apologies for the jargon. FPWD is W3C specific shorthand for a key
step in the process that eventually results in a formal, official W3C
technical recommendation.

Example: The current W3C Web Content Accessibility Guidelines (WCAG)
technical recommendation is version 2.1. Those of us working in the W3C
Web Accessibility Initiative (WAI) are aware a version 2.2 is nearing
completion and may be the current version by this time next year--but it
doesn't happen until it happens!

FPWD stands for "First Public Working Draft." In the specific situation
of work on what will eventually become WCAG 3.0, the FPWD is the first
instance when W3C requests wide review and comments from the wider
community of interested stakeholders. The WCAG 3.0 FPWD was formally
announce on  key W3C web pages, and on the WAI-Announce email list and
published just amonth ago. If you missed that email, you can find it
here:

https://lists.w3.org/Archives/Public/public-wai-announce/2021JanMar/0002.html

Meanwhile, if you'd like to know more about the formal W3C process that
results in the various W3C technical recommendations, those details are
available here:

http://www.w3.org/Guide/

hth

Janina


Rajiv Shah writes:
> 
> Hi,
> 
> Following up on this, Janina, I love your suggestions. But may I ask, what is an FPWD?
> 
> Rajiv
> ----- Original Message -----
> From: Janina Sajka <janina@rednote.net>
> To: Patrick H. Lauke <redux@splintered.co.uk>
> Cc: Brooks Newton <brooksallennewton@gmail.com>, w3c-wai-ig@w3.org
> Sent: Wed, 17 Feb 2021 23:07:00 -0500 (EST)
> Subject: Re: Question regarding browser-specific issues
> 
> In the past WAI attempted to address this with separate specifications
> WCAG for content, ATAG for authoring, UAAG for user agents.
> 
> The current AGWG Charter rolls this all into WCAG 3, though the recently
> published FPWD doesn't reflect this expectation yet.
> 
> I propose a good starting point for Silver, something I have raised and
> will raise again, would be low hanging fruit. My top suggestions:
> 
> *	Auto-playing audio. There's no reason a browser can't block
> *	that.
> 
> *	Constraints on flashing can also be mitigated by user agents. I
> *	would far rather depend on a user agent for such prophylaxis
> *	than on the good behavior of content creators.
> 
> May I note that flashing is life threatening to many who are sensitive
> to flashing. I think it's unique in that sense among WCAG SC.
> 
> Best,
> 
> Janina
> 
> Patrick H. Lauke writes:
> > On 17/02/2021 23:21, Brooks Newton wrote:
> > > There will be no appetite if you haven't taken the first step in making
> > > it a possibility, which is to include all parties to the user experience
> > > in the master plan framework for accessibility. The W3C, or any other
> > > standards body for that matter, lacks the direct capacity to compel
> > > content authors to adjust their sites, apps, etc. to follow WCAG rules.
> > > So how did it work it out that WCAG only speaks to content authors, and
> > > not the other parties to the user experience?
> > 
> > Again, I'd refer you to UAAG and ATAG and the work that WAI has attempted in
> > the past at getting browser devs, AT devs, etc around the table. Sure, it
> > might be worth another shot, but let's not make it sound like this hasn't
> > actually been attempted before...
> > 
> > P
> > -- 
> > Patrick H. Lauke
> > 
> > https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> > https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> > twitter: @patrick_h_lauke | skype: patrick_h_lauke
> 
> -- 
> 
> Janina Sajka
> https://linkedin.com/in/jsajka
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:	http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> 
> 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Received on Monday, 22 February 2021 12:08:09 UTC