all users are disabled
TRANSCRIPT
ALL USERS ARE DISABLED
even you
WHEN YOU SWITCH FROM YOUR DESKTOP TO SMARTPHONE CAN YOU?
➤ RIGHT CLICK?
➤ VIEW THE SOURCE OF A WEBPAGE?
➤ VIEW 5 APPS AT ONCE?
➤ GOBBLE UP ALL THE BITS YOU PLEASE?
WHEN YOU SWITCH BACK TO YOUR DESKTOP DOES IT?
➤ KNOW WHERE IT IS IN THE WORLD?
➤ FIT IN YOUR POCKET?
➤ PINCH ZOOM?
➤ PLACE CALLS?
WHEN THE BATTERIES IN YOUR MOUSE DIE
➤ CAN YOU USE IT?
WHEN JAVASCRIPT CAKES ITS PANTS DOES YOUR SITE WORK?
➤ I HOPE SO…
➤ ¯\_(ツ)_/¯
DOES YOUR USER’S
BROWSER SUPPORT
WEBFONTS?Who knows?
THERE ARE PEOPLE AND THERE ARE USERS
There are people and there are users and any given person can be a number of users throughout the day.
Your abilities are not just relative to yourself; they are also relative to the device you access experiences through
ARCHITECTING THE WEB
➤ Experiences you create are buildings entered, re-visited, and avoided by a wide audience of users
➤ while our abilities may very greatly and change with time we all justly deserve access
➤ just like in the real world
ASSISTIVE TECH IS THE BEST TECHDesign is for everyone – design for everyone
DESIGN FOR
JUSTICEnot for equality
ACCESSIBLE ICON
➤ The Accessible Icon Project is an ongoing work of design activism.
➤ It starts with a graphic icon, free for use in the public domain, and continues its work as a collaboration among people with disabilities and their allies toward a more accessible world
➤ Brazilians work 1 hour for every 14.5MB of access to the web
➤ Some people pay for web access by the byte, not bythe month
➤ People pay *cash* to access the experiences you author.Never forget that.
➤ Be as light as you can on bandwidth
➤ Optimize Images
➤ Always put your content behind GZIP’ed HTML
➤ Leverage the Browser Cache
➤ Don’t use Icon Fonts.Seriously though don’t use Icon Fonts.Ever.
BANDWIDTH AND ACCESSIBILITY
HOW DO YOU SUPPORT LOW BANDWIDTH UERS?
➤ Your experience is only as strong as your weakest point of access
➤ By starting HTML first and progressively enhancing you win half the battle…… but there is more to consider
➤ GZIP! GZIP! GZIP!
➤ Far Future Reaching Expiry Dates
➤ HTTP/2?
➤ Silence your CSS Footprint
YOU ARE NOT YOUR DISABILITYAssistive Technology allows the physically impaired just access
and opportunity in the digital age
ISN’T JAVASCRIPT
EVERYWHERE?Nope.
JAVASCRIPT
➤ is risky
➤ fatally crashes on missing semicolon
➤ is awesome
➤ provides amazing asynchronous enhancements
➤ is not designed to deliver semantic content
➤ ~1% failure rate
WHY SHOULD WE SUPPORT USERS WITHOUT JAVASCRIPT?
➤ performance
➤ search engine optimization
➤ reliability
➤ reach
➤ accessibility
➤ standards
HOW DO WE SUPPORT USERS WITHOUT JAVASCRIPT?
➤ <noscript>?
➤ <noscript> is great, but doesn’t help in situations when JavaScript is enabled but fails to load or dies on a fatal error
HOW DO WE SPLIT UP FRONT END PRIORITIES?
WHAT DO PEOPLE COME TO YOUR
WEBSITE FOR?
JAVASCRIPT?
NOPE.
AJAX?
NOPE.
REACT!
NOPE.
THAT PRETTY STYLESHEET?
(sorry designers)
NOPE.
SO WHAT THEN?
CONTENT
PRIORITIZE CONTENT THROUGHOUT YOUR PROCESS
PRIORITIES ARE DEPENDENT TO EACH PROJECT
➤ Look at your metrics and analytics
➤ Evaluate what is bringing people to your experience
➤ Ask yourself what is more important branding or async enhancements?
➤ Focus on content, branding, then enhancements
CONTENT, BRANDING, ENHANCEMENTS
make asynchronous enhancements your last priority
CSS NAKED
DAYflaunt your DOM
April 9th
