- CSS standard is weak
- Pre-processors can be buggy and even LESS/Sass have quirks/edge cases
- JS is standardized, and we understand it
- Can extend it, generate it, etc...
- Can modularize easily, using NPM to reuse style modules, or utility helpers
- Represent as json, use a "toCSS" method to convert it
- Because you can't hand it off to a designer
- Too much freedom, makes it harder to search
- We should be harnessing the multicore power of modern machines
- Considerations include how we should handle shared memory and syntax
- Wait a year and reevaluate
- Exploratory code in FF nightly
- Google says they intend to eventually add it to chrome
- Use Aria to notify screenreader new content is available (on playlist item)
- for Android make each page it's own View and Activity (avoid memory leaks between page views)
- hack your own user-agent in mobile apps
- nice hybrid mobile app insight
Slides here
- Use Safari with TTS turned on to tab through UI
- Use Chrome (Canary) "Accessibility Developer Tools" to audit (extension adds audit check box)
- chrome://accessibility