Comment 3 for bug 271487

It seems that the vte.Terminal.ref_accessible method is the way to get the atk object with python. However, it returns a atk.NoOpObject which means that there are method collisions (atk.Selection.add_selection shadows atk.Text.add_selection, for example). And, in my limited tests, all of the methods are broken (get_text always returns None, get_character_at_offset always returns \0, get_bounded_ranges dies with the cryptic "error return without exception set"). So I'm not sure if the accessibility interface is incomplete in VTE, or the python bindings are botched, or I'm using it incorrectly--but something is screwy with it (the ruby bindings didn't work either--they threw Vte-CRITICALs when I tried to call any method on the atk object returned from ref_accessible--same thing when I manually instantiated a Vte::TerminalAccessible).