[whatwg] <picture> / <img srcset> not needed

Scott González scott.gonzalez at gmail.com
Thu May 17 07:32:45 PDT 2012

On Thu, May 17, 2012 at 10:24 AM, Aldrik Dunbar <aldrik at gmail.com> wrote:

> On 2012/05/17 09:17, Scott González wrote:
> > I don't think this should just be about device capability. Users with
> > vision problems may opt-in to high contract mode and you may need to load
> > different resources based on this.
> I think assertive technology's can handled high contrast and colour
> blindness filters (additional images aren't really needed). Also
> monochrome can already be catered for with SVG/CSS.

Assistive technology can't magically detect that your image has low
contrast and provide a better image. I don't think that AT even comes into
play as high contrast mode is handled by the OS. High contrast mode is not
the same as choosing a monochrome display. On Windows, the default high
contrast display is mostly white on black, but there are still colors, and
text is larger. On OS X, high contrast mode is just extremely contrasty
with lots of detail getting washed out; you can separately choose to use
grayscale and/or invert colors.

Authors may want to provide images with lots of detail, but fall back to
images with less detail and/or larger objects/text in the case of high
contrast mode.

More information about the whatwg mailing list