Navigation Menu

Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Cannot access test results with screen-reader #3444

Closed
lukeis opened this issue Mar 3, 2016 · 3 comments
Closed

Cannot access test results with screen-reader #3444

lukeis opened this issue Mar 3, 2016 · 3 comments
Assignees
@lukeis
Labels
Priority-Medium Restrict-AddIssueComment-Commit Status-WorkingAsIntended Type-Defect

Comments

@lukeis
Copy link
Member

lukeis commented Mar 3, 2016

Originally reported on Google Code with ID 3444

Using Firefox 10.0.2 on Windows 7 with the JAWS 13 screen-reader.

I am completely blind and started using Selenium today. I notice that the UI is quite
accessible, likely because of issue 1266. I found that I could create a testcase, record
actions, add custom actions, and play back the test.

I was not able to review the results of the test. The console where the testing results
are displayed is not accessible to screen-readers.

Reported by zufeltej@yahoo.com on 2012-02-26 09:51:31
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

After further attempts I was able to access the list of commands executed and the results.
This issue can be closed.

Reported by zufeltej@yahoo.com on 2012-02-26 12:52:41

@lukeis lukeis self-assigned this Mar 3, 2016
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

Glad we're accessible to the blind!

Reported by dawagner on 2012-02-28 14:41:09

  • Status changed: WorkingAsIntended

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by luke.semerau on 2015-09-17 18:14:54

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 3, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lukeis lukeis

Labels
Priority-Medium Restrict-AddIssueComment-Commit Status-WorkingAsIntended Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukeis