Fifth Asset, Inc. Accessibility Conformance Report, WCAG Edition

(Based on VPAT® Version 2.5)

Name of Product/Version
DebtBook v.1.141.0
Report Date
Sep 18, 2024 10:14 am EDT
Product Description

DebtBook is a leading cloud-based software platform designed to help finance teams in government, higher education, and healthcare sectors manage their financial obligations more accurately and efficiently. DebtBook streamlines debt, lease, subscription, and cash management by replacing manual processes with automated, digital workflows, allowing organizations and their external partners to easily track, manage, and report on financial data while ensuring compliance with accounting standards.

DebtBook's platform offers a suite of integrated products that address key areas of public finance, used by both internal finance teams and external professional partners such as accounting firms, legal counsel, municipal advisors, and other financial experts:

  1. Debt Management: Provides finance teams and their advisors with tools to manage, track, and report on debt obligations in real-time, ensuring accurate records and comprehensive reporting.
  2. Lease and Subscription Management: This product simplifies the tracking and reporting of leases and subscriptions, ensuring compliance with new accounting standards like GASB 87, 96, and 94. It allows both finance teams and external auditors to manage lease and subscription contracts efficiently, reducing the risk of errors in financial reporting.
  3. Cash Management: Gives users the ability to manage and forecast cash flow, providing real-time insights into liquidity. Finance teams and their external partners can collaborate more effectively on cash reserves and optimize investment strategies.
  4. Sizing: Assists finance teams and their financial advisors in modeling and analyzing future debt issuances, allowing them to plan effectively and make data-driven decisions about funding capital projects.
  5. Disclosure Management: Enables organizations and their legal counsel to manage and track their continuing disclosure obligations, ensuring compliance with regulatory requirements and reducing the risk of penalties for non-compliance.

DebtBook helps organizations increase transparency, improve accuracy, and enhance collaboration between internal teams and external partners by providing a centralized platform for managing all financial obligations. This comprehensive suite of products ensures that finance teams, along with their professional advisors, have the tools they need to manage financial obligations efficiently and effectively.

Contact Information
For questions or inquiries regarding accessibility, please contact us at: accessibility@debtbook.com
Notes

We evaluated “DebtBook v.1.141.0" accessibility by considering the following user flows:

  • Dashboard and Global Elements
  • Add Member
  • Bank Free Analysis
  • Agreements
  • Sign In
  • Profile Summary
  • Bucket View
  • Issue Detail

The following recurring components were also identified across the user journeys:

  • Header
  • Navigation
Evaluation Methods Used
  • TBT (Tool-Based Testing): UsableNet AQA automatic evaluations
  • ATP (Assistive Technology Previews): UsableNet AQA tools helping manual tests grayscale, text spacing, accessibility labels
  • MAT (Manual Accessibility Testing): Keyboard testing with visual focus; Videos; Screen Reader Testing; Inspection

Applicable Standards/Guidelines

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

Applicable Standards/Guidelines table
Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.0 Level A (Yes)
Level AA (Yes)
Level AAA (No)
Web Content Accessibility Guidelines 2.1 Level A (Yes)
Level AA (Yes)
Level AAA (No)
Web Content Accessibility Guidelines 2.2 Level A (Yes)
Level AA (Yes)
Level AAA (No)

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 only be used in WCAG Level AAA criteria.

WCAG 2.x Report

Note: When reporting on conformance with the WCAG 2.x 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

WCAG 2.x Success Criteria, Level A
Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content
(Level A) 		Partially Supports

Test methods: TBT; MAT

"Navigation" recurring component does not completely support this criterion:
  • Form control doesn't have an accessible name
"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Informative SVG element is marked as decorative
  • SVG element without alternative
"Add Member" user flow does not completely support this criterion:
  • Button without text
  • Form control accessible name is not meaningful
  • SVG element without alternative
"Bank Free Analysis" user flow does not completely support this criterion:
  • Button without text
  • Form control accessible name is not meaningful
  • Form control doesn't have an accessible name
  • Informative SVG element is marked as decorative
  • SVG element without alternative
"Agreements" user flow does not completely support this criterion:
  • SVG element without alternative
"Profile Summary" user flow does not completely support this criterion:
  • Button without text
  • Form control doesn't have an accessible name
  • SVG element without alternative
"Bucket View" user flow does not completely support this criterion:
  • Button without text
  • Form control accessible name is not meaningful
  • Form control doesn't have an accessible name
  • SVG element without alternative
"Issue Detail" user flow does not completely support this criterion:
  • "Edit" fields do not have an accessible name
  • Button without text
  • Form control accessible name is not meaningful
  • Form control doesn't have an accessible name
  • SVG element without alternative
1.2.1 Audio-only and Video-only (Prerecorded)
(Level A) 		Not Applicable

Test methods: TBT

The analyzed pages don't contain prerecorded audio-only or prerecorded video-only media.
1.2.2 Captions (Prerecorded)
(Level A) 		Not Applicable

Test methods: TBT

The analyzed pages don't contain prerecorded audio content.
1.2.3 Audio Description or Media Alternative (Prerecorded)
(Level A) 		Not Applicable

Test methods: TBT

The analyzed pages don't contain prerecorded videos.
1.3.1 Info and Relationships
(Level A) 		Partially Supports

Test methods: TBT; ATP; MAT

"Header" recurring component does not completely support this criterion:
  • Element with aria-describedby attribute refers to a missing element
  • Incorrect parent element in list
  • User interface component without accessible name and aria-labelledby attribute referring to a missing element
"Navigation" recurring component does not completely support this criterion:
  • Form control is not associated with a text label
"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Carousel is not accessible
  • Date picker is not accessible
  • Elements not in a list
  • Fly-out overall structure is not appropriate
  • H3 element has been used for visual effect
  • Incorrect parent element in list
  • Keyboard pattern should be improved
  • Level two heading missing
  • Listbox options are "infinitively" loaded
  • Main navigation is not implemented correctly
  • Milestones timeline is not accessible
  • Modal dialog is missing an accessible name
  • Navigation landmark needs an accessible name
  • Required fields are not programmatically determined
  • Tabs are used for navigation
  • Tooltip is not accessible
"Add Member" user flow does not completely support this criterion:
  • An input with accessible name given by placeholder attribute but without any associated LABEL element
  • Aside navigation is not implemented correctly
  • Avatar is exposed to assistive technologies
  • Definition list not exposed correctly
  • Duplicated ID attribute value
  • Element with aria-describedby attribute refers to a missing element
  • Incorrect child element in list
  • Incorrect parent element in list
  • Missing headings in the page
  • Named list is not clear
  • Order of headings is not correct
  • Separator element is used for layout purposes
  • Table header contains no text
  • Table rows are "infinitively" loaded
  • Tabs are not appropriate
  • Tooltip is not accessible
"Bank Free Analysis" user flow does not completely support this criterion:
  • "No data" text is clearer than long dash symbol
  • "Show details" drawer is not implemented as a modal dialog
  • Aside navigation is not implemented properly
  • Bulk actions container should be a landmark
  • Categories navigation is not implemented properly
  • Content is not structured
  • Drawer must be implemented as a modal dialog
  • Duplicated ID attribute value
  • Element with aria-describedby attribute refers to a missing element
  • Element without accessible name and aria-labelledby attribute referring to a missing element
  • Fields are not grouped
  • Form control is not associated with a text label
  • H1 element has been used for visual effect
  • H3 element has been used for visual effect
  • Incorrect child element in list
  • Incorrect parent element in list
  • LABEL element is not associated to a form control
  • Main content area's structure must be improved
  • Modal dialog implementation must be improved
  • Navigation landmarks must be improved
  • Order of headings is not correct
  • Pagination is not labelled
  • Secondary navigation is not implemented correctly
  • Single transactions need a proper reference inside the table
  • Sortable table is not fully accessible
  • Tab implementation is not totally appropriate
  • Table header contains no text
  • Tabs are used for navigation
  • Tooltip is not accessible
"Agreements" user flow does not completely support this criterion:
  • Definition list not exposed correctly
  • History section must be improved
  • Order of headings is not correct
  • Tabs are not implemented correctly
"Sign In" user flow does not completely support this criterion:
  • An input with accessible name given by placeholder attribute but without any associated LABEL element
  • Duplicated ID attribute value
  • Missing headings in the page
"Profile Summary" user flow does not completely support this criterion:
  • Date picker is not accessible
  • Drawer should be implemented as a modal dialog
  • Elements not in a list
  • Form control is not associated with a text label
  • Initial step is exposed to assistive technologies
  • LABEL element is not associated to a form control
  • Missing headings in the page
  • Selected issues bottom panel needs an accessible name
  • Symbol is exposed to assistive technologies
  • Table header contains no text
  • Tabs are not implemented correctly
"Bucket View" user flow does not completely support this criterion:
  • Carousel is not accessible
  • Component should be implemented as a menubar
  • Component should be implemented as a modal dialog
  • Date pickers are not accessible
  • Fields are not grouped
  • Form control is not associated with a text label
  • Missing headings in the page
  • Table header contains no text
  • Tables are not accessible
  • Tooltips are not accessible
"Issue Detail" user flow does not completely support this criterion:
  • Carousel is not accessible
  • Form control is not associated with a text label
  • Milestone timeline is not accessible
  • Missing headings in the page
  • TABLE without TH in a table with scope data
  • Tables are not fully accessible
  • Tabs are not implemented correctly
  • Tooltips are not accessible
1.3.2 Meaningful Sequence
(Level A) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Bank Free Analysis", "Bucket View", "Issue Detail"
  • The order of the content is not in a meaningful sequence
1.3.3 Sensory Characteristics
(Level A) 		Supports

Test methods: TBT; MAT
1.4.1 Use of Color
(Level A) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Bank Free Analysis", "Profile Summary", "Bucket View", "Issue Detail"
  • Links, controls and their statuses can only be identified using color
1.4.2 Audio Control
(Level A) 		Not Applicable

Test methods: TBT

The analyzed pages don't contain audio content.
2.1.1 Keyboard
(Level A) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Bank Free Analysis", "Profile Summary", "Bucket View", "Issue Detail"
  • Functionality is not operable through a keyboard interface
2.1.2 No Keyboard Trap
(Level A) 		Supports

Test methods: TBT; MAT
2.1.4 Character Key Shortcuts
(Level A 2.1 and 2.2) 		Supports

Test methods: TBT; MAT
2.2.1 Timing Adjustable
(Level A) 		Partially Supports

Test methods: MAT

"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Successful milestone creation toast message disappears after a few seconds
"Add Member" user flow does not completely support this criterion:
  • Error toast message disappears after a few seconds
"Bank Free Analysis" user flow does not completely support this criterion:
  • Export data toast message disappears after a few seconds
The following user flows do not fully support this criterion:
"Profile Summary", "Bucket View", "Issue Detail"
  • Toast message disappears after a few seconds
2.2.2 Pause, Stop, Hide
(Level A) 		Partially Supports

Test methods: MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Bank Free Analysis"
  • Infinitively animated visible focus indicator
2.3.1 Three Flashes or Below Threshold
(Level A) 		Supports

Test methods: TBT; MAT
2.4.1 Bypass Blocks
(Level A) 		Partially Supports

Test methods: MAT

"Bank Free Analysis" user flow does not completely support this criterion:
  • A mechanism to bypass the categories navigation is not provided
2.4.2 Page Titled
(Level A) 		Partially Supports

Test methods: TBT; MAT

All user flows do not fully support this criterion:
  • Title is not meaningful
2.4.3 Focus Order
(Level A) 		Does Not Support

Test methods: TBT; ATP; MAT

"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Focus order is not appropriate
  • Focusable components do not receive focus in an order that preserves meaning and operability
The following user flows do not fully support this criterion:
"Add Member", "Bank Free Analysis", "Agreements", "Sign In", "Issue Detail"
  • Focusable components do not receive focus in an order that preserves meaning and operability
"Profile Summary" user flow does not completely support this criterion:
  • Focus is not managed properly
  • Focusable components do not receive focus in an order that preserves meaning and operability
"Bucket View" user flow does not completely support this criterion:
  • Focusable components do not receive focus in an order that preserves meaning and operability
  • Operable control with aria-hidden="true" is keyboard focusable
  • Operable link with aria-hidden="true" is keyboard focusable
2.4.4 Link Purpose (In Context)
(Level A) 		Partially Supports

Test methods: TBT; ATP

"Header" recurring component does not completely support this criterion:
  • Link is not meaningful within the context
  • Links with same text and different locations are not meaningful within the context
The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Sign In", "Profile Summary"
  • Link is not meaningful within the context
"Bank Free Analysis" user flow does not completely support this criterion:
  • Empty link
2.5.1 Pointer Gestures
(Level A 2.1 and 2.2) 		Supports

Test methods: TBT; MAT
2.5.2 Pointer Cancellation
(Level A 2.1 and 2.2) 		Supports

Test methods: TBT; MAT
2.5.3 Label in Name
(Level A 2.1 and 2.2) 		Partially Supports

Test methods: TBT; ATP; MAT

"Header" recurring component does not completely support this criterion:
  • Accessible Name does not contain the visible label of the UI component
The following user flows do not fully support this criterion:
"Add Member", "Bucket View"
  • Accessible Name does not contain the visible label of the form control
"Bank Free Analysis" user flow does not completely support this criterion:
  • Accessible Name does not contain the visible label of the UI component
  • Accessible Name does not contain the visible label of the form control
2.5.4 Motion Actuation
(Level A 2.1 and 2.2) 		Supports

Test methods: TBT; MAT
3.1.1 Language of Page
(Level A) 		Supports

Test methods: TBT; MAT
3.2.1 On Focus
(Level A) 		Supports

Test methods: TBT; MAT
3.2.2 On Input
(Level A) 		Partially Supports

Test methods: MAT

"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Custom dropdown selection causes a change of context
3.2.6 Consistent Help
(Level A 2.2 only) 		Supports

Test methods: TBT; MAT
3.3.1 Error Identification
(Level A) 		Supports

Test methods: TBT; MAT
3.3.2 Labels or Instructions
(Level A) 		Partially Supports

Test methods: TBT; MAT

All recurring components do not fully support this criterion:
  • Labels or instructions don't let users know which input data is expected
The following user flows do not fully support this criterion:
"Add Member", "Bank Free Analysis", "Sign In", "Bucket View"
  • Labels or instructions don't let users know which input data is expected
"Profile Summary" user flow does not completely support this criterion:
  • Issues selection functionality needs proper instructions
3.3.7 Redundant Entry
(Level A 2.2 only) 		Supports

Test methods: TBT; MAT
4.1.2 Name, Role, Value
(Level A) 		Partially Supports

Test methods: TBT; MAT

"Header" recurring component does not completely support this criterion:
  • Control has not been properly managed
"Navigation" recurring component does not completely support this criterion:
  • Control has not been properly managed
  • Form control doesn't have an accessible name
"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Autocomplete custom dropdowns are not accessible
  • Custom dropdown is not accessible
  • Custom select-only dropdown is not accessible
  • Disclosure controls are not accessible
  • Form fields have not got an accessible name
  • The role="menu" is not appropriate for the current element or its descendants are not properly managed
"Add Member" user flow does not completely support this criterion:
  • "Actions" buttons are not accessible
  • Control has not been properly managed
  • Form control doesn't have an accessible name
  • Grid implementation is not appropriate
"Bank Free Analysis" user flow does not completely support this criterion:
  • Accessible name of link can not be programmatically determined
  • Accordions are not accessible
  • Action button is not accessible
  • Actions buttons are not accessible
  • Clickable rows should be implemented with a modal dialog opening control
  • Control has not been properly managed
  • Form control doesn't have an accessible name
  • Sortable table is not accessible
"Agreements" user flow does not completely support this criterion:
  • Control has not been properly managed
"Profile Summary" user flow does not completely support this criterion:
  • Control has not been properly managed
  • Custom combobox with autocomplete is not fully accessible
  • Elements are not implemented as a checkboxes
  • Form control doesn't have an accessible name
"Bucket View" user flow does not completely support this criterion:
  • Aria-hidden="true" attribute has been improperly set to form control
  • Aria-hidden="true" attribute has been improperly set to link
  • Control has not been properly managed
  • Controls should be dropdowns
  • Custom dropdown is not accessible
  • Form control doesn't have an accessible name
"Issue Detail" user flow does not completely support this criterion:
  • "Actions" button is not accessible
  • Control has not been properly managed
  • Custom dropdown is not accessible
  • Disclosure controls are not accessible
  • Form control doesn't have an accessible name

Table 2: Success Criteria, Level AA

WCAG 2.x Success Criteria, Level AA
Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live)
(Level AA) 		Not Applicable

Test methods: TBT

The analyzed pages don't contain live audio content.
1.2.5 Audio Description (Prerecorded)
(Level AA) 		Not Applicable

Test methods: TBT

The analyzed pages don't contain prerecorded videos.
1.3.4 Orientation
(Level AA 2.1 and 2.2) 		Supports

Test methods: TBT; MAT
1.3.5 Identify Input Purpose
(Level AA 2.1 and 2.2) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Add Member", "Sign In"
  • The purpose of input field collecting information about the user is not programmatically determined
1.4.3 Contrast (Minimum)
(Level AA) 		Partially Supports

Test methods: TBT; MAT

"Header" recurring component does not completely support this criterion:
  • Elements without foreground specified
"Dashboard and Global Elements" user flow does not completely support this criterion:
  • Elements without background specified
  • Focused state causes current item's text not to contrast enough
  • Placeholder text does not contrast enough
"Add Member" user flow does not completely support this criterion:
  • Elements without background specified
  • Focused state does not contrast enough
  • Hover style does not contrast enough
  • Placeholder text does not contrast enough
"Bank Free Analysis" user flow does not completely support this criterion:
  • Focused state does not contrast enough
  • Placeholder text does not contrast enough
"Sign In" user flow does not completely support this criterion:
  • Input field does not contrast enough when in error
  • Not enough contrast between text and its background
"Profile Summary" user flow does not completely support this criterion:
  • Elements without background specified
  • Elements without foreground specified
  • Inner text becomes invisible when the control is focused
  • Not enough contrast between text and its background
"Bucket View" user flow does not completely support this criterion:
  • Elements without background specified
  • Elements without foreground specified
"Issue Detail" user flow does not completely support this criterion:
  • Hover style does not contrast enough
  • Not enough contrast between text and its background
1.4.4 Resize text
(Level AA) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Bank Free Analysis", "Profile Summary", "Issue Detail"
  • Resizing visually rendered up to 200 percent causes the text, image or controls to be clipped, truncated, obscured or not resized
1.4.5 Images of Text
(Level AA) 		Supports

Test methods: TBT; MAT
1.4.10 Reflow
(Level AA 2.1 and 2.2) 		Does Not Support

Test methods: TBT; MAT

All user flows do not fully support this criterion:
  • Reflow is not properly working
1.4.11 Non-text Contrast
(Level AA 2.1 and 2.2) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Bank Free Analysis"
  • The contrast ratio of Graphical Objects is not sufficient
  • The contrast ratio of the visual information necessary to indicate state is not sufficient
"Agreements" user flow does not completely support this criterion:
  • The contrast ratio of the visual information necessary to indicate state is not sufficient
"Profile Summary" user flow does not completely support this criterion:
  • The contrast ratio of Graphical Objects is not sufficient
  • The contrast ratio of User Interface Components is not sufficient
The following user flows do not fully support this criterion:
"Bucket View", "Issue Detail"
  • The contrast ratio of Graphical Objects is not sufficient
1.4.12 Text Spacing
(Level AA 2.1 and 2.2) 		Partially Supports

Test methods: TBT; MAT

"Bank Free Analysis" user flow does not completely support this criterion:
  • Loss of content due to text style properties
1.4.13 Content on Hover or Focus
(Level AA 2.1 and 2.2) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Issue Detail"
  • Content on hover or focus is not perceivable
2.4.5 Multiple Ways
(Level AA) 		Supports

Test methods: TBT; MAT
2.4.6 Headings and Labels
(Level AA) 		Partially Supports

Test methods: TBT; ATP; MAT

All recurring components do not fully support this criterion:
  • Button is not meaningful
"Add Member" user flow does not completely support this criterion:
  • Button is not meaningful
  • Empty button
  • Label describing form control is not meaningful
"Bank Free Analysis" user flow does not completely support this criterion:
  • Button is not meaningful
  • Empty button
  • Heading is not meaningful
  • Label describing form control is not meaningful
"Agreements" user flow does not completely support this criterion:
  • Heading is not meaningful
The following user flows do not fully support this criterion:
"Profile Summary", "Bucket View"
  • Button is not meaningful
  • Empty button
"Issue Detail" user flow does not completely support this criterion:
  • Empty button
2.4.7 Focus Visible
(Level AA) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Bank Free Analysis", "Profile Summary", "Bucket View", "Issue Detail"
  • Focus indicator is not visible
2.4.11 Focus Not Obscured (Minimum)
(Level AA 2.2 only) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Bank Free Analysis"
  • Sticky component hiding focused item
"Add Member" user flow does not completely support this criterion:
  • "Actions" fly-out obscures focused element
  • Sticky component hiding focused item
"Bucket View" user flow does not completely support this criterion:
  • Additional filters fly-out obscures focused item
"Issue Detail" user flow does not completely support this criterion:
  • Disclosed content obscures focused item
2.5.7 Dragging Movements
(Level AA 2.2 only) 		Not Applicable

Test methods: TBT

The analyzed pages don't implement drag and drop features.
2.5.8 Target Size (Minimum)
(Level AA 2.2 only) 		Partially Supports

Test methods: TBT; MAT

"Bank Free Analysis" user flow does not completely support this criterion:
  • The form control target size is too small
3.1.2 Language of Parts
(Level AA) 		Supports

Test methods: TBT; MAT
3.2.3 Consistent Navigation
(Level AA) 		Supports

Test methods: TBT; MAT
3.2.4 Consistent Identification
(Level AA) 		Supports

Test methods: TBT; MAT
3.3.3 Error Suggestion
(Level AA) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Add Member", "Sign In"
  • An input error is automatically detected but the suggestion is not meaningful
3.3.4 Error Prevention (Legal, Financial, Data)
(Level AA) 		Supports

Test methods: TBT; MAT
3.3.8 Accessible Authentication (Minimum)
(Level AA 2.2 only) 		Supports

Test methods: TBT; MAT
4.1.3 Status Messages
(Level AA 2.1 and 2.2) 		Partially Supports

Test methods: TBT; MAT

The following user flows do not fully support this criterion:
"Dashboard and Global Elements", "Bank Free Analysis", "Sign In", "Profile Summary", "Bucket View", "Issue Detail"
  • Status messages are missing or not valid
"Add Member" user flow does not completely support this criterion:
  • Email address domain error message is not announced or not managed properly
  • Status messages are missing or not valid

Legal Disclaimer (Fifth Asset, Inc.)

The information herein is provided in good faith based on the website at the time of the review and does not represent a legally-binding claim.