REQUEST MORE INFO
Speak With a Live Admissions Advisor:
865-322-9919 | Mon-Fri 9am to 6pm Local TimeAt The University of Tennessee Knoxville, we are committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and applying the relevant accessibility standards.
The University of Tennessee Knoxville takes the following measures to ensure accessibility of The University of Tennessee Knoxville:
The Web Content
Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
The University of Tennessee Knoxville is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
In addition to WCAG requirements The University of Tennessee Knoxville also conformes to Section 508.
We welcome your feedback on the accessibility of The University of Tennessee Knoxville. Please let us know if you encounter accessibility barriers on The University of Tennessee Knoxville:
E-mail: accessibility@quickstart.com
The University of Tennessee Knoxville is designed to be compatible with the following assistive technologies:
The University of Tennessee Knoxville is not compatible with:
Accessibility of The University of Tennessee Knoxville relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
These technologies are relied upon for conformance with the accessibility standards used.
Despite our best efforts to ensure accessibility of The University of Tennessee Knoxville, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.
The University of Tennessee Knoxville Learning, Inc. assessed the accessibility of The University of Tennessee Knoxville by the following approaches:
Name of Product/Version: The University of Tennessee Knoxville v1.0
Report Date: Nov 2022
Product Description: Funnel Marketing website template for Universities
Contact information: accessibility@quickstart.com
Notes: Remain transparent to your shareholders, users, visitors, etc… of your
current WCAG/508 Level AA status during your evaluation and remediation process.
Evaluation Methods Used: This product was evaluated using an automated script,
manual testing, and the Trusted Tester process.
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 | Level A
(Yes) Level AA (Yes) Level AAA (No) |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | (Yes) |
Table Information for VPAT® Readers
For each of the standards, the criteria are listed by chapter in a table. The structures of the
tables are: the first column contains the
criteria being evaluated, the second column describes the level of conformance of the product
regarding the criteria and the third
column contains any additional remarks and explanations regarding the product.
Terms
The terms used in the Conformance Level information are defined as follows:
WCAG 2.0 Report
Tables 1 and 2 also document conformance with Revised Section 508:
Notes: 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.
| Criteria | Conformance Level | Remarks & Explanations | |
|---|---|---|---|
| 1.1.1 Non-text
Content (Level
A) Also applies to: Revised Section 508
|
Supports | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. | |
| 1.2.1
Audio-only and
Video-only (Prerecorded) (Level A) Also applies to: Revised Section 508
|
Supports | Not Required | |
| 1.2.2
Captions
(Prerecorded) (Level A) Also applies to: Revised Section 508
|
Does Not Apply | The multimedia provides accurate captions for the audio content. | |
| 1.2.3
Audio Description
or Media Alternative
(Prerecorded) (Level A) Also applies to: Revised Section 508
|
Supports | An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | |
| 1.2.4 Captions
(Live) (Level AA) Also applies to: Revised Section 508
|
Does Not Apply | There is no live video or audio. | |
| 1.2.5 Audio
Description (Prerecorded) (Level AA) Also applies to: Revised Section 508
|
Does Not Apply | There is no synchronized media. | |
| 1.3.1
Info and Relationships (Level A) Also applies to: Revised Section 508
|
Supports | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | |
| 1.3.2
Meaningful Sequence (Level A) Also applies to: Revised Section 508
|
Supports | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | |
| 1.3.3
Sensory Characteristics (Level A) Also applies to: Revised Section 508
|
Supports | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. | |
| 1.4.1
Use of Color (Level A) Also applies to: Revised Section 508
|
Supports | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | |
| 1.4.2 Audio
Control (Level A) Also applies to: Revised Section 508
|
Supports | If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | |
| 1.4.3 Contrast
(Minimum) (Level AA) Also applies to: Revised Section 508
|
Supports | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. | |
| 1.4.4 Resize
text (Level AA) Also applies to: Revised Section 508
|
Supports | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | |
| 1.4.5
Images of
Text (Level AA) Also applies to: Revised Section 508
|
Supports | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text. | |
| 2.1.1
Keyboard (Level A) Also applies to: Revised Section 508
|
Supports | The content is operable through a keyboard interface without requiring specific timings. | |
| 2.1.2 No Keyboard
Trap (Level A) Also applies to: Revised Section 508
|
Supports | Keyboard focus can be moved to a component of the page using a keyboard interface, and can be moved away from that component using only a keyboard interface. | |
| 2.2.1 Timing
Adjustable (Level A) Also applies to: Revised Section 508
|
Does Not Apply | For each time limit that is set by the content. | |
| 2.2.2 Pause,
Stop, Hide (Level A) Also applies to: Revised Section 508
|
Does Not Apply | For moving, blinking, scrolling, or auto-updating information. | |
| 2.3.1
Three Flashes or
Below Threshold (Level A) Also applies to: Revised Section 508
|
Does Not Apply | If NO flashing content is found, then this Test Condition DOES NOT APPLY (DNA). If flashing content IS found, then this test should be recorded as NOT TESTED. | |
| 2.4.1 Bypass
Blocks (Level A) Also applies to: Revised Section 508
|
Supports | A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | |
| 2.4.2 Page
Titled (Level A) Also applies to: Revised Section 508
|
Supports | Web pages have titles that describe topic or purpose. | |
| 2.4.3 Focus
Order (Level A) Also applies to: Revised Section 508
|
Supports | If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | |
| 2.4.4 Link Purpose
(In Context) (Level A) Also applies to: Revised Section 508
|
Supports | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | |
| 2.4.5 Multiple
Ways (Level AA) Also applies to: Revised Section 508
|
Does Not Apply | More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | |
| 2.4.6 Headings
and Labels (Level AA) Also applies to: Revised Section 508
|
Support | Headings and labels describe topic or purpose. | |
| 2.4.7 Focus
Visible (Level AA) Also applies to: Revised Section 508
|
Support | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | |
| 3.1.1
Language of Page (Level A) Also applies to: Revised Section 508
|
Support | The default human language of each Web page can be programmatically determined. | |
| 3.1.2
Language of Parts (Level AA) Also applies to: Revised Section 508
|
Does Not Apply | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | |
| 3.2.1 On
Focus (Level A) Also applies to: Revised Section 508
|
Supports | When any component receives focus, it does not initiate a change of context. | |
| 3.2.2
On Input (Level A) Also applies to: Revised Section 508
|
Supports | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | |
| 3.2.3
Consistent Navigation (Level AA) Also applies to: Revised Section 508
|
Supports | Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. | |
| 3.2.4
Consistent Identification (Level AA) Also applies to: Revised Section 508
|
Supports | Components that have the same functionality within a set of Web pages are identified consistently. | |
| 3.3.1
Error
Identification (Level A) Also applies to: Revised Section 508
|
Supports | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | |
| 3.3.2
Labels or
Instructions (Level A) Also applies to: Revised Section 508
|
Supports | Labels or instructions are provided when content requires user input | |
| 3.3.3 Error
Suggestion (Level AA) Also applies to: Revised Section 508
|
Supports | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | |
| 3.3.4
Error
Prevention (Legal, Financial, Data) (Level AA) Also applies to: Revised Section 508
|
Supports | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses. | |
| 4.1.1
Parsing (Level A) Also applies to: Revised Section 508
|
Not Evaluated | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. | |
| 4.1.2 Name,
Role, Value (Level A) Also applies to: Revised Section 508
|
4.1.2 Name, Role, Value | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. | |
Revised Section 508 Report
Notes:
Chapter 3: Functional
Performance Criteria (FPC)
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | ||
| 302.2 With Limited Vision | ||
| 302.3 Without Perception of Color | ||
| 302.4 Without Hearing | ||
| 302.5 With Limited Hearing | ||
| 302.6 Without Speech | ||
| 302.7 With Limited Manipulation | ||
| 302.8 With Limited Reach and Strength | ||
| 302.9 With Limited Language, Cognitive, and Learning Abilities |
An Accessibility Audit was competed by Certified Accessibility Developer at
Kaffeinated Kodemonkey on February 2023 in accordance
with WCAG/508 2.1 Level AA. The Certified A11y Develpper completed the ACR as
part of a POC Certification.
The ACR demonstrates the level of compliance, status of each criteria, date of
Accessibility Audit, and works in conjunction with the
Accessibility Statement to explain why a component may or/may not be compliant.
While the Accessibility Statement explains in further
detail how the client is currently handling the issue(s).
A POC Certification includes the following documents:
Due to code revisions, documents, and standard updates, it is nearly impossible to reach 100% compliance. Therefore Quick Start is committed to working with an accessibility agency to monitor accessibility and stay compliant
Kaffeinated Kodemonkey
Heather Welsh | Accessibility Developer
Trusted Tester #TT-2311-03604
IAAP Professional Member
