Shakedown Social

0 posts0 participants0 posts today

C.<a href="https://mindly.social/tags/Web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Web</a> <a href="https://mindly.social/tags/usability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#usability</a> and <a href="https://mindly.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> ...This is from crimethinc.com, but I'm not trying to pick particularly on them. There are many, many, many sites just as bad or worse.This is a screenshot from an article on their site today, rendered in Firefox (Linux).See the hair-thin font? See the fact that it's light grey on a white background? There's virtually no contrast between the text and the background.This is an accessibility nightmare for those with any sort of vision problem. Picking the colour out of the screenshot (I didn't look at the CSS), it appears the text is basically 45% grey. This is ludicrous.If the font face had some heft, it might be still be half-assed readable with contrast this low. But as is... If I were to take my contacts out, I wouldn't even be able to tell that this screenshot *had* any of the normal-sized text in it, much less be able to read any of it.Web designers, I beg you: please consider more than the appearance of what you're creating when you're making design choices. Remember that not everyone is a 20- or 30-something with near-perfect vision. Remember that people have cataracts or other types of eye cloudiness which necessitate high-contrast text to be able to read, even if they scale the fonts up by a huge amount.Remember that vision degrades naturally in people in many ways other than "just wear glasses" can fix.<a href="https://mindly.social/tags/WebDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDesign</a> <a href="https://mindly.social/tags/WebDesigner" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDesigner</a> <a href="https://mindly.social/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#web</a> <a href="https://mindly.social/tags/design" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#design</a> <a href="https://mindly.social/tags/font" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#font</a> <a href="https://mindly.social/tags/contrast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#contrast</a> <a href="https://mindly.social/tags/vision" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vision</a> <a href="https://mindly.social/tags/eye" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eye</a> <a href="https://mindly.social/tags/readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#readability</a> <a href="https://mindly.social/tags/legibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#legibility</a> <a href="https://mindly.social/tags/unreadable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unreadable</a>

Kevin Karhan :verified:<a href="https://m.ai6yr.org/@ai6yr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ai6yr</a> nodds in agreement whereas the "akshual coding" is "relatively simple" if one doesn't mind <a href="https://infosec.space/tags/readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#readability</a>, <a href="https://infosec.space/tags/maintainability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#maintainability</a> or using understandable variablr names...<ul><li><a href="https://infosec.space/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> and having <a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReproduceableBuilds</a> as well as <a href="https://infosec.space/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Documentation</a> (even just <a href="https://infosec.space/tags/comments" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#comments</a> in <a href="https://infosec.space/tags/code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#code</a>!) Is way more important, cuz that'll make it maintainable!</li></ul>Testing can be automated if one builds and documebts the tests that is...<ul><li>So yeah, one does not remove or automate away these things easily, cuz even the best <a href="https://infosec.space/tags/autogenerated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autogenerated</a> documentation needs <a href="https://infosec.space/tags/proofreading" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proofreading</a> and <a href="https://www.youtube.com/watch?v=j-6N3bLgYyQ" rel="nofollow noopener noreferrer" target="_blank">testing for correctness and completeness</a>!!!</li></ul>"<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a>" can't do this because those <a href="https://infosec.space/tags/LLM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLM</a>|s don't learn organically but merely act as "<a href="https://infosec.space/tags/StochasticParrot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StochasticParrot</a>" and not as intelligent beings that is able or even willing to transfer * exchange information freely...

everton137Another thing I'm wondering about is the manual creation of hashtags. If we had an automatic classification of posts based on its text, wouldn't it make the life of the person creating a post and the readability easier?<a href="https://social.vivaldi.net/tags/hashtags" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hashtags</a> <a href="https://social.vivaldi.net/tags/SocialMedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialMedia</a> <a href="https://social.vivaldi.net/tags/Automation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Automation</a> <a href="https://social.vivaldi.net/tags/readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#readability</a> <a href="https://social.vivaldi.net/tags/creativity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#creativity</a> P. S. I think it took me almost the same time to share the main thought of this post as the time I needed to think about what hashtags to use.

SpaceLifeForm<a href="https://infosec.exchange/@SecureOwl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@SecureOwl</a> The easy fix was to turn the monitor upside down.<a href="https://infosec.exchange/tags/Orientation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Orientation</a> <a href="https://infosec.exchange/tags/Readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Readability</a>

Likely Jan LukasThe story doesn't end here, of course.Because unlike <a href="https://mstdn.ca/tags/typesetters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#typesetters</a> and other <a href="https://mstdn.ca/tags/designers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#designers</a> who have a plethora of typefaces and sizes to choose from--including the choice to make them thin and such low-contrast as to be unreadable--Braille comes in just two sizes, and the bigger is only really used for labels on signage.Here's an overview of the <a href="https://mstdn.ca/tags/specifications" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#specifications</a>:<a href="https://www.brailleauthority.org/size-and-spacing-braille-characters" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.brailleauthority.org/size-and-spacing-braille-characters</a><a href="https://mstdn.ca/tags/Braille" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Braille</a> <a href="https://mstdn.ca/tags/brailling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#brailling</a> <a href="https://mstdn.ca/tags/tactility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tactility</a> <a href="https://mstdn.ca/tags/readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#readability</a>13/x

Julia :v_bi:I am <a href="https://eepy.moe/tags/begging" rel="nofollow noopener noreferrer" target="_blank">#begging</a> people to <a href="https://eepy.moe/tags/stop" rel="nofollow noopener noreferrer" target="_blank">#stop</a> <a href="https://eepy.moe/tags/writing" rel="nofollow noopener noreferrer" target="_blank">#writing</a> their posts like <a href="https://eepy.moe/tags/this" rel="nofollow noopener noreferrer" target="_blank">#this</a>. It doesn't help <a href="https://eepy.moe/tags/discoverability" rel="nofollow noopener noreferrer" target="_blank">#discoverability</a>, it just harms <a href="https://eepy.moe/tags/readability" rel="nofollow noopener noreferrer" target="_blank">#readability</a>.

Mark Wyner Won’t Comply :vm:Hi, friends. I wrote a small post about hashtag accessibility that went a little viral on me (at least by my humble standards). Now it’s also catching fire on LinkedIn.Lots of you had many great questions, feedback, and insights. So I captured everything and wrote a piece to go deeper into the topic. If you want to learn more, I invite you to give it a read:<a href="https://markwyner.medium.com/hashtag-accessibility-by-everyone-for-everyone-298667b2d891" rel="nofollow noopener noreferrer" target="_blank">https://markwyner.medium.com/hashtag-accessibility-by-everyone-for-everyone-298667b2d891</a><a href="https://mas.to/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Accessibility</a> <a href="https://mas.to/tags/WebAccessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebAccessibility</a> <a href="https://mas.to/tags/Usability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Usability</a> <a href="https://mas.to/tags/Readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Readability</a> <a href="https://mas.to/tags/Hashtags" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hashtags</a> <a href="https://mas.to/tags/SocialNetworking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialNetworking</a> <a href="https://mas.to/tags/Blogging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Blogging</a> <a href="https://mas.to/tags/UX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UX</a>

Mark Wyner Won’t Comply :vm:Update: moved this to my new writing site so there’s a new URL.Every hashtag on every post on every platform should ALWAYS be pascal case. I wrote this to illustrate how screenreaders read hashtags based on their case.It’s a small thing that all of us can do to build a more inclusive, accessible internet for all. Please take the time to use pascal case.Read more: <a href="https://markwrites.io/hashtag-accessibility-by-everyone-for-everyone" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://markwrites.io/hashtag-accessibility-by-everyone-for-everyone</a><a href="https://mas.to/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Accessibility</a> <a href="https://mas.to/tags/WebAccessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebAccessibility</a> <a href="https://mas.to/tags/Usability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Usability</a> <a href="https://mas.to/tags/Readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Readability</a> <a href="https://mas.to/tags/Hashtags" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hashtags</a> <a href="https://mas.to/tags/SocialNetworking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialNetworking</a> <a href="https://mas.to/tags/Blogging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Blogging</a> <a href="https://mas.to/tags/UX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UX</a>

Carl T. Bergstrom<a href="https://mastodon.gamedev.place/@Doobius" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Doobius</a> In my view that’s a weakness of client design and availability. Hashtags are intended for discovery, not for filtering, as far as I’m concerned. Imposing norms that confuse this will be <a href="https://fediscience.org/tags/extremely" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#extremely</a> <a href="https://fediscience.org/tags/detrimental" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#detrimental</a> to <a href="https://fediscience.org/tags/readability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#readability</a>.

Recent searches

Search options

Administered by:

Server stats:

#readability