UsableNet AQA

Accessibility conformance summary

FAEIS Information Site

Team: Virginia Tech - College of Agriculture and Life Sciences
Type of test: web accessibility
Standard: WCAG 2.1 AA (filtered)

Jul 3, 2023 - 8:16 am EDT

Table of contents

1. Conformance improvement history

Improvement is calculated by comparing the most recent results with the oldest ones.
Recurring issues are calculated by comparing current results with oldest ones.
Issues breakdown by user journey
1 - Full Site Crawl page collection, 264 pages grouped in 8 batches
Date Low severity issues Med. severity issue High severity issues Recurring issues Total issues
Jun 30, 2023 3:15 pm EDT 0 8 2 0 10
Jun 30, 2023 2:49 pm EDT 0 154 3 15 157
Mar 10, 2023 9:43 am EST 6 565 28 599
Improvement 100.0% 98.5% 92.8% 98.3%

2. Conformance overview based on WCAG 2.1 AA (filtered) standard

Overall conformance

1 user journey | 10 issues to fix

  • 89% Passed
    41 Success Criteria
  • 11% Failed
    5 Success Criteria

This section show which WCAG 2.1 AA (filtered) Success Criteria failed across the entire scope and communicates the broad issues that will needed to be understood and remedied.

Principle 1: Perceivable
Needs fix ( 2 )
  1. 1.1.1
  2. 1.2.1
  3. 1.2.2
  4. 1.2.3
  5. 1.2.4
  6. 1.2.5
  7. 1.3.1
  8. 1.3.2
  9. 1.3.3
  10. 1.3.5
  11. 1.4.1
  12. 1.4.2
  13. 1.4.3
  14. 1.4.4
  15. 1.4.5
  16. 1.4.10
  17. 1.4.11
  18. 1.4.12
  19. 1.4.13
Principle 2: Operable
Needs fix ( 6 )
  1. 2.1.1
  2. 2.1.2
  3. 2.1.4
  4. 2.2.1
  5. 2.2.2
  6. 2.3.1
  7. 2.4.1
  8. 2.4.2
  9. 2.4.3
  10. 2.4.4
  11. 2.4.5
  12. 2.4.6
  13. 2.4.7
  14. 2.5.2
  15. 2.5.3
Principle 3: Understandable
Needs fix ( 0 )
  1. 3.1.1
  2. 3.1.2
  3. 3.2.1
  4. 3.2.2
  5. 3.2.3
  6. 3.2.4
  7. 3.3.1
  8. 3.3.2
  9. 3.3.3
Principle 4: Robust
Needs fix ( 2 )
  1. 4.1.1
  2. 4.1.2
  3. 4.1.3

Code quality

Average A11Y Score
99.8%
4592/4600

The average A11Y Score is the sum of all the score results and divided by the number of the evaluated user journeys. It represents a basic indicator of the overall code quality across the scope of the test.

Remediation focus
  • 10 total issues to fix
  • 2 issues have a high impact on the site's user experience
  • Full Site Crawl is the user journey where high severity issues are more concentrated
  • Full Site Crawl is the user journey with the highest number of issues

3. Failed Criteria Data Breakdown

Success criteria A11Y score Issues to fix High severity issues
1.4.11: Non-Text Contrast 100 2
2.1.1: Keyboard 98 2
2.4.7: Focus Visible 98 2 2
2.5.2: Pointer Cancellation 98 2
4.1.3: Status Messages 98 2

4. Issue classification by check type

Semi-automated 10
Automated 0
Manual 0
Total 10

5. Issue classification by responsibility

Development 8
Design 2
Content 0
Total 10

6. Issues overview by severity and complexity

Low severity Medium severity High severity Total
Easy complexity 0 0 0 0
Average complexity 0 8 2 10
Hard complexity 0 0 0 0
Total 0 8 2 10
Breakdown by Severity
Breakdown by Complexity

7. In-scope user journeys

  • page collection
    Full Site Crawl
    Entry point URL:
    https://faeis.cals.vt.edu/
    User journey ID:
    T126361
    Device:
    Chrome 102 (Windows), standard 1280 x 800
    No. of pages:
    264

8. Testing results

User journey Review status Conformance [1] A11y score [2] Issues to fix
Full Site Crawl 100% reviewed
Passed: 41
Failed: 5
99.8%
very high
4593/4600
 10

[1] Depending on the current review status, the Conformance column displays the temporary or final state of Success Criteria for each tested user journey. For WCAG 2.1 AA (filtered) standard (used in this test), there are 46 Success Criteria you can find listed as passed, pending review or failed. ↩

[2] The A11Y Score of each evaluated user journey may fall into one of the following levels: ↩
  • Estimated ( Not reviewed )
  • Very low ( < 40% )
  • Low ( 41% – 55% )
  • Medium ( 56% – 75% )
  • High ( 76% – 95% )
  • Very high ( 96% – 100% )

9. Fixes needed by user journey

User journey Issues to fix Severity Complexity
low medium high easy average hard
1
Full Site Crawl
 10 0 8 2 0 10 0

10. Definitions

Check type
Issue check type indicates how the issue was created and reviewed.
Automated
These issues were generated by UsableNet AQA's own issue detection process resulting in a "need fix" status.
Semi-automated
These issues were first detected by UsableNet AQA's own detection process as an element that could be an issue or has to be checked manually due to its nature, resulting in a "check manually" initial status. Subsequently, a human has reviewed the item and updated it to a "need fix" status.
Manual
These issues were created by a human reviewer using a range of manual review processes and given a "need fix" status.
Responsibility
Responsibility describes which team / department or competence should be involved to solve the issue.
Content
These issues are related to the text content and text alternatives in the web page.
Design
These issues are related to the design decision made on visual aspect of the web page components across whole site structure.
Development
These issues are related to the way web page structure and functionalities have been implemented.
Severity
The issues severity has been classified under three levels, depending on the impact it has on the user.
High
These issues should be considered as the most dangerous for Web Accessibility, since they are including defects which drastically impact the navigation and can be treated as blocker issues for assistive technology used by a big part of users (e.g. screen readers, braille displays, etc...).
Medium
This level of severity includes all those issues that break in a moderate way the website navigation; they often include informative attributes missing in the page content, which could be helpful for users in order to better understand what they are looking at.
Low
These issues don't affect in a huge way the site navigation, but they could be relevant in order to let the user understand all the information included into website's pages appropriately.
Complexity
The classification of fixes complexity has been done under three levels, depending on the general approach developers should have in order to provide the correct fix to the defect. These values are partially subjective, since they could depend on the framework used, third parts involved and readiness client has got to interact with the site code, e.g. CMS (Content Management System).
Hard
Issues with this level of complexity may be very hard to resolve (in terms of time and resources), generally because the features affected by these issues are framework-related and the development team should significantly change (or, in the worst case, entirely re-build) their implementation; an example could be provided looking at those actions executed in asynchronous mode, instead of using synchronous (or predictable) technologies, such as server-side computations.
Average
This level of complexity includes all those issues that will take some level of understanding to resolve and affect the website navigation or informative attributes missing in the page content, which are used by users in order to better understand what they are looking at.
Easy
The challenge to fix this kind of issue is quite low and should not take much time to provide the solution/ workaround; most typical issues included in this category are concerning easy data management, information that could be presented to the user in a more accessible way and content which can be improved with quick fixes.

11. Success criteria

Principle 1: Perceivable

1.1.1: Non-text Content

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A)

1.2.1: Audio-only and Video-only (Prerecorded)

For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)

  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

1.2.2: Captions (Prerecorded)
1.3.1: Info and Relationships
1.3.2: Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined . (Level A)

1.3.3: Sensory Characteristics

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

1.3.5: Identify Input Purpose

The purpose of each input field collecting information about the user can be programmatically determined when:

(Level AA)

1.4.1: Use of Color

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)

1.4.2: Audio Control

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

1.4.3: Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4. 5:1, except for the following: (Level AA)

1.4.4: Resize text

Except for captions and images of text , text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)

1.4.5: Images of Text

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)

Note: Logotypes (text that is part of a logo or brand name) are considered essential.

1.4.10: Reflow

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

  • Vertical scrolling content at a width equivalent to 320 CSS pixels;
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning.

1.4.11: Non-Text Contrast

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

User Interface Components
Visual information required to identify user interface components and states , except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
Graphical Objects
Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.

(Level AA)

1.4.12: Text Spacing

In content implemented using markup languages that support the following text style properties , no loss of content or functionality occurs by setting all of the following and by changing no other style property:

  • Line height (line spacing) to at least 1.5 times the font size;
  • Spacing following paragraphs to at least 2 times the font size;
  • Letter spacing (tracking) to at least 0.12 times the font size;
  • Word spacing to at least 0.16 times the font size.

Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.

(Level AA)

1.4.13: Content on Hover or Focus

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

Dismissable
A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
Hoverable
If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
Persistent
The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.

Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute .

Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.

(Level AA)

Principle 2: Operable

2.1.1: Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

2.1.2: No Keyboard Trap

If keyboard focus can be moved to a component of the page using a keyboard interface , then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

2.1.4: Character Key Shortcuts

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

Turn off
A mechanism is available to turn the shortcut off;
Remap
A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
Active only on focus
The keyboard shortcut for a user interface component is only active when that component has focus.

(Level A)

2.2.1: Timing Adjustable

For each time limit that is set by the content, at least one of the following is true: (Level A)

  • Turn off: The user is allowed to turn off the time limit before encountering it; or

  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or

  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or

  • 20 Hour Exception: The time limit is longer than 20 hours.

2.2.2: Pause, Stop, Hide

For moving, blinking , scrolling, or auto-updating information, all of the following are true: (Level A)

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause , stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential ; and

  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

2.3.1: Three Flashes or Below Threshold

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds . (Level A)

2.4.1: Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages . (Level A)

2.4.2: Page Titled

Web pages have titles that describe topic or purpose. (Level A)

2.4.3: Focus Order

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

2.4.4: Link Purpose (In Context)

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

2.4.5: Multiple Ways

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 . (Level AA)

2.4.6: Headings and Labels

Headings and labels describe topic or purpose. (Level AA)

2.4.7: Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

2.5.2: Pointer Cancellation

For functionality that can be operated using a single pointer , at least one of the following is true:

No Down-Event
The down-event of the pointer is not used to execute any part of the function;
Abort or Undo
Completion of the function is on the up-event , and a mechanism is available to abort the function before completion or to undo the function after completion;
Up Reversal
The up-event reverses any outcome of the preceding down-event;
Essential
Completing the function on the down-event is essential .

Functions that emulate a keyboard or numeric keypad key press are considered essential.

This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

(Level A)

2.5.3: Label in Name

For user interface components with labels that include text or images of text , the name contains the text that is presented visually. (Level A)

A best practice is to have the text of the label at the start of the name.

Principle 3: Understandable

3.1.2: Language of Parts

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. (Level AA)

3.2.1: On Focus

When any component receives focus, it does not initiate a change of context . (Level A)

3.2.2: On Input

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

3.2.3: Consistent Navigation

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. (Level AA)

3.2.4: Consistent Identification

Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

3.3.1: Error Identification

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

3.3.2: Labels or Instructions

Labels or instructions are provided when content requires user input. (Level A)

3.3.3: Error Suggestion

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. (Level AA)

Principle 4: Robust

4.1.1: Parsing

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

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

4.1.3: Status Messages

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. (Level AA)

12. References