Adapt Learning Community: Adapt framework v2

Hi,

The work on implementing WAI AA accessibility into Adapt is nearly complete. We have uploaded a test package for the core team and community to review the functionality. This is now live in our pre-release testing area, which is open to everyone.

There are some very 'light' notes on how to test, too. We will elaborate on the documentation ahead of the release.

If you have a moment, please have a look. It would be great to have your feedback both from a functionality and a technical perspective.

Many thanks and happy Christmas to everyone in the community!

Sven

For any interested more technical people, you can check out the exact changes in the pull request on GitHub. Any comments and feedback are welcomed (and encouraged).

Bugs should ideally be reported on the repo for the accessibility library itself rather than the PR.

Show parent | Reply

Have had a test of this on Mac OS X using VoiceOver, and it works really well. Some of the things I particularly liked:

All tabbing works really well, and the tab order seemed logical and consistent (something which I definitely don't take for granted).
Descriptions of each component as first tab item, read out prior to interacting with it.
"Popup opened" message in feedback popups etc.
Component progress as last item in each component.

I have a few questions so far:

Do we have any way of indicating the beginning/end of pages/articles/blocks? I'd find this particularly useful at the end of pages, as I found myself expecting to be taken to another component, but instead being jumped back up to the top, as I'd reached the end (I guess this is something that may prove to be a non-issue in practical implementations, as there is likely to be some component/final instruction).
There are a few areas which I would argue are missing some detail (i.e. progress on menu items and page-level progress items). Is this something which is taken care of in the relevant component/extension, and would it be a fairly trivial task to add to if so needed?

There are also a few more technical issues I came across, which I'll add to the library repository, as I don't think they really have a place here.

Going to have a go on mobile shortly, but just like to say how impressive everything is looking so far.

Show parent | Reply

Hej Tom,

1. The end of page notification is one Kirsty and I have not yet thought about. As you've pointed out, the wrapping behaviour works nicely, so that instead of tabbing off the end of the page you're returned to the menu.

It'd be extremely simple to add an EOP notification. Something like:

<span tabindex="0" class="aria-label">You have reached the end of the page</span>

Added to the end of the page.hbs or in the pageView. This would provide an transparent+tabbable text region that would be read by the screen reader but invisible to the eye.

2. The demo is not 'refined' finished. I had to concentrate mostly on the core and the core components. So plp and menu progress are things Kirsty and I have put into courses already but that I didn't have time to role into the text package. But the same principle applies, it's very easy to make things accessible with the library and some standard rules.

Thanks for the ideas. Keep them coming!

Show parent | Reply

Accessibility testing ipad.pdf

Accessibility testing chrome.pdf

Hi everybody,

here are my testing notes for Chrome on PC and Safari on iPad iOS 8.1

Petra

Show parent | Reply