Accessible Document Navigation Using AT-SPI
Please use this page to suggest improvements to and prose for the unpopulated and underpopulated sections of Accessible Document Navigation Using AT-SPI.
Comments should also be posted [2] to the publicly archived accessibility-atspi emailing list [3]
For Reference:
Terminology
Common Assumptions
Use Case: Navigate or Collect All Accessible Content by Unit [5]
Scenario 1: Navigate to the next, previous, current, first, or last item in the document [6]
Scenario 2: Navigate to the next, previous, current, first, or last interactive and enabled element in the document [7]
Scenario 3: Navigate to the next, previous, current, first, or last hyperlink in the document [8]
Scenario 4: Navigate to the next, previous, current, first, or last enabled form control in the document [9]
Scenario 5: Collect all elements with a shortcut key in the document [10]
Scenario 6: Navigate to the next, previous, current, first, or last frame in the document [11]
Scenario 7: Navigate to the next, previous, current, first, or last section identified by a heading in the document [12]
Scenario 8: Navigate to the next, previous, current, first, or last data table in the document [13]
Scenario 9: Navigate to the next, previous, current, first, or last embedded object or graphic in the document [14]
Scenario 10: Navigate table cells by moving across rows and up and down columns within a grid or table [15]
Scenario 11: Navigate to next, previous, current, first, last, up or down in a tree-style set of items or controls [16]
Use Case: Where Am I? [17]
Scenario 1: Ask where your point of regard is within a document and within containers in the document [18]
Use Case: Document Summary [19]
Scenario 1: Ask for a summary of the types of elements and containers in the document [20]
AT-SPI Interfaces to Collect Element Characteristics for AT Rendering [21]
Desireable Roles for Document Objects and Navigation