Edit comment LC-926 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-848 Next: LC-1413

Comment LC-926: Comment Shortname:; Commenter: Andi Snow-Weaver <andisnow@us.ibm.com> on behalf of IBM; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Definition of "programmatically determined" is confusing.

Proposed Change:

Proposal for definition of ""programmatically determined"":

""available through content markup (element name, attributes, or properties) or style sheet properties in the case of markup languages or through accessibility APIs in the case of GUI applications.

Note: User agents can extract this information from content markup and style sheet properties and make it available to an assistive technology through programmatic means such as through the DOM or accessibility API. Accessibility APIs may be defined by the technology owner or in a publicly documented alternative recognized as explicitly supporting accessibility.; Related issues: (space separated ids); WG Notes: [EDITORZ] [HOLD] NOTES FROM CLARIFICATION DISCUSSION WITH COMMENTER (IBM) on 7/5/06. SUGGESTIONS BELOW FOR EDITS CAME UP DURING DISCUSSION AND WERE OK TO COMMENTER. PROVIDED HERE AS FURTHER INPUT TO DELIBERATION PROCESS - NOT AS RESOLUTION. Proposal for definition of "programmatically determined": "available through content markup (element name, attributes, or properties) or style sheet properties in the case of markup languages or through accessibility APIs in the case of NON-MARKUP BASED applications. Note: AT COULD ACCESS THIS INFORMATION DIRECTLY OR User agents can extract this information from content markup and style sheet properties and make it available to an assistive technology through programmatic means such as through the DOM or accessibility API. Accessibility APIs may be defined by the technology owner or in a publicly documented alternative API recognized as explicitly supporting accessibility. ------------ QUESTION: In text above, should it be "AT supported Markup Languages"? THOUGHT: No this should be in Baseline or else everyone has to do AT testing. This should be done by those setting baseline, not here. ------------ BBC: To include information about style sheet properties here seems to be in conflict with the principles of CSS. This also removes the requirement that information be provided in a user-agent supported manner. Discussed in the 25 January 2007 telecon: resolution: accept 926 as proposed http://www.w3.org/WAI/GL/2007/01/25-wai-wcag-minutes.html {partial accept} SEE ACTIONS FOR LC-756 BBC: Updated resolution to match 1013. Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0080.html; Resolution: We have not changed the definition to distinguish between markup and non-markup languages, but we have added several examples to the definition to highlight the use of direct access and access via accessibility APIs.; (Please make sure the resolution is adapted for public consumption)