608724 - Performing a flight search on lufthansa.com, results aren't readable with NVDA

Status: VERIFIED WORKSFORME

(Core :: Disability Access APIs, defect)

Description

[Marco Zehe (:MarcoZ)]

STR:
1. Go to http://www.lufthansa.com
2. As the start City, enter Hamburg
3. As the end city enter any city like London or Vienna.
4. Choose start date and end date as you like, leave all other settings as they are and click "search for flights".

Result: The next page that appears has the flight results in a table.
Expected: Screen readers should be able to pick this u.
Actual: NVDA does not see the flight reults at all. It only sees the top and bottom parts up to the "search" box and down at the bottom the footer.
JAWS, and other iSimpleDOM consuments, do see all of the content just fine.

This is NOT new in 4.0, but is also the case in 3.6. It is also not solved by the try-server build in bug 606125.

Comment 1

[alexander :surkov (:asurkov)]

It sounds it's bug 604560. The structure of section (div element that contains that table and other things) is:

section
  internal frame - invisible, offscreen
  internal frame - contains search results
  text node - whitespace I think
  form - invisible offscreen

chars count is 4, getText(0, 4) returns two embedded objects instead of tree, the first iframe has display: none and it doesn't has frame object I think therefore we don't take into account it in getText() calculation.

1) we need keep getCharsCount/getText in sync (to be safe)
2) we shouldn't expose this iframe at all

Comment 2

[alexander :surkov (:asurkov)]

Though I get slightly different results when NVDA is running, I don't get that invisible frame. The tree is:

section
  text leaf
  internal frame - contains search results
  form

characterCount is 2, getText(0, 2) is two embedded characters. IAccessibleHyperText nHyperlinks is 2, hyperLink(0) is internal frame containing search results. So we should be in good shape if NVDA uses hypertext interface to transform embedded character to accessible object

Comment 3

[alexander :surkov (:asurkov)]

(In reply to comment #2)
> So we should be in good shape if NVDA uses hypertext
> interface to transform embedded character to accessible object

if it's not timing issue when NVDA grabs some bad results and didn't get updated. Jamie, could you check this on your side?

Comment 4

[alexander :surkov (:asurkov)]

Jamie, ping on this.

Comment 5

[alexander :surkov (:asurkov)]

Some results observations. With the patch from bug 498015 I can navigate to the form ("from" text field inside a table) but I can't type anything, on pressing 'e' it says "there's no next edit field", if I press shift+e then it moves me "return on" text field, I can navigate to "from" text field and then 'e' pressing works. Definitely we get progress with bug 498015 (flight form can be traversed in some way) but we still have problems.

Comment 6

[Marco Zehe (:MarcoZ)]

I cannot reproduce the observations from comment #5 with the try-server build from bug 498015. For me, all of the above steps yield the expected results, and I can jump from edit field to edit field just fine.

Comment 7

[alexander :surkov (:asurkov)]

Marco, can you reproduce this on nightly?

Comment 8

[Marco Zehe (:MarcoZ)]

No, I no longer can reproduce this in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b11pre) Gecko/20110126 Firefox/4.0b11pre