W3C:IndieUI in its context Andy Heath 2014-03-29 : Paris, France Braillnet 8th European e-Accessibility Forum: User-driven e-Accessibility
Presentation Context • These are my own views, not necessarily those of any organisation • I do this work because I want to live in an inclusive world where we use technology to make life better and easier for us all • Nobody pays me (I would like that they did) • Two routes through these slides – route 1 - techy and concise but hard, route 2 - easy and woffly, explains the IndieUI context (get the technical detail later), audience choice 1
Route 1 IndieUI • http://www.w3.org/WAI/IndieUI/ • Participants include: Apple, IBM, Google, Opera, The Inclusive Design Research Centre Toronto, me + 8 other orgs • For Mobile - consists of – Events https://dvcs.w3.org/hg/IndieUI/raw- file/default/src/indie-ui-events.html – User Context https://dvcs.w3.org/hg/IndieUI/raw- file/default/src/indie-ui-context.html – Both at 1.0 Editors drafts 2
Route 1 Events • Low level interface events delivered through OS eventually to web app • IndieUI: Events 1.0 is an abstraction between physical, device-specific user interaction events and inferred user intent such as scrolling or changing values. This provides an intermediate layer between device- and modality- specific user interaction events, and the basic user interface functionality used by web applications. IndieUI: Events focuses on granular user interface interactions such as scrolling the view, canceling an action, changing the value of a user input widget, selecting a range, placing focus on an object, etc. Implementing platforms will combine modality-specific user input, user idiosyncratic heuristics to determine the specific corresponding Indie UI event, and send that to the web application in addition to the modality-specific input such as mouse or keyboard events, should applications wish to process it. • Essentially for 1.0 – fix the problems • Developer must know about the event and register interest in that event (less impact on DOM) 3
• 3. UI Request Events3.1 Interface UIRequestEvent Route 1 – 3.1.1 Attributes – 3.1.2 Determining the Event Receiver – 3.1.3 UIRequestEventInit • 3.1.3.1 Dictionary UIRequestEventInit Members – 3.1.4 UIRequestEvent Types • 3.2 Interface UIFocusRequestEvent – 3.2.1 Attributes – 3.2.2 Enumeration FocusRequestFocusType – 3.2.3 UIFocusRequestEventInit • 3.2.3.1 Dictionary UIFocusRequestEventInit Members – 3.2.4 UIFocusRequestEvent Types • 3.3 Interface UIManipulationRequestEvent – 3.3.1 Attributes – 3.3.2 UIManipulationRequestEventInit • 3.3.2.1 Dictionary UIManipulationRequestEventInit Members – 3.3.3 Discrete UIManipulationRequestEvent Types – 3.3.4 Continuous UIManipulationRequestEvent Types • 3.4 Interface UIScrollRequestEvent – 3.4.1 Attributes – 3.4.2 Enumeration ScrollRequestScrollType – 3.4.3 UIScrollRequestEventInit • 3.4.3.1 Dictionary UIScrollRequestEventInit Members – 3.4.4 UIScrollRequestEvent Types – 3.4.5 Continuous UIScrollRequestEvent Types • 3.5 Interface UIValueChangeRequestEvent – 3.5.1 Attributes – 3.5.2 Enumeration ValueChangeRequestChangeType – 3.5.3 UIValueChangeRequestEventInit • 3.5.3.1 Dictionary UIValueChangeRequestEventInit Members – 3.5.4 UIValueChangeRequestEvent Types 4
Route 1 User Context • The primary goal of IndieUI User Context is to provide authorized web applications access to information about a user's relevant settings and preferences, to provide the best possible user experience to all users. Some complex web applications can provide a much better experience if given access to information such as a user's preferred color, font, screen, and even *restricted* assistive technology settings such as a preference to render captions, or whether a screen reader is on. General web pages developed using best practices may never need access to restricted user settings, but complex web applications can utilize this information to enhance the performance and user interface. • 1.0 is fairly low level preferences 5
• 5. Settings Keys and Related Media Feature counterparts5.1 User Color Settings Route 1 – 5.1.1 Key: user-color • 5.1.1.1 Associated Media Feature: user-color – 5.1.2 Key: user-background-color • 5.1.2.1 Associated Media Feature: user-background-color – 5.1.3 Key: colors-inverted • 5.1.3.1 Associated Media Feature: colors-inverted – 5.1.4 Key: user-contrast • 5.1.4.1 Associated Media Feature: user-contrast – 5.1.5 Key: monochrome • 5.1.5.1 Associated Media Feature: monochrome • 5.2 User Type/Font Settings – 5.2.1 Key: user-font-size • 5.2.1.1 Associated Media Feature: user-font-size – 5.2.2 Key: user-minimum-font-size • 5.2.2.1 Associated Media Feature: user-minimum-font-size – 5.2.3 Key: user-line-height – 5.2.4 Key: user-letter-spacing – 5.2.5 Key: user-word-spacing • 5.3 User Media Settings – 5.3.1 Key: subtitles – 5.3.2 Key: subtitle-languages – 5.3.3 Key: subtitle-type – 5.3.4 Key: user-subtitle-color • 5.3.4.1 Associated Media Feature: user-subtitle-color – 5.3.5 Key: user-subtitle-background-color • 5.3.5.1 Associated Media Feature: user-subtitle-background-color – 5.3.6 Key: audio-description • 5.4 Screen Reader Settings – 5.4.1 Key: screenreader • 5.4.1.1 Associated Media Feature: screenreader 6
Route 1 Beyond 1.0 • Work in Progress – http://www.w3.org/WAI/IndieUI/wiki/Proposals/K eyValueProperties – http://www.w3.org/WAI/IndieUI/wiki/User_Conte xt/Requirements • I hope – Higher level abstract media and UI preferences interoperable with some other pieces 7
Route 2 Accessibility • Is a relationship • Producer Consumer • Every effort to improve it is based on a way to cross the producer/consumer gap. It’s a hard gap to cross 8
Route 2 A few Models • Medical (e.g. ICIDH) • Social • Arthritic wrists – can’t • Society disables us turn door handles by its choices • Negative “you don’t • Yes I like this, but have X, you aren’t how do we normal” implement it ? • It’s a model and people (choose to) forget that 9
Route 2 Some Models • Technological bio-psychosocial • Evaluation, testing, UK Incapacity what can we do with content to Benefits: make it accessible (e.g. WCAG)? I think your • Yes this is good but capabilities are X, Y, its often producer- Z and you can work side only and often defeated by complexity This is RUBBISH 10
Route 2 Some Models • User Needs • Instead of “arthritic wrists, can’t turn handle” • Needs handle that can be turned with low force • Can optimise designs and deliveries for individual users 11
Route 2 A Very Big Problem: • Producer: I know what you need • Consumer: This is rubbish, I can’t use it • I believe this is built in to how perception works (categorisation) • Accessibility is a relationship • To improve it both sides need to have influence 12
Route 2 Another Problem • Not just one producer – Many producers – Many technologies – Market Place • Need to get some coherence and interoperability – otherwise accessibility gets forgotten and after-the-fact companies cannot fill the gap (too complex, too expensive to keep up) 13
Route 2 Desktops • Originally no accessibility • Now standard Accessibility API’s for major platforms ISO:13066 standardised in ISOIEC SC35 User Interfaces • Developers (e.g. screen readers) can develop to them and it works • Still have many platforms and versions and changes cost a lot to developer companies • Still have e.g. interoperability issues (partly security) – often what works on one platform won’t on another 14
Route 2 Mobile Platforms • Can we do better ? YES (well we can try) • Common API to Web Apps (like Desktop API’s) • Individual Preferences (so users have some control and influence in what they get). – These together are IndieUI (Events and User Context) – Content and UI adapt to preferences in context • Challenges: – Getting organisations doing pieces of this in harmony – What preferences ? – Diverse business strategies (e.g. walled gardens and open ones, security and privacy) 15
Route 2 Some organisational pieces • Metadata on content and UI – http://www.w3.org/wiki/WebSchemas/Accessibility • Preferences to match these – In progress, developed from IMS Access for All V3.0 (http://www.imsglobal.org/accessibility/#afav3 ) and ISO/IEC Individualised Adaptability and Accessibility in L.E.T. (http://www.iso.org/iso/home/news_index/news_arc hive/news.htm?refid=Ref1217 ) – currently under re- design 16
Route 2 • accessibilityFeature • E.g – alternativeText – annotations – audioDescription – bookmarks – braille • Notes: – captions – ChemML – describedMath • This is Metadata on – displayTransformability – highContrastAudio – highContrastDisplay Content – index – largePrint – latex • Its low level, also – longDescription – MathML – none need a high level – printPageNumbers – readingOrder abstract sensory – signLanguage – structuralNavigation – mode we call tableOfContents – taggedPDF – tactileGraphic accessMode in IMS – tactileObject – timingControl – transcript – ttsMarkup – unlocked 17
Recommend
More recommend
