urc based accessible tv
TRANSCRIPT
June 04, 2009, Leuven
URC Based Accessible TVGorka Epelde: [email protected]
2
Providing multiple levels of service interactivity
Accessibility efforts focused on content Subtitling for the hearing impaired
Audio description of programming for the visually impaired
Accessibility in remote control Advancements in remote controller’s usability
Interaction paradigm based on infrared remote control unchanged
Current State of Affairs URC Based Accessible TV
Not accessible or personalized for all
user groups
3
In Contrast URC Based Accessible TV
Current Research
• Interaction through a single controller
• Limited UI
• Limited user base
Our Work
• Interaction through multiple controllers
• Pluggable UIs
• Tailored to the user
4
Universal Remote Console
• Introduces the User Interface Socket as the interaction point between a pluggable
user interface and a target device or service.
• ISO/IEC 24752 standard
• Choose from different interface technologies: HTML, Web 2.0, C#, Flash, Java, ...
• User interface updates and 3rd party contributions via resource server
Universal Control Hub
• URC conformant middleware architecture UCH = URC in a box
• Connects non-URC compatible controllers and non-URC compatible target
devices/services
• Bridges across multiple targets and target platforms
• Provides a choice of user interfaces for various controller platforms
The URC frameworkURC Based Accessible TV
5
The URC frameworkURC Based Accessible TV
Universal Control Hub (UCH)
6
Proposed architecture for Accessible TVURC Based Accessible TV
Proprietary
7
ImplementationURC Based Accessible TV
8
TV’s integration in the UCH architecture
• Define XML documents specified by the URC standard:
Target Description: Information required by a client to connect to a TV’s UI socket.
User Interface Socket Description: XML document with a machine-readable description of
TV functionalities.
Target Resource Sheet: Definition of resources that can be used to build the UI. (language
specific strings, icons, ...)
ImplementationURC Based Accessible TV
• Specific code for the UCH architecture:
Target Discovery Module:Module responsible for
discovering targets (TV, DVDs,...) to be controlled by the
UCH.
Target Adapter: Module that connects a specific target (TV)
in its native protocol (Vista Media Center's API), with the
relevant UI socket instance.
9
PUI 1 – Accessible DHTML for the visually impaired
• Target Users: Persons with visual impairments.
• DHTML page running on a vertically handled tablet-pc.
Developed in accordance to WCAG 2.0 guidelines.
Colours & fonts can be adapted using style sheets.
Tagged to be compatible with screen readers.
Connects to the UCH using URC-HTTP over a wireless connection. (JavaScript implementation)
ImplementationURC Based Accessible TV
10
PUI 2 – Multimodal UI on Smartphone
• Target Users: Persons with mild cognitive impairments.
• Multimodal UI developed using Ontology-based Dialogue Platform (ODP)
HTC 7500 Advantage PDA: relatively large touch screen & modern design
Combined speech and finger gesture input.
Designed with fewer navigation steps & large icons.
Connects to the UCH using URC-HTTP over a wireless connection. (.NET Compact Framework
implementation)
ImplementationURC Based Accessible TV
11
TV sets accessible for all
Standard based architecture allowing the deployment of Plug-and-Play
UIs
Customised UIs can be easily deployed through resource servers.
• New Market for UIs
Implementation
• Vista Media Center as a TV set.
• Two pluggable UIs developed: for the visually impaired and for users with mild
cognitive impairments
UCH to be embedded into existing TV sets or TV Set-Top boxes
Validation with target users in progress: promising preliminary results
An architecture to contribute to the development of TV technologies to
their full potential
• Advanced UIs, Natural language UIs and UIs that span over multiple devices &
services. (DVD players, Home Automation, interactive services,...)
ConclusionsURC Based Accessible TV
12
Authors
Gorka Epelde (VICOMTech)
Eduardo Carrasco (VICOMTech)
Gottfried Zimmermann (Access
Technologies Group)
Jürgen Bund (Meticube)
Markus Dubielzig (Siemens AG)
Jan Alexandersson (DFKI)
Thank you!
Acknowledgements
This work was partially funded by the EU 6th Framework Program under grant FP6-033502 (i2home).
Questions?
Contact: [email protected]