6 ms·
WYSIWYG mode, unfortunately, ignores the needs of screen readers and other methods of accessing content. The risk of WYSIWYG tools is they lie to you; not all y
by shadowgovt 7y ago
WYSIWYG mode, unfortunately, ignores the needs of screen readers and other methods of accessing content. The risk of WYSIWYG tools is they lie to you; not all your users can actually see what you see. And that's to say nothing of the less exotic scenarios like different screen sizes or devices.
... unless you're working in a space allowed to discriminate against users that need assistive access to your content of course, in which case you can spring for the WYSIWYG dream.
- tzjmetron 7y ago. allowed to discriminate against users What a cunt you are!
- Wowfunhappy 7y agoIf screen reader accessibility was the only thing holding us back from a WYSIWYG dream, I would advocate just maintaining separate content-only versions of all pages. I don't think that's actually where we are though. As you touch on, code is inherently necessary in order to build responsive pages. A static layout will never know how to reflow itself when the window size changes; it needs code to define that behavior.
- chrisweekly 7y ago>"A static layout will never know how to reflow itself when the window size changes; it needs code to define that behavior." I know what you mean wrt fixed-width layouts, but want to point out that reflow is the default browser behavior in the absence of problematic markup and styling rules. That's the beauty of mobile-first RWD and progressive enhancement when done right; the starting point is just the content, full stop. The first media query is the absence of support for media queries. Then min-width rules to guide layout changes across progressively larger breakpoints.
- inetknght 7y agoChanging the layout of a page just because the window was resized is moronic.
- chipotle_coyote 7y agoBecause if a page designed for ~1200 pixels across looks like crap on a mobile phone in portrait mode, it's the user's fault for using a damn phone?
- deleted 7y ago[deleted]
- tabtab 7y agoI don't think it's realistic to declaratively define a UI that works well under both a 15 inch screen and a 2 inch screen. One is probably going to have to programmatically take different courses of action under each of those scenarios. For example, for mobile you'll probably want to split actions into multiple screens that are best done in a single screen with a big monitor.
- lugg 7y ago> A static layout will never know how to reflow itself when the window size changes; it needs code to define that behavior. This is no longer true. CSS grid solves this completely. https://youtu.be/7kVeCqQCxlk https://youtu.be/7kVeCqQCxlk
- hutzlibu 7y agoVisually designing is by definition allways for people who can see. And for those who cannot, there can and should be a simple htmltext fallback. But that should not cripple the manority who enjoy nice looking things, which are way easier to achieve with WYSIWYG tools which is why flash was loved among designers.
- shaki-dora 7y ago> [..] cripple the manority who enjoy nice looking things That's... quite the Freudian slip. At least you have an idea where your jingoistic ignorance of other's needs comes from.
- hutzlibu 7y agoYou know that the "j" and "n" are next to each other on the keyboard? And apart from that, are you sure that I am the ignorant one, when I wrote "there can and should be a simple htmltext fallback."? Anyway, since your needs seem to be, being self righteous, I won't interfere with that anymore.
- cosmotic 7y agoWYSIWYG does not preclude accessibility. Macromedia and/or Adobe could have added accessibility features to the Flash player.
- greglindahl 7y ago... and they chose not to. Which is one of many, many reasons why their products have fatal flaws in the eyes of many.
- repolfx 7y agoThat's not true. Flash had accessibility features added to it some time ago: https://www.adobe.com/accessibility/products/flash.html https://www.adobe.com/accessibility/products/flash.html
- AndrewUnmuted 7y agoOne should not go using terms like "discriminate" against people who are clearly not doing so. Assistive access to content is an afterthought for almost everyone in software, and that's perfectly fine. It's an extremely uncommon and unnecessary use case for nearly the entire device-using population.
- jdietrich 7y ago>Assistive access to content is an afterthought for almost everyone in software, and that's perfectly fine. It's not perfectly fine - it's illegal. https://en.wikipedia.org/wiki/Americans_with_Disabilities_Act_of_1990 https://en.wikipedia.org/wiki/Americans_with_Disabilities_Ac...
- AndrewUnmuted 7y agoShow me where the ADA says that software developers must think about assistive access to content, and that not doing so is illegal. What you have cited here is an issue of compliance for certain public services and commercial products, and you are attempting to justify thought police and the private regulation of development of software standards/protocols with it. EDIT: Also, would you care to explain how the ADA has any impact on anyone's behavior outside of the United States?
- dmoy 7y agoIt's in title III of the ADA, if you want to read it. However because of the way US law works, you probably need context on court cases, such as the recent supreme court ruling: https://www.scotusblog.com/case-files/cases/dominos-pizza-llc-v-robles/ https://www.scotusblog.com/case-files/cases/dominos-pizza-ll... Going back to GG(G?)P, if you're writing software outside of the commercial or government space in the US, then maybe you're fine not complying with accessibility guidelines in the ADA, e.g. screen readers or what have you. If you're outside of the US, then I don't know what protections there are. But in the US, for commercial or government purposes, then yes, it's illegal in the above sense. Edit: borski above describes context pretty well too, since it depends on the commercial context in which you're operating Edit 2: also this latest ruling is new enough that we'll have to wait to see how the dust settles w.r.t. new lawsuits
- oh_sigh 7y agoNothing says accessibility needs to be immediately incorporated into the same content as the non-accessible content. Restaurants can offer Braille menus. They aren't forced to put translations in Braille immediately next to every piece of text on the menu they give to everyone.
- shadowgovt 7y agoSure, but if they offer Braille menus, but then they just render photographs of menus on their website (instead of the text itself), they're likely opening themselves up to a lawsuit. ... granted, they're also screwing themselves over because anyone trying to integrate something like UberEats against them to provide delivery is gonna skip them over for the competitor with the more-easy-to-scrape online presence. ;)
- tabtab 7y agoI disagree WYSIWYG or coordinate-based positioning inherently "can't do accessibility". It perhaps may take more discipline to make sure the necessary meta data is supplied to the client, but it doesn't outright prevent it. PDF's, for example, can be made accessible if created properly.