- From: Ian Jacobs <ij@w3.org>
- Date: Wed, 11 Oct 2000 16:57:35 -0400
- To: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
- CC: w3c-wai-ua@w3.org
Jon Gunderson wrote: > > WAI UA Telecon for October 12th, 2000 > > Chair: Jon Gunderson > Date: Thursday, 12 October > Time: 2:00 pm to 4:00 pm Eastern Standard Time, USA > Call-in: Longfellow Bridge (+1) (617) 252-1038 > > Agenda > > Open Action Items > > 1.IJ: Propose text for a note explaining the implementation issues > related to providing user agent generated content through the DOM I think I satisfied this in section 3.10 of the techniques document of 29 Sep [1]: > 3.10 Content repair techniques > > Several scenarios may result in the user agent repairing or modifying content for the user's benefit: > > The author has provided invalid markup. > The author has omitted optional information that is important for accessibility. > The user agent is missing resources (e.g., a font family) for handling or rendering content. > The user has configured the user agent in some way that changes the content (e.g., turning off support for images, which causes a placeholder icon to appear in place of each > image that has not been loaded). > > User agent developers should be aware of the following issues when implementing a repair feature: > > Users may want to distinguish content (in the document object model) provided by the author from content generated by the user agent. For example, the user may trust > author-supplied content more than generated content. > Repair content should be accessible. For example, if the user agent inserts a graphical placeholder icon in the document object model, that icon should have a text equivalent: > since the icon is known to the user agent developer, the developer can provide a sensible text equivalent to accompany it (for the benefit of users of assistive technologies). > Notification of user agent-initiated changes to the document object model may be made through "DOM events" (refer to the "Document Object Model (DOM) Level 2 Events > Specification" [DOM2EVENTS]). > > Refer also the section on table cell header algorithm for information about repairing tables. Refer also to the W3C document "Techniques For Accessibility Evaluation And Repair Tools" > [AERT]. [1] http://www.w3.org/WAI/UA/WD-UAAG10-TECHS-20000929/#repair-techniques -- Ian Jacobs (jacobs@w3.org) http://www.w3.org/People/Jacobs Tel: +1 831 457-2842 Cell: +1 917 450-8783
Received on Wednesday, 11 October 2000 16:57:38 UTC