- From: Janina Sajka <janina@rednote.net>
- Date: Mon, 9 Feb 2015 01:35:23 -0500
- To: public-pfwg@w3.org
While I support publication of this document as an FPWD at this time, I
do want to make two editorial suggestions. Addressing my suggestions
should NOT hold up publication, as my concerns can certainly be
addressed in future revisions.
1.) Introduction Section
This document currently enumerates the various related ARIA AAM
specifications. As the set of AAMs is likely to change from time to
time, I suggest it may be more prudent to refer to a stable URI where
the ARIA specifications set is explained. I don't believe we're
currently doing this, so this suggestion can't be implemented just yet,
but we do need to create it.
SUGGESTION: PF should create a referenceable document showing the
various ARIA specifications and their interrelationship.
2.) Relationship to Core AAM, Etc.
I'm not satisfied that the true relationship between this particular AAM
and the Core AAM is sufficiently explained. Is it not the expectation
that implementations of this specification should have already
implemented Core? In other words, there's no meaningful implementation
of ONLY this specification, without there being also an implementation
of the Core AAM?
The words currently used regarding this relationship are:
* "based on" (Status Section)
* "designed to leverage" (Status Section)
* "relies heavily on ...but defines * changes" (Introduction)
I suggest the above language intimates the relationship, but we actually need
language that makes the relationship unambiguously clear.
SUGGESTION: Reword to make it clear that implementation of Core AAM and
Nav Calculation is requisite to successful implementation of this
specification. Also add a similar sentence regarding this relationship to the
conformance section of this specification.
Janina
Janina Sajka writes:
> Colleagues:
>
> This is a Call for Consensus (CfC) to the Protocols and Formats Working
> Group to approve publication of a First Public Working Draft (FPWD) of:
>
> SVG Accessibility API Mappings (SVG-AAM) Specification
> http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html
>
> Authorization Breadcrumbs
>
> The SVG Accessibility Task Force resolution requesting FPWD publication of this
> document as logged at:
> http://www.w3.org/2015/01/30-svg-a11y-minutes.html
> And is forwarded to the PFWG in:
> http://lists.w3.org/Archives/Public/public-pfwg/2015Jan/0180.html
>
> The regular weekly PF teleconference meeting on Wednesday 4 February
> approved a resolution to advance this document to FPWD status as
> recorded at:
> https://www.w3.org/2015/02/04-pf-minutes.html#item06
>
> ACTION TO TAKE
>
> According to our agreed Consensus Procedures, this CfC is now open for
> objection, comment, as well as statements of support via email. Silence
> will be interpreted as support, though messages of support are certainly
> welcome.
>
> If you object to this proposed action, or have any comments concerning
> this proposal, please respond by replying on list to this message no
> later than 23:59 (Midnight) Boston Time on Tuesday 10 February.
>
> Janina
>
>
> --
>
> Janina Sajka, Phone: +1.443.300.2200
> sip:janina@asterisk.rednote.net
> Email: janina@rednote.net
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Protocols & Formats http://www.w3.org/wai/pf
> Indie UI http://www.w3.org/WAI/IndieUI/
>
> --
>
> Janina Sajka, Phone: +1.443.300.2200
> sip:janina@asterisk.rednote.net
> Email: janina@rednote.net
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Protocols & Formats http://www.w3.org/wai/pf
> Indie UI http://www.w3.org/WAI/IndieUI/
>
> Colleagues:
>
> This is a Call for Consensus (CfC) to confirm the sufficiency and
> accuracy of guidance on the alternative text attribute for images as
> provided by the following two related HTML-WG documents. It is also a
> Call for Consensus regarding proposed next steps for each of these
> documents.
>
> You will recall the relationship between these documents is that the
> first was initially created to elaborate criticisms against the
> sufficiency of alt guidance in the second. In other words, initially
> guidance in these two documents was different, and the two did not agree
> one with the other.
>
> We believe that over the past few years these differences have been
> successfully resolved. This CfC tests this assertion. For the record we
> are requesting the HTML-A11Y Task Force confirm this understanding,
> or point out specific remaining insufficiencies.
>
> 1.) HTML5: Techniques for providing useful text alternatives
> http://rawgit.com/w3c/alt-techniques/master/index.html
>
> This document was initially created to help remedy insufficiencies in
> early drafts of the HTML 5.0 specification. Over the past few years,
> guidance originally present in this document has been migrated to the
> HTML specification itself and removed from this document. However, it is
> believed that the remaining content in this document still provides
> valuable guidance to HTML authors.
>
> Recent edits to this document can be seen in the W3C Bugzilla bugs shown
> at the following URI:
>
> http://tinyurl.com/kjvj3bb
>
> A permanent, though very long URI for these bugs is:
>
> https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&component=CR%20alt%20techniques%20%28editor%3A%20Steven%20Faulkner%29&list_id=37965&product=HTML%20WG&query_format=advanced
>
> QUESTION 1: Does the Task Force
> a.) Accept these identified changes to this document
> b.) Recommend that work on this document be terminated; and
> c.) Support publication of this document by the HTML-WG
> as a W3C Note.
>
> 2.) HTML 5.0 Sec. 4.7.1.1 Requirements for providing text to act as
> an alternative for images
> http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#alt
>
> As noted above there have been significant edits to this section of the
> HTML 5.0 specification in order that this specification might best
> reflect current consensus guidance regarding alt. These changes are
> documented by the following W3C Bugzilla bugs:
>
> {Insert Bug List Here}
>
> QUESTION 2: Does the Task Force:
> a.) Accept these identified changes to this specification;
> b.) Recommend that work on this specification be terminated; and
> c.) Support publication of this section of this
> specification by the HTML-WG as part of W3C HTML 5.0.
>
> ACTION TO TAKE
>
> According to agreed HTML-A11Y Task Force Consensus Procedures [1], this
> CfC is now open for objection, comment, as well as statements of support
> via email. Silence will be interpreted as support, though messages of
> support are certainly welcome.
>
> If you have objections to any part of the above two questions, or any
> comments concerning the proposed next steps for either of the above
> documents, please respond by replying on list to this message no later
> than midnight Boston Time, Wednesday 4 June.
>
> Janina on behalf of the Task Force Facilitators
>
> [1] http://www.w3.org/WAI/PF/HTML/consensus-procedures
>
> --
>
> Janina Sajka, Phone: +1.443.300.2200
> sip:janina@asterisk.rednote.net
> Email: janina@rednote.net
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Protocols & Formats http://www.w3.org/wai/pf
> Indie UI http://www.w3.org/WAI/IndieUI/
>
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina@rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
Received on Monday, 9 February 2015 06:35:45 UTC