280 likes | 407 Vues
This presentation by Ted Drake from Yahoo's Accessibility Lab explores what an accessible website looks like when designed with web standards. It covers essential features such as semantic data, mobile accessibility, and the importance of expandable content and keyboard navigation. Key considerations for diverse user needs, including cognitive and physical challenges, are highlighted to ensure inclusivity. Learn how to create a versatile web experience that caters to everyone, enhancing usability beyond traditional standards.
E N D
Segment 2: Web Standards & Accessibility Ted Drake, Yahoo Accessibility Lab Slideshare.net/7mary4
What does an Accessible Site Designed with Web Standards Look Like?
Topics • Features of an accessible site designed with Web Standards? • Beyond the blind • When web standards is not enough • Mobile Users
Solid • Versatile • Semantic Data • Device Independent
New Visual & Auditory Concerns • Expandable content • Editable text • Drag and Drop • Gestures • Closed Captions • Regularly updated content • Dialogue boxes • Keyboard focus control
Drag and Drop Provide non-mouse alternative
Expandable Content • Button for expand/contract • Place focus into expanded area • Tell user the container can be expanded
Live Regions • Define regions of the page that update automatically. • Should the screen reader user get a notification every time it changes?
Cognitive and Physical Concerns • Memory loss • Different cognitive levels of understanding content. • What helps some will distract others • Dyslexia • Keyboard navigation • Voice recognition
Voice Recognition • Dragon Naturally Speaking • Images with text must have matching alt text. • Don’t autofocus form elements • Avoid multiple links to different URLs with the same text.
Avoid long sentences • Avoid large blocks of text • Avoid justified alignment • Give the user white space • Dyslexie: font designed for dyslexia
iPhone and iPad • Full featured VoiceOver • Safari browser supports HTML5, CSS3, JavaScript • Custom gestures will conflict with VoiceOver. • No Flash support
Android, Blackberry, Nokia • Screen reader is available, but not as sophisticated as VoiceOver • Use clean, structural markup for better performance • Android’s browser is full featured. Blackberry and Nokia are not as robust.
Questions? Question mark in Esbjerg Some rights reserved by alexanderdrachmann