W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2017

RE: Negative numbers

From: Subramanian, Poornima (PCL) <psubramanian@hagroup.com>
Date: Thu, 5 Oct 2017 14:03:22 +0000
To: Bart Simons <bart.simons@anysurfer.be>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <CY4PR0701MB3649F80354D407173A4376FFC0700@CY4PR0701MB3649.namprd07.prod.outlook.com>
>> It can be used, but the question is whether it makes sense to label something that has no role?

I remember referring to the below link where the aria-label and aria-labelledby used along with different elements including span, div. I am not sure whether it end up in accessibility tree or api mapping, the results may vary when interpreting with different technologies or platforms.

https://dequeuniversity.com/testsuite/aria/aria-label-aria-labelledby/


Again for elements like image, button, link, etc. it should include the HTML tags img, button, a. When not possible, roles must be included to describe that element first.
And aria-label is secondary to include label or descriptive text to it.

>> My preference would be to describe the link or button in the actual link or button text and use aria-label only in very rare cases where there is no HTML alternative

Of course yes, only when there is no native HTML alternative to make "link" or "button text" serve the contextual meaning the aria-label can be of help. Earlier I was in misconception that "aria-label" text contain only the additional words required to make it complete. But learnt that few screen reader like JAWS ignore the link or button text, and read only the "aria-label" text. That's the reason, I would like to add this point when aria-label topic is discussed.

It's great to hear everyone's opinion about the appropriate usage.

Best,
Poornima.

-----Original Message-----
From: Bart Simons [mailto:bart.simons@anysurfer.be]
Sent: Thursday, October 05, 2017 4:35 AM
To: w3c-wai-ig@w3.org
Subject: Re: Negative numbers

Op 4/10/2017 15:08, Subramanian, Poornima (PCL) schreef:
> > To my understanding, aria-label can be used along with the tags
> > span,
 > div, a, button, and also with aria-roles.

It can be used, but the question is whether it makes sense to label something that has no role?

 > When using "aria-label", few of the screen readers would ignore  > the actual link or button text. It is best to describe the link or  > button in the "aria-label" text itself.

My preference would be to describe the link or button in the actual link or button text and use aria-label only in very rare cases where there is no HTML alternative

The question is not "does it work in a screenreader" but "does the text of an aria-label on a span-element end up in the accessibility tree"?

Regards
Bart Simons


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________
The information contained in this email and any attachment may be confidential and/or legally privileged and has been sent for the sole use of the intended recipient. If you are not an intended recipient, you are not authorized to review, use, disclose or copy any of its contents. If you have received this email in error please reply to the sender and destroy all copies of the message. Thank you.

To the extent that the matters contained in this email relate to services being provided by Princess Cruises and/or Holland America Line (together "HA Group") to Carnival Australia/P&O Cruises Australia, HA Group is providing these services under the terms of a Services Agreement between HA Group and Carnival Australia.
Received on Thursday, 5 October 2017 14:04:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 December 2017 16:04:47 UTC