Accessibility statement for Numbas exams¶
Numbas should be accessible to everyone who needs to or would like to use it.
Accessibility is an important consideration during the design and development process. We regularly test Numbas against a variety of accessibility requirements.
This statement was prepared in October 2019.
What’s covered by this statement¶
The Numbas runtime, as seen by students, using the default theme.
What’s not covered by this statement¶
This statement does not cover the Numbas editor or Numbas LTI tool provider.
This statement does not cover the text content of questions written using Numbas - the question author is responsible for ensuring it’s accessible.
Authors often embed content such as videos in Numbas questions. Apart from these, the Numbas interface doesn’t include any videos or sound effects.
Numbas supports custom interface themes and extensions to provide new functionality. Themes and extensions developed by the Numbas team are designed with the same accessibility considerations as the main Numbas system, but third-party themes and extensions are the responsibility of their authors.
Particular accessibility requirements we’ve designed around¶
Still usable when zoomed to 200%.
Colour is never used as the sole means of conveying information.
Ensure a colour contrast ratio of at least 7:1 (WCAG level AAA) throughout the interface.
The interface can be navigated entirely with the keyboard.
All content on the page is screen-readable, with sensible descriptions.
Very few animations; reduce motion as much as possible when browsers request it.
Layout is responsive and usable on screens with a variety of resolutions, including mobile devices.
Compatibility with browsers¶
We have tested Numbas on the following browsers. Any more recent versions should be assumed to work.
Chrome version 73 (released 2019-03-12).
Firefox version 81 (released 2020-09-22).
Edge version 79 (released 2020-01-15).
macOS Safari version 13 (released 2019-09-19).
iOS Safari (iPhone/iPad) version 13 (released 2019-09-19).
Android WebView version 73 (released 2019-03-12).
Accessibility guide¶
Interacting with a question¶
Each question is separated into three areas: introductory “question statement” text, one or more parts, and “Advice”, which is only shown when the answers to the parts have been revealed.
The statement text is at the top of the question, followed by a separator. There is typically no interactive content in the question statement.
Each question part begins with a level 4 header, then some prompt text, typically followed by an input control to enter your answer. Answer inputs can be text boxes, radio buttons, select boxes, or sometimes more complicated interfaces such as interactive diagrams. The input control for a part is labelled with the part it corresponds to, for example Answer to part a.
When the answer is a mathematical expression, a rendering of your expression in conventional mathematical notation is displayed after the input box. This rendering updates immediately whenever your answer changes.
If the answer you have entered is invalid, a box with an explanation of the error is shown next to the input box, as long as the input is focused. Screenreaders will read this explanation as soon as it appears.
After the answers to a question have been revealed, there is often a box showing the expected answer after each input.
After the prompt text and input controls is a button labelled Submit part. Clicking this button causes your answer to be marked. You may be shown some immediate feedback after the Submit part button, and your score for the part.
You may submit answers as many times as you like.
Some parts are gap-fills, with one or more input controls interspersed with the text. You can submit the part after filling on only one input, but normally you must enter an answer in every input in order to complete the part.
At the end of the question is a navigation area, containing buttons to submit all the parts in the question, your total score for the question, a button labelled Try another question like this one, and a button labelled Reveal answers. Some of these elements may not be shown, depending on the exam’s settings.
The Try another question like this one first shows a confirmation dialog, then removes the current question and displays a similar one, starting from scratch.
The Reveal answers button also shows a confirmation dialog, then reveals all the expected answers to the parts, and the Advice section. You may not change your answers to any of the parts after revealing answers.
The Advice section usually contains a worked solution to the whole question.
How to adapt Numbas to your needs¶
Change the colours of text and the page background¶
Click the Display options button to change the colour of text and the page’s background.
Your browser’s colour picker is used. In most browsers, you can pick a colour by clicking on a colour wheel, or by typing a colour value in hexadecimal or RGB format.
Changing the size of text¶
Use your browser’s zoom setting to change the size of text and interface elements.
This is often under ‘Zoom’ in the browser’s settings menu; you can also zoom in or out by pressing Ctrl + or Ctrl - on the keyboard (Cmd + or Cmd - on Macs).
Mobile users can use a pinch gesture to zoom in and out.
Enlarging images¶
You can click on an image to enlarge it to nearly fill the screen. Click outside the image or press the Escape key to return to the main interface.
Printing a Numbas exam¶
The default Numbas theme contains a print stylesheet which your browser can use to produce a printed version of an exam. After starting a Numbas exam, use your browser’s Print feature.
Using a screenreader¶
A screenreader such as NVDA, JAWS or Orca will read all of the content in a Numbas exam. We’ve tested Numbas with NVDA and Orca.
When you submit an answer, the score and any feedback messages will be read out.
Mathematical notation is made accessible to a screenreader by the MathJax accessibility extensions.
Who to contact if you have problems or want to give feedback¶
Students should contact their instructor, in the first instance.
Instructors and authors of Numbas content can contact us through any of the following:
Email numbas@ncl.ac.uk.
File an issue on the Numbas GitHub repository.
Post on the numbas-users group.