WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Embarrassing question - text isn't read but it's neither a control nor is it non-text content


From: Detlev Fischer
Date: Jan 27, 2023 7:52AM

It is not uncommon that content in a native app is exposed in one OS,
but not the other.
Check for example comments in the YouTube native app: The comment's text
content is exposed (but badly, grouped with surrounding controls) on
iOS, but inaccessible to TalkBack on Android (here you just get the
Given that TalkBack is clearly able to expose similar content in other
apps (e.g. amazon, ebay) I think it fair to assume this is not a SR bug
but down to they way content is implemented (or automatically converted
from some dev framework).

Am 27.01.2023 um 11:46 schrieb Steve Green:
> I am wary of making such definitive claims of non-conformance based only on assistive technology behaviour. It may be a screen reader bug, so I would really want to see the code before declaring it a non-conformance. Has the behaviour been replicated on other devices with the same or different operating system and browser versions?
> Steve Green
> Managing Director
> Test Partners Ltd
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Patrick H. Lauke
> Sent: 27 January 2023 10:29
> Subject: Re: [WebAIM] Embarrassing question - text isn't read but it's neither a control nor is it non-text content
> On 27/01/2023 10:27, Detlev Fischer wrote:
>> I think this is clearly a 1.3.1 Info and Relationships issue: Info is
>> visually available, but not programmatically.
> Seconded. Possibly even touches on 1.3.2 Meaningful Sequence.
> P
> --
> Patrick H. Lauke
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > > > > --
Detlev Fischer
(Testkreis is now part of DIAS GmbH)

Mobil +49 (0)157 57 57 57 45

Beratung, Tests und Schulungen für barrierefreie Websites