- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Thu, 23 Feb 2012 23:35:59 +0100
- To: Janina Sajka <janina@rednote.net>
- Cc: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Sam Ruby <rubys@intertwingly.net>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, Michael Smith <mike@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, public-html@w3.org, Judy Brewer <jbrewer@w3.org>, Steven Faulkner <faulkner.steve@gmail.com>
Janina Sajka, Thu, 23 Feb 2012 17:05:05 -0500: > Leif Halvard Silli writes: >>>>>> Btw, I agree that two HTML5 specs should not contradict each others. >>>>>> But I do think HTML5 'proper' should contain basic advice and rules. >>>>> >>>>> Are you asserting that alternative text applies only to HTML? >>>> >>>> Why do you ask, when the CP *does* suggest to have have a HTML5 >>>> specific guide - in the form of Steve's alt techniques spec? Changing >>> >> Sorry. I admit that it was hard to grok. >> > OK. Then let me point you to items #3 and #4 in the third paragraph of > the Summary section. What is your response? Do you agree, or no? > > Is alternative text just about HTML or no? Of course not. E.g. the ARIA 1.0 spec is for any mark-up based host language. But it is not new info that alternative text is not an issue specific to HTML5. In a way, what you say, is that Ian and Steve's two spec's are so good with regard to @alt, that what their content should be lifted out of HTML5 and be made applicable for — I guess — images in general. So on one side the CP focuses on problems within the HTML working group, on the other side it says that is has produced good and useful texts on @alt. At any rate: The document 'HTML5 techniques for providing useful text alternatives' remains a HTML5 specific document. Why else should the HTML working group be co-responsible for it? -- Leif Halvard Silli
Received on Thursday, 23 February 2012 22:36:35 UTC