- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Tue, 28 Aug 2007 16:30:32 -0400
- To: WAI-AUWG List <w3c-wai-au@w3.org>
Hi, My action from yesterday's call was to simplify the language in the "Authoring Actions/Outcomes/Practices" terminology set. Here goes: AUTHORING ACTION Any action that *authors* can take using the *authoring tool user interface* that causes a modification of the *content* being edited (e.g., typing text, selecting a "center justified" option, pressing delete with an element selected). Actions that do not modify the content are excluded (e.g., setting tool preferences, opening the help system). AUTHORING OUTCOME A characteristic of the *content* when it is rendered, played or executed that results from the application of one or more *authoring actions* (e.g., text is center justified). Two examples of content may share some authoring outcomes, but not others (e.g., headings that are implemented with header markup versus presentation markup both have the authoring outcome of being visually evident, but one lacks the authoring outcome of allowing header navigation). AUTHORING PRACTICE A technique that *authors* or the authoring tool follow in order to select *authoring actions* that will achieve particular *authoring outcomes*. An ACCESSIBLE AUTHORING PRACTICE is one that leads to an accessible authoring outcome (e.g., providing text alternatives for non-text content to enable non-visual use). Cheers, Jan Jan Richards wrote: > > Short meeting today (4:40-5:00 ET): > > PARTICIPANTS: > Jan R > Jutta T > Greg P > Tim B. (joined a bit later) > > GLOSSARY: > > assistive technology @@ok'd by JT,JR,GP > > direct accessibility @@ok'd by JT,JR,GP > Features of mainstream software applications and hardware that augment > accessibility by people with disabilities (e.g., keyboard navigation, > zoom functions, text-to-speech). > > mainstream technology @@ok'd by JT,JR,GP > Software applications and hardware for which augmenting accessibility is > secondary to some other purpose, as opposed to assistive technology. > Mainstream technologies may include direct accessibility features. > > ACTION JR: Keep but simplify the authoring action/authoring > outcome/authoring practice framework. > > NEXT MEETING Sept. 10 > > Cheers, > Jan > > > Jan Richards wrote: >> >> Hi everyone, >> >> NOTE: There will be a SPECIAL LATE START because I don't know if Jutta >> will be back from vacation and I have a medical appointment before the >> call. >> >> >> >> Just a reminder that there will be an AUWG teleconference on Monday 27 >> August 2007 at 4:30 pm - 5:00 pm ET: >> >> Call: (617) 761-6200 ext. 2894# >> IRC: server: irc.w3.org, port: 6665, channel: #au >> >> Agenda: >> >> 1. Glossary edits (including Assistive Technology, etc.): >> http://lists.w3.org/Archives/Public/w3c-wai-au/2007JulSep/0035.html >> >> (see here for original wording >> http://www.w3.org/WAI/AU/2007/WD-ATAG20-20070515/WD-ATAG20-20070515.html) >> >> 2. F2F at Plenary (8-9 November) >> >> Please send regrets to the list. >> >> >> Cheers, >> Jan >> >> > -- Jan Richards, M.Sc. User Interface Design Specialist Adaptive Technology Resource Centre (ATRC) Faculty of Information Studies University of Toronto Email: jan.richards@utoronto.ca Web: http://jan.atrc.utoronto.ca Phone: 416-946-7060 Fax: 416-971-2896
Received on Tuesday, 28 August 2007 20:30:05 UTC