- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Wed, 03 Mar 2010 10:05:31 -0500
- CC: WAI-AUWG List <w3c-wai-au@w3.org>
Thanks Tim - I think your feedback helped make the wording much more clear. Cheers, Jan On 03/03/2010 8:54 AM, Boland Jr., Frederick E. wrote: > I think the example is helpful in clarification. Thanks Jan! > Tim Boland NIST > > > -----Original Message----- > From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf Of Jan Richards > Sent: Tuesday, March 02, 2010 10:11 AM > To: WAI-AUWG List > Subject: ATAG2 Action: re: encode continuous input > > Hi all (especially Tim who has an action to review this), > > My action was to "To flesh out the watercolor example with more details > e.g. frequency and why it is practically hard to do with keyboard" - in > doing this I also added a bit of wording around web content properties: > > <UNCHANGED> > content (web content) > Information and sensory experience to be communicated to the end user by > means of a user agent, including code or markup that defines the > content's structure, presentation, and interactions. In ATAG 2.0, the > term is primarily used to refer to the output that is produced by the > authoring tool. Content produced by authoring tools may include web > applications, including those that act as web-based authoring tools. > Accessible web content is web content that conforms to a particular > level of WCAG 2.0 (see Relationship to WCAG 2.0 section). Structured web > content is content that includes machine-readable internal structure > (e.g., markup elements), as opposed to unstructured content, such as > raster image formats or plain human language text. > </UNCHANGED> > <NEW> > *Web content properties* are the individual pieces of information that > make up the web content (e.g., the attributes and contents of elements, > stylesheet information, etc.). While many web content properties have > discrete values (e.g., a single value for size, color, font, etc.), some > types of web content (especially graphics) may includes properties that > can be said to *encode continuous input* because they incorporate > frequent data samples (e.g., the location, speed, pressure, angle, etc. > of a pointing device) . For example, a freehand line graphic object > might have a "continuous" path property that encodes thousands of > individual x-y location values, but "discrete" properties for setting > the color and thickness of the line. A "watercolor stroke" graphic > object might have multiple "continuous" properties (e.g., path, speed, > pressure) in order to graphically mimic the diffusion effects that occur > when a real paint brush is moved in a similar manner. > </NEW> > > > > Cheers, > Jan > > -- (Mr) Jan Richards, M.Sc. jan.richards@utoronto.ca | 416-946-7060 Adaptive Technology Resource Centre (ATRC) Faculty of Information | University of Toronto
Received on Wednesday, 3 March 2010 15:05:58 UTC