Browser Support Policy
How we test and validate browsers
Blackboard's approach to determining browser testing and validation is driven by two main considerations:
- We want to test and validate the latest browsers, especially where browser auto-updates drive rapid end user upgrades.
- We want to test and validate an appropriately broad set of browsers that are being used among our clients.
When a browser is listed as tested and validated, Blackboard is committed to supporting client usage in two main ways:
- Before a Blackboard Learn release, by testing the available browser and operating system combinations to prevent any browser issues from being released.
- After a Blackboard Learn release, by rapidly addressing client issues by:
- Accepting Support cases on the platform technology, assisting with resolution, and escalating the issues for resolution, regardless of the browser in use.
- Working to resolve any browser issues in product releases as with any other type of issue.
Blackboard tests and validates four primary browsers for Blackboard Learn releases.
This includes browsers that follow a traditional software update path with periodic releases of new versions as Generally Available, typically tied to a particular operating system (OS):
- Safari from Apple
Certain Internet Explorer configuration options can make it difficult to use some features of Blackboard Learn. To learn more, see the Internet Explorer Security Zones and Compatibility View topic in this section.
This also includes three browsers that follow a cross-operating system, channel-based rapid software update path:
- Edge from Microsoft
- Firefox from Mozilla
- Chrome from Google
With these browsers, Blackboard tests their latest "stable" release channel at the time of testing, which is the channel that gets the most testing by the browser vendors themselves before being released to users.
In addition, Blackboard tests and validates Firefox's specialized Extended Support Release (ESR) channel, which is a subset of their stable channel designed for enterprise-wide deployment. To learn more, see Firefox's Extended Support Release page.
If you need information about the specific versions of each browser that were tested and validated when a particular version of Blackboard Learn was released, see the Release Notes for that released.
Blackboard's approach to rendering in browsers
Our universal design approach focuses on interoperability. This means that wherever possible we do not write code specific to a certain browser or we use the minimum amount of encapsulation to handle variations among the browsers.
- The rendering layer of Blackboard Learn interacts with the rendering engine of your browser, which is the part that draws the web pages in the main part of the browser window.
- WebKit, which powers Safari, Chrome, and Opera
- Blink, a version of WebKit that powers the most recent versions of Chrome
- Trident, which powers Internet Explorer
- Gecko, which powers Firefox
This design approach to the rendering layer of Blackboard Learn allows us to be confident that new versions of browsers, when released, will continue to work with current versions of Blackboard Learn.
Blackboard's approach to browser testing
To verify this confidence with each new release, Blackboard executes our browser compatibility test suite against newly released browser versions on multiple OS combinations to ensure function prior to releasing a given version. This testing leverages the full set of automation and manual testing strategies available to ensure confidence in testing.
Newer browser versions
Because of the increased frequency of new browser version released by some vendors, Blackboard's policy is to support all new browser versions released to the market as Generally Available or by supported release channels, even if the browser is released after testing has concluded for the release. We address any critical browser issues found by clients in the field against a provisionally supported browser as a top priority. We execute frequent test cycles against new browsers to ensure the system continues to perform as expected and will update client facing supported browser documentation appropriately.
Just as we recommend keeping up with the latest version of Blackboard Learn for the best experience, the browser vendors make the same recommendation about their software. Some older versions of browsers from some vendors may have rendering issues with newer versions of Blackboard Learn, and some newer browser versions may have rendering issues with older versions of Blackboard Learn.
Blackboard still accepts client issues for these browsers reported to Support and will attempt to replicate the issue on a fully supported browser. If it cannot replicate the issue, Blackboard will recommend that the client move to a browser version fully supported by Blackboard. In some cases, an additional recommendation might be to update to a more modern version of Blackboard Learn.
Additional acceptance of persistent cookies or third-party cookies may be required for some features in Blackboard Learn 9.1 to function correctly, including WebDAV access to course files or content collection files.
Blackboard also provides a Building Block to allow users to acknowledge a cookie disclosure statement when logging in to Blackboard Learn, as is required in some places. To learn more about this Building Block, see the Security Management - Cookie Disclosure topic.
Java and other browser plugins
A handful of Blackboard Learn features require particular additional software to be installed. Without these, the features themselves do not function. Users may be prompted to install the additional software when accessing these features, or depending on individual browser security settings, users may need to acknowledge a browser message allowing the plugin to run on their system.
If you need information about the specific features that require browser plugins for a particular release of Blackboard Learn or version information for the plugins themselves, see the Release Notes for that release.
Blackboard Learn can be used to serve media content or other types of specialized content that requires a browser plugin such as Java, Flash Player, Apple QuickTime, or other plugins to render the content. In these scenarios, the version of the plugin and the browsers that are compatible with the plugin, as well as installation and configuration instructions for the plugin, are determined by the nature of the content and will vary.
Assistive software and accessibility
For the best Blackboard Learn experience with your screen reader, use ChromeTM and Jaws on a Windows® system. On a Mac® use Safari® and VoiceOver.
Blackboard strives to make all its products as accessible as possible. To learn more about assistive technologies, visit http://access.blackboard.com