Timeline for How to avoid solutions in answers with foundational accessibility issues, in line with Stack Exchange’s policies
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 13, 2022 at 2:39 | comment | added | Ryan M | Nonetheless, it's important to include any major "gotchas" caused by using the answer as-is. People coming to Stack Overflow for code can't be expected to understand every possible downside to an answer, even if they're not blatantly copying answers. Someone seeing a highly upvoted answer may reasonably think it's the "correct" way to do things, when actually it's a hack that should never be used in production. | |
| Jul 12, 2022 at 15:28 | comment | added | Makoto | @Andy: Yes, I'm aware of this. Acutely aware of this. This doesn't change my position since it shifts the responsibility of the quality and fitness of the code away from the only party that matters in the equation. | |
| Jul 12, 2022 at 11:13 | comment | added | Andy | Unfortunately this is not how most people use the site. Most people blindly copy the code, never reference neither the source, nor the author in their code, and they do not even consider that there might be conditions that apply. I got insulted for mentioning that all the code on stack overflow was published under a license. | |
| Jul 11, 2022 at 20:37 | comment | added | ColleenV | +1 Example code should illustrate the answer, not be a template if the perfect way to implement something. If I'm trying to understand how to bind a function to a Widget A event, I don't need an explanation of how those widgets have accessibility issues, especially since it's difficult to understand the extent of and best remedy for a potential issue with such limited context. | |
| Jul 11, 2022 at 20:30 | history | edited | SpevacusMod | CC BY-SA 4.0 |
-F-or :)
|
| Jul 11, 2022 at 20:18 | history | answered | Makoto | CC BY-SA 4.0 |