Picture of Sam Cook
Adapt Framework version 2.0 testing update
by Sam Cook - Thursday, 2 July 2015, 4:05 PM

The testing team at Kineo are now finalising their second round of testing of the Adapt Framework v2.0, prior to its release into the open source community. A test package was created with a representative layout and the full set of components included in this new release. Please note that the scope of the test did not cover an exhaustive variation of all core component configurations.


As many of the issues we reported from our first round of testing in March had been addressed, most of the bugs we found were fairly minor or content related, rather than any significant functional issues. 


We conducted cross compatibility testing across the agreed tech spec, and also carried out screen reader testing using both JAWS on desktop and the iOS Voiceover app on iPad. 


Here’s a breakdown of the type of issues we found:

  • Most were contextual, issues around styling the various elements to fit the art direction and small errors around layout, overruns and how things respond when scaling which have to be set up on a case-by-case basis. However there were far less of the frequent, endemic issues that we have seen in older versions of the Adapt framework.
  • There were issues that occurred due to the idiosyncrasies of each mobile OS/device.
    • Windows phone was the most problematic platform, not only because of the pop-up blocker in Mobile IE11 which cannot be disabled, but because we have not had to test on this OS as a project requirement, so we have not had a chance to account for its idiosyncrasies as we have for iOS and Android.
  • As we would expect there was a larger proportion of IE8 specific issues than any other browser due to how outdated it is.
  • We also used this as an opportunity to add/modify aria screen reader text for generic components.
  • Although approximately 25 accessibility issues have been entered into JIRA, the majority of them are of a minor to normal level and have to do with general navigational issues, inaccessible functionalities and unclear/incorrect alt text or completion states. These are mostly issues that affect the user experience rather than their ability to effectively use the course with accessibility software.

-Sam Cook, Head of Testing, Learning Content Team, Kineo