1. 18
  1. 11

    Making things plain text and giving images good descriptions is accessible.

    Making a website as per current fashion while making it accessible is a nightmare, sure.

    1. 1

      Not a very informative article. It would help a lot more if it gave information on how to make things accessible.

      1. 3

        While I’m also after such things, I don’t think that was the purpose of this particular article. It’s more on how to go about finding out what you need to do kind of thing. Accessibility doesn’t start and end with a checklist after all.

        1. 4

          The article doesn’t even really help you to do that. The most specific accessibility help it offers is to know that individual solutions may only apply to certain technologies or (degrees of) impairment. Besides that, I thought the article was generically saying “You won’t be good at complicated things the first time you try. Do the complicated things anyway, and use these universal techniques to get better at doing them.” Everything about accessibility seemed really surface-level, and even the advice on “getting better at complicated things” was generic. The impression I came away with was that this was a low-effort article.

          I would have liked the article to be more specific. Ideas that come to mind:

          • have examples (at least one) of things that people often get wrong when they try to make technology accessible
          • examples on what accessibility looks like in different contexts (websites, desktop applications, mobile apps)
          • different approaches that accessibility programs (JAWS and NVDA are mentioned) make things accessible, and how (or when/when not) to cater to or accomodate those differences
          • specific books, organizations, presentations, case studies, etc. that are at least representative of useful resources on accessibility