I attended a conference called Strange Loop in St. Louis last week. I don't have notes or thought on every talk I attended, but here were a few I enjoyed most.
I learned that in high contrast modes, often overlays will appear to be floating on top of the page with no outline, since high contrast modes make the backgrounds all one color. You can add
border: 1px solid transparent to the overlay container to make sure there will be a visual distinction between the overlay and the background.
Ian talked a bit about curb cuts and how they were originally conceived for people with disabilities who use assistive technology (wheelchairs), but ended up helping lots of other people (people with grocery carts and strollers, the elderly, etc). He likened how awful it would be to remove curb cuts for aesthetic reasons to how awful it is when website designers remove link underlines or focus outlines for aesthetic purposes. Those features are affordances so people with varying ability levels and ways of using the computer are able to understand what they're doing on the web.
"I don't like the way curb cuts look so let's remove them to make the intersection more aesthetically pleasing" - how you sound when you want to remove link underlines without thinking it through, or disable focus outlines. #a11y by @ianforr at #strangeloop— Cassey Lottman (@CasseyLottman) September 14, 2019
Remember: all images need alt attributes but not all need alt text inside those attributes.
On a list of books, are the cover images adding something to the page that isn't already there, or are they just decorative? If they're decorative, don't make your alt text
cover of bookname. Just make it a decorative image by adding
That book cover image? If it's decorative but also a link, and the link is a duplicate of a link whose text is the book title, make the image link aria-hidden so screenreader and keyboard users don't get fatigued by the repetition.
Artificial Unintelligence: How Computers Misunderstand the World
There are a lot of talks on machine learning and AI that I've been avoiding at #StrangeLoop because I don't believe the hype that AI will save us. This one by @merbroussard on "how computers misunderstand the world" is more up my alley. pic.twitter.com/J9EEtPklyI— Cassey Lottman (@CasseyLottman) September 14, 2019
Meredith gave an overview of what people usually mean when they say artificial intelligence (that is, machine learning) and why its powers are more limited than most people believe.
She also talked about bias in algorithms due to bad training data and the lack of diversity in the field. In 2017 there were 0 women in the Harvard faculty as senior mathematicians. But this bias goes back centuries, and the idea is that math is special and doesn't need to be concerned with the petty social concerns of other disciplines.
Computer science is a descendant of mathematics. It has inherited the biases of its predecessors, so we have bias embedded in the technology we build.
Strange Loop was located in downtown St. Louis, and though it was a dense, under many definitions "walkable" area, as a pedestrian going between conference venues, restaurants, and my hotel I did not feel very safe. One car, travelling fast through a left turn, came within a couple feet of hitting me as I used a crosswalk. Many crosswalks either had no pedestrian signaling or a pedestrian signal that didn't work. There were intersections with pedestrian signals permanently set on "Don't Walk" that never seemed to change, and had no button I could find to indicate that someone was waiting to cross.
How To Teach Programming
Felienne gave a wonderful keynote on "how to teach programming". Many programmers are self-taught and just "figured stuff out", so we assume that everyone can just "figure it out" and that this is a good way to learn. But programming isn't special - research in the best way to help people learn applies to programming, too! Felienne laid out some of that research including original research on programming education.
Lara Schenck gave a great talk on CSS Algorithms which covered a lot of ground, including "what is a programming language" and how CSS meets most definitions of one. She has a blog post on CSS Algorithms that covers a bit of what the talk got into, but the full video is worth a watch, when it comes out.
Community Driven Development
Christine Zagrobelny gave a talk on Community Driven Development, or what she has learned as the primary tech contributor to an organization helping immigrants file asylum cases and work within the American immigration system. It had good insights for open source maintainers and developers and product managers wanting to work with cause-based organizations. It led me to reflect on how I'm using my time, which is something I've been thinking a lot about over the last few weeks. What impact am I making outside of work, and how can I make that impact sustainable?
Tweet My Wedding Dress
Jo Franchetti gave a talk on how she built a wedding dress that has embedded lights that change colors based on tweets to a specific account that contain a color word. It was an interesting lesson in building wearable devices, hardware hacking, and creativity.
Voice Driven Development
Emily Shea gave a talk on "Voice Driven Development", about how she uses voice dictation to control her computer and code, after developing severe RSI. It was eye-opening to learn how doable voice-controlled coding is (though it took her a month to learn and develop speed).
Imogen Heap was the ending keynote speaker. She talked about problems in the music industry (especially around how creators get paid) and how tech can help. She also demoed and performed with her fancy gloves that she uses to make music. She also talked a bit about being a new mom (several years ago) and how that affected her career. She once wrote a song that used the beat of her breast pump as the tempo.
The whole thing was quite inspiring!