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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9233





--- Comment #6 from Shelley Powers <shelleyp@burningbird.net>  2010-03-13 21:35:57 ---
(In reply to comment #5)
> > I don't understand how exactly you want the specification to change.
> 
> The intent of this bug as described above seems to be:
> 
> To strike from the spec the sentence:
> 
> "User agents may also apply image analysis heuristics to help the user make
> sense of the image when the user is unable to make direct use of the image,
> e.g. due to a visual disability or because they are using a text terminal with
> no graphics capabilities." 
> 
> And replace it with a statement something like:
> 
> "For User Agent advice on techniques for repairing missing content please refer
> to the UAAG." 
> 

No.

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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Saturday, 13 March 2010 21:36:00 UTC