Open Bug 526311 Opened 15 years ago Updated 2 years ago

[faceted search] Make the faceted search results window more accessible, part 2.

Categories

(Thunderbird :: Search, defect)

defect

Tracking

(blocking-thunderbird3.1 -)

Tracking Status
blocking-thunderbird3.1 --- -

People

(Reporter: bwinton, Unassigned)

References

Details

(Keywords: access)

From bug 516680, comment #3:
A second phase would be to add what I'd call geometric keyboard nav, so that
people can navigate between the two columns, for example -- it's hard to do
that in a way that works across all keyboard layouts.  I'm not sure whether
it's safe to assume that locales imply keyboard layouts.  I'm sure that using
the up/down/left/right arrows will be controversial.

From bug 516680, comment #19:
Then all we have to do is deal with the big blue boxy elephant in the room. How
does someone who doesn't use a mouse limit their results by date? Does the
timeline, which I can use to limit by some random month, or by a particular
month if my results have matches in at least every other month of a year, so I
don't have to guess what month a totally unlabelled bar "um, maybe four or five
widths from the start of the year" represents, even *exist*, as something
completely unusable, to Marco?

From bug 516680, comment #22:
Roger on all that.  I'll do a next rev after string freeze.  As to the timeline
localization, I suspect what I'd like is to hear from MarcoZ what it's like to
deal w/ Google's timeline:
http://www.google.ca/search?q=accessibility&hl=en&sa=G&tbo=1&output=search&tbs=tl:1
I suspect we won't be able to get to full a11y of the timeline for TB3, but
Google's timeline seems to provide a possible path.

Finally, from bug 516680, comment #43:
The button that opens the graph showing the search results overtime is still not labelled.
Flags: blocking-thunderbird3.1?
Component: Mail Window Front End → Search
QA Contact: front-end → search
Summary: Make the gloda pane more accessible, part 2. → [faceted search] Make the faceted search results window more accessible, part 2.
Bryan/Blake, do you think we should block for this? Do we have an WIP on this, for at least some limited accessibility?
blocking-thunderbird3.1: --- → ?
Flags: blocking-thunderbird3.1?
We don't have an WIP on this, so I would lean towards "no", but I could bug MarcoZ (and/or DavidB) tomorrow about it, to see what sort of stuff we could add in the amount of time we have.
I'm going to assert that if this were the last bug standing, we wouldn't hold the e release for it, though it would be great to get.  Marking blocking-, wanted+.
blocking-thunderbird3.1: ? → -
Flags: wanted-thunderbird+
Depends on: 516680
Keywords: access
(In reply to comment #2)
> We don't have an WIP on this, so I would lean towards "no", but I could bug
> MarcoZ (and/or DavidB) tomorrow about it, to see what sort of stuff we could
> add in the amount of time we have.

Blake, do we have results of this, and bugs to go with them?
No, we dont…

Mr. Bolter, do you have any people who might be able to take this on?

Thanks,
Blake.

Is there another bug for this? (I seem to remember discussing it somewhere else)

Flags: needinfo?(alessandro)
Target Milestone: Thunderbird 3.1a1 → ---

I'm only aware of this: bug 929845
Not sure if totally related.

Flags: needinfo?(alessandro)
See Also: → 929845
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.