Breakout Session Summary Transparencies
Areas to advance within W3C
W3C Workshop on Web Device Independent Authoring
Wednesday 4 October 2000
Group 1 - Accessibility
- Suggest UAAG 2.0 should become technology independent!
- Example: All devices that interact with web. Phones, set top boxes, as well as PCs
- All web devices must be directly accessible (c.f. trace research etc)
or interact successfully with assistive technologies
- Which comes first, WCAG or UAAG?
- Browser accessibility improvements (one persons work can increase access loads…)
- Web site accessibility improvements (lots of sites are off limits…)
Group 2 - Markup
Issues
- Do we want as few languages as possible?
- Is there a distinction between presentation language and authoring language?
- Acceptance / learning takes time
- Authoring making DTDs
Requirements
- Empirical research into what people do at the moment
- Ability to transform languages / map their semantics
- Don’t needlessly reinvent things
- Ability to describe and to factor out:
- Logic(s) of application
- Presentation(s) of information
- Interaction(s) / navigation
- Relationships among elements
- Device capabilities / requirements
- Describe user / author interaction / processes
- Coordinate device independence and voice multi-modality work
Group 3 - Modalities
- Account for natural continuity of effort by authors (UIML?)
- I don't care
- I care about this group of devices
- I care about this particular device
- Verification of results on different devices
- Assistance in authoring for particular devices
- Need useful taxonomy (derived from CC/PP?)
Group 4 - Interaction
We want the W3C to undertake the following discovery activities:
Top down
- Generating a generic model of::
- Flow - spatial v temporal
- Interaction
- State - request/response v event (v sample)
- Behaviour - 'dialogue'
Bottom up
- Discovering how interaction is captured currently, in markup and scripting
- Extract commonalities
Topics of interest
- Granularity of interaction
- Context shared across UAs & apps
- Scope
- User & developer metaphors