You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fulfill the W3 Standard1.3.1 - Info and Relationships (Recommendation)
To support the use of the application by people with Hard of sight and Keyboard or Screen Reader users. And maximize compatibility with current and future user agents, including assistive technologies. Pull request #974
When the recording starts, there is a visual identification saying that the recording has started. A Screen Reader is not able to recognize that and read it. There is a possibility of using aria alert for that.
Expected behavior
The Screen Reader should be able to read back when the Recording has started.
Project file reproducing this issue (highly encouraged)
This is a issue with the UI, not of a specific Selenium scenario.
Environment
OS: Windows 10
Selenium IDE Version: 3.16.1
Browser: Google Chrome
Browser Version: 80.0.3987.116 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered:
ansarmie
changed the title
Support Accessibility regarding ability to Zoom in and Announcing that the Recording has started
Support Accessibility regarding Announcing that the Recording has started
Feb 28, 2020
馃悰 Bug Report
Fulfill the W3 Standard 1.3.1 - Info and Relationships (Recommendation)
To support the use of the application by people with Hard of sight and Keyboard or Screen Reader users. And maximize compatibility with current and future user agents, including assistive technologies. Pull request #974
More info here:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Project file reproducing this issue (highly encouraged)
This is a issue with the UI, not of a specific Selenium scenario.
Environment
OS: Windows 10
Selenium IDE Version: 3.16.1
Browser: Google Chrome
Browser Version: 80.0.3987.116 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: