VPAT Statement

Our Voluntary Product Accessibility Template (VPAT) outlines how EDGT aligns with accessibility standards. For full details, see the sections below and contact us if you need an alternative format.

Overview & Scope

Voluntary Product Accessibility Template (VPAT)

Name of Product: EDGT Online Nursing Education Platform Product Description: Online nursing tutorials, practice tests, assessments, and institutional management tools Report Date: February 15, 2026 Last Updated: February 15, 2026 Product Version: Current Production Release Contact Information: [email protected] | 1-888-882-9800

Notes

This report covers conformance for the EDGT web application (www.edgt.com) including public-facing pages, student portal, instructor portal, school administrator portal, and system administrator portal. Product documentation and support services are not covered in this VPAT.

Evaluation Methods Used

Manual source code audit of HTML, CSS, and ARIA attributes across all page templates
Manual keyboard navigation testing of all primary user flows
Color contrast analysis of CSS values against WCAG 2.1 thresholds
Semantic HTML and landmark structure review
ARIA pattern review for interactive components (dropdowns, modals, sliders)
Review of focus management and tab order across authenticated user roles

Executive Summary

EDGT is committed to making its online nursing education platform accessible to all users. This Voluntary Product Accessibility Template (VPAT) is based on the ITI VPAT® 2.4 format and evaluates EDGT's conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Levels A and AA.

The EDGT platform has undergone significant modernization in 2025–2026, including new responsive navigation bars, modern page layouts, and a redesigned login and password reset flow. The modern pages demonstrate strong accessibility practices including proper form labeling, ARIA attributes on interactive elements, and semantic HTML5 landmarks. Some legacy pages remain that use older table-based layouts and require further remediation.

Applicable Standards / Guidelines

This report covers the following standards:

WCAG 2.1 — Web Content Accessibility Guidelines 2.1 (Level A and Level AA)

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.
Not Evaluated: The product has not been evaluated against the criterion.

Scoping

This VPAT reports on the entire EDGT web application including:

Public pages: Home page, login, password reset, EULA, privacy policy, refund policy, VPAT, shopping cart
Student portal: Dashboard, tutorials, tests, scores, assignments, certificates
Instructor portal: Dashboard, test scores, tutorial activity, reports, progress, student management
School admin portal: Dashboard, access keys, users, student groups, products, billing
System admin portal: Dashboard, access keys, schools, users, contacts, Zoho integration

Conformance is scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Contact EDGT

Phone

1-888-882-9800 (Toll Free)
1-630-734-8414 (Chicago)
Fax: 1-630-734-8447

Email

[email protected]

Office Hours

Monday–Friday, 9:00 AM–4:00 PM Central Time.

If you need help accessing EDGT content, contact our team. We can provide guidance and alternate formats upon request.

Detailed Conformance Information

WCAG 2.1 — Level A Success Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content	Partially Supports	Modern pages: Logo images have appropriate alt text. SVG icons in the public header use `aria-hidden="true"` correctly. Home page uses emoji characters as decorative icons in feature cards without text alternatives. Screen readers may read these inconsistently. Navigation bar SVG icons in authenticated pages lack `aria-hidden="true"`, causing screen readers to attempt to parse SVG path data alongside link text. Login password toggle uses emoji character; mitigated by `aria-label` on the button.
1.2.1 Audio-only and Video-only (Prerecorded)	Supports	The platform primarily delivers text-based tutorials and assessments. Audio and video content, where present, has text alternatives.
1.2.2 Captions (Prerecorded)	Supports	Prerecorded media content includes captions where applicable.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Supports	Media alternatives are provided for prerecorded video content used in tutorials.
1.3.1 Info and Relationships	Partially Supports	Modern pages (login, password reset, EULA, dashboards): Proper use of semantic HTML5 elements (`<main>`, `<header>`, `<footer>`, `<nav>`, `<section>`). Form fields have associated `<label>` elements with `for` attributes. Legacy pages (privacy policy, refund policy, EULA rejection): Use table-based layouts for page structure, which confuses screen readers that interpret table semantics. Missing semantic landmarks. Some navigation dropdowns lack ARIA role attributes (`role="menu"`, `role="menuitem"`) to convey their interactive purpose.
1.3.2 Meaningful Sequence	Partially Supports	Modern pages maintain a correct reading sequence in the DOM. The public layout template produces duplicate `<html>` and `<body>` tags due to both the layout and head include emitting document structure, which could confuse some assistive technologies.
1.3.3 Sensory Characteristics	Supports	Instructions do not rely solely on sensory characteristics. Interactive elements use text labels alongside icons.
1.3.4 Orientation	Supports	Content does not restrict display to a single orientation. All pages use responsive CSS that adapts to both portrait and landscape modes.
1.3.5 Identify Input Purpose	Supports	Login, password reset, and registration forms use `autocomplete` attributes (`username`, `current-password`, `new-password`, `email`) to identify input purpose.
1.4.1 Use of Color	Partially Supports	Active navigation items use color combined with background highlight, not color alone. Some links in body text (e.g., footer, help text) rely on color (#5c54ff) as the sole visual differentiator from surrounding text without an additional indicator like underline.
1.4.2 Audio Control	Not Applicable	The platform does not auto-play audio content.
2.1.1 Keyboard	Partially Supports	Login form, password reset, and EULA are fully keyboard operable. Public header account dropdown and mobile drawer support Escape key to close. Backend navigation "Change View" dropdown (admin, school, instructor navbars) lacks keyboard support: no `aria-expanded` attribute, no Escape key handler, no arrow key navigation. Student navbar user dropdown uses `onclick` on a `<div>` element instead of a `<button>`, making it not keyboard accessible by default. Home page testimonial slider buttons are keyboard accessible via native `<button>` elements.
2.1.2 No Keyboard Trap	Partially Supports	No keyboard traps exist in modern pages. Mobile navigation drawer does not trap focus when open. Tab key can move focus to elements behind the drawer overlay, which could confuse keyboard users.
2.1.4 Character Key Shortcuts	Not Applicable	The platform does not implement character key shortcuts.
2.2.1 Timing Adjustable	Supports	Session timeouts redirect to login with an informational message. Password reset tokens have a 1-hour expiry with clear messaging.
2.2.2 Pause, Stop, Hide	Supports	The home page testimonial slider does not auto-advance; it requires user interaction. No auto-updating content exists.
2.3.1 Three Flashes or Below Threshold	Supports	No content flashes more than three times per second.
2.4.1 Bypass Blocks	Partially Supports	Legacy pages using `header1.cfm` include a "Skip Navigation" link that targets `#mainBody`. Modern public layout (`layout_public.cfm`) and all modern navigation bars (admin, school, instructor, student) do not include a skip-to-content link. Users must tab through all navigation items to reach main content. The modern layout does use a `<main id="mainBody">` landmark, which screen readers can use to jump to content, but sighted keyboard users have no visible skip mechanism.
2.4.2 Page Titled	Partially Supports	The shared `head.cfm` include outputs a static title ("EDGT Online: Nursing Tutorials and Practice Tests") for all public pages regardless of page content. Standalone pages (login, EULA, password reset) set their own descriptive titles. Backend pages do not consistently set unique page titles.
2.4.3 Focus Order	Partially Supports	Modern pages follow a logical DOM order: navigation, then main content, then footer. Mobile drawer: when opened, focus is not moved to the drawer, and keyboard focus can reach elements behind the overlay. Backend dropdown menus: focus does not move into the dropdown when opened and does not return to the trigger when closed.
2.4.4 Link Purpose (In Context)	Partially Supports	Most links have descriptive text or `aria-label` attributes (e.g., "Shopping cart", "Account"). Logout icon-only links in backend navigation bars use `title` attribute ("Logout") instead of `aria-label`. The `title` attribute is not reliably announced by all screen readers. Home page "Learn More" links all have identical text without programmatic context to distinguish which tutorial they reference.
2.5.1 Pointer Gestures	Not Applicable	The platform does not require multipoint or path-based gestures.
2.5.2 Pointer Cancellation	Supports	All interactive elements use standard click (up-event) activation. No custom down-event handlers.
2.5.3 Label in Name	Supports	Interactive elements with visible labels have accessible names that contain the visible text. Navigation items combine SVG icons with visible text labels.
2.5.4 Motion Actuation	Not Applicable	The platform does not use device motion or user motion for any functionality.
3.1.1 Language of Page	Partially Supports	Modern pages (`layout_public.cfm`, login, EULA, password reset) correctly declare `<html lang="en">`. Legacy pages (privacy, refund, EULA rejection) use older includes that may not declare the `lang` attribute.
3.2.1 On Focus	Supports	No component initiates a change of context when receiving focus.
3.2.2 On Input	Supports	Form submissions require explicit button activation. No unexpected context changes on input.
3.3.1 Error Identification	Supports	Login errors are displayed in a visible alert with descriptive text. Password reset shows clear success/error messages. Password strength requirements are listed before submission.
3.3.2 Labels or Instructions	Supports	Form fields include visible labels and, where applicable, placeholder text and instructions (e.g., password requirements).
4.1.1 Parsing	Partially Supports	The public layout template (`layout_public.cfm`) and its `head.cfm` include both emit `<!doctype html>`, `<html>`, and `<body>` tags, resulting in duplicate document structure elements in the rendered HTML. Modern standalone pages (login, EULA, password reset) produce well-formed HTML. Some legacy pages may contain table nesting issues.
4.1.2 Name, Role, Value	Partially Supports	Public header: Account dropdown button correctly uses `aria-expanded`, `aria-controls`, and `aria-label`. Mobile burger button also uses correct ARIA pattern. Backend "Change View" dropdown toggles lack `aria-expanded` and `aria-controls` attributes. Screen readers cannot determine the state of the dropdown. Student navbar user dropdown uses a `<div>` with `onclick` rather than a `<button>`, so the interactive role is not communicated to assistive technologies.
4.1.3 Status Messages	Partially Supports	Password reset page uses `role="status"` with `aria-live="polite"` for success and `role="alert"` with `aria-live="assertive"` for errors. Good practice. Login page error alerts do not use `role="alert"`, so they may not be automatically announced by screen readers. Home page testimonial slider: when slides change, the new content is not announced to screen readers (no `aria-live` region).

WCAG 2.1 — Level AA Success Criteria

Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live)	Not Applicable	The platform does not offer live audio or video content.
1.2.5 Audio Description (Prerecorded)	Supports	Audio descriptions are provided where applicable for prerecorded video content.
1.4.3 Contrast (Minimum)	Partially Supports	Primary text colors (#1a202c on #fff, #475569 on #fff) meet 4.5:1 requirements. Navigation user role text (#94a3b8 on #fff) has approximately 3.0:1 contrast ratio, failing the 4.5:1 requirement for normal-size text. Muted helper text (#64748b on #fff) is approximately 4.6:1, borderline passing. EULA hint text and footer muted text use similar borderline values.
1.4.4 Resize Text	Supports	Modern pages use responsive CSS with `clamp()`, `min()`, and relative units. Content remains readable at 200% zoom without horizontal scrolling.
1.4.5 Images of Text	Supports	Text is used to convey information rather than images of text. The EDGT logo image is appropriately used for branding only.
1.4.10 Reflow	Partially Supports	Modern public pages use responsive grid layouts that reflow at 320px width. Backend navigation bars (admin, school, instructor) do not include mobile-responsive breakpoints. On narrow viewports, nav items may overflow or become inaccessible.
1.4.11 Non-text Contrast	Supports	Interactive UI components (buttons, form inputs, navigation items) have sufficient contrast against their backgrounds. Button borders and backgrounds meet the 3:1 requirement.
1.4.12 Text Spacing	Supports	No loss of content or functionality occurs when text spacing properties are modified. Modern layouts use flexible CSS that accommodates spacing changes.
1.4.13 Content on Hover or Focus	Partially Supports	Public header account dropdown: can be dismissed with Escape key. Good. Backend "Change View" dropdowns: open on click (not hover), but cannot be dismissed with Escape key from keyboard.
2.4.5 Multiple Ways	Supports	Users can access pages through direct navigation links, the main navigation menu, footer links, and dashboard quick-action cards.
2.4.6 Headings and Labels	Partially Supports	Modern pages use descriptive headings (h1 for page title, h2/h3 for sections). Some pages have inconsistent heading hierarchy when combining layout templates with page content (e.g., vpat.cfm uses h1 in the hero section and h2 for content, while included content starts at h2).
2.4.7 Focus Visible	Partially Supports	Login page defines explicit `:focus` styles with a visible 2px purple outline. Modern CSS (`modern.css`) and navigation CSS (`nav_modern.css`, `admin_navbar.css`) do not define `:focus` styles for navigation links, buttons, or interactive elements. Keyboard users may rely solely on browser default focus indicators, which vary in visibility.
3.1.2 Language of Parts	Supports	All content is in English. No mixed-language passages require separate `lang` attributes.
3.2.3 Consistent Navigation	Supports	Navigation components are consistent within each user role. Each role (student, instructor, school admin, system admin) has a dedicated navigation bar that appears in the same position on every page of that role.
3.2.4 Consistent Identification	Supports	Components with the same functionality use consistent labeling and styling across the application. Navigation items, buttons, and form elements follow consistent patterns within each design system (modern and legacy).
3.3.3 Error Suggestion	Supports	Login errors suggest checking username/password. Password reset provides specific guidance. Password strength requirements are displayed with specific criteria (8+ characters, letter + number).
3.3.4 Error Prevention (Legal, Financial, Data)	Supports	EULA acceptance requires explicit button click. Password reset requires confirmation (enter password twice). Shopping cart provides review before purchase.

WCAG 2.1 — Level AAA Success Criteria

Level AAA criteria are not required for conformance and are provided here for informational purposes. EDGT has not formally evaluated against Level AAA criteria at this time.

Criteria	Conformance Level	Remarks and Explanations
1.2.6 Sign Language (Prerecorded)	Not Evaluated
1.2.7 Extended Audio Description	Not Evaluated
1.2.8 Media Alternative (Prerecorded)	Not Evaluated
1.2.9 Audio-only (Live)	Not Applicable	No live audio content.
1.3.6 Identify Purpose	Not Evaluated
1.4.6 Contrast (Enhanced)	Not Evaluated
1.4.7 Low or No Background Audio	Not Evaluated
1.4.8 Visual Presentation	Not Evaluated
1.4.9 Images of Text (No Exception)	Not Evaluated
2.1.3 Keyboard (No Exception)	Not Evaluated
2.2.3 No Timing	Not Evaluated
2.2.4 Interruptions	Not Evaluated
2.2.5 Re-authenticating	Not Evaluated
2.2.6 Timeouts	Not Evaluated
2.3.2 Three Flashes	Not Evaluated
2.3.3 Animation from Interactions	Not Evaluated
2.4.8 Location	Not Evaluated
2.4.9 Link Purpose (Link Only)	Not Evaluated
2.4.10 Section Headings	Not Evaluated
2.5.5 Target Size	Not Evaluated
2.5.6 Concurrent Input Mechanisms	Supports	The platform does not restrict input modalities.
3.1.3 Unusual Words	Not Evaluated
3.1.4 Abbreviations	Not Evaluated
3.1.5 Reading Level	Not Evaluated
3.1.6 Pronunciation	Not Evaluated
3.2.5 Change on Request	Not Evaluated
3.3.5 Help	Not Evaluated
3.3.6 Error Prevention (All)	Not Evaluated

Remediation Roadmap

EDGT is actively working to improve accessibility. The following items are planned for remediation:

Priority	Issue	Criteria	Planned Fix
High	No skip-to-content link in modern layout	2.4.1 Bypass Blocks	Add visually-hidden skip link to public layout and all backend navigation bars
High	Missing focus styles in modern CSS	2.4.7 Focus Visible	Add consistent `:focus-visible` styles to navigation and interactive elements
High	Backend dropdowns lack keyboard support	2.1.1, 4.1.2	Add `aria-expanded`, Escape key handling, and keyboard navigation to all dropdown components
Medium	Duplicate HTML document structure	4.1.1 Parsing	Refactor `head.cfm` to not emit `<html>`/`<body>` when included by `layout_public.cfm`
Medium	SVG icons not hidden from assistive technology	1.1.1 Non-text Content	Add `aria-hidden="true"` to decorative SVGs in backend navigation bars
Medium	Logout links use `title` instead of `aria-label`	2.4.4 Link Purpose	Replace `title` with `aria-label="Logout"`
Medium	Low contrast on nav user role text	1.4.3 Contrast	Darken #94a3b8 to meet 4.5:1 minimum ratio
Low	Legacy pages use table layout	1.3.1 Info and Relationships	Migrate legacy pages (privacy, refund) to modern layout template
Low	Static page titles	2.4.2 Page Titled	Set dynamic `<title>` based on `request.page.title`
Low	Login error not using `role="alert"`	4.1.3 Status Messages	Add `role="alert"` to login error message container