Yes, but only if it’s populated appropriately by the populating university. The table overleaf provides a summary of each of the Success Criteria in WCAG 2.1 along with our assessment of whether this is something that Vepple should meet as standard, something our university partners are exclusively responsible for meeting or whether it requires input from both parties.
| Principle | Guideline | # | Item | Level | 1 line summary (may not give the whole story!) |
Responsibility |
|
1. Perceivable
|
1.1 Text Alternatives Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. |
1.1.1 | Non-text Content | A | Provide text alternatives for non-text content | University |
|
1.2 Time-based Media
Provide alternatives for time-based media. |
1.2.1 | Audio-only and Video-only (Prerecorded) | A | Provide an alternative to video-only and audio-only content. (note we seldom do audio only/silent video) | University | |
| 1.2.2 | Captions (Prerecorded) | A | Provide captions for videos with audio | University | ||
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Video with audio has a supporting transcript or audio description | University | ||
| 1.2.4 | Captions (Live) | AA | Live videos have captions | University | ||
| 1.2.5 | Audio Description (Prerecorded) | AA | Users have access to audio description for video content | University | ||
|
1.3 Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure. |
1.3.1 | Info and Relationship | A | Logical structure | Vepple | |
| 1.3.2 | Meaningful Sequence | A | Present content in a meaningful order | University | ||
| 1.3.3 | Sensory Characteristics | A | Use more than one sense for instructions | Both | ||
| 1.3.4 | Orientation | AA | Content can be display in portrait and landscape orientation | Vepple | ||
| 1.3.5 | Identify Input Purpose | AA | Each input field must be able to be determined programmatically, a user should be able for example to autofill inputs | Vepple | ||
|
1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background. |
1.4.1 | Use of Color | A | Don’t use presentation that relies solely on colour | Both | |
| 1.4.2 | Audio Control | A | Don’t play audio automatically | Both | ||
| 1.4.3 | Contrast (Minimum) | AA | Contrast ratio between text and background is at least 4.5:1 for normal copy and 3:1 for 18pt+ or 14pt bold. | University | ||
| 1.4.4 | Resize text | AA | Text can be resized to 200% without loss of content or function | Vepple | ||
| 1.4.5 | Images of Text | AA | Don’t use images of text | University | ||
| 1.4.10 | Reflow | AA | User must be able to browse a website using a 320 pixel wide screen without having to scroll horizontally (There are some exceptions) | Vepple | ||
| 1.4.11 | Non-text Contrast | AA | Extend color contrast of at least 3:1 to non-text content such as infographics, diagrams, states, etc. | University | ||
| 1.4.12 | Text Spacing | AA | Changing text style properties shouldn’t break the page (line height, spacing after paragraph, letter spacing, word spacing) | Vepple | ||
| 1.4.13 | Content on Hover or Focus | AA | Elements that are being shown on focus or hover (skip navigation, tooltip) should be dismissible(Esc), hoverable, persistent | Vepple | ||
|
2.1 Keyboard Accessible Make all functionality available from a keyboard |
2.1.1 | Keyboard | A | Accessible by keyboard only | Vepple | |
| 2.1.2 | No Keyboard Trap | A | Don’t trap keyboard users | Vepple | ||
| 2.1.4 | Character Key Shortcuts | A | If using single letter keyboard shortcut, the shortcut should be able to be turn off, or remap, or active only on focus | Vepple | ||
|
2.2 Enough Time Provide users enough time to read and use content. |
2.2.1 | Timing Adjustable | A | Time limits have user controls | Vepple | |
| 2.2.2 | Pause, Stop, Hide | A | Provide user controls for moving content | Vepple | ||
|
2.3 Seizures and Physical Reactions Do not design content in a way that is known to cause seizures or physical reactions. |
2.3.1 | Three Flashes or Below Threshold | A | No content flashes more than three times per second | Both | |
|
2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are. |
2.4.1 | Bypass Blocks | A | Provide a ‘Skip to Content’ link | Vepple | |
| 2.4.2 | Page Title | A | Use helpful and clear page titles | University | ||
| 2.4.3 | Focus Order | A | Logical order | Vepple | ||
| 2.4.4 | Link Purpose (In Context) | A | Every link’s purpose is clear from its context | Both | ||
| 2.4.5 | Multiple Ways | AA | Offer several ways to find pages | Vepple | ||
| 2.4.6 |
Headings and Labels |
AA | Use clear headings and labels | University | ||
| 2.4.7 | Focus Visible | AA | Ensure keyboard focus is visible and clear | Vepple | ||
|
2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard. |
2.5.1 | Pointer Gestures | A | Complex gesture (Pinch, zooming, swiping) should have a simpler gesture alternative (Tap, double taps, long press) | Vepple | |
| 2.5.2 | Pointer Cancellation | A | When using single pointer events, one of the following should be true, No Down-Event, Abort or Undo, Up Reversal, Essential | Vepple | ||
| 2.5.3 | Label in Name | A | Text in buttons or label should be readable by assistant technologies and can be used with Text-to-speech | Vepple | ||
| 2.5.4 | Motion Actuation | A | Functionalities trigger by moving the device should have a fallback without (Eg some apps use shake to undo) | Vepple | ||
|
3. Understandable
|
3.1 Readable
Make text content readable and understandable. |
3.1.1 | Language of Page | A | Page has a language assigned | Vepple |
| 3.1.2 | Language of Parts | AA | Tell users when the language on a page changes | Vepple | ||
|
3.2 Predictable
Make Web pages appear and operate in predictable ways. |
3.2.1 | On Focus | A | Context does not change when elements receive focus | Vepple | |
| 3.2.2 | On Input | A | Elements do not change when they receive input | Vepple | ||
| 3.2.3 | Consistent Navigation | AA | Use menus consistently | Vepple | ||
| 3.2.4 | Consistent Identification | AA | Use icons and buttons consistently | University | ||
|
3.3 Input Assistance
Help users avoid and correct mistakes. |
3.3.1 | Error Identification | A | Clearly identify input errors | Vepple | |
| 3.3.2 | Labels or Instructions | A | Label elements and give instructions | Vepple | ||
| 3.3.3 | Error Suggestion | AA | Suggest fixes when users make errors | Vepple | ||
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Reduce the risk of input errors for sensitive data | Vepple | ||
| 4. Robust |
4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies. |
4.1.1 | Parsing | A | No major code errors | Vepple |
| 4.1.2 | Name, Role, Value | A | Build all elements for accessibility | Vepple | ||
| 4.1.3 | Status Messages | AA | Content that is updated dynamically must be notified to users of assistive technologies without getting visual focus | Vepple |
Comments
0 comments
Please sign in to leave a comment.