Arboretum and Arbility: Improving Web Accessibility Through a Shared Browsing Architecture
summary
Arboretum implements a managed shared‑browsing architecture that uses Chrome DevTools protocol to clone and rewrite a page’s DOM, CSS and resources so remote helpers see a faithful simulacrum; Arbility adds a chat and propose and accept/reject workflow so helpers suggest actions without taking unilateral control. A user study with 9 blind participants shows completion rates rise to near‑sighted levels for previously impossible tasks, at the cost of longer task time, and raises privacy and long‑term accessibility concerns. Arboretum and Arbility are real prototypes that work on most pages.
AI-written summary · about
chapters (8)
- 0:00Introduction and apology
- 1:10Accessibility gaps on the web
- 6:11Goal of Arboretum and Arbility
- 7:38Arboretum architecture explained
- 12:40Arbility in action
- 13:44Evaluation with blind participants
- 16:57Future directions and automation
- 17:19Q&A session
related talks
21mRethinking web accessibility: Using AR for people with disabilities
24mAccessibility: The Land Time to Interactive Forgot
12mHarnessing the Accessibility Tree
34mAccessibility: the land that time to interactive forgot
44mWeb accessibility for Artisans
43mBeyond the DOM: what’s in the accessibility tree for you?
37mAccessibility Matters: Creating a Better Web
23mPractical A11Y for Web Apps