Accessibility
Voluntary Product Accessibility Template (VPAT) documenting Section 508 and WCAG 2.2 AA conformance.
iManage Accessibility Conformance Report
Revised Section 508 Edition
(Based on VPAT® Version 2.5)
Name of Product/Version: iManage Research Study Management System
Report Date: December 2025
Product Description: iManage is a web-based research study management application that enables participants to complete assessments, track session progress, and engage with study materials. Administrators and coordinators manage studies, modules, and participant enrollments.
Contact Information: accessibility@imanage.udel.edu
Notes: This report covers the iManage web application accessed via modern web browsers. The application does not include native mobile apps, desktop software, or hardware components.
Evaluation Methods Used:
Automated Testing:
- axe-core integrated into the test suite, running automatically after each test step
- WCAG tags tested:
wcag2a,wcag2aa,wcag21a,wcag21aa,wcag22aa,best-practice - Chrome Lighthouse accessibility audits
Manual Testing:
- Screen reader testing with NVDA (Windows) and VoiceOver (Mac)
- Verified all form labels are properly associated
- Confirmed dynamic content updates are announced
- Keyboard-only navigation testing through all interactive elements
- Verified focus is visible throughout
- Checked for keyboard traps
- Visual testing at 200% browser zoom
- Color contrast verification
- Color blindness simulator testing
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 Level A | Yes |
| Web Content Accessibility Guidelines 2.0 Level AA | Yes |
| Web Content Accessibility Guidelines 2.1 Level A | Yes |
| Web Content Accessibility Guidelines 2.1 Level AA | Yes |
| Web Content Accessibility Guidelines 2.2 Level A | Yes |
| Web Content Accessibility Guidelines 2.2 Level AA | Yes |
| Web Content Accessibility Guidelines 2.x Level AAA | No |
| Revised Section 508 standards (January 18, 2017) | Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.0 Report
Tables 1 and 2 document conformance with:
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
- Revised Section 508: Chapter 6 – 602.3 Electronic Support Documentation
Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All images include appropriate alt text. Decorative images use empty alt attributes. Form inputs have associated labels. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | Video content includes transcripts. The application does not contain audio-only content. |
| 1.2.2 Captions (Prerecorded) | Supports | All prerecorded video content includes closed captions. Videos support caption file uploads. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Supports | Video content is supplemented with text descriptions where visual information is essential. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML is used throughout. Forms use proper label associations. Tables include headers. Headings follow logical hierarchy. |
| 1.3.2 Meaningful Sequence | Supports | Content reading order matches visual presentation. DOM order reflects logical sequence. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, visual location, or sound. |
| 1.4.1 Use of Color | Supports | Color is not used as the only visual means of conveying information. Links are underlined or otherwise distinguishable. |
| 1.4.2 Audio Control | Supports | No audio plays automatically. Users control all audio playback. |
| 2.1.1 Keyboard | Supports | All functionality is accessible via keyboard. Interactive elements are focusable and operable. |
| 2.1.2 No Keyboard Trap | Supports | Keyboard focus can be moved away from all components. No keyboard traps exist. |
| 2.2.1 Timing Adjustable | Supports | Session timeout provides warning and option to extend. Users are notified before automatic logout. |
| 2.2.2 Pause, Stop, Hide | Supports | No auto-updating content. Users control video playback. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | Skip navigation links are provided. Landmark regions define page structure. |
| 2.4.2 Page Titled | Supports | All pages have descriptive, unique titles. |
| 2.4.3 Focus Order | Supports | Focus order follows logical reading sequence. Tab order matches visual layout. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text describes destination or purpose. No ambiguous "click here" links. |
| 3.1.1 Language of Page | Supports | HTML lang attribute is set to "en" on all pages. |
| 3.2.1 On Focus | Supports | No context changes occur on focus. |
| 3.2.2 On Input | Supports | Form submissions require explicit user action. No automatic context changes on input. |
| 3.3.1 Error Identification | Supports | Form errors are clearly identified in text. Error messages describe the issue. |
| 3.3.2 Labels or Instructions | Supports | Form fields have visible labels. Required fields are indicated. Instructions are provided where needed. |
| 4.1.1 Parsing | Supports | Per WCAG 2.0 errata (September 2023), this criterion is always considered supported. |
| 4.1.2 Name, Role, Value | Supports | Custom components use appropriate ARIA attributes. Form controls have accessible names. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The application does not include live audio content. |
| 1.2.5 Audio Description (Prerecorded) | Supports | Prerecorded video content includes audio descriptions where visual information is essential. |
| 1.4.3 Contrast (Minimum) | Supports | Text and interactive elements meet 4.5:1 contrast ratio for normal text and 3:1 for large text. |
| 1.4.4 Resize Text | Supports | Text can be resized up to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | Text is used instead of images of text, except for logos. |
| 2.4.5 Multiple Ways | Supports | Multiple navigation methods available: main navigation, session list, and direct links. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe topic or purpose. Heading hierarchy is logical. |
| 2.4.7 Focus Visible | Supports | Keyboard focus indicator is visible on all interactive elements. |
| 3.1.2 Language of Parts | Supports | No content in languages other than English. Lang attribute would be used if multilingual content were added. |
| 3.2.3 Consistent Navigation | Supports | Navigation is consistent across all pages. Menu structure remains stable. |
| 3.2.4 Consistent Identification | Supports | Components with the same functionality are identified consistently throughout. |
| 3.3.3 Error Suggestion | Supports | Error messages include suggestions for correction when possible. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | The application does not process legal, financial, or test data that requires error prevention measures beyond standard form validation. |
WCAG 2.1 Report
WCAG 2.1 extends WCAG 2.0 with additional success criteria. All WCAG 2.0 criteria documented above also apply to WCAG 2.1 conformance.
Table 3: Success Criteria, Level A (WCAG 2.1 Additions)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.3.4 Orientation | Supports | Content displays in both portrait and landscape orientations. No orientation lock is enforced. |
| 1.3.5 Identify Input Purpose | Supports | Form inputs use appropriate autocomplete attributes to identify their purpose (name, email, etc.). |
| 1.3.6 Identify Purpose | Not Applicable | Level AAA criterion - not included in this report. |
| 2.1.4 Character Key Shortcuts | Supports | No single-character keyboard shortcuts are implemented. All shortcuts require modifier keys. |
| 2.5.1 Pointer Gestures | Supports | All functionality that uses multipoint or path-based gestures can be operated with a single pointer. No complex gestures required. |
| 2.5.2 Pointer Cancellation | Supports | For functionality operated by a single pointer, at least one of the following is true: no down-event, abort/undo available, up reversal, or essential. |
| 2.5.3 Label in Name | Supports | For user interface components with visible text labels, the accessible name contains the visible text. |
| 2.5.4 Motion Actuation | Supports | No functionality is triggered by device motion. All functions are available via standard interface controls. |
Table 4: Success Criteria, Level AA (WCAG 2.1 Additions)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.3.6 Identify Purpose | Not Applicable | Level AAA criterion - not included in this report. |
| 1.4.10 Reflow | Supports | Content reflows without horizontal scrolling at 320 CSS pixels width (equivalent to 400% zoom at 1280px). No loss of information or functionality. |
| 1.4.11 Non-text Contrast | Supports | User interface components and graphical objects have at least 3:1 contrast ratio against adjacent colors. Focus indicators, form boundaries, and icons meet contrast requirements. |
| 1.4.12 Text Spacing | Supports | No loss of content or functionality occurs when users override text spacing (line height 1.5x, paragraph spacing 2x, letter spacing 0.12x, word spacing 0.16x). |
| 1.4.13 Content on Hover or Focus | Supports | Additional content that appears on hover or focus is dismissible, hoverable, and persistent. Tooltips and dropdowns meet these requirements. |
| 4.1.3 Status Messages | Supports | Status messages are programmatically determined through role or properties so they can be presented to the user by assistive technologies without receiving focus. Flash messages use appropriate ARIA live regions. |
WCAG 2.2 Report
WCAG 2.2 extends WCAG 2.1 with additional success criteria. All WCAG 2.0 and 2.1 criteria documented above also apply to WCAG 2.2 conformance.
Note: WCAG 2.2 removed Success Criterion 4.1.1 Parsing as it is obsolete for modern HTML.
Table 5: Success Criteria, Level A (WCAG 2.2 Additions)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 3.2.6 Consistent Help | Supports | Help mechanisms (contact information, help links) are located in the same relative order on each page. Footer contains consistent support links. |
| 3.3.7 Redundant Entry | Supports | Information previously entered by or provided to the user that is required to be entered again is either auto-populated or available for the user to select. Session data persists across form steps. |
Table 6: Success Criteria, Level AA (WCAG 2.2 Additions)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | Supports | When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. Fixed headers and modals do not obscure focused elements. |
| 2.4.12 Focus Not Obscured (Enhanced) | Not Applicable | Level AAA criterion - not included in this report. |
| 2.4.13 Focus Appearance | Not Applicable | Level AAA criterion - not included in this report. |
| 2.5.7 Dragging Movements | Supports | Functionality that can be operated by dragging has a single-pointer alternative. Drag-and-drop for session ordering includes up/down button alternatives. |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets are at least 24x24 CSS pixels, or have sufficient spacing from adjacent targets, or have an equivalent alternative. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Authentication does not require cognitive function tests. Standard username/password login is used without CAPTCHA or puzzle requirements. |
| 3.3.9 Accessible Authentication (Enhanced) | Not Applicable | Level AAA criterion - not included in this report. |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | Screen reader compatible. All content has text alternatives. |
| 302.2 With Limited Vision | Supports | Supports browser zoom to 200%. High contrast support. |
| 302.3 Without Perception of Color | Supports | Information not conveyed by color alone. |
| 302.4 Without Hearing | Supports | Captions provided for video. No audio-only content. |
| 302.5 With Limited Hearing | Supports | Captions and visual alternatives provided. |
| 302.6 Without Speech | Not Applicable | Application does not require speech input. |
| 302.7 With Limited Manipulation | Supports | Full keyboard accessibility. No complex gestures required. |
| 302.8 With Limited Reach and Strength | Supports | Standard keyboard and mouse input supported. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Clear navigation, consistent layout, simple language used throughout. |
Chapter 4: Hardware
Not Applicable – iManage is a web application and does not include hardware components.
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope | See WCAG 2.0 Tables | Conformance is documented in WCAG 2.0 Level A and AA tables above. |
| 502 Interoperability with Assistive Technology | Not Applicable | Web application uses standard HTML/CSS/JavaScript accessible to assistive technologies via the browser. |
| 503 Applications | Not Applicable | Web application criteria covered under WCAG conformance. |
| 504.2 Content Creation or Editing | Not Applicable | Application is not an authoring tool. Administrators configure studies but do not create web content. |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Supports | Documentation describes keyboard navigation and screen reader compatibility. |
| 602.3 Electronic Support Documentation | See WCAG 2.0 Tables | Online help and documentation conform to WCAG 2.0 Level A and AA. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All documentation is provided electronically. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Accessibility features are documented and available to users upon request. |
| 603.3 Accommodation of Communication Needs | Supports | Support available via email. Alternative formats provided upon request. |
Resources
- WCAG 2.2 Specification
- WCAG 2.2 Quick Reference
- What's New in WCAG 2.2
- Section 508 Standards
- axe-core Rules
- Chrome Lighthouse
Legal Disclaimer
This Accessibility Conformance Report is provided for informational purposes. Conformance levels are based on evaluation methods described above and may vary based on user configuration, browser version, and assistive technology used.
VPAT® is a registered service mark of the Information Technology Industry Council (ITI).