Re: draft text for charter

> On 27 Feb 2017, at 17:47, deborah.kaplan <deborah.kaplan@suberic.net> wrote:
> 
> I am fine with this text. It's longer than I thought Ivan wanted it to
> be,  but if he thinks it's aan acceptable length I think it's relatively
> clear while also being explicit  about the fact that we will incorporate
> accessibility requirements in any recommendation-track deliverables,,
> and the fact that we will be coordinating with other groups.


Well… it is a little bit too long, compared to the rest of the charter. That, by itself, may be ok, however (if I play devil's advocate, the following text:

[[
The Working Group will incorporate accessibility considerations into the
Working Group's deliverables. Recommendation-track deliverables  will
contain mechanisms to make Web Publications accessible to a broad range of
readers with different needs and capabilities.
]]

may be considered to be superfluous in the charter. The reason is that this is a requirement for any W3C recommendation, mainly when talking about user-facing specifications like this. In other words, this does not add anything to what is already a default requirement, does it?

For me, the important point is:

[[
...additional extended requirements will be
identified as conformance requirements in the Working Group’s normative
specifications. Profiles of Web Publications may be defined with more
stringent accessibility requirements.
]]

because it shows that we _may_ have extra requirements and we intend to put these into the spec as well. For me, _that_ is the important point...


> 
> My only issue  is the following:
> 
> "The Digital Publishing Working Group will coordinate with the WCAG Working
> Group to integrate accessibility requirements created as part of its
> recommendation-track deliverables into generalized technology."
> 
> I don't think we should be limiting ourselves to coordinating with WCAG.
> I would prefer  "will coordinate with the WCAG Working Group, as well as
> any other  working groups as needed, to integrate …"

This may be vague, what about "wg-s concerned with accessibility', or something like that?

Ivan


> 
> Deborah
> 
> On Mon, 27 Feb 2017, Avneesh Singh wrote:
> 
>> Dear all,
>> 
>> A reminder, we need to complete the text for accessibility soon. Please provide your comments so that it can be published with next update of charter.
>> 
>> 
>> With regards
>> Avneesh
>> -----Original Message----- From: Avneesh Singh
>> Sent: Tuesday, February 21, 2017 12:34
>> To: George Kerscher ; 'Ivan Herman'
>> Cc: 'Deborah Kaplan' ; public-dpub-accessibility@w3.org
>> Subject: Re: draft text for charter
>> 
>> Dear accessibility group,
>> 
>> After our call yesterday, George has merged the old accessibility text that
>> was proposed by Matt with the new text added by Ivan in the branch.
>> I will also like to mention that in the branch created by Ivan, the
>> accessibility text is placed at more than one places. The first paragraph
>> was placed by Ivan in the scope statement, and other part was placed at the
>> places where the charter talked about coordination with ARIA and WCAG.
>> We are fine with this split, and the new text snippet is the rewrite of only
>> the scope statements.
>> 
>> New text for scope statement:
>> The Working Group will incorporate accessibility considerations into the
>> Working Group's deliverables. Recommendation-track deliverables  will
>> contain mechanisms to make Web Publications accessible to a broad range of
>> readers with different needs and capabilities. This includes general WCAG
>> and WAI requirements of the W3C; additional extended requirements will be
>> identified as conformance requirements in the Working Group’s normative
>> specifications. Profiles of Web Publications may be defined with more
>> stringent accessibility requirements.
>> 
>> And following is the text in coordination section:
>> The Digital Publishing Working Group will coordinate with the WCAG Working
>> Group to integrate accessibility requirements created as part of its
>> recommendation-track deliverables into generalized technology. One or more
>> pipeline of the requirements will be maintained to manage diverse turnaround
>> times of the W3C groups.
>> 
>> With regards
>> Avneesh


----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704