- From: <bugzilla@jessica.w3.org>
- Date: Wed, 25 Jul 2012 12:44:35 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18384 Peter Winnberg <peter.winnberg@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.winnberg@gmail.com --- Comment #5 from Peter Winnberg <peter.winnberg@gmail.com> 2012-07-25 12:44:35 UTC --- Some comments about this. First of all I think it's great if we can get so called "responsive images" into a spec so that there is a recommended way to do it. But I see some issues about this and alternate text. In the proposal [1] it is said that all source elements in a picture element should represent the same subject matter. I don't think that will be the case. Take this example, someone makes a so called "mobile" design for their site. Both the regular site and the mobile design have a top banner image (but the mobile design's banner image takes up less space than the regular one). But they don't share the same subject matter. When the site is viewed with a width that is less than say 15em then the site switches to the mobile design. The problem now is that if we only have alt text for 1 image and the mobile design doesn't have the same content then the alt text would be incorrect. One way to solve this would of course be to have a alt attribute for each source attribute. On the other hand the specification could clearly state that all different source elements needs to share the same subject matter. But if people start (ab)using it the way I described above then there is no way for a validator to check this. I generally feel that if style="display:none" is needed then the design usually needs to be rethinked because it assumes that CSS is available everywhere, which it isn't. So it really only solves it for a subset of the user agents. [1] http://www.w3.org/community/respimg/wiki/Picture_Element_Proposal -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 25 July 2012 12:44:36 UTC