3 ms·
To me, accessibility is all about providing proper access to information. It doesn't matter to me if it is because a screenreader, a Lynx browser, a preference
by blauwbilgorgel 15y ago
To me, accessibility is all about providing proper access to information.
It doesn't matter to me if it is because a screenreader, a Lynx browser, a preference, or a no-script plug-in. All that matters to me is my users can access my content on a broad range of devices.
CSS on/Images off is an unlikely scenario, but it is a possible scenario (also consider the possibility of images not loading for whatever reason). If I were a user stuck in that scenario, I'd say: "I can't access core parts of this website". For a website developer, you could call that an accessibility problem, no?
Relevant thread on WebAIM: http://webaim.org/discussion/mail_thread?thread=3785 http://webaim.org/discussion/mail_thread?thread=3785
A little more cheeky: http://www.arespritesaccessible.net/explain.php http://www.arespritesaccessible.net/explain.php
Wikipedia: Web accessibility refers to the inclusive practice of making websites usable by people of all abilities and disabilities.
- Isofarro 15y ago"CSS on/Images off is an unlikely scenario, but it is a possible scenario (also consider the possibility of images not loading for any reason). If I were in a user stuck in that scenario, I'd say: I can't access core parts of this website. For a website developer, you could call that an accessibility problem, no?" No. I'd call it a connection/network issue. The universality consideration (which is what you are really advocating here) then points to progressive enhancement -- defensive design -- as a technique to mitigate the failure to load a page's supplementary assets.