COE Conference

The Council for Opportunity in Education (COE) 2025 Conference is in Chicago, IL. Please save the date for September 7, 2025 - September 10, 2025

Got TRiO News?

Lacai Accessibility Conformance Report

WCAG and 508

(Based on VPAT® Version 2.5Rev)

Name of Product/Version: Lacai (2025 Rolling Release)
Report Date: June 2025
Product Description: Web-based Student Contact Management System
Contact Information:
Notes: This report covers accessibility conformance for Lacai available to end users. This report does not discuss back-end integration tools only used by system administrators and supporting IT staff.
Evaluation Methods Used: Conformance to the listed accessibility standards has been evaluated by Carney Inc using a combination of static analysis tools and manual testing with assistive technologies.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ Level A – Yes

Level AA – Yes

Level AAA – No
Web Content Accessibility Guidelines 2.1, at https://www.w3.org/TR/WCAG21/ Level A – Yes

Level AA – Yes

Level AAA – No
Web Content Accessibility Guidelines 2.2, at https://www.w3.org/TR/WCAG22/ Level A – Yes

Level AA – Yes

Level AAA – No
Revised Section 508 standard published January 18, 2017 and corrected January 22, 2018, at http://www.Section508.gov Yes

Terms

The terms used in the Conformance Level information are defined as follows:

 

WCAG 2.x Report

Tables 1, 2, and 3 also document conformance with:

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 (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses standard HTML techniques for providing text equivalents of non-text elements. This includes the use of <alt> attributes for images.

Some purely decorative elements that have no functional or informational purpose may not provide a text alternative.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai does not include audio or video content by default. However, end users may choose to upload video content to profiles. In such cases, users may include alternative representations (such as text transcripts) that present equivalent information to the videos.
1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Does Not Support Lacai does not include audio or video content by default. However, end users may choose to upload video content to profiles. In that case, Lacai does not provide capabilities for captioning or defining audio descriptions of user-specified video content.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not use synchronized media.
1.3.1 Info and Relationships (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.
1.3.2 Meaningful Sequence (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai generates semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls.
1.3.3 Sensory Characteristics (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not depend solely on sensory characteristics such as shape, size, visual location, orientation, or sound to understand content.
1.4.1 Use of Color (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.

Lacai provides capabilities for defining text alternatives of user-specified content.
1.4.2 Audio Control (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai does not include audio or video content by default. However, end-users may choose to include video content in profiles within Lacai. Lacai utilizes browser functionality for audio controls on user-specified video content.
2.1.1 Keyboard (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai is a web-based application that supports standard keyboard navigation and input functions (such as pressing [Tab] to move between input fields, pressing the arrow keys to move between list items, and pressing [Space] or [Enter] to make selections).
2.1.2 No Keyboard Trap (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai is a web-based application that supports standard keyboard navigation and ensures that keyboard users cannot be trapped in a subset of content.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not implement keyboard shortcuts using printable characters in content with the exception for standard web-based elements such as listboxes that are active only on focus.
2.2.1 Timing Adjustable (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Partially Supports Lacai has a session timeout alert to notify users when a session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message and choose to extend their session.
2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not include moving, blinking, scrolling, or auto-updating information.
2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not use flashing interface elements.
2.4.1 Bypass Blocks (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software) Does not apply to non-web software
  • 602.3 (Support Docs) Does not apply to non-web docs
 Supports A hidden link (available to screen readers) allows users to jump to the main content of each page.
2.4.2 Page Titled (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Web pages within Lacai have descriptive titles that indicate the topic or purpose of each page.
2.4.3 Focus Order (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses a logical tab order through interactive elements such as links and form controls.

Lacai also uses semantically correct markup, ensuring that the markup matches the visual presentation of content on the page.
2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses descriptive text, such as adding a <title> attribute to icon links, to identify the purpose of links.
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai allows functionality to be operated by a click/tap, double-click/tap, long press, or click and hold instead of multipoint or path-based gestures.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses the up-event for any javascript function completion, and the function can be aborted by changing focus from the element.
2.5.3 Label in Name (Level A 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai matches the accessible name to the visible label, and for icons with no accompanying text the hover text displays the accessible name.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai does not depend solely on device motion to control page content.
3.1.1 Language of Page (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses the language attribute on the HTML element to specify the default language of a page.
3.2.1 On Focus (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports When a component in a Lacai user interface receives focus, it does not initiate a change of context.
3.2.2 On Input (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Changing the setting of a component in a Lacai user interface does not initiate a change of context.
3.2.6 Consistent Help (Level A 2.2 only)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports E-mail and phone support information is at the bottom of every page in Lacai. Self-help tools and documentation are always available under the System menu.
3.3.1 Error Identification (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai provides capabilities for specifying error text for user interface components configured by users with Lacai.
3.3.2 Labels or Instructions (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses standard HTML attributes to associate labels and instructions to user interface elements.
3.3.7 Redundant Entry (Level A 2.2 only)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai allows address copying between primary and connection records, browser auto-populate can be used throughout the interface.
4.1.1 Parsing (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses semantically-correct markup for all interface elements. The markup is programmatically generated to prevent parsing errors.
4.1.2 Name, Role, Value (Level A)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses standard HTML attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live) (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not use synchronized media.
1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not use synchronized media.
1.3.4 Orientation (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Display orientation is not restricted and can be adjusted for user preference.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Where form fields prefer specific input, recommendations are displayed but not required, Ex: grade fields displaying letter grades, but allowing numeric entry.
1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Partially Supports The visual presentation of text in Lacai provides sufficient contrast. Administrators may configure custom color schemes for Lacai. Any web-supported color scheme may be selected, allowing for satisfactory contrast requirements.
1.4.4 Resize text (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai user interfaces support standard zoom capabilities built into modern web browsers and operating systems.
1.4.5 Images of Text (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai does not use images of text by default.
1.4.10 Reflow (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Text and content in Lacai wrap based on adaptive screen dimensions (viewport) down to 320x256, with the exception of user-generated reports that may contain tables with many columns of data that require scrolling in two dimensions to view all of the output.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Elements and controls maintain at least a 3:1 contrast ratio with adjacent colors, and borders are used to indicate a visual boundary where colors are not used.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports No loss of content or controls occurs if user-defined text settings are used to override or adjust text spacing in Lacai.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai does not present content based on hover/focus, with the exception of user agent controlled content such as title attributes.
2.4.5 Multiple Ways (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software) Does not apply to non-web software
  • 602.3 (Support Docs) Does not apply to non-web docs
 Supports Lacai provides navigation links and search functions within its user interface.
2.4.6 Headings and Labels (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses semantically-correct markup for all interface elements, including headings and labels.
2.4.7 Focus Visible (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai uses visual changes to elements to indicate the current position of focus.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai does not have sticky visual elements that would obscure a focused element.
2.5.7 Dragging Movements (Level AA 2.2 only)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Not Applicable Lacai does not use dragging movements for operations within the interface beyond functionality determined by the user agent.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Partially Supports At default 100% browser zoom, there are side-by-side pointer inputs in Lacai that are 16x16 pixel dimensions, but increasing the zoom will make the target sizes larger based on user preference to 24x24 pixel and larger.
3.1.2 Language of Parts (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Does Not Support In Lacai, the language of a page can be programmatically determined. However, there is no mechanism to specify different languages for subsets of a page.
3.2.3 Consistent Navigation (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software) Does not apply to non-web software
  • 602.3 (Support Docs) Does not apply to non-web docs
 Supports Lacai uses the same navigation mechanisms across pages.
3.2.4 Consistent Identification (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software) Does not apply to non-web software
  • 602.3 (Support Docs) Does not apply to non-web docs
 Supports Lacai ensures consistent functionality and presentation across pages.
3.3.3 Error Suggestion (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai provides suggestions for correcting errors such as identifying required fields using CSS style including supplemental text notifying users of form errors such as required fields that were not completed.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai provides methods in its user interface for error prevention. Specific fields check for input errors, ensuring that submissions are reversible, and allowing users to review and confirm information prior to submission.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai allows the use of a password manager or copy and paste for authentication.
4.1.3 Status Messages (Level AA 2.1 and 2.2)

Also applies to:

Section 508

  • 501 (Web)(Software)
  • 602.3 (Support Docs)
 Supports Lacai status messages are presented to the user on screen and allow use of assistive technologies for interpretation.

Table 3: Success Criteria, Level AAA

Notes: Lacai has not been evaluated for WCAG 2.0 Level AAA conformance.

 

Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Supports Lacai uses standard HTML attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.
302.2 With Limited Vision Supports Lacai supports standard browser magnification and contrast adjustments.
302.3 Without Perception of Color Supports Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.
302.4 Without Hearing Not Applicable Lacai does not include audio-only features that require hearing to be used.
302.5 With Limited Hearing Not Applicable Lacai does not include audio-only features that require hearing to be used.
302.6 Without Speech Not Applicable Lacai does not require speech input.
302.7 With Limited Manipulation Supports Lacai supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions.
302.8 With Limited Reach and Strength Not Applicable
302.9 With Limited Language, Cognitive, and Learning Abilities Supports

Chapter 4: Hardware

Notes: Lacai is a web software application and is not subject to the requirements of this section.

Chapter 5: Software

Criteria Conformance Level Remarks and Explanations
501.1 Scope Incorporation of WCAG 2.0 AA See WCAG 2.0 section See information in WCAG section
502 Interoperability with Assistive Technology
502.2.1 User Control of Accessibility Features Not Applicable Lacai is not considered platform software as defined by Section 508.
502.2.2 No Disruption of Accessibility Features Supports Lacai is compatible with operating system and browser accessibility features configured by the user.
502.3 Accessibility Services
502.3.1 Object Information Supports Lacai uses HTML attributes to describe the description of user interface elements to Assistive Technologies.
502.3.2 Modification of Object Information Supports Lacai uses standard HTML object roles for maximum compatibility with assistive technologies.
502.3.3 Row, Column, and Headers Supports Lacai uses standard HTML attributes to define table structure and relationships, including column and row headers, to Assistive Technologies.
502.3.4 Values Supports Lacai uses standard HTML object attributes for maximum compatibility with assistive technologies.
502.3.5 Modification of Values Supports Lacai uses standard HTML object attributes for maximum compatibility with assistive technologies.
502.3.6 Label Relationships Supports Lacai uses standard HTML attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of <label> attributes.
502.3.7 Hierarchical Relationships Supports Lacai uses standard HTML markup to express hierarchical relationships.
502.3.8 Text Supports Lacai renders strings as plain text values in HTML for maximum compatibility with assistive technologies.
502.3.9 Modification of Text Supports Lacai renders strings as plain text values in HTML for maximum compatibility with assistive technologies.
502.3.10 List of Actions Supports Lacai uses standard HTML object attributes for maximum compatibility with assistive technologies.
502.3.11 Actions on Objects Supports Lacai uses standard HTML object attributes for maximum compatibility with assistive technologies.
502.3.12 Focus Cursor Supports Lacai uses visual changes to elements to indicate the current position of focus.
502.3.13 Modification of Focus Cursor Supports Lacai uses standard HTML elements with standard cursor controls for user input.
502.3.14 Event Notification Partially Supports Lacai has a session timeout alert to notify users when a session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message and choose to extend their session.
502.4 Platform Accessibility Features Not Applicable Lacai is not considered platform software as defined by Section 508.
503 Applications
503.2 User Preferences Supports Lacai respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, Lacai user interface will display with high contrast.
503.3 Alternative User Interfaces Not Applicable Lacai does not provide any alternative user interfaces that function as assistive technology.
503.4 User Controls for Captions and Audio Description
503.4.1 Caption Controls Does Not Support Lacai does not provide capabilities for captioning or defining audio descriptions of user-specified video content.
503.4.2 Audio Description Controls Does Not Support Lacai does not provide capabilities for captioning or defining audio descriptions of user-specified video content.
504 Authoring Tools
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) Not Applicable
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Not Applicable
504.2.2 PDF Export Not Applicable
504.3 Prompts Not Applicable
504.4 Templates Not Applicable

Chapter 6: Support Documentation and Services

Criteria Conformance Level Remarks and Explanations
601.1 Scope
602 Support Documentation
602.2 Accessibility and Compatibility Features Supports Documentation for Lacai lists and explains the accessibility and compatibility features of the product
602.3 Electronic Support Documentation See WCAG 2.0 Section See information in WCAG 2.0 section
602.4 Alternate Formats for Non-Electronic Support Documentation Supports Documentation can be made available in the format of the user's choice upon request
603 Support Services
603.2 Information on Accessibility and Compatibility Features Supports Support services (technical support and training) for Lacai provides information on the accessibility and compatibility features of the product.
603.3 Accommodation of Communication Needs Supports Lacai Support;
For more information about the maintainers of the VPAT itself please see the contact information below:

ITI Global Headquarters
1101 K Street NW, Suite 610
Washington, DC 20005
Phone: 202-737-8888
Email: info@itic.org
Internet: http://itic.org
Printable Copy