- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Jul 2015 15:58:45 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28943 --- Comment #2 from John Foliot <john.foliot@deque.com> --- > > > It is annoying that a search for "Warning!" in the document fails (at > > > least on Chrome and Firefox) because it is injected from a content > > > style property. > > > > This seems a bit like a personal preference to me. As such, I don't > > think it should block the LCWD publication although if Glenn created a > > PR that was agreeable to Robin, then I don't see any harm in merging it. > > Actually, it is an A11Y concern. Text that comes in via CSS is often missed > by screen readers. This text should be inline in the document so that it > appears in the DOM. There are many sources for such information about those > limitations, including guidance from the W3C. For a decent non-standards > article about just why it is bad, see > http://www.ssbbartgroup.com/blog/csscontentproperty/ +1 to the accessibility concerns here. Agree that it is not sufficient to stop progress *at this time*, but reserve the right to come back to this as a blocker for Rec Status. Philippe, should this concern be moved to a new bug? Happy to file it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 13 July 2015 15:58:47 UTC