Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368877

Summary:	Status Messages cannot be read by screen reader
Product:	[ECD] Orion	Reporter:	Max Li <maxli>
Component:	Client	Assignee:	Susan McCourt <susan>
Status:	RESOLVED FIXED	QA Contact:	Carolyn MacLeod <carolynmacleod4>
Severity:	normal
Priority:	P3	CC:	maxli
Version:	0.4	Keywords:	accessibility
Target Milestone:	0.4 RC1
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:
Bug Blocks:	365361

Description Max Li

2012-01-17 15:30:12 EST

The status messages on the top left of the screen (e.g. when editing a site, the Save and Start/Stop links generate these sort of messages) are relatively inaccessible. The screen reader cannot read them (or perhaps they are very far away in the tab order) and they disappear quickly so that it is hard to know that the messages were even there.

Comment 1 Max Li

2012-01-19 10:38:04 EST

I have fixed this bug in the following repository in the accessibility branch.
https://github.com/max-li/orion.client.git

Comment 2 Susan McCourt

2012-01-24 11:26:08 EST

I can look at this but the link 404s

Comment 3 Max Li

2012-01-24 11:32:28 EST

This is the actual commit.

https://github.com/max-li/orion.client/commit/37937d27dcab9963601cfdc05ac81794ff4b0e98

Comment 4 Susan McCourt

2012-01-24 19:39:46 EST

I'm not sure how to test that the problem is fixed.
Note the status messages have moved to the bottom (and probably will move again in the next couple of days).  So I merged the commit by hand and tried the change.  However I can't test that it works because I can't tab out of the editor.

I suggest we hold off on fixing this one until we get a stable place for the status message, and then you can submit a fix that is up to date with the latest.

Comment 5 Susan McCourt

2012-02-07 11:22:59 EST

pushed a fix.
Thanks, Max, and sorry it took so long.

Note the notifications area is now a div, not a span.
I assumed that the original fix would still work based on our previous discussions.

Max, can you confirm that this is fixed?

Comment 6 Max Li

2012-02-07 13:10:18 EST

This has been fixed.