RE: ATAG2 proposal re: at least as prominent

Hi all,

I haven't received any comments on this, so hopefully people don't have major objections to the  concept of counting opening actions.

Thinking more about it some more...I think that:
- "(a) same container" is really just a sub-set of (b), since if two things are in the same container they will take exactly the same number of opening actions to become visible. 
- there needs to be clarification around the start point of the measurement
- there needs to clarification re: keyboard shortcuts and search since both are actions but are unrelated to prominence. 

So here's a rewording that may clarify things (even if it is a bit longer):

At least as prominent:
----------------------
A *user interface component* A is considered to be "at least as prominent" as another component B when, from a default state, component A becomes displayed (and enabled) with the same number or less "opening" actions than are required for component B to become displayed (and enabled).

- Note 1: When a container is open, all of the enabled components in the same container (e.g. items in a list, items in a menu, buttons in a toolbar, all components on a dialog box, etc.) are considered to be displayed (and therefore are at least as prominent as each other), even if the container must be scrolled for them to become visible. This takes into account that different screen sizes and user settings will affect which components are visible at a given time.

- Note 2: "Opening actions" are actions made by authors on components within the user interface that result in new components becoming displayed or enabled. For example:
 + keyboard shortcut to a top-level menu item to display a sub-menu, 
 + keyboard selection on a button to display a dialog box, 
 + mouse click on a checkbox to enable previously disabled sub-items, etc.

- Note 3: Other actions are not counted as "opening actions" because they do not cause new components to become actionable (e.g., moving focus, scrolling a list).

- Note 4: Keyboard shortcuts to components in closed containers are not counted, because the components have no prominence when they are not displayed. The same is true when authors must use "search" to reveal components in closed containers.

- Note 5: The "default state" is the state of the authoring tool at the beginning of an authoring session as set by the developer. The default state of many document authoring tools is an editing view.



Cheers,
Jan


-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/
Faculty of Design | OCAD University


> -----Original Message-----
> From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
> Of Richards, Jan
> Sent: April 5, 2011 1:14 PM
> To: AUWG
> Subject: RE: ATAG2 proposal re: at least as prominent
> 
> Rewording around "visible" statement:
> 
> At least as prominent:
> For purposes of conformance to ATAG 2.0, a *user interface component* A is
> considered to be "at least as prominent" as a component B, if at least one of
> the following is true:
> *(a) same container:* both components occur in the same container (e.g. list,
> pop-up menu, sub-menu, toolbar, dialog box, web page, etc.); or
> *(b) same or less "opening" actions:* component A, or its container (e.g.
> list, pop-up menu, sub-menu, toolbar, dialog box, web page, etc.), becomes
> visible with less than or equal the number of "opening" actions required for
> component B (or its container) to become visible. Opening actions are user
> interface actions (e.g., keyboard selections, mouse clicks, etc.) that result
> in components, or component containers, becoming visible (e.g. opening a menu,
> opening a dialog box, etc.). Other actions are not counted (e.g., pressing tab
> to move focus).
> Note: The term "visible" refers to what can be seen on the screen or what is
> available without an opening action.
> 
> Ed. Notes:
> (a) so it is sufficient for the accessible templates (etc.) to be in the same
> list as the others. They don't need to be list first in the list because there
> are other relevant sort criteria, such as the type of template, author, save
> date etc.
> (b) This is intended to cover comparisons where A and B are not in the same
> container, such as "Check Spelling" being placed under a "Text" menu and
> "Check Accessibility" being placed under an "Accessibility" menu. The term
> "visible" is necessary in order to practically compare things that are equally
> available to most authors, but may differ in terms of their order when
> accessed via the keyboard.
> 
> 
> --
> (Mr) Jan Richards, M.Sc.
> jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
> Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/
> Faculty of Design | OCAD University
> 
> 
> > -----Original Message-----
> > From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
> > Of Richards, Jan
> > Sent: April 5, 2011 12:59 PM
> > To: AUWG
> > Subject: ATAG2 proposal re: at least as prominent
> >
> > Hi all,
> >
> > I took an action to revisit "at least as prominent". Here's my reboot:
> >
> > At least as prominent:
> > For purposes of conformance to ATAG 2.0, a *user interface component* A is
> > considered to be "at least as prominent" as a component B, if at least one
> of
> > the following is true:
> > *(a) same container:* both components occur in the same container (e.g.
> list,
> > pop-up menu, sub-menu, toolbar, dialog box, web page, etc.); or
> > *(b) same or less "opening" actions:* component A, or its container (e.g.
> > list, pop-up menu, sub-menu, toolbar, dialog box, web page, etc.), becomes
> > visible with less than or equal the number of "opening" actions required for
> > component B (or its container) to become visible. Opening actions are user
> > interface actions (e.g., keyboard selections, mouse clicks, etc.) that
> result
> > in components, or component containers, becoming visible (e.g. opening a
> menu,
> > opening a dialog box, etc.). Other actions are not counted (e.g., pressing
> tab
> > to move focus).
> > Note: The term "visible" refers to what can be seen on the screen.
> >
> > Ed. Notes:
> > (a) so it is sufficient for the accessible templates (etc.) to be in the
> same
> > list as the others. They don't need to be list first in the list because
> there
> > are other relevant sort criteria, such as the type of template, author, save
> > date etc.
> > (b) This is intended to cover comparisons where A and B are not in the same
> > container, such as "Check Spelling" being placed under a "Text" menu and
> > "Check Accessibility" being placed under an "Accessibility" menu. The term
> > "visible" is necessary in order to practically compare things that are
> equally
> > available to most authors, but may differ in terms of their order when
> > accessed via the keyboard.
> >
> >
> > Where is it used?
> > -----------------
> > B.2.2.1 Accessible Option Prominence (WCAG): If authors are provided with a
> > choice of authoring actions for achieving the same authoring outcome (e.g.
> > styling text), then options that will result in accessible web content
> (WCAG)
> > are *at least as prominent* as options that will not. (Level A)
> >
> > B.2.4.2 Template Selection Mechanism: If authors are provided with a
> template
> > selection mechanism, then both of the following are true: (Level AA)
> > (a) Indicate: The selection mechanism indicates the accessibility status of
> > templates (if known); and
> > (b) Prominence: Any accessible template options are *at least as prominent*
> as
> > other template options.
> >
> > B.2.5.1 Pre-Authored Content Selection Mechanism: If authors are provided
> with
> > a selection mechanism for pre-authored content other than templates (e.g.
> clip
> > art gallery, widget repository, design themes), then both of the following
> are
> > true: (Level AA)
> > (a) Indicate: The selection mechanism indicates the accessibility status of
> > the pre-authored content (if known); and
> > (b) Prominence: Any accessible options are *at least as prominent* as other
> > pre-authored content options.
> >
> > B.4.1.4 Feature Prominence: Accessible content support features are *at
> least
> > as prominent* as comparable features related to other types of web content
> > problems (e.g. invalid markup, syntax errors, spelling and grammar errors).
> > (Level AA)
> >
> > APRIL 1 PROPOSAL:
> > -----------------
> > At least as prominent:
> > For purposes of conformance to ATAG 2.0, an item A is considered to be "at
> > least as prominent" as an item B if at least one of the following is true:
> > (a) item A occurs higher in the default reading order than item B; or
> > (b) both items occur in the same item container (e.g. menu of items, list of
> > items, list of tabs, dialog of text entry fields) and if item B is always
> > highlighted, then so is item A; or
> >
> > CURRENTLY IN DRAFT:
> > -------------------
> > at least as prominent:
> > For purposes of conformance to ATAG 2.0, item A is considered to be "at
> least
> > as prominent" as item B if:
> > (a) both items occur in the same item container (e.g. a menu for menu items,
> a
> > list for list items, a dialog box for text boxes); [and]
> > (b) if item B is emphasized, then so is item A; and
> > (c) item A occurs higher in the reading order or immediately follows item B.
> >
> >
> > *Thoughts? (Tim: What do you think of its testability?)*
> >
> >
> > Cheers,
> > Jan
> >
> > --
> > (Mr) Jan Richards, M.Sc.
> > jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
> > Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/
> > Faculty of Design | OCAD University
> >
> >
>

Received on Thursday, 7 April 2011 16:21:23 UTC