- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 21 Jul 2020 00:40:37 +0100
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
On 21/07/2020 00:07, Catherine Ailanjian wrote: > Yes, it's because the "Linearize page" step causes CSS-background images to disappear ... if they are meaningful, then we need to programmatically communicate that content to users - like adding a text element that conveys the image's information and is visible when CSS is turned off. Again, the fact that these images disappear is a byproduct of the way you're testing for content order. It's not a requirement of WCAG that for 1.3.2 a site must work when CSS is suppressed/the page is forcibly linearised. > So, I'm evaluating https://shop.westerndigital.com ... many of CSS-background images are decorative (AKA "lifestyle"), but we have run into some on our pages that are meaningful and communicate content that cannot be found elsewhere on the page. The problem you describe with CSS background images being meaningful is nothing to do with 1.3.2, but rather a 1.1.1 issue. Ensure that there is a text alternative that conveys the same meaning. This *can* be visually hidden text, for instance. And again, it's irrelevant whether or not this shows up when you use that forcible page linearisation feature of the web developer extension...that's not what WCAG requires (the linearisation is merely a way to help you evaluate if the content order is reliant on visual layout). 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 Monday, 20 July 2020 23:40:52 UTC