type__error’s Twitter Archive
—№ 9,365
⇤ Newest
Tweet
⇠ Newer
Tweet
Older
Tweet
⇢
…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.
Permalink
On twitter.com
2020 Oct 16
Mood +
2
🙂
…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.
On twitter.com
2020 Oct 16
Mood
0