Accessible Options for Web Security Experience, Section 6.5

While i'm not sure why a table is used to contain the following information, one thing is for sure -- it provides a morass of conflicting explicit association patterns, as the cell containing the link or links needs to be contextualized along the x/y axis, and each link must be distinguished from the other, as there are numerous links that use identical hyperlink text to point to different targets. This means that there is a collision between the contextual information provided for navigating the table as a table, and contextualizing each link, so as to provide contextualizing text for the terse repetitive hyperlink text. Only one explicit association pattern is available to most AT users, which makes it quite difficult to determine not only where one is in the table, but the target at which each hyperlink points -- two essential pieces of information for anyone processing the TABLE non-visually or through an extremely restricted viewport, such as the case of an individual using screen magnification. A summary, scope, and headers/id bindings have been defined for the TABLE, which would also benefit from a CAPTION.

Note, as well, that although HTMLTidy validates this page as XHTML 1.0 Strict, it cannot be validated through the W3C MarkUp Validator, due to the repetition of id values in the comparative examples.

6.5 Scenarios

	Providing	Believing	Installing
Identified source, Identified destination	any any	any any	any
Identified source, Unidentified destination	any	any	any any
Unidentified source, Identified destination	any, any smartphone		any any
Unidentified source, Unidentified destination	any	any any any any	any

6.5 Scenarios

Identified source, Identified destination: Providing: Use Case 1 (any), Use Case 2 (any); Believing: Use Case 1 (any), Use Case 2 (any); Installing: Use Case 1 (any)
Identified source, Unidentified destination: Providing: Use Case 1 (any); Believing: Use Case 1 (any); Installing: Use Case 1 (any) Use Case 2 (any)
Unidentified source, Identified destination: Providing: Use Case 1 (any), Use Case 2 (any) Use Case 3 (smartphone); Believing: no use case; Installing: Use Case 1 (any), Use Case 2 (any)
Unidentified source, Unidentified destination: Providing: Use Case 1 (any), Use Case 2 (any); Believing: Use Case 1 (any), Use Case 2 (any), Use Case (any), Use Case 4 (any); Installing: Use Case 1 (any)