New web services are being built to a self-defeatingly low UX and performance standard, and existing experiences are now pervasively re-developed on unspeakably slow, JS-taxed stacks. At a business level, this is a disaster, raising the question: why are new teams buying into stacks that have failed so often before?
Part I in a series that explores inclusive design at Betterment. This post focuses on making the case to remove the ‘gender question’ as well as some takeaways for building inclusive products.
Die hier kurz vorgestellten Apps liegen dem Autor entweder als Testversion oder mit erworbener Lizenz vor. Das Hauptkriterium zur Auswahl war eine aktive Entwicklung der Programme.
Web Accessibility is a must in every web development project, yet it seems to remain a mystery for many web developers. Like it's something legendary instead of an essential skill needed for the job. There are many misconceptions surrounding Web Accessibility, most of the time fueled by a lack of knowledge (or interest) in the matter. This article is a collection of some of those accessibility misconceptions or myths. :: Blog post at Alvaro Montoro's Personal Website.
I’ve been reading lots more non-fiction books than normal. And I’m getting increasingly annoyed about footnotes1. Footnotes are a weird skeuomorph hangover from the days of printed text…
[…] how we can improve websites legibility using some modern CSS techniques, great new technologies like variable fonts and putting into practise what we learned from doing scientific researches.
Inclusive design describes methodologies to create products that understand and enable people of all backgrounds and abilities. It may address accessibility, age, economic situation, geographic location, language, race, and more.