I got the Adapt sample courses tested on Windows XP and 7 on IE, FF and Chrome and observed the following.
Any suggestions, why this is happening?
Hey Jitendra,
Accessibility had to take a back seat during our first release as we had some tight deadlines to hit. However this is something we've been looking at and know that there is some work to be done here. We're hoping to have the keyboard tabbing and buttons working in the upcoming release.
Thanks,
Daryl
Thanks for the quick response, Daryl. Do you have any tentative dates of upcoming releases?
Hey Jitendra,
We have said this release will come in May. The reason for the slightly longer delay is due to some functionality/features that really enhance Adapt's core. We're also calling this a bigger release because there are some breaking changes. All of this will be put on the community site when the release is ready.
The community testing came back and all those bugs have been fixed however if you'd like to keep an overview of the progress check out the milestone tasks here.
We're looking to add this into Jira too as we've just moved over to it. But for now the Github milestones are the best place to see the progress.
Thanks,
Daryl
Hey Daryl, thanks for sharing the list of issues, gives a good insight.
We are currently building some plugins based on the current available source of Adapt. As you said you are enhancing Adapt's core does that mean the plugins we are currently developing will lose their compatibility with the new release?
Hey Jitendra,
A lot of the plugins architecture stays the same. The main changes are in the themes and templates. In terms of JSON updates there are a few things to watch out for. For example all objects should have an underscore - graphic: {} should be _graphic:{}
If you're building something that has a popup then you'll be able to use some of the new core features that help with popups. Also Drawer can be used to house plugins. More on this when we do a release.
Thanks,
Daryl