The Salt House LLC Accessibility Conformance Report WCAG Edition
(Based on VPAT® Version 2.5)
Name of Product: The Salt House Skills Tracker
Report Date: November 2026
Product Description: Web application used to document student skill completion.
Scope: This report covers the pages used by program customers: students, instructors, program managers, internship managers and internship site supervisors, plus the public website and sign-in pages. It does not cover the Salt House internal administration area, which is available only to Salt House staff.
Contact Information: Joe Craddock, The Salt House LLC
Reporting an Accessibility Issue:
If you find an accessibility barrier, you can report it without signing in using the accessibility issue report form. We will acknowledge your report within 5 business days and provide a fix or a workaround within 30 days of your report.
Evaluation Methods Used:
- Chrome Browser
- Keyboard accessibility testing
- Accessibility testing tools: Lighthouse, WAVE Web Accessibility Evaluation Tool, and an in-browser script that checks WCAG 2.2 A/AA criteria across program pages
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.2 |
Level A (Yes)
Level AA (Yes)
Level AAA (No)
|
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | (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.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.2 Report
Tables 1 and 2 also document conformance with Revised Section 508:
- Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
- Chapter 6 – 602.3 Electronic Support Documentation
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.1.1 Non-text Content (Level A)
Also applies to:
Revised Section 508
|
Supports | The product provides text alternatives for nontext items. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not have prerecorded audio only or prerecorded video-only media. |
|
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
Revised Section 508
|
Supports | The video content includes captions of the spoken word audio. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
Revised Section 508
|
Supports | There are 3 instructional videos provided for the program director that have closed captioning available on YouTube. Links are provided. |
|
1.3.1 Info and Relationships (Level A)
Also applies to:
Revised Section 508
|
Supports | The product conveys information, structure, and relationships by accessible methods. Data tables use header cells with scope; form fields are grouped with fieldsets, radio groups or labelled sections; headings are real heading elements; decorative icons are hidden from assistive technology. |
|
1.3.2 Meaningful Sequence (Level A)
Also applies to:
Revised Section 508
|
Supports | The correct reading sequence is meaningful throughout the product. |
|
1.3.3 Sensory Characteristics (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not rely on sensory characteristics for instructions |
|
1.4.1 Use of Color (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not rely on color-alone to convey information. |
|
1.4.2 Audio Control (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not have audio content. |
|
2.1.1 Keyboard (Level A)
Also applies to:
Revised Section 508
|
Supports | All functionality is accessible using the keyboard only throughout the product. Skill reordering can be done with Move up / Move down buttons as well as drag and drop. |
|
2.1.2 No Keyboard Trap (Level A)
Also applies to:
Revised Section 508
|
Supports | There are no keyboard traps present in the product. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) | Supports | The product does not provide character key shortcuts. |
|
2.2.1 Timing Adjustable (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not include content with a timeout. |
|
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not have content that blinks, scrolls, or updates regularly. |
|
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not have flashing content. |
|
2.4.1 Bypass Blocks (Level A)
Also applies to:
Revised Section 508
|
Supports | The product provides a shortcut to bypass the header navigation. A skip link is present on the signed-in and public layouts and moves focus to the main content. |
|
2.4.2 Page Titled (Level A)
Also applies to:
Revised Section 508
|
Supports | Pages are properly titled. |
|
2.4.3 Focus Order (Level A)
Also applies to:
Revised Section 508
|
Supports | The product has a meaningful focus order. |
|
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
Revised Section 508
|
Supports | The product has meaningful link phrases. Repeated Edit / View links include the item name in text available to assistive technology. |
| 2.5.1 Pointer Gestures (Level A 2.1 only) | Supports | The product does not use multipoint or path-based gestures for operation. |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) | Supports | The product does not execute any functionality on the down-event of the pointer. |
| 2.5.3 Label in Name (Level A 2.1 only) | Supports | The product presents user interface components whose accessible name contains the text presented visually. |
| 2.5.4 Motion Actuation (Level A 2.1 only) | Supports | The product does not contain user interface components that require device or user motion. |
|
3.1.1 Language of Page (Level A)
Also applies to:
Revised Section 508
|
Supports | The product identifies the default language of the page. |
|
3.2.1 On Focus (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not cause a change of context on focus. |
|
3.2.2 On Input (Level A)
Also applies to:
Revised Section 508
|
Supports | The product does not cause a change of context when interacting with elements. |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | Help and contact mechanisms (Site Map, Report an accessibility problem, Privacy complaints and disputes, and the Contact link) appear in the same place, the page footer, on every page. |
|
3.3.1 Error Identification (Level A)
Also applies to:
Revised Section 508
|
Supports | If an input error is detected in the product, the error is described to the user in text. |
|
3.3.2 Labels or Instructions (Level A)
Also applies to:
Revised Section 508
|
Supports | The product has labels for form controls. Required fields are marked with an asterisk that is explained on the page, and also carry aria-required. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | Within a process, information users have already provided is carried forward or can be selected (for example saved internship supervisor contacts and dates); users are not asked to re-enter it. |
|
4.1.1 Parsing (Level A)
Also applies to:
Revised Section 508
|
Supports | Duplicate and empty id attributes found during the November 2026 audit were removed. No known parsing errors affect assistive technology. (4.1.1 is obsolete in WCAG 2.2 and is kept because Revised Section 508 incorporates WCAG 2.0.) |
|
4.1.2 Name, Role, Value (Level A)
Also applies to:
Revised Section 508
|
Supports | The product provides the correct name, role, state, and other important accessibility information for user interface components. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.2.4 Captions (Live) (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product does not have live audio content. |
|
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
Revised Section 508
|
Supports | There are 3 instructional videos provided for the program director that have closed captioning available on YouTube. Links are provided. |
|
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
Revised Section 508
|
Supports | The product supports change in orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) | Supports | The purpose of the input fields can be determined via programmatically associated labels on the product. Name and email fields on the user preferences page carry autocomplete tokens. |
|
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product has sufficient contrast between the foreground and background colors. Help text, outline buttons, report notes and call-to-action buttons were darkened in November 2026 to meet 4.5:1. |
|
1.4.4 Resize text (Level AA)
Also applies to:
Revised Section 508
|
Supports | Pages render properly with browser zoom functionality. |
|
1.4.5 Images of Text (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product does not contain images of text. |
| 1.4.10 Reflow (Level AA 2.1 only) | Supports | Pages reflow to a single column at 320 CSS pixels. Wide data tables scroll horizontally inside their own container, which is permitted for data tables. |
| 1.4.11 Non-text Contrast (Level AA 2.1 only) | Supports | The program presents user interface components and graphical objects that meet the minimum contrast ratio. Form control and checkbox borders are at least 3:1 (#7a858d) against the page. |
| 1.4.12 Text Spacing (Level AA 2.1 only) | Supports | The product does not present text where content or functionality are lost when setting custom spacing. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) | Supports | The product does not contain controls that become visible on pointer hover or keyboard focus. |
|
2.4.5 Multiple Ways (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product supports multiple ways of locating screens. Standard navigation plus a full sitemap is available. |
|
2.4.6 Headings and Labels (Level AA)
Also applies to:
Revised Section 508
|
Supports | Headings and labels for the form controls are descriptive. Heading structure follows proper hierarchy. |
|
2.4.7 Focus Visible (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product provides a visible focus indicator for all actionable elements. Focus is shown with a 2px black outline, and a white outline on dark surfaces such as table headers and call-to-action banners. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | Fixed bottom Save bars and sticky table headers do not hide the control that has keyboard focus. The page reserves space under fixed bars and scrolls a focused control clear of them. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Supports | Skill reordering by drag and drop has a single-pointer alternative: Move up and Move down buttons. No other function requires dragging. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | Interactive targets are at least 24 by 24 CSS pixels, or meet the spacing or equivalent-control exceptions (for example table sort labels and footer links). |
|
3.1.2 Language of Parts (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product does not contain changes in language. |
|
3.2.3 Consistent Navigation (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product uses consistent navigation methods. |
|
3.2.4 Consistent Identification (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product consistently identifies components that have the same functionality. |
|
3.3.3 Error Suggestion (Level AA)
Also applies to:
Revised Section 508
|
Supports | Where input errors are automatically detected, suggestions for correction are provided to the user. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
Revised Section 508
|
Supports | The product does not make legal or financial commitments |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | Sign-in uses an email address and password, or the institution's single sign-on. There are no cognitive function tests, and pasting and password managers are supported. |
| 4.1.3 Status Messages (Level AA 2.1 only) | Supports | Dynamic updates such as quick-select counts and skill reorder results are announced through status regions. Static call-out boxes are not live regions. |
Table 3: Success Criteria, Level AAA
Notes: Not Evaluated for Level AAA
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | The product uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies. |
| 302.2 With Limited Vision | Supports | The product 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 | Supports | The product does not include audio-only features that require hearing to be used. Where audio is available, captions are provided. |
| 302.5 With Limited Hearing | Supports | The product does not include audio-only features that require hearing to be used. |
| 302.6 Without Speech | Not Applicable | The product does not require speech input. |
| 302.7 With Limited Manipulation | Supports | The product 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 | Does Not Support |
Chapter 4: Hardware
Notes: The product 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.2 section | See information in WCAG 2.2 section. |
| 502 Interoperability with Assistive Technology | Heading cell – no response required | Heading cell – no response required |
| 502.2.1 User Control of Accessibility Features | Not Applicable | The product is not considered a platform software defined by section 508. |
| 502.2.2 No Disruption of Accessibility Features | Supports | The product is compatible with operating system and browser accessibility features configured by the user. |
| 502.3 Accessibility Services | Heading cell – no response required | Heading cell – no response required |
| 502.3.1 Object Information | Supports | The product uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “ariarequired” attributes. |
| 502.3.2 Modification of Object Information | Supports | The product uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
| 502.3.3 Row, Column, and Headers | Supports | See WCAG 2.2 1.3.1 Info and Relationships (Level A) |
| 502.3.4 Values | Supports | The product uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.5 Modification of Values | Supports | The product uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.6 Label Relationships | Supports | The product uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes. |
| 502.3.7 Hierarchical Relationships | Supports | The product uses standard HTML markup to express hierarchical relationships. |