- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Tue, 27 May 2014 08:30:38 -0400
- To: "Hoffman, Allen" <allen.hoffman@hq.dhs.gov>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <422f1b6023372bed67e6c5a5cc9bcdc4@mail.gmail.com>
[Al wrote] Maybe this is the wrong place to enlighten me, but do you mean not exposed to people not using AT, or screen readers To my knowledge aria-label is not used by any AT other than screen readers. aria-label does not seem appropriate for an AT such as screen magnifiers (excluding those with speech). There are some ARIA attributes that could be useful to screen magnifiers such as aria-activedescendant that when used would help screen magnifiers track the programmatic focus. Other AT such as speech recognition software could use aria-label or other aria labeling properties on interactive elements to allow voice access to these elements. The challenge in this case is letting the speech recognition user know what text is to activate the item. For example, if aria-label is used how might a sighted speech recognition user know what that aria-label is to be voiced? You could also argue that it’s the responsibility of the user agent to replace the background image with the aria-label when high contrast mode is on. One challenge with this is that there is often not enough space for the text to be displayed. This issue may occur in non-interactive situations and thus you couldn’t rely on the keyboard or the mouse for that matter to trigger the content in a tooltip. IMO, the name of the CSS property is background-image – i.e. it’s meant to be used as a background – for presentation and not meant to be used to convey meaning Jonathan *From:* Hoffman, Allen [mailto:allen.hoffman@hq.dhs.gov] *Sent:* Tuesday, May 27, 2014 7:57 AM *To:* Jonathan Avila; WCAG *Subject:* RE: aria label on a div alternative text for background images. Maybe this is the wrong place to enlighten me, but do you mean not exposed to people not using AT, or screen readers specifically? Just looking to be clear in my head if this is AT-type specific or not. For example can screen magnifier access the ARIA info? I have to say that use of IT without use of programmatically exposed information seems like a completely different use case than otherwise. *From:* Jonathan Avila [mailto:jon.avila@ssbbartgroup.com<jon.avila@ssbbartgroup.com>] *Sent:* Monday, May 26, 2014 3:32 PM *To:* WCAG *Subject:* RE: aria label on a div alternative text for background images. [David wrote] I was going to provide advice to use aria label on the div like this with the view to make a technique for us. <div role=image class="backgroundimage" aria-label="this is the aria label">Some test text</a></div> I agree with Ramon, background images should only be used for presentation and there must be an equivalent for users with low vision on the screen. Aria-label is not exposed to users who are not using screen readers. I believe use of a background image to convey meaning would be a failure of SC 1.1.1 unless a visual textual equivalent is provided. Jonathan *From:* David MacDonald [mailto:david100@sympatico.ca] *Sent:* Monday, May 26, 2014 11:46 AM *To:* WCAG *Subject:* aria label on a div alternative text for background images. I've been coming across lots of CSS images in background lately. 1. I was going to provide advise to use aria label on the div like this with the view to make a technique for us. <div role=image class="backgroundimage" aria-label="this is the aria label">Some test text</a></div> 2. But neither NVDA or JAWS most recent versions in most recent versions of FF and IE read the aria label. SAFARI and VoiceOver worked however... 3. I looked it up in the ARIA test harness and the aria label should report to the API... have other people had this experience. Test page: http://davidmacd.com/test/aria-label-on-div-surrounding-image-with-alt-text.html Cheers, David MacDonald *CanAdapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> www.Can-Adapt.com * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html> On Mon, May 26, 2014 at 5:21 AM, Wilco Fiers <w.fiers@accessibility.nl> wrote: Regrets for tomorrow's call. ________________________________________ Van: Joshue O Connor [joshue.oconnor@cfit.ie] Verzonden: vrijdag 23 mei 2014 13:52 Aan: WCAG Onderwerp: Agenda for 27 May 2014 WCAG call The WCAG WG will be meeting on Tuesday, 27 May 2014 at 11AM Eastern US (Length: up to 90 minutes) Bridge: +1.617.761.6200 (US) Passcode: 9224# IRC: irc.w3.org<http://irc.w3.org> port: 6665 channel #wai-wcag Scribe list: https://www.w3.org/WAI/GL/wiki/Scribe_List Survey/Agenda 1) Brief item on meeting with EOWG regarding LC-2895. 2) Brief update on progress regarding the review of EO accessibility tutorials. 3) Action item purge. Can everyone please have a look at any action items with their names on them and close any that you have either dealt with or have been over taken by events. Any action items that you are not sure about please let us know. http://www.w3.org/WAI/GL/track/actions/ Note: You can use ‘My Tracker’ to see any outstanding action items that are yours. 4) Continuation from this last weeks survey: Starting at item 2 https://www.w3.org/2002/09/wbs/35422/20140520/ 5) Survey: Proposed responses to public comments: https://www.w3.org/2002/09/wbs/35422/2705_2014/ 6) Every week we will spend some time doing a review of open issues/actions http://www.w3.org/WAI/GL/track/issues/ 7) There are still some comments that need responses (feel free to pick one): https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses -- Joshue O Connor/Andrew Kirkpatrick WCAG working group co-chairs
Received on Tuesday, 27 May 2014 12:31:22 UTC