W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections

From: <bugzilla@wiggum.w3.org>
Date: Sat, 13 Mar 2010 21:55:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NqZJP-0000Sd-NZ@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9233





--- Comment #7 from Laura Carlson <laura.lee.carlson@gmail.com>  2010-03-13 21:55:58 ---
(In reply to comment #6)

> Mixing directives to UAs and authors in the same section is a bad idea. 
> 
> I agree with striking the text as regards Issue 66. However, that is a separate
> bug/issue, though it tangentially related. 
> 
> During the Issue 66 discussion, several people made requests to add a link to
> UAAG within the sections related to UA implementation. This bug is documenting
> these requests. 
> 
> The UAAG 2.0 specification, section 3.4 does discuss "repairing" text
> alternatives, but that section does not entail image analysis heuristics, which
> is what is described in the section related to Issue 66. The UAAG 2.0
> guidelines are far more practical. 
> 
> However, the information in UAAG 2.0 is purely UA specific in nature, and
> should be separate from the authoring guidelines and the general discussion of
> the HTML and the alt attribute.
> 
> A better place for the link would be in the UA section, or what would be part
> of the UA webcore split, if this split occurs.

Yes, placing a link in a UA section makes good sense. Thanks for the
clarification Shelley. 


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 13 March 2010 21:56:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 13 March 2010 21:56:04 GMT