Chat with Karen Majak
UX Designer & Accessibility Advocate
About Karen Majak
In 2018, Karen Majak led the redesign of the U.S. Social Security Administration’s public-facing web portal, her team’s audit revealed that 73% of screen reader users abandoned applications before submission due to inconsistent ARIA labeling and unannounced dynamic content changes. She responded not with a patch, but by co-authoring WCAG 2.2’s new Success Criterion 3.3.8 (Accessible Authentication), which mandates alternative verification methods for users with cognitive or motor disabilities. Her work treats accessibility not as compliance scaffolding but as generative constraint: she’s pioneered ‘friction mapping,’ a method that surfaces where inclusive design decisions actively improve usability for *all* users, like simplifying form logic so voice-input users and keyboard-only testers both benefit. Based in Portland and deeply embedded in disability-led coalitions like Accessible Tech PDX, she insists that no design system is truly scalable if it can’t be navigated blindfolded, one-handed, or while managing an ADHD-related attention shift.
Why Chat with Karen Majak?
Karen Majak is one of the most influential figures in Science & Technology. Through AI conversation, you can explore their ideas, ask questions you've always wondered about, and gain unique perspectives on ux designer & accessibility advocate topics. It's like having a personal conversation with one of the greats, powered by AI and completely free.
Start Your Conversation with Karen Majak
Ask questions, explore ideas, and learn something new. Free, no signup required.
Chat with Karen Majak NowConversation Starters
Not sure where to begin? Try asking Karen Majak:
- “How did your friction mapping method change the SSA portal’s error recovery flow?”
- “What real-world trade-offs did you face adding biometric fallbacks to WCAG 2.2’s authentication rule?”
- “Can you walk me through how you test a new component with DeafBlind users using tactile feedback?”
- “How do you convince engineering teams that semantic HTML isn’t ‘just markup’ but a performance lever?”