Re: Non-text content loophole

Hi Patrick

Yes, but I meant it's not as general as 'users changing things' as you said it's hard to pinpoint dos and don'ts. I'm talking about a very specific type of technique clients can use which doesn't seem to be covered by WCAG. But yes, I am talking about it from the perspective of users who require the ability to adapt the visual presentation of the page.

The example is intended to illustrate content that is constructed from CSS background-color and <div> elements which is what my original question is about. The only difference is that my example is text and I'm talking about check marks. This is in essence creating an image using css and div.

I'm talking about AT used to adjust the visual presentation of the page. So, it seems to me you have two aspects to this: the semantic element which is visually hidden but detectable to screen reader users, the image used to covey the same information to non-screen reader users through a visual mechanism.

The visual mechanism doesn't need an alternative for screen reader users. In fact,  adding one would probably be confusing. But for low vision users you're now in a position where the actual input is hidden and the visual mechanism also doesn't have a means of being identified as an image or any form of actual content that can be recognised as anything other than decorative so that it can be modified.

Thanks

Sarah

Sent from Outlook for iOS<https://aka.ms/o0ukef>