Breakout Session Summary Transparencies
Device Independence SWOT analysis
W3C Workshop on Web Device Independent Authoring
Wednesday 4 October 2000
Group 1 - Accessibility Focus
Strengths
- Legislation
- Cost saving
- Many devices
- W3C
- Fashion
Weaknesses
- Hard to define
- Learning curve
- Legacy
- Complexity
- No standards (e.g. TV, phone)
- Lack of education
Opportunities
- WAI
- Market
- Education
- Internationalisation, translation
Threats
- Chicken and egg - who will start?
- Proprietary authoring tools
- Many guidelines - which one to use?
- Misconception
Action
- W3C certification
- Train the trainers
- Increase industry involvement
Wishlist
- Usable tools
- Tool integration
- Train users
Focus
- Education
- Tool development
- Involvement of industry
Contingencies
Group 2 - General Focus
Strengths
- Increases audience
- Leads to increased content
Weaknesses
- Lack of compelling use cases
- Variable quality of service / experience
- Fixing legacy content
Opportunities
- Future proofing
- Cool gadgets - feature creep marketing
- New kinds of services
- New content markets
- Optimise user experience
Threats
- Perceived cost
- Fragmented web
- Copyright / control of content presentation
- People can wait
- May not be (seen as) necessary /useful
- [Dilbert's manager icon]
Wishlist
- Phones (etc) with APIs for Voice in/out, GUI / WIMP etc
- Multimodal preview in tools
Group 3 - Device Independent Application Model Focus
Strengths
- Allows for content repurposing
- Accounts for digital TV concerns
- Allows for coping strategies
- Provides state and scope
- Rich user experience
Weaknesses
- Doesn't account for 'close to the metal'
- yacc [Yet Another Compiler Compiler]
Opportunities
- Leverage VoiceXML, XForms etc
- Tie in existing 'standards' without binding authors to specific schemas
- Leverage trends in localization
Threats
- Large scope of work
- Requires memetic engineering (training, thought patterns)
Action
- Find user cases and business cases
- Focus on channels adapting authors intent
Wishlist