type__error’s avatartype__error’s Twitter Archive—№ 9,365

    1. …in reply to @phunkren
      phunkren StuRobson What I suggest in the article is that you shouldn’t be going back over the code and making it accessible afterwards - if you build it in an accessible way from the start it shouldn’t take you any longer.
  1. …in reply to @type__error
    phunkren StuRobson So your initial release would be AA(A) compliant as you’ve taken that approach from the word go.