I understand WCAG is technology agnostic, so it doesn't specify which browsers, devices, and operating systems that a website needs to be accessible on.

However, our site isn't responsive on certain platforms, like Opera or IE6/Windows XP. This affects accessibility, because suddenly content will be broken and inaccessible. For example, in IE6, black text over a white background ends up hovering over a black background, making it unreadable.

But it's impossible to account for every device, browser, and OS ever. So I feel like my only option is to be compliant for major browsers/devices, and then meet the Robust principle. So even if text contrast breaks on IE6/Windows XP, I won't get sued for non-compliance.

Our goal here is to not get sued for WCAG non-compliance. We don't know how likely we'll be sued for not supporting Windows XP, but the site owner is very worried about the legalities.

More on Understanding Conformance

  • Do you really need to support IE6 and Windows XP? Those are really really far past their end of life... Jan 27, 2020 at 15:37
  • @PatrickMevzek we just don't want to be sued for not supporting them. Even though our user base most likely won't use those.
    – meicheng
    Jan 27, 2020 at 15:39
  • 1
    "we just don't want to be sued for not supporting them. " Interesting, you may want to expand on that. Because with that reasoning, why do you stop there? Why not support for IE4 or Windows 2000, or even MS-DOS and lynx browser for example. I mean you can not expect your site to be compatible and great for all and every OS/browser that exist since Internet was invented... So why pick IE6 specifically and Windows XP? What about old versions of Safari and MacOS for example? Jan 27, 2020 at 15:44
  • That's my problem, there's all these old systems that we can't possibly all be responsive on. So which systems do we meet compliance on, in order to not get sued? I found this article on WCAG Robustness... so maybe if the responsive design still breaks, it'll still be compliant if it meets these? boia.org/blog/wcag-2.1-principles-explained-robustness
    – meicheng
    Jan 27, 2020 at 15:57
  • IANAL (and neither is this website) and not in your shows/knowing your constraints, but specifically trying to support systems that are past their expiration life based on the producer own data seems quite an impossible endeavor (except if you have infinite time and money). You may wish to enhance your question by telling more who are the visitors on your website and why do you fear to get sued. Browsers change, even if 100% valid today, you can become invalid tomorrow with "some" new version. Did you try various "famous" websites over IE6/XP? I bet they would not fare better than yours. Jan 27, 2020 at 16:03


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.