W3C home > Mailing lists > Public > public-html@w3.org > February 2011

Re: ISSUE-122 shalott-example: Call for revisions

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 07 Feb 2011 12:33:25 -0800
Cc: HTML WG <public-html@w3.org>
Message-id: <875DA44C-4FF2-40A6-A60A-822B3026352E@apple.com>
To: Steve Faulkner <faulkner.steve@gmail.com>

On Feb 7, 2011, at 12:25 PM, Steve Faulkner wrote:

> Hi Maciej, 
> 
> so do you want me to include required changes to the html5 spec as well?
> 
> otherwise I am unclear on what is required.

I refer you to the previous issues on this from October:

http://lists.w3.org/Archives/Public/public-html/2010Oct/0393.html
http://lists.w3.org/Archives/Public/public-html/2010Oct/0400.html

Note that if you take no action, it seems likely the issue will be closed without prejudice, resulting in no change to the alt-requirements draft. But if you do want to make revisions, see the messages above.

Regards,
Maciej

> 
> regards
> Stevef
> 
> On 7 February 2011 19:12, Maciej Stachowiak <mjs@apple.com> wrote:
> 
> The Chairs have reviewed the proposals for ISSUE-122 shalott-example, and find them both wanting as written. If they are not updated within a week, by February 14, 2011, they will be dropped from consideration. If no proposals remain, the issue will be closed without prejudice.
> 
> * Steve's null Change Proposal does not apply a consistent resolution to all WG drafts, as previously mentioned by the chairs: <http://www.w3.org/html/wg/wiki/ChangeProposals/thematicimages>.
> 
> * Laura's proposal to remove text alternative examples goes considerably beyond the scope of the issue, in the judgment of the chairs <http://www.w3.org/html/wg/wiki/ChangeProposals/TextAlternativesIssue122>. The original scope of the issue was about the details of one particular example. This proposal removes all accessibility advice for textual equivalents, and in the course of doing so entirely deletes a WG draft. It is reasonable to propose this, but not as part of this narrow issue. We offer the following options:
> 
>   ** Revise the Change Proposal to fit the narrower scope of ISSUE-122 (just the one example that was at issue).
> 
>   ** File a bug requesting the changes in the proposal, and if necessary escalate it. It will then be treated as its own issue.
> 
> It's fine to do either or both of these things (or none if there is no desire to pursue the issue further).
> 
> Regards,
> Maciej
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> with regards
> 
> Steve Faulkner
> Technical Director - TPG
> 
> www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner
> HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/
> Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html 
> 
Received on Monday, 7 February 2011 20:33:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:22 UTC