Skip to Main Content

Accessibility

Monsido Test Page

Rubric Overview

The rubric below outlines accessibility considerations for meeting WCAG 2.1 A, AA, and AAA levels of accessibility. While Iona aims for AA accessibility, it's instructive to illustrate the application of WCAG criteria; some criteria lack AA or AAA requirements, while others lack AA requirements. This allows us to understand the component parts of an WCAG AA accessible guide while finding areas for further growth and exploration.

This rubric is largely based on a rubric from Tori Linville Hopper’s 2021 article Accessibility and LibGuides in Academic Libraries from The Southeastern Librarian.

Rubric

Criteria Optimum Accessibility (AAA)

Improved Accessibility  

(AA)

Minimum Accessibility  
(A)
Inaccessible Tools for Criteria Compliance
Text Alternatives (WCAG 2.1 1.1): Provide for non-text content within web pages so content can be changed into other forms that people need. (1.1.1) N/A N/A All non-text content has text alternatives, exemptions noted in criteria (1.1.1). Missing alternative text for required non-text content. W3C Alt Text Decision Tree
Time-based Media (WCAG 2.1 1.2): Provide various accessible alternatives. (1.2.1-1.2.9)

All pre-recorded audio in synchronized media has sign language (1.2.6)

All pre-recorded video in synchronized media provides extended audio descriptions when needed (1.2.7)

All pre-recorded media have a text alternative (1.2.8)

All live audio uses caption service (1.2.9)

All live audio in synchronized media have captions (1.2.4)
All pre-recorded video in synchronized media have audio descriptions when needed (1.2.5)

All pre-recorded media have an alternative content format (1.2.1, 1.2.3)

All pre-recorded media have captions (1.2.2)

Fails to meet level A – missing alternative format and/or captions. Captioning tools included in SnagIt and Niche Academy
Adaptable (WCAG 2.1 1.3): Create content that can be presented in different mediums without losing information. (1.3.1-1.3.6) In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined (1.3.6)

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape unless essential for meaning (1.3.4)

Purpose of each input field is clearly identifiable and justifiable (1.3.5)

All content preserves structure and relationships regardless of presentation (1.3.1)

All content has a logical reading order, preserved regardless of presentation (1.3.2

All instructions do not solely rely on senses alone (shape, color, or sound) to make meaning (1.3.3)

Fails to meet level A – content loses meaning when applied to different medium. N/A
Distinguishable (WCAG 2.1 1.4): Easier for users to hear and see content (1.4.1-1.4.13)

All text and images of text have a contrast ratio of 7:1 except for large text, decorative UX elements, and logos (1.4.6)

All pre-recorded audio of speeches have at least 20 dB between the speech and background audio, or the ability to turn background audio off (1.4.7)

All blocks of text should meet 5 guidelines noted (1.4.8)

Text should be used instead of an image of text unless used in logo or decorative purposes (1.4.9)

All text and images of text have a contrast ratio of at least 4:5:1 except for large text, decorative UX elements, and logos (1.4.3)

Aside from captions and images of text, all text can be resized up to 200% without losing content or meaning (1.4.4)

Text is used rather than images to convey information (1.4.5)

UX interface components and graphical objects should have a 3:1 contrast ratio (1.4.11)

No content uses color alone to distinguish an element (1.4.1)

No audio plays longer than three seconds automatically without the typical user controls being provided for it (1.4.2)

Fails to meet level A – content relies on color to distinguish element and/or audio automatically plays WebAIM Color Contrast Checker
Keyboard Accessibility (WCAG 2.1 2.1): All functionality available from a keyboard (2.1.1-2.1.4) All website functionality is keyboard accessible without requiring specific timing for keystrokes (2.1.3) N/A

All website functionality is keyboard accessible, with a few exceptions not relevant to LibGuides (2.1.1)

No keyword traps; if non-standard keys are required to move focus, the user is notified (2.1.2)

Keyboard shortcuts implemented on content with letters, punctuation, numbers, and symbols must have the ability to be turned off, remapped, or active only on focus (2.1.4)

Fails to meet level A – content is not keyboard accessible N/A
Enough Time (WCAG 2.1 2.2): Users are provided enough time to read content (2.2.1-2.2.6)

Barring real events or interactive synchronized media, content is not dependent on timing (2.2.3)

Interruptions can be postponed or suspended (2.2.4)

Largely not applicable, but reauthentication will not result in data loss (2.2.5)

Users are warned of situations where inactivity can cause data loss (2.2.6)

N/A

Largely not applicable, but any time-limited content must be able to be turned off, adjusted, extended, or have ample exceptions (2.2.1)

Non-essential content that blinks, moves, or scrolls for more than 5 seconds can be paused, hidden, or stopped by user (2.2.2)

Fails to meet level A – content is time-limited and cannot be adjusted or suspended N/A
Seizures and Physical Reactions (WCAG 2.1 2.3): Don't design content known to cause seizures and physical reactions (2.3.1-2.3.3)

Webpage does not contain content that flashes more than three times a second (2.3.2)

Motion animation triggered by interaction can be disabled (2.3.3)

N/A Webpage does not include content that flashes more than three times a second or falls below both general and red flash thresholds (2.3.1) Fails to meet level A – includes animation that flashes more than three times a second or falls below general and red flash thresholds N/A
Navigable (WCAG 2.1 2.4.1-2.4.10): Help users navigate, find content, and determine where they are on each web page with directions (2.4.1-2.4.10)

Information about user’s location in a website is available, like a breadcrumb trail (2.4.8)

The purpose of link text can be determined from text alone (2.4.9)

Section headings are used to organize content (2.4.10)

Webpages are locatable in multiple ways except when page is step in sequential process (2.4.5)

Headings and labels describe content and purpose (2.4.6)

Keyboard focus is visible when keyboard operable component is used (2.4.7)

Blocks of repetitive content on multiple webpages can be skipped (2.4.1)

Webpages have descriptive titles (2.4.2)

Components receive sequential focus that retains their meaning (2.4.3)

The purpose of hyperlinks can be determined from text itself (2.4.4)

Fails to meet level A N/A
Readable (WCAG 2.1 3.1.1-3.1.6): Text content is readable and understandable (3.1.1-3.1.6)

All specialized words are defined (3.1.3)

All acronyms and abbreviations are defined (3.1.4)

All content is available in a secondary education reading level (3.1.5)

When required for meaning, a mechanism is available for pronouncing words (3.1.6)

Barring certain exceptions – like words or phrases that have entered the vernacular – language deviating from default language is noted (3.1.2) All webpages have a default human language (3.1.1) Fails to meet level A – no default human language N/A
Predictable (WCAG 2.1 3.2): Web pages appear and operate in predictable ways (3.2.1-3.2.5) Any changes in context are strictly user initiated and can be turned off by user (3.2.5)

Navigation appearing on multiple web pages remains consistent, occurring in the same relative place on the webpage (3.2.3)

Components with the same functionality across webpages are consistently identified (3.2.4)

When receiving focus, no content loses context (3.2.1)

Context does not automatically change when user changes settings, unless user is advised before adjusting settings (3.2.2)

Fails to meet level A – context is easily lost in UX components N/A
Input Assistance (WCAG 2.1 3.3): Help users avoid and correct mistakes (3.3.1-3.3.6)

Context-sensitive help is provided in webpage (3.3.5)

Where users are required to submit information, submission can be reversed, checked, or confirmed (3.3.6)

If input error is automatically detected and identifiable, input suggestions are provided unless security or purpose of content is jeopardized (3.3.3)

If input error is automatically detected, error is described and identified (3.3.1)

When content requires user input, controls have labels or instructions (3.3.2)

Fails to meet level A – input errors are not identified and lack labels or instructions N/A
Compatible (WCAG 2.1 4.1): Maximize compatibility with current and future agents, including assistive technologies (4.1.1-4.1.3) N/A Status messages can be determined with role or properties in a legible format for assistive technologies (4.1.3)

No code validation errors (4.1.1)

Name and role of all UI components are identified and available to user (4.1.2)

Fails to meet level A – content has validation errors and elements are not identified WAVE Browser Extension