WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXT]Removing CSS Background image for legibility an Accessibility requirement?

for

From: Steve Green
Date: Mar 15, 2022 10:55AM

True, but none of those involve the intentional removal of a relied-on, accessibility supported technology. And WCAG does not require us to test what happens if any file types fail to load.

Steve


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Jared Smith
Sent: 15 March 2022 16:52
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXT] Re: Removing CSS Background image for legibility an Accessibility requirement?

> This is essentially testing that once a user has customised their experience, things still work, which is outside of WCAG.

As a counter-point, the Resize Text, Reflow, User of Color, and Text Spacing success criteria in WCAG all require certain levels of support and accessibility after end-user customizations have been applied. All of these - resizing text, zooming, overriding colors or text styles, etc. - can result in text with very low or no contrast if a background color is not defined or inherited. In these cases, text might be repositioned outside the boundaries of a background image or the system may not be able to calculate sufficient color changes when a background is in place, but not a fall-back CSS background color. G183 supports text accessibility in these cases.

Additionally, images might fail to download or the user might be in a very low bandwidth environment, so having a fall-back color ensures legible text in these situations that may be out of the user's control.

Jared Smith
WebAIM