https://bugzilla.wikimedia.org/show_bug.cgi?id=40632
--- Comment #14 from Danny B. <[email protected]> 2012-10-03 16:57:43 UTC --- (In reply to comment #11) > (In reply to comment #10) > > (In reply to comment #8) > > > Nobody is talking about inline styles. This is technical representation > > > only. > > > This is not related to accessibility. > > > > The feature converts old presentational attributes to inline stylesheets. > > Neither of which are related to content, only style. > > Accessibility related applications that still don't understand CSS, can't be > taken seriously. And even if someone would disagree with that statement, its > pointless. The vast majority of layout is already CSS-only (and has been for > over almost a decade). So for whatever accessibility related software that > doesn't understand CSS, a couple of "align=center" and "valign=top" attributes > here and there are the least of its worries. Nobody was talking about any software not understanding CSS, but about inline styles. So again: *inline styles* are key accessibility problem. Besides, it has been proved, that this feature does in certain cases wrong conversions, so in certain cases the mispositioning of elements causes overlapping or disappearing of content which obviously is an accessibility issue even for people with good eyes. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
