Closed Bug 702978 Opened 13 years ago Closed 6 years ago

Table headers not read when arrowing through a grid row of the expense form

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: MarcoZ, Unassigned)

References

(Blocks 1 open bug, )

Details

STR:
1. Open http://oaa-accessibility.org/example/18/ with NVDA and Firefox.
2. Arrow down into the grid until you land on the "Date Row 1" cell.
3. NVDA will automatically switch to focus mode since this part of the grid is an application.
4. RightArrow through the cells.

Expected: NVDA should speak the column headers.
Actual: It will not speak the column headers. So the user does not know from just arrowing through the cells which information goes in what cell.
We expose headers via IAccessibleTableCell, it appears NVDA doesn't pick up them from this interface. Jamie?

Marco, what about JAWS?
there's another problem here, we don't expose row headers but they are specified by @headers attribute that points to th element having role="gridcell". We ignore accessible having different role than row header when we traverse through @headers attribute. 

Steve, should we expose anything as a header if it's pointed by @headers attribute?
(In reply to alexander surkov from comment #2)
> there's another problem here, we don't expose row headers but they are
> specified by @headers attribute that points to th element having
> role="gridcell". We ignore accessible having different role than row header
> when we traverse through @headers attribute. 
> 
> Steve, should we expose anything as a header if it's pointed by @headers
> attribute?

I would suggest yes, as that's what the @headers attribute is providing a reference(s) to.
(In reply to steve faulkner from comment #3)

> > Steve, should we expose anything as a header if it's pointed by @headers
> > attribute?
> 
> I would suggest yes, as that's what the @headers attribute is providing a
> reference(s) to.

I filed bug 704465 for this issue to keep it separate from this bug.
The dependent bug has been fixed, but the original example is hidden behind a 500 internal server error nowadays. Not sure what to do with this.
we probably have nothing to do with it, closing as incomplete
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.