Exercise steps should be used sparingly and thought should be given to if the type of activity already exists on FutureLearn in the form of another step.
We aim for all content presented on futurelearn.com to comply with WCAG 2.0 AA: http://about.futurelearn.com/accessibility-testing/
We ask partners to submit the code for any exercise step content in advance of the course starting for technical QA by the FutureLearn development team. Please allow at least 30 days before the course start for this QA.
Content must be served over HTTPS. We enforce this in Course Creator.
Content must be able to be served in an iframe hosted on futurelearn.com with no framebusting.
Content will be forced to be full width and full height, with a 75px FutureLearn header.
Your content will be forced to fit the full width and height of the device, with no scrolling. Content will not flow outside of the screen size by default. If your content is required to scroll we recommend using a third party library or implementing it in your own CSS.
Exercises should be available in line with our browser support matrix where possible: http://about.futurelearn.com/browser-support/. Where content cannot be provided to meet the FutureLearn browser matrix, this should be detected and a message provided to users explaining how they can access the content.
|Orientation||Portrait (standard)||Landscape (standard)||Portrait (inc. FutureLearn header)||Landscape (inc. FutureLearn header)|
FutureLearn support and test that content is usable on mobile and tablets down to the above resolution, including testing in both orientations, and in switching between orientations.
Hit areas & behaviours should not be able to be confused with native UI elements. E.g., be careful when implementing swiping as on iOS it is used as the back button in the default browser, and be careful adding elements to the bottom of the screen on iOS where they may trigger the Control Center.
The recommended range of target for hit areas on mobile is 7-10mm. (See the BBC mobile accessibility guidelines for touch targets). Though these are for mobile app development the principles are the same given the smaller screen size.
Content on desktop devices using modern browsers should be keyboard accessible, navigable and usable without a mouse. (http://www.w3.org/TR/WCAG20/#keyboard-operation)
Users should be able to access and navigate around the content using the tab, arrow and enter keys.
Focussed elements should have a clear focus indication.
Text size should be a minimum of 14px for standard text, and 18px for large text, regardless of physical screen size.
Text should have a minimum of 4.5:1 contrast ratio for standard text, and 3:1 for large text.
Graceful degradation / fallback
Where content cannot be provided to meet the accessibility guidelines detailed above, text-based alternatives should also be provided (http://www.w3.org/TR/WCAG20/#text-equiv-all).