Hi all >So do aria-describedby implementations suffer from the same problem of starting to read at the referred element rather than just reading the referred element? aria describedby does not provide the user with access to the referred element, it just takes the text content of the referred element and uses it as the accessible description for the element with aria-describedby attribute. in the case of controls this content is usually announced by default after the label text (accessible name) for the control -- Regards SteveF HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> On 29 August 2013 13:32, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > > > On Thu, Aug 29, 2013 at 5:58 AM, Charles McCathie Nevile < > chaals@yandex-team.ru> wrote: > >> On Wed, 28 Aug 2013 01:15:37 +0200, Silvia Pfeiffer < >> silviapfeiffer1@gmail.com> wrote: >> >> Isn't that functionality provided by aria-describedby ? >>> >> >> only in the case where the target of describedby is local to the >> document. Unlike longdesc, aria-describedby cannot support external >> descriptions. >> >> (The long-term picture is that aria-describedat might be implemented and >> change this, but currently it hasn't happened). >> >> > So do aria-describedby implementations suffer from the same problem of > starting to read at the referred element rather than just reading the > referred element? > > I'd suggest to use the same wording across both specs. > > Silvia. >
Received on Thursday, 29 August 2013 12:39:40 UTC