Plesk Accessibility and Usability Information

Color contrast barriers

In light mode, the blue used for links and grey used for some text throughout the platform do not have sufficient contrast with the white background. Additionally, the color combinations for highlighting active page names and some icons do not have sufficient contrast. 

In dark mode, some buttons and menus don’t have sufficient contrast with the background of the page. 

In both light and dark mode, the color combination for warning text does not have sufficient contrast. 

This barrier primarily relates to the following accessibility guidelines:

• • Perceivable: All visual elements have sufficient color contrast. (1.4)

Missing alt text

The DoIT Shared Hosting logo includes the filename in its alt text 

alt="apSKwN6witA.gif - Homepage"

This barrier primarily relates to the following accessibility guidelines:

• • Perceivable: All content has text alternatives. (1.1.1)

Inconsistent and low visibility indication of keyboard focus

The visual styling of keyboard focus takes several forms throughout the platform, some more apparent than others. Some elements receive a faint blue outline, while other elements like buttons receive a slight shift in color, like a blue or grey wash.  

Expected behavior: The visual indication of focus should be strong and high contrast and, ideally, consistent throughout the platform to make it easier for the user to identify which element has focus. 

This barrier primarily relates to the following accessibility guidelines:

• • Operable: Each item receiving focus has a visible indicator (2.4.7)

Screen reader barriers in folder panel 

When the folder panel first receives screen reader focus, the screen reader begins to announce the entire panel until the user interrupts the announcement. Then, as the user navigates through the list, each folder has two “unlabeled” elements before the user reaches the actual tab stop for the folder. The following video demonstrates both of these barriers: Screen reader barriers in folder panel

Expected behavior: First, the screen reader would only announce the first item in the panel and the number of additional items in the list. Then, both the expand arrow and folder would have unique labels when they receive keyboard focus. 

This barrier primarily relates to the following accessibility guidelines:

• • Perceivable: All content has text alternatives. (1.1.1)

  • Understandable: Make web content operate in predictable ways (3.2)

Keyboard and screen reader barriers in file manager table

The column that holds the actions menu has an empty column header, which can be confusing for screen reader users. Additionally, when navigating via keyboard, the user cannot place focus on the clickable file or folder name or the permissions column. While it appears that the user can access permissions from the actions menu, there does not appear to be an equivalent for selecting the folder name without returning to the sidebar. 

The following screenshot shows the empty column header: 

The following screenshot shows the expanded actions menu, with an option to rename the folder or change permissions, but not to drill down into the “private” folder:

Expected behavior: All columns must have a column header. Additionally, all actions available through click must be available by keyboard only navigation.

This barrier primarily relates to the following accessibility guidelines:

• • Operable: Elements are selectable and interactive via keyboard. (2.1)

Viewport is crowded at higher levels of magnification

When the user magnifies the screen to 300% or 400%, the banner and Save/Cancel buttons crowd most of the viewport and the content becomes difficult, or impossible, to view.

The following screenshot shows the content at 300% magnification:

The following screenshot shows the content at 400% magnification:

Expected behavior: Content should reflow and adjust so that it is still easily viewable at higher levels of magnification.

This barrier primarily relates to the following accessibility guidelines:

• • Perceivable: Content reflows as it is magnified or the screen orientation changes. (1.4.10)

Anchor links are not included in keyboard navigation

The Domain Settings and Webspace Settings anchor links in the Hosting Settings menu are not included in the keyboard navigation order. This could lead to a perceived loss of functionality for keyboard users. The following screenshot shows the anchor links from the flyout menu:

Expected behavior: All actions available through click must be available by keyboard only navigation.

This barrier primarily relates to the following accessibility guidelines:

• • Operable: Elements are selectable and interactive via keyboard. (2.1)