Simon: if a hierarchy is not marked up hierarchically in the HTML etc, but is only faked via CSS, the browser needs to create a simplified hierarchy...

17:19:16 [AllanJ]

SH: perhaps should be in 4.7 per GregL message.

17:19:22 [patrickhlauke]

AllanJ: are we happy with comment by Greg to move this to 4.7?

17:19:26 [AllanJ]

+1

17:19:29 [patrickhlauke]

+1

17:19:52 [AllanJ]

Bim and Kim +1

17:20:34 [patrickhlauke]

Bim: ...avoiding duplication and clearly separating the intents

17:20:58 [patrickhlauke]

Kim: happy with it as it basically says "you need to tag things properly"

17:21:25 [patrickhlauke]

can we cross-reference 3.1 to 4.7?

17:22:36 [jeanne]

Action: Jeanne to move 3.3.2 to 4.7 and add a resource to Implementing 3.3.1 that links to the new location for former 3.3.2

17:22:37 [trackbot]

Created ACTION-338 - Move 3.3.2 to 4.7 and add a resource to Implementing 3.3.1 that links to the new location for former 3.3.2 [on Jeanne Spellman - due 2010-04-08].

17:23:25 [AllanJ]

PL: what is browser mechanism to make this happen. some algorithm to create a breadcrumb

17:24:19 [AllanJ]

SH: yes. Artist, Album, track, song name. if it makes up its own structure, then it should share that implied structure.

17:25:15 [AllanJ]

PL: so the UA would build its own model, from its implied structure

17:26:17 [AllanJ]

...simple example. broken page with bad markup, it will repair and create its own markup.

17:26:34 [AllanJ]

it = browser

17:29:13 [AllanJ]

PL: this would only apply when there is no structure. Author coding vs browser inference. Author must follow WCAG

17:31:04 [AllanJ]

PL: authoring tool should help repair content during writing of the code. browser should not infer meaning. too many variables

17:35:58 [AllanJ]

Discussion of browser repair functions and author responsibilities

17:36:41 [AllanJ]

BE: quirks mode, strange characters on the screen.

17:38:20 [patrickhlauke]

Patrick: request some time to put this back to list and flesh out some more

17:40:06 [patrickhlauke]

Patrick: danger at the moment that wording of 3.3.2 (even if moved) is too general and may not be possible in all cases (not all the time UA can infer a structure of visually positioned/presented items beyond knowing internally that there's a form of visual canvas and there are things positioned here and there, overlap a bit, etc)

17:40:57 [patrickhlauke]

AllanJ: move 3.3.2 as it is in current draft to 4.7 and we then work on rewording in situ?

A low vision user needs control over what visual elements work best for highlighting. These include foreground colors, background colors, and visual borders.

17:45:03 [patrickhlauke]

Examples of Success Criterion 3.5.2:

17:45:03 [patrickhlauke]

A low vision wants to know where the text boxes are on a web form. The user wants to set a thick black border around all text boxes. The user agent provides a dialog box allowing the user to override any author settings.