13444 2011-07-29 05:09:31 +0000 introduction to semantics does not convey their importance to people with disabilities/users of AT, nor the negative impact incorrect or insufficient semantics can have on the user experience 2011-08-17 00:43:22 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED FIXED http://www.w3.org/TR/2011/WD-html5-20110525/elements.html#elements a11y, a11ytf P2 normal --- 1 joshue.oconnor ian ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51728 0 joshue.oconnor 2011-07-29 05:09:31 +0000 While this section of the spec [3.2 Elements & 3.2.1 Semantics] introduces the use of semantics and how they relate to conformance, the examples given don’t convey the negative impact incorrect or insufficient semantics can have on the user experience, in particular for users of Assistive Technology. I suggest the following or similar spec text be added to the ‘Elements’ section to illustrate these issues and to provide a deeper sense of context and purpose behind the need to create conformant content. This text could go in either ‘3.2.1 Semantics’ or in the following section ‘3.2.2 Elements in the DOM’. [1] Draft Spec text <sample spec text> "At all stages, in a dynamically generated or altered document the semantic integrity of the document snapshot must be maintained at each step in the document mutation – in particular where the document is in a ‘steady’ state (after a user interaction for example). These rules may be relaxed to some degree during transitional steps involve background transition or operations with other APIs but, if the document is to be a conformant HTML5 doc, then suitable elements/attributes from this spec must be used in a way that supports the documents integrity, the UA parsing requirements and above all the user experience as this can impact on the usability and accessibility of the content. Maintaining this integrity will assist user agents such as Assistive Technologies understand and successfully interact with the DOM or other user agent structures, [ref]. This means that a dynamic widget which is semantically structured to be accessible on a page load, will when responding to user interaction/input have to maintain its semantic structure as scripting or other dynamic events are applied and the widget content/structure is altered, in order to be considered conforming html. This example is applicable to processes such as a checking out cart, or in mashup type applications and semantic integrity will help to maintain the interoperability of application/document structures as well as facilitate a more consistent user experience. ** Examples of where this kind of mutation or dynamically altered content can impact on the user can be found in WCAG." </sample spec text> Related WCAG SC, Fails etc **SC 2.4.5: note wcag reference to dynamic processes [2] F76: Failure of Success Criterion 3.2.2 due to providing instruction material about the change of context by change of setting in a user interface element at a location that users may bypass(context change in an interface) [3] G13: Describing what will happen before a change to a form control that causes a change of context to occur is made. [4] [1] http://www.w3.org/TR/2011/WD-html5-20110525/elements.html#elements [2] http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-mult-loc.html [3] http://www.w3.org/WAI/GL/WCAG20-TECHS/F76.html [4] http://www.w3.org/TR/WCAG20-TECHS/G13 53827 1 mike 2011-08-04 05:17:43 +0000 mass-move component to LC1 55256 2 ian 2011-08-17 00:42:46 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: Add text explaining the reasoning behind the requirements in this section. 55257 3 contributor 2011-08-17 00:43:22 +0000 Checked in as WHATWG revision r6479. Check-in comment: Explain requirements http://html5.org/tools/web-apps-tracker?from=6478&to=6479