Issues:
Digital accessibility audit Planon Accelerator

(Issues only)

Scope of the evaluation

Detailed audit results

1. Perceivable

1.1 Text Alternatives

1.1.1 Non-text Content (Level A)

Information about success criterion 1.1.1 Non-text Content

Finding 1: Adjusted finding as a result of re-audit:
The Planon logo has no appropriate text alternative. The alternative text is now "Company logo, go to homepage, Home page". This does not adequately describe the content of the image. Adjust the alternative text, e.g. to Planon logo, go to homepage'.

Finding 2: Adjusted finding as a result of re-audit:
The Planon logo on the login page (Login, https://bcberkwcagaudit-prod.plnd.cloud/j_security_check
) has a text alternative of "Company logo". This text doesn't describe the image properly. Change the alternative text to 'Planon logo'.

Finding 3: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), the delete buttons have an accessible name of "Close". This does not accurately describe the purpose of these buttons. Give the button a better accessible name such as "Delete".

Finding 4: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), the "+" icon signifies that the button can be used to add a gadget. However, this is not indicated in the accessible name of these buttons. Ensure the accessible name contains a text alternative for this icon, such as "Add widget ...".

Finding 5: Adjusted finding as a result of re-audit:
The chart "Investment option" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient) does not have a proper text alternative. An aria-label is added to the svg-element, however, there also needs to be a role of 'img' added to the svg-element to make the aria-label valid. Consider instead providing a text description or a (link to a) table displaying the data, instead of adding aria-labels to excisting data and tying it together. If an appropriate alternative is provided next to, or outside the chart, ensure the chart is marked as a decorative image

Finding 6: Adjusted finding as a result of re-audit:
In REM - Portfolio > Properties (https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603): Users now have the option of adding their own text alternative and Planon has no control over the text they enter. As long as a text alternative is not provided, a standard text alternative is added to indicate this. This page does not conform, but would conform to WCAG 2.1 at level AA if the following parts from uncontrolled sources were removed. When property details are shown, there is a photo of the property. The alternative text is 'no text alternative provided Image'. This does not adequately describe the content of the image. Adjust the alternative text, for example to 'Building exterior of *add name/address of property*'.

Finding 7: Adjusted finding as a result of re-audit:
My telephone directory (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient): Users now have the option of adding their own text alternative and Planon has no control over the text they enter. As long as a text alternative is not provided, a standard text alternative is added to indicate this. This page does not conform, but would conform to WCAG 2.1 at level AA if the following parts from uncontrolled sources were removed. The alternative text of the contact images is 'no text alternative provided Image'. Change the alternative text to, for example, 'Photo of *add the name of the contact here*'.

Finding 8: My Phone directory (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient): After expanding a row and clicking "more details", a dialog opens. This dialog has a button next to "space" to view a CAD drawing of the users' location. However, this button is named "Choose value", which does not describe the purpose of this button.

Finding 9: Adjusted finding as a result of re-audit:
The button to turn a filter on or off has a name (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603), of 'Filter on' (when the filter is off) and 'Filter off' (when the filter is on). Toggle button names are often ambiguous, so make very clear what the button does, for example by updating the button text (aria-label): 'Turn filter off' and 'Turn filter on' to describe what the button will do when the user clicks on it.

1.3 Adaptable

1.3.1 Info and Relationships (Level A)

Information about success criterion 1.3.1 Info and Relationships

Finding 10: Adjusted finding as a result of re-audit:
When clicking on an element in the pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. This dialog contains an iframe without a title attribute. Set the title attribute to a descriptive name for the iframe. Iframes without a title attribute are present throughout the application, for example, the iframes that contain the data graphs on the homepage.

Finding 11: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient): After adding a widget to the home screen, there is no audio feedback for a screen reader user that confirms the action. A solution could be adding an aria-live area or a status message (role=status) somewhere on the homepage that gives feedback via the screen reader and also visually notifying the user that the item was added to the bottom of the page.

1.4 Distinguishable

1.4.3 Contrast (Minimum) (Level AA)

Information about success criterion 1.4.3 Contrast (Minimum)

Finding 12: New finding as a result of re-audit:
Under the chart "Investment option" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient) is a button called "Investment option". Clicking this button shows or hides the bars in the chart. When the chart is hidden, the contrastratio of the text (HEX #CCCCCC) on the background (HEX #E6E6E6) is 1,2:1 where it should at least be 4,5:1/

1.4.10 Reflow (Level AA)

Information about success criterion 1.4.10 Reflow

Finding 13: It is not possible to zoom to 400% at a viewport width of 1280px and still be able to use the application as intended (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient).

1.4.11 Non-text Contrast (Level AA)

Information about success criterion 1.4.11 Non-text Contrast

Finding 14: In the widget 'Projects per status' (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), the colour contrasts between colours of the sections in the pie chart are not sufficient. This could be solved by adding some white space between the sections. This will only work if the chosen colours themselves have a contrast of at least 3:1 against a white background.

Finding 15: Adjusted finding as a result of re-audit:
After selecting multiple properties from the tree and choosing 'Modify within selection' (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603), a dialog is shown with 3 tabs. There is a button to select an image. Activating this option opens another dialog 'Open' with folders to choose from, containing several formfields.The borders around the fields. The contrast ratio of the grey outline (HEX #D8D8D8) on the white background is 1,4:1 where it should at leat be 3:1.

1.4.12 Text Spacing (Level AA)

Information about success criterion 1.4.12 Text Spacing

Finding 16: Setting the text spacing according to the requirements in this success criterion results in some text being truncated or hidden to the point that the user can't properly identify controls (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603).

2. Operable

2.1 Keyboard Accessible

2.1.1 Keyboard (Level A)

Information about success criterion 2.1.1 Keyboard

Finding 17: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), there is no way to move gadgets using the keyboard. Provide an alternative to the drag and drop interface. To be compliant with WCAG 2.2 in the future, provide visible buttons on screen to move the gadgets and not just keyboard hotkeys.

Finding 18: The pi chart on the homepage in the "Projects per status" gadget can be rotated using a mouse. There is no keyboard equivalent for this functionality. Ensure the chart can also be rotated using a keyboard.

Finding 19: After selecting multiple properties from the tree and choosing 'Modify within selection' (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603), a dialog is shown with 3 tabs. There is a button to select an image. Activating this option opens another dialog 'Open' with folders to choose from. With a mouse, you can double-click a folder to move into it. This is not possible with the keyboard.

2.4 Navigable

2.4.3 Focus Order (Level A)

Information about success criterion 2.4.3 Focus Order

Finding 20: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), when activate the "Close edit mode" button, the focus is lost. Ensure the focus is set on the "Edit mode" button.

Finding 21: After clicking an element in the pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. When switching result pages, the focus is lost. Ensure the focus stays where it was, on the previous/next button.

Finding 22: After moving gadgets in edit mode and exiting edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient). The gadgets are visually rearranged, but the order of gadgets in the DOM stays the same as before editing. This causes focus order issues. Ensure the visual order matches the order in the DOM.

Finding 23: In edit mode: After adding a widget to the home screen, the element is removed from the list. No other element receives focus. Fix the focus so it is set to the next item in the library after adding one to the page. When no blocks/gadgets are left in the library, show a text in the library that “no gadgets are available in the library” and set the focus on that.

Finding 24: Adjusted finding as a result of re-audit:
When adding a filter (with `<button class="btn-28 pn-font-icon filterGroupButton" title="Filter option"></button>`) and clicking OK (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603), the dialog disappears. The focus moves to the 'Properties' tab when instead it should move back to the filter button.

2.5 Input Modalities

2.5.3 Label in Name (Level A)

Information about success criterion 2.5.3 Label in Name

Finding 25: Adjusted finding as a result of re-audit:
The accessible name of the user menu is "User info, current user is AUDITJULY" and is set using aria-label. An aria-label overrides the contents of an element and it's descendants, so the initials of the logged in user are no longer part of the element's accessible name. The alternative text of the initials of the logged in user is now 'Shows the currently logged in user'. Ensure all visible text is included in the accessible name for all interactive elements and that the accessible name describes the element.

Finding 26: In the tab 'Properties details' (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603) there is a quick search field just above the list with properties. You can choose between 'Code' and 'Name'. The accessible name of the select element is 'Search expression', but the visible label is whichever option is selected in the select element. This is caused by `aria-label="Search expression"`. It is possible to name the select, via a (visually hidden) label-element. Make sure that visible labels (not necessarily label-elements!) contain the same text as the accessible name.

Finding 27:
New finding as a result of re-audit:
The accessible name of the field with the visible label 'No filter - click to select an existing filter. Use the 'Filter option' button to add new filters' is 'Filter name' (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603). Make sure the visible name is part of the accessible name. In this case, consider moving the instructions to above the form field and adding the visible label for 'Filter name'.

3. Understandable

3.3 Input Assistance

3.3.1 Error Identification (Level A)

Information about success criterion 3.3.1 Error Identification

Finding 28: New finding as a result of re-audit:
Not every error message clearly describes the error made by the visitor.
For example, the error message '* The field Property code must contain a value. (PN_T00397)' on Properties - Element list - Datagrid, if for example the property value is not entered. Add error identifacation messages, for example: 'The field 'Property code' is not filled in.'

3.3.2 Labels or Instructions (Level A)

Information about success criterion 3.3.2 Labels or Instructions

Finding 29: New finding as a result of re-audit:
The "Filter name" field (REM - Portfolio / Properties, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603) has instructions ('No filter - click to select an existing filter. Use the 'Filter option' button to add new filters.') but they disappear once a visitor starts typing. Make sure labels and instructions for form fields remain permanently visible.

4. Robust

4.1 Compatible

4.1.2 Name, Role, Value (Level A)

Information about success criterion 4.1.2 Name, Role, Value

Finding 30: Many buttons (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient
), such as the "Edit mode" button, can't be activated by pressing the space bar. This is expected for a button. Ensure all elements with `role=button` can be activated by pressing space bar.

Finding 31: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient
), the buttons to add widgets are marked up as links. These elements should be identified as buttons, add a `role=button` attribute, or use the native `<button>` element.

Finding 32: In edit mode (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), the set of current gadgets is not labelled as such. Give the containing `ul` element a descriptive aria-label, such as "Current gadgets". Also, either remove the menu role or let this component behave as a menu.

Finding 33: When clicking an element in the "Projects per status" pi chart (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. This dialog has no accessible name. Add an aria-label to the dialog that describes it's purpose.

Finding 34: After clicking an element in the pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. If the previous/next button is disabled, this state is not communicated to assistive technologies. Add an aria-disabled attribute to the disabled buttons, or use the native `button` element and add a `disabled` attribute.

Finding 35: After clicking an element in the pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. Select the blue button with the white arrow "Choose value: property", another dialog opens. Leave all fields empty and press search. The resulting list has selectable rows. The selected state of the row is not communicated to assistive technologies.

Finding 36: After clicking an element in the pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. Select the blue button with the white arrow "Choose value: property", another dialog opens. Leave all fields empty and press search. The resulting list has a checkbox to select all items, this checkbox does not have an accessible name. Add an accessible name such as "Select all".

Finding 37: The pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient) contains text elements with the project status and the number of projects. These text elements are buttons, but don't have the role of button. Also, they should be grouped in a list which describes the chart's purpose, such as "Projects per status".

Finding 38: Adjusted finding as a result of re-audit:
Under the chart "Investment option" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient) is a button called "Investment option". Clicking this button shows or hides the bars in the chart. It's state is not communicated in the accessibility tree and therefore not available to assistive technologies.

Finding 39: Adjusted finding as a result of re-audit:
In the menu in the header of the page: When a menu item is expanded, for example the user info button, it does not communicate its state of expanded or collapsed. An aria-expanded attribute is added, however it does not change to 'true' when the button is expanded.

4.1.3 Status Messages (Level AA)

Information about success criterion 4.1.3 Status Messages

Finding 40: After clicking an element in the pi chart "Projects per status" (homepage, https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient), a dialog opens. In this dialog is a status messages that changes when switching result pages, for example "11 - 19 of 19". This status message is not automatically announced. Ensure this status is conveyed to assistive technology by setting a `role=status` attribute on the status message.

Basis for this evaluation

The audit was conducted based on the evaluation method of the W3C, WCAG-EM. This is largely done manually by taking a sample. For a quickscan we use parts of this methodology. Despite all the researcher's care and experience, it is possible that a problem has not been identified. Keep in mind that in a next audit certain parts could be assessed differently because of further development of techniques and assistive software. Tools are used in the manual audit.

Sample of audited web pages

• Homepage:
  https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient
• REM Portfolio, Properties:
  https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603
• REM Turnover rent, Configuration:
  https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient#PfM65-0000001686
• Login:
  https://bcberkwcagaudit-prod.plnd.cloud/j_security_check
• Clik the user avatar/name, followed by My Account:
  My Account

Relied upon techniques

• HTML5
• CSS
• WAI-ARIA
• DOM
• ECMAScript 5
• SVG

Resources:

• Website Accessibility Conformance Evaluation Methodology (WCAG-EM)
  www.w3.org/WAI/eval/conformance
• Web Content Accessibility Guidelines (WCAG)
  www.w3.org/WAI/intro/wcag
• How to Meet WCAG 2.1 Quick Reference
  www.w3.org/WAI/WCAG21/quickref/

This report is mainly created with the online W3C report tool.