Re: For content to be accessible should it inform if what you are interacting with is an ad or not ad

On 16/08/2022 09:48, bryan rasmussen wrote:

> This just came up on an Hacker News discussion - if some platform has ad 
> content and non ad content together (specific discussion referenced 
> FaceBook) and a screen reader user cannot tell the difference between 
> the two is that an accessibility issue?
> 
> By which I mean, yes of course it is an issue but would you be able to 
> file a claim against the people mixing content and ads in this way and 
> force them to clearly delineate the two (because of violating 
> accessibility standards)

My gut feeling on this would be no, noting that mixing ad content into a 
page in a way that doesn't immediately make it clear it's an ad rather 
than part of the content itself can be a problem for all users (not 
specifically AT users, keyboard users, etc).

Of course, this will depend exactly on the situation, with all other 
things being equal (i.e. 1.3.1 Info and Relationships, 2.4.4 Link 
Purpose (In Context), and so on being satisfied). You could, at a 
stretch, look at 1.3.6 Identify Purpose (AAA), but there's no clear 
"right" way to identify a region that is intended to be a ad content. 
Possibly also under 1.3.1 looking at perhaps marking up ad content as an 
<aside>, but it's not really a strong enough case I'd say to fail 
something if it doesn't do this.

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

Received on Tuesday, 16 August 2022 09:13:06 UTC