develwoutacause’s Twitter Archive

9 results for a11y

1. develwoutacause’s Twitter Archive—№ 875

   built-in improvements like: - Faster prod builds - Enhanced component a11y - Improved tes…

2. develwoutacause’s Twitter Archive—№ 916

   #UX, rejects functional req). 2. Screenshot the tweet (bad for #a11y). 3. Ask for consent (bad #UX, bad #perf, and misleading because I don't track you). 4. Build my own

3. develwoutacause’s Twitter Archive—№ 1,078

   @Nartc1410 We have a FR to add diagnostics for common a11y mistakes and best practices. Upvote or add suggestions for what you'd like to see! https://github.com/angular/angular/issues/44869. github.com/angular/angular/issues/44869

4. develwoutacause’s Twitter Archive—№ 1,630

   productionization, monitoring, logging, alerting, unit testing, end-to-end testing, #webperf testing, #a11y testing, security, backups, replication, ...

5. develwoutacause’s Twitter Archive—№ 365

   #WebDev #a11y question: When line breaks are disabled and must be manually specified by the text content (such as a code block), what is a good rule of thumb for