Keyboard traps may also occur in one browser but not another, and is another test that should be performed in both browsers.Clearly identify where the problem does and does not occur (which browser, which controls) in AMP entries. Visual keyboard focus may be different in Firefox and IE due to various CSS properties, and so visible focus should be tested in both browsers.If a customer requires Level to test other, not-recommended versions, make sure the client understands and acknowledges the risks of doing so, and consider suggesting that they have Level test both so as to better identify the risk. The above are Level Access's recommendations, but the customer's needs take precedence.9 Notes of Differences Between Firefox and Chrome (on Android with TalkBack).We have not independently confirmed that this combination meets that level of support yet (April 2018). † Freedom Scientific's What's New in JAWS 2018 Screen Reading Software page claims that when JAWS 2018 is used with Edge on Windows 10 Creators update (version 1703) or later, it provides a level of support something like 'Supports with exceptions'. No longer recommended due to removal of Legacy Edge. Recommended (With FF 61, use JAWS 20 release or later) Only recommended for organizations that require IE.

Firefox vs safari 2018