New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 626978 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Chrome does not expose framesets to VOiceOver

Project Member Reported by vtsaran@chromium.org, Jul 11 2016

Issue description

Version: latest Canary build
OS: Mac OS X (10.11.5)

What steps will reproduce the problem?
(1) Launch VoiceOver screen reader with CMD+F5.
(2) Open Chrome and go to http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_frame_cols
(3) At the bottom of the page there is a live example of frameset, however, VoiceOver does not see it at all. By comparison running the same example in Safari exposes this frameset just fine.

What is the expected output?
VoiceOver should be able to see the frameset.

What do you see instead?
VoiceOver does not see anything at all.
I realize that HTML5 no longer supports frame sets, however, we need to support these for backward compatibility. For example, I ran across this bug while viewing an HTML documentation for a hardware device I am using.


Please use labels and text to provide additional information.
 

Comment 1 by shrike@chromium.org, Jul 12 2016

Status: Assigned (was: Untriaged)

Comment 2 by nek...@chromium.org, Nov 14 2016

Cc: nek...@chromium.org ellyjo...@chromium.org
Owner: ----
Status: Available (was: Assigned)
Labels: NewComponent-Accessibility-Compatibility
Labels: NewComponent-Accessibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 23 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
WontFixing as this issue has been open for almost two years. If this should be fixed, feel free to reopen.

Sign in to add a comment