- From: Greg Lowney <gcl-0039@access-research.org>
- Date: Thu, 04 Sep 2014 11:49:03 -0800
- To: Jeanne Spellman <jeanne@w3.org>
- CC: UAWG <w3c-wai-ua@w3.org>
- Message-ID: <5408C22F.4040704@access-research.org>
Hi Jeanne, Per ACTION-1034, here is the revised glossary entry for "element" (the stem changed from "element, element type" to just "element", the third sentence replaced, and its original moved to become a third bullet item and revised): element Primarily, a syntactic construct of a document type definition (DTD) for its application. This is the sense employed by the XML 1.0 specification ([XML], section 3). This sense is also relevant to structures defined by XML schemas. UAAG 2.0 also uses the term "element" more generally any discrete unit within the content (e.g. a specific image, video, sound, heading, list, or list item). o enabled element: An element with associated behaviors that can be activated through the user interface or through an API. The set of elements that a user agent enables is generally derived from, but is not limited to, the set of elements defined by implemented markup languages. o disabled element: A potentially enabled element that is not currently available for activation (e.g. a "grayed out" menu item). o element type: A category of elements (such as images, videos, sounds, first level headings, lists, or list items). For comparison, here is the existing version: element, element type Primarily, a syntactic construct of a document type definition (DTD) for its application. This is the sense employed by the XML 1.0 specification ([XML], section 3). This sense is also relevant to structures defined by XML schemas. UAAG 2.0 also uses the term "element" more generally to mean a type of content (such as video or sound) or a logical construct (such as a header or list). o enabled element: An element with associated behaviors that can be activated through the user interface or through an API. The set of elements that a user agent enables is generally derived from, but is not limited to, the set of elements defined by implemented markup languages. o disabled element: A potentially enabled element that is not currently available for activation (e.g. a "grayed out" menu item). -------- Original Message -------- Subject: Re: finishing up MS04 - Sequential Navigation Between Elements From: Greg Lowney <gcl-0039@access-research.org> To: Jeanne Spellman <jeanne@w3.org>, UAWG <w3c-wai-ua@w3.org> Date: 9/3/2014 11:17 PM > Hi Jeanne, > > Re 2.2.1 Sequential Navigation Between Elements, I don’t think the added wording is necessary, and in fact the current wording may already be redundant, because: > > 1. "recognized" is no longer required because we put in UAAG 2.0 Conformance Applicability Note #3, which says all SC about content apply only to content that’s recognized, and > > 2. "in the rendered content" isn’t strictly necessary because "element" is already defined as being in content. > > I also notice, though, that the definition of "element" isn't quite right. It says in part "UAAG 2.0 also uses the term 'element' more generally to mean a type of content (such as video or sound) or a logical construct (such as a header or list)." That seems to be confusing the two terms "element" and "element type". How about replacing that sentence with something like: > > "UAAG 2.0 also uses the term 'element' more generally any discrete unit within the content (e.g. a specific image, video, sound, heading, list, or list item)." > > And then to add the following sub-definition bullet item (to join the two that are already there): > > "element type: a category of elements (such as images, videos, sounds, first level headings, lists, or list items)." > > Thanks, > Greg > > -------- Original Message -------- > Subject: finishing up MS04 > From: Jeanne Spellman <jeanne@w3.org> > To: UAWG <w3c-wai-ua@w3.org> > Date: 9/2/2014 12:25 PM >> 2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. (Level A) >> Change to "...all recognized enabled elements in the rendered content of the current viewport." [rendered content is linked to definition] >
Received on Thursday, 4 September 2014 18:50:10 UTC