Label has been added but is not sufficiently descriptive. Add the year and month to the Export buttons it is associated with i.e. ="Export Details of 2022 January"

Resolve: All instances

The form field present below "You can enter any other APEXA registration tokens" rely on the placeholder attribute to supply its accessible name. [User Impact] Users with cognitive disabilities may be unable to determine the purpose of the field after the placeholder disappears. 

Resolve: All instances

"Corporate profile status" and "verbal password" still function as headings but do not have heading markup

Resolve: All instances

There is visually hidden "Separator" line meant to be hidden from all users, but it can still be accessed by keyboard or screen reader users.

Resolve: All instances

The "Apexa logo" image link is provided with insufficiently descriptive textual equivalent. The alternative text "logo" does not provide enough meaning to the image link. Apexa logo does not have all the text information in the logo present in its textual equivalent. eg. alt="Apexa simply connected". Atlassian logo still has no textual equivalent.

Resolved: All instances

There must be sufficient contrast between foreground and background text colors and images of text (including the hover and focus state of text and images of text). Sufficient contrast ensures that people with low vision, people who are color blind, users viewing the page without color, and users of monochrome screens can understand page content.

These changes include:

• Breadcrumb
• Message Component
• Links
• Placeholder
• Validated Input
• Menu
• Header
• Footer
• Tags
• Buttons

Resolved: 44 instances

At a basic level, all custom controls within a web application should provide identifying information about the component. This includes a name, type (role) and may contain state, value, and description information (applicable). When custom elements do not expose identifying information, users of assistive technology may not be able to identify and interact with the element. 

These changes include: 

• Breadcrumb
• Menu 

Resolve: 17 instances

Remove redundant placeholders found on the following pages and components. The gray doesn't contrast well with the white background.

Resolve: 8 instances

The web page does not support reflow when the page had a viewport width of 320 CSS pixels. The following message is displayed "Your web browser is currently too small to use APEXA (a minimum width of 1260 pixels is required)."

Date of incorporation fields overlap other text at 320px viewport and content in the data table is unreadable.

Resolve: All instances

At a basic level, all custom controls within a web application should provide identifying information about the component. This includes a name, type (role) and may contain state, value, and description information (applicable).

Resolve: 2 instances

There are input fields that do not provide a programmatically associated label that describes the purpose of each field. Examples include: - Month (MM) - Day (DD) - Year (YYYY)

Resolve: 1 instance

APEXA "Service desk" now opens in a new tab instead of a dialog but does not announce that a new tab will open. 

Resolve: All instances

When new status content is added to the screen without changing the user's context, users should be made aware of the important changes in content that are not given focus in a way that doesn't unnecessarily interrupt their work.

Resolve: 11 instances

There are form controls with visual labels that are not programmatically associated with the control. Examples include: - Imported - Data Match - Import Scheduled

Resolve: 1 instance

Page tab controls need to provide proper textual equivalent and accessibility properties to ensure name, role, and state are communicated. When accessibility properties are not provided, users may not know which page tab is select or that the control is a page tab.

Resolve: 2 Instances

Resolve identified issue with API function when pulling current address for an Advisor by date to ensure it doesn't throw an error when the advisor has 2 current addresses in the system.