Closed Bug 456820 Opened 16 years ago Closed 16 years ago

messagereader: ensure accessibility

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: davida, Assigned: MarcoZ)

References

Details

(Keywords: access, helpwanted, Whiteboard: [need info MarcoZ])

From MarcoZ in bug 449691: - Make each header focusable (tabstop). - Make each address a link or something similar so actions on it can be performed easily and it can be focused. - Make the message body easily discoverable. many screen readers offer ways to navigate to headings. So if it is made sure that the subject always preceeds the message body in the markup, make it a heading 1 from a markup pov, so screen reader users can quickly jump to it, skipping all header information if they're not interested in them right now. - Make other parts also be exposed as headings, for example the Attachments section.
It would be great to get this for Tb3. In order to understand how to prioritize it, I'd like to know how the new message reader compares to what we shipped with tb2 from an accessibility standpoint. A little better? Similar? A lot worse? Adding Marco in the hopes that he can render an opinion here...
Flags: wanted-thunderbird3+
Flags: blocking-thunderbird3?
Keywords: access, helpwanted
Whiteboard: [need info MarcoZ]
Assigning to marco so that he sees it.
Assignee: nobody → marco.zehe
(In reply to comment #1) > It would be great to get this for Tb3. In order to understand how to > prioritize it, I'd like to know how the new message reader compares to what we > shipped with tb2 from an accessibility standpoint. A little better? Similar? > A lot worse? Adding Marco in the hopes that he can render an opinion here... Well I believe this bug somewhat obsoleted itself. :-) The original comment that David quotes in comment #0 assumed that the whole message reading pane would be turned into HTML (or at least that's what I gathered from the discussion in bug 449691). Since that hasn't happened, and since the fix for bug 449560 landed, things are indeed a big improvement over Thunderbird 2 already. An issue that is still present is bug 469204. And also the keyboard inconsistencies with the reply button space bar pressing also causing the message to scroll/advance should be looked at.
OK, marking RESOLVED. If you feel bug 469204 or other bugs should block, please nominate them separately. Thanks!
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Flags: blocking-thunderbird3?
You need to log in before you can comment on or make changes to this bug.