<scribe> Scribe: Andi

bug 13206

definition of managed states: A state that is relevant to accessibility APIs but whose value is read and set by the user agent. The application author does not always manage these states, but needs to be aware that the user agent will. In some cases the application author does manage these states as well. Common managed states include focus and selection.

definition of managed states: A state that is relevant to accessibility APIs but whose value is read and set by the user agent. The application author does not always manage these states, but needs to be aware that the user agent will. In some cases the application author does manage these states as well. Common managed states include focus and selection.

CS: do we want to say these may or may not map to the WAI-ARIA states?

AS: that doesn't say much either
... a managed state is one that is managed by the user agent instead of the web application

CS: accessibility API state that is managed by the user agent instead of the web application.

AS: but what about the sentence "In some cases the application author does manage these states as well."?

CS: because WAI-ARIA is a one-way UI, if the user agent changes the states, the web application may or may not be notified
... there might be an event and there might not be one
... related WAI-ARIA state won't be updated and might get out of sync
... do we need to say that Web authors need to be aware that related WAI-ARIA states won't always be updated?

managed state: Accessibility API state that is controlled by the user agent. Examples are focus and selection. Managed states often have corresponding CSS pseudo-classes (such as :focus and ::selection) to define style changes. In contrast, the states in this specification are typically controlled by the author and are called unmanaged states. Some states are managed by the user agent, such as aria-posinset and aria-setsize, but the author can override them if th

Some managed states can be overridden by the web application author, such as aria-posinset and aria-setsize.

managed state: Accessibility API state that is controlled by the user agent. Examples are focus and selection. Managed states often have corresponding CSS pseudo-classes (such as :focus and ::selection) to define style changes. In contrast, the states in this specification are typically controlled by the author and are called unmanaged states. Some managed states can be overridden by the web application author, such as aria-posinset and aria-setsize, but the auth

managed state: Accessibility API state that is controlled by the user agent. Examples are focus and selection. Managed states often have corresponding CSS pseudo-classes (such as :focus and ::selection) to define style changes. In contrast, the states in WAI-ARIA are typically controlled by the author and are called unmanaged states. Some managed states can be overridden by the web application author, such as aria-posinset and aria-setsize.

<cyns> Some managed states can be overridden by the web application author, such as aria-posinset and aria-setsize.

<cyns> Some managed states (such as aria-posinset and aria-setsize) can be overridden by the web application author.

issues http://www.w3.org/WAI/PF/Group/track/products/10

issue-458 and issue-459

text in UAIG: Note that aria-describedby may reference structured or interactive information where users would want to be able to navigate to different sections of content. User agents MAY provide a way for the user to navigate to structured information referenced by aria-describedby and assistive technology SHOULD provide such a method.

Cynthia comments at walkthrough: add URL example?

AS: maybe add the example of a user agent providing a link to the structured content referenced by aria-describedby
... how would the UA know when to do this

CS: UA could provide both a link to the structured information and put the text in the accessible description

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/this specification/WAI-ARIA/
Found Scribe: Andi
Inferring ScribeNick: Andi
Default Present: [Microsoft], Andi_Snow-Weaver
Present: [Microsoft] Andi_Snow-Weaver

WARNING: Fewer than 3 people found for Present list!

Got date from IRC log name: 10 Aug 2011
Guessing minutes URL: http://www.w3.org/2011/08/10-aapi-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.