Fringe a11y (Techniques That Shouldn’t Be)
summary
Shows concrete anti-patterns and fixes: reCAPTCHA often ships with tabindex >0 which jumps keyboard focus to the captcha, so use tabindex="-1" for scripted focus and tabindex="0" only when needed; Flexbox and Grid can reorder visual focus so test tabbing across Chrome and Firefox to keep source order meaningful; don’t disable zoom by locking viewport max‑scale, allow pinch zoom; avoid relying on color alone so keep link underlines or matching 3:1 contrast; provide captions/transcripts (NoMoreCraptions, WebVTT), set lang for correct screen reader pronunciation, and test Windows high contrast.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:59Fringe Accessibility Techniques (That Probably shouldn't Be)
- 2:28About Adrian Roselli
- 3:38What is ally?
- 4:54What We'll Cover
- 5:25Common(?) Techniques
- 8:05Use Link Underlines
- 11:09Use : focus Styles
- 13:47Use Wisely
- 17:08Use Only One per Page
- 18:39Source Order Matters
- 21:20Don't Use tabindex 0
- 23:05Maybe Use tabindex=0
- 26:19Set lang attribute on
- 28:04Don't Disable Zoom
- 29:31Use Captions/Subtitles
- 31:48Test in Windows High Contrast Mode
- 33:08Avoid Infinite Scroll
- 34:29Reconsider Typefaces for Dyslexia
- 36:05Use On-Page Descriptions
- 37:16role="search" on is OK
- 37:51Try Not to Tweet Pictures of Text
- 39:47Share ally Experiences
- 42:18Stairamp
- 42:52Process
- 43:07Snowtreeramp
related talks
48mCoding For Accessibility Best Practices from the Front Lines
46mFocusing on Focus
33mAccessibility Done Right
41mWhat If We Talked About Web Accessibility?
32mCommon ways we break accessibility and how to avoid them
41mTales of Accessibility Failures
35mAccelerating accessibility in web
36mShift your mindset on accessibility & inclusion