Hi Geri
has Alistair mentioned we are looking into both the issues you reported but it's never quite as simple as it seems! :-(
As an example the first issue you mentioned re page change feedback I may be misunderstanding here but when a screen reader user tabs to and selects the next or previous buttons to navigate to the next or previous page the title of that next or previous page is read out. e.g. in your example navigating to page 2 reads The PROMPT Criteria and then to page 3 reads Summary. What doesn't happen at the moment is that the main content of that page is automatically given focus. Is that what your user expected to happen?
Your example is quite simple and only has 3 pages but say for instance a user was navigating a Xerte resource with 30+ pages. They may well tab to the next button, hit enter, hear the page title and then click enter to move to the next page and hear that page title and so on e.g. the focus stays on the navigation buttons so that they can do that. They could of course then choose to access one of the pages and use other keys like landmark or headings to then access the main content. e.g. the next and previous buttons are in the navigation landmark so upon hearing the page they want use whatever key jumps to the previous landmark which will typically be the main contents and then continuing reading from there. With NVDA that might mean Shift + D then down arrow etc.
So personally I'm not sure at the moment whether or not we should automatically move focus to the main content upon page change or not and we will seek expert advice on that. However if you wanted to see how that would work try the following:
1. Add an optional script icon to your LO
2. Add the following script:
function customPageChanged(pagetype) {
setTimeout(function(){
$('#pageContents').attr('tabIndex', 0).focus();
}, 50);
}See if that works for what your user expected or wanted to happen?
You should see that it automatically focusses and reads the next or previous pages contents but if you were wanting to use those buttons to cycle forward or back through the pages you now have to tab around again to get to the buttons to move to the next or previous page.
Re the tabbed navigator we've been testing that and are going to include a change in the next update or release that should resolve that.
I should also have mentioned previously that the next update/release also includes a hidden skip to main contents link. We've not had that previously in the XOT template because typically in the header there are only the two titles and nothing else. However we had a report of keyboard only users not being able to scroll a text only page in Chrome so added the hidden skip link to resolve that.
We'll reply again here when a new update or release to address these two issues is available.
HTH
Ron
