W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2008

[Bug 5807] User Agent display of title attribute content not defined

From: <bugzilla@wiggum.w3.org>
Date: Fri, 27 Jun 2008 09:10:12 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1KC9y8-0006Qj-U7@wiggum.w3.org>

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





--- Comment #4 from steve faulkner <faulkner.steve@gmail.com>  2008-06-27 09:10:12 ---
(In reply to comment #3)
> I don't think it would be wise to have a bazillion links to UAAG all the way
> along HTML5. Better to have UA developers read UAAG separately.
> It's not clear to me what you would want HTML5 to say, anyway. Surely how
> accessibility they are is something browser vendors will naturally compete
> over?

I don't think it would be wise to have a bazillion links to UAAG all the way
> along HTML5.

I haven't proposed that "a bazillion links to UAAG" be added. I have proposed
that one link be added to point vendors to requirements for providing access to
conditional content, that has never been exposed to non mouse users in a usable
way. 



>Surely how
> accessibility they are is something browser vendors will naturally compete
> over?

obviuosly not. 

Suggested text addition:
UA requirements for showing the title attribute content: UAs must expose the
title attribute content(conditional content [1]) via a device independent
mechanism.

[1] http://www.w3.org/TR/UAAG10/guidelines.html#tech-conditional-content


-- 
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 Friday, 27 June 2008 09:21:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 June 2008 09:21:20 GMT