New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PROBLEMS WITH DIALOG BOXES ON WEB PAGES IN FIREFOX #1418
Comments
Comment 1 by KevanGC on 2011-03-27 00:00 Here's a link where you guys can e-mail the Facebook Accessibility team if you want. http://www.facebook.com/#!/help/contact.php?show_form=accessibility |
Comment 2 by jteh on 2011-03-27 00:06 The reason it behaves differently in IE is that we don't support ARIA dialogs properly in IE and instead treat them as documents, which is actually a bug in NVDA that happens to work for the better in this case. Nevertheless, this is incorrect behaviour. |
Comment 3 by KevanGC on 2011-03-27 00:28 |
Comment 4 by jteh on 2011-03-27 00:54 |
I was not able to reproduce this using the STR provided in #1418 (comment), step 4, as I believe the events page has changed since this was created. @jcsteh, does NVDA treat ARIA dialogs any differently since this was created? |
Before #7433 (which has only happened in the last couple of weeks), dialogs in all browsers (except Edge) did not use browse mode. Due to changes in ARIA 1.1 and the prevalence of web dialogs relying on users being able to browse document content (including Facebook), PR #7433 (issue #4493) changes this so that browse mode is used for dialogs. Closing as a duplicate of #4493. |
Reported by dharvey on 2011-03-18 11:57
Hi,
Has anyone noticed when using some websites EG Facebook when interacting with the site IE replying to an event or message, or sending a friend request an inaccessible dialog box pops up when using Firefox 3.6.15? IE isn't affected by this issue.
STR using FB.
Try the same instructions in IE, notice there's no change? You can still review the page as normal and jump to elements IE Radio button, form field ETC, but using FF has the dialog problem, and has domedone resets to see if it was my browser that was causing it.
The text was updated successfully, but these errors were encountered: