- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Wed, 6 Aug 2014 23:29:11 +0000
- To: James Craig <jcraig@apple.com>, Birkir Gunnarsson <birkir.gunnarsson@deque.com>
- CC: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Plus, in the case of background images for icons, such as opening in a new window and so on, the bug filed regarding aria-haspopup at https://www.w3.org/Bugs/Public/show_bug.cgi?id=25851 In combination with an explicit label, should correct many of these issues when a suitable attribute is added. It seems odd to me, to try and get this information through CSS as well, which wouldn't be detectable until after the content was fully rendered. -----Original Message----- From: James Craig [mailto:jcraig@apple.com] Sent: Wednesday, August 06, 2014 1:46 PM To: Birkir Gunnarsson Cc: W3C WAI Protocols & Formats Subject: Re: Pending review on two CSS issues The addition of the "alt" property in CSS is limited to generated content that has no element reference (hence the name pseudo-element) on which to add accessibility through standard means. For general elements, the problem is already solvable with content attributes like @aria-label. > On Aug 6, 2014, at 10:52 AM, Birkir Gunnarsson <birkir.gunnarsson@deque.com> wrote: > > We need a suitable alt property for .background images more than anything. > There is a trend of .background images being used for icons (such as > "opens in a new window" "document" "secure content" etc.). > We have had to device workarounds through hidden link text or title > attributes, which is less than desireable. > I admit to not having read the references you gave, I am very busy > with meeting today, but wanted to express a serious concern if alt > text solutions are restricted to .before and .after and do not include > .background Thanks > > > -----Original Message----- > From: James Craig [mailto:jcraig@apple.com] > Sent: Wednesday, August 6, 2014 1:26 PM > To: W3C WAI Protocols & Formats > Subject: Pending review on two CSS issues > > I believe these two PF/CSS issues can be closed. If you disagree, > please respond before the next PF call on the morning of Wednesday August 13th. > Thanks. > > >> ACTION-931: Drive working with CSS on how various mouse cursor >> options > should be chosen > >> https://www.w3.org/WAI/PF/Group/track/actions/931 > > > I think this works well as-is. The CSS cursor property defines types > and the large mouse cursors work well on OS X for standard and HiDPI > displays. If there is a problem with a particular property or system, > we'll need a more specific action. > > >> ACTION-932: Explore CSS generated content more >> https://www.w3.org/WAI/PF/Group/track/actions/932 > > This will be addressed in the CSS4 Generated Content module as a new > "alt"property. Like the "content" property, it is limited to > CSS-generated content, so only allowed on ::before/::after pseudo-elements, counters, etc. > http://lists.w3.org/Archives/Public/www-style/2012Nov/0319.html > > WebKit nightlies and OSX/iOS betas support -webkit-alt in the meantime. > https://bugs.webkit.org/show_bug.cgi?id=120188 > > For example: > > link.new::after { > content: url(./img/star.png); > alt: "New!" /* or localized value as attr(data-foo); */ > -webkit-alt: "New!"; > } > > >
Received on Wednesday, 6 August 2014 23:29:45 UTC