home.social

#readability — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #readability, aggregated by home.social.

  1. Consider this:

    If your website doesn't render sensibly in a #textmode #browser (emacs-eww, lynx, links2, w3m, chawan, just to name a few), or if javascript is disabled in a graphical browser, then it probably also doesn't work for people who need screen readers. If you're not testing with text-mode browsers and screen readers, guess who's the asshole (hint: it's not the visitor.)

    Web standards matter.
    w3.org/WAI/standards-guideline

    #webdev #readability #PSA

  2. #macOS 27 will feature a slight #redesign to improve #readability and an AI-powered Safari feature to automatically group tabs. These changes, along with others, will be unveiled at WWDC 2026 on June 8th. macrumors.com/2026/05/10/two-m #tech #media #news

  3. #macOS 27 will feature a slight #redesign to improve #readability and an AI-powered Safari feature to automatically group tabs. These changes, along with others, will be unveiled at WWDC 2026 on June 8th. macrumors.com/2026/05/10/two-m #tech #media #news

  4. #macOS 27 will feature a slight #redesign to improve #readability and an AI-powered Safari feature to automatically group tabs. These changes, along with others, will be unveiled at WWDC 2026 on June 8th. macrumors.com/2026/05/10/two-m #tech #media #news

  5. #macOS 27 will feature a slight #redesign to improve #readability and an AI-powered Safari feature to automatically group tabs. These changes, along with others, will be unveiled at WWDC 2026 on June 8th. macrumors.com/2026/05/10/two-m #tech #media #news

  6. #macOS 27 will feature a slight #redesign to improve #readability and an AI-powered Safari feature to automatically group tabs. These changes, along with others, will be unveiled at WWDC 2026 on June 8th. macrumors.com/2026/05/10/two-m #tech #media #news

  7. One #accessibility issue I mention frequently is web designers, presumably for aesthetic reasons, making low-contrast colour choices. It also frequently goes along with selecting a #font so small that only people with excellent vision (and no #presbyopia) can read them, even if the #contrast were higher.

    Here's an example. I'm not pointing out the software in question, even though you could identify it easily, because this isn't a dunk on that project, specifically.

    This is the reference #documentation for an API, a small excerpt from the navigation links that run down a column on the left side of the page. The #text is darkish #grey on a lighter grey background. The contrast is terrible, particularly ignoring the highlighted entry because that's bolded as the current selection.

    If you have #cataracts or any other #vision problem, you're going to have trouble with this. But it gets worse.

    That text is 7 pixels high. On my monitors, it's 3 mm high. Ridiculous. Note that if you have fine motor-control problems or use alternative input devices, these are also extremely difficult to click on.

    Here's the kicker: for this site, I have Firefox set to #scale the text up to 133%. That 7 pixels / 3 mm is *after* enlarging it.

    #Web folks, please try to remember that not everyone is a twenty-something able-bodied person with zero accessibility issues.

    #WebDesign #WebDesigner #usability #readability #legibility #WebPage

  8. One #accessibility issue I mention frequently is web designers, presumably for aesthetic reasons, making low-contrast colour choices. It also frequently goes along with selecting a #font so small that only people with excellent vision (and no #presbyopia) can read them, even if the #contrast were higher.

    Here's an example. I'm not pointing out the software in question, even though you could identify it easily, because this isn't a dunk on that project, specifically.

    This is the reference #documentation for an API, a small excerpt from the navigation links that run down a column on the left side of the page. The #text is darkish #grey on a lighter grey background. The contrast is terrible, particularly ignoring the highlighted entry because that's bolded as the current selection.

    If you have #cataracts or any other #vision problem, you're going to have trouble with this. But it gets worse.

    That text is 7 pixels high. On my monitors, it's 3 mm high. Ridiculous. Note that if you have fine motor-control problems or use alternative input devices, these are also extremely difficult to click on.

    Here's the kicker: for this site, I have Firefox set to #scale the text up to 133%. That 7 pixels / 3 mm is *after* enlarging it.

    #Web folks, please try to remember that not everyone is a twenty-something able-bodied person with zero accessibility issues.

    #WebDesign #WebDesigner #usability #readability #legibility #WebPage

  9. One #accessibility issue I mention frequently is web designers, presumably for aesthetic reasons, making low-contrast colour choices. It also frequently goes along with selecting a #font so small that only people with excellent vision (and no #presbyopia) can read them, even if the #contrast were higher.

    Here's an example. I'm not pointing out the software in question, even though you could identify it easily, because this isn't a dunk on that project, specifically.

    This is the reference #documentation for an API, a small excerpt from the navigation links that run down a column on the left side of the page. The #text is darkish #grey on a lighter grey background. The contrast is terrible, particularly ignoring the highlighted entry because that's bolded as the current selection.

    If you have #cataracts or any other #vision problem, you're going to have trouble with this. But it gets worse.

    That text is 7 pixels high. On my monitors, it's 3 mm high. Ridiculous. Note that if you have fine motor-control problems or use alternative input devices, these are also extremely difficult to click on.

    Here's the kicker: for this site, I have Firefox set to #scale the text up to 133%. That 7 pixels / 3 mm is *after* enlarging it.

    #Web folks, please try to remember that not everyone is a twenty-something able-bodied person with zero accessibility issues.

    #WebDesign #WebDesigner #usability #readability #legibility #WebPage

  10. One #accessibility issue I mention frequently is web designers, presumably for aesthetic reasons, making low-contrast colour choices. It also frequently goes along with selecting a #font so small that only people with excellent vision (and no #presbyopia) can read them, even if the #contrast were higher.

    Here's an example. I'm not pointing out the software in question, even though you could identify it easily, because this isn't a dunk on that project, specifically.

    This is the reference #documentation for an API, a small excerpt from the navigation links that run down a column on the left side of the page. The #text is darkish #grey on a lighter grey background. The contrast is terrible, particularly ignoring the highlighted entry because that's bolded as the current selection.

    If you have #cataracts or any other #vision problem, you're going to have trouble with this. But it gets worse.

    That text is 7 pixels high. On my monitors, it's 3 mm high. Ridiculous. Note that if you have fine motor-control problems or use alternative input devices, these are also extremely difficult to click on.

    Here's the kicker: for this site, I have Firefox set to #scale the text up to 133%. That 7 pixels / 3 mm is *after* enlarging it.

    #Web folks, please try to remember that not everyone is a twenty-something able-bodied person with zero accessibility issues.

    #WebDesign #WebDesigner #usability #readability #legibility #WebPage

  11. One #accessibility issue I mention frequently is web designers, presumably for aesthetic reasons, making low-contrast colour choices. It also frequently goes along with selecting a #font so small that only people with excellent vision (and no #presbyopia) can read them, even if the #contrast were higher.

    Here's an example. I'm not pointing out the software in question, even though you could identify it easily, because this isn't a dunk on that project, specifically.

    This is the reference #documentation for an API, a small excerpt from the navigation links that run down a column on the left side of the page. The #text is darkish #grey on a lighter grey background. The contrast is terrible, particularly ignoring the highlighted entry because that's bolded as the current selection.

    If you have #cataracts or any other #vision problem, you're going to have trouble with this. But it gets worse.

    That text is 7 pixels high. On my monitors, it's 3 mm high. Ridiculous. Note that if you have fine motor-control problems or use alternative input devices, these are also extremely difficult to click on.

    Here's the kicker: for this site, I have Firefox set to #scale the text up to 133%. That 7 pixels / 3 mm is *after* enlarging it.

    #Web folks, please try to remember that not everyone is a twenty-something able-bodied person with zero accessibility issues.

    #WebDesign #WebDesigner #usability #readability #legibility #WebPage

  12. I've been playing with as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value , , etc. I agree that some ways of using for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

  13. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  14. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  15. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot

  16. I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

    dev.to/drhyde/god-is-my-copilo

    #GithubCopilot