Report:
Digital accessibility audit Planon Accelerator
- Evaluator
- Bram, Swink; Marjon, Swink; Renate, Swink
- Date
- 5 July 2024
- Commissioner
- Planon Software
Summary of the evaluation findings
The website Planon Accelerator does not comply to WCAG 2.1 level AA yet. 13 out of 50 success criteria contain one or more issues. This document describes to what extent the website meets the accessibility requirements captured in WCAG, the Web Content Accessibility Guidelines.
The Planon Accelerator web application was audited between February 19 and February 29 2024. The re-audit was conducted between July 1st and July 5th. The audit was conducted using the WCAG-EM evaluation method. A testing instance of the application was provided by Planon. A subset of the application has been audited to get a good overview of the current state of the application. The aim of the audit is to provide clear accessibility issues to stakeholders, such as Planon's clients and developers. We are glad to see that many problems that have been found earlier have been fixed, or partially fixed by Planon. A few key findings include:
- The homepage has a set of widgets that are not fully keyboard accessible, including 'edit mode'.
- The focus order within several parts of the application is not logical.
- Several images and graphics within the application lack proper alternative text.
The audit focuses specifically on the accessibility of the website for people with a disability, such as people who are blind, deaf, low-literate or have other functional problems. For them it is important that the website is technically and substantively designed in such a way that the site is usable. Optimizing a website for accessibility has more advantages; it makes the website more usable for everyone (for example also for people who look at their mobile phone in a sunny environment) and it makes the site easier to find in search engines.
Scope of the evaluation
Website name | Planon Accelerator |
---|---|
Scope of the website |
The scope of the audit includes:
|
Conformance target | WCAG 2.1 level AA |
Accessibility support baseline | Common browsers and assistive software. |
Overview of audit results
Principle | Passed | Failed | Can't tell |
---|---|---|---|
1 Perceivable | 14 | 6 | 0 |
2 Operable | 14 | 3 | 0 |
3 Understandable | 8 | 2 | 0 |
4 Robust | 1 | 2 | 0 |
Total | 37 | 13 | 0 |
Reading Guide
This evaluation is a snapshot. The website might have been changed. The problems found are only examples. Therefore, check for any problem whether this also occurs in other places. This evaluation is just a sample of a few pages. As many different types of pages are included in the sample as possible to get the best impression of the accessibility. Pay attention! New problems may arise when making improvements or changes to the website/app. Success criteria marked with "Not present" are automatically approved. Success criteria marked with "Unknown" or "Can't tell" are not approved.
Detailed audit results
1. Perceivable
1.1 Text Alternatives
1.1.1 Non-text Content (Level A)
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.
- Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
- Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
- Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
- Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
- CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
- Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
Information about success criterion 1.1.1 Non-text Content
Outcome: Failed
Findings: 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'.
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'.
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".
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 ...".
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
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*'.
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*'.
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.
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.2 Time-based Media
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
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:
- 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.
Information about success criterion 1.2.1 Audio-only and Video-only (Prerecorded)
Outcome: Inapplicable
1.2.2 Captions (Prerecorded) (Level A)
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Information about success criterion 1.2.2 Captions (Prerecorded)
Outcome: Inapplicable
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Information about success criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)
Outcome: Inapplicable
1.2.4 Captions (Live) (Level AA)
Captions are provided for all live audio content in synchronized media.
Information about success criterion 1.2.4 Captions (Live)
Outcome: Inapplicable
1.2.5 Audio Description (Prerecorded) (Level AA)
Audio description is provided for all prerecorded video content in synchronized media.
Information about success criterion 1.2.5 Audio Description (Prerecorded)
Outcome: Inapplicable
1.3 Adaptable
1.3.1 Info and Relationships (Level A)
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Information about success criterion 1.3.1 Info and Relationships
Outcome: Failed
Findings: 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.
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.3.2 Meaningful Sequence (Level A)
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Information about success criterion 1.3.2 Meaningful Sequence
Outcome: Passed
1.3.3 Sensory Characteristics (Level A)
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.
Information about success criterion 1.3.3 Sensory Characteristics
Outcome: Passed
1.3.4 Orientation (Level AA)
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Information about success criterion 1.3.4 Orientation
Outcome: Passed
1.3.5 Identify Input Purpose (Level AA)
The purpose of each input field collecting information about the user can be programmatically determined when:
- The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
Information about success criterion 1.3.5 Identify Input Purpose
Outcome: Passed
1.4 Distinguishable
1.4.1 Use of Color (Level A)
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Information about success criterion 1.4.1 Use of Color
Outcome: Passed
1.4.2 Audio Control (Level A)
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.
Information about success criterion 1.4.2 Audio Control
Outcome: Passed
1.4.3 Contrast (Minimum) (Level AA)
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
- Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
- Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
- Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
Information about success criterion 1.4.3 Contrast (Minimum)
Outcome: Failed
Findings: 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.4 Resize text (Level AA)
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Information about success criterion 1.4.4 Resize text
Outcome: Passed
1.4.5 Images of Text (Level AA)
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:
- Customizable: The image of text can be visually customized to the user's requirements;
- Essential: A particular presentation of text is essential to the information being conveyed.
Information about success criterion 1.4.5 Images of Text
Outcome: Inapplicable
1.4.10 Reflow (Level AA)
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.
Information about success criterion 1.4.10 Reflow
Outcome: Failed
Findings: 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)
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.
Information about success criterion 1.4.11 Non-text Contrast
Outcome: Failed
Findings: 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.
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)
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.
Information about success criterion 1.4.12 Text Spacing
Outcome: Failed
Findings: 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).
1.4.13 Content on Hover or Focus (Level AA)
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.
Information about success criterion 1.4.13 Content on Hover or Focus
Outcome: Passed
2. Operable
2.1 Keyboard Accessible
2.1.1 Keyboard (Level A)
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.
Information about success criterion 2.1.1 Keyboard
Outcome: Failed
Findings: 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.
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.
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.1.2 No Keyboard Trap (Level A)
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.
Information about success criterion 2.1.2 No Keyboard Trap
Outcome: Passed
2.1.4 Character Key Shortcuts (Level A)
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.
Information about success criterion 2.1.4 Character Key Shortcuts
Outcome: Passed
2.2 Enough Time
2.2.1 Timing Adjustable (Level A)
For each time limit that is set by the content, at least one of the following is true:
- 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.
Information about success criterion 2.2.1 Timing Adjustable
Outcome: Passed
2.2.2 Pause, Stop, Hide (Level A)
For moving, blinking, scrolling, or auto-updating information, all of the following are true:
- 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.
Information about success criterion 2.2.2 Pause, Stop, Hide
Outcome: Passed
2.3 Seizures and Physical Reactions
2.3.1 Three Flashes or Below Threshold (Level A)
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.
Information about success criterion 2.3.1 Three Flashes or Below Threshold
Outcome: Passed
2.4 Navigable
2.4.1 Bypass Blocks (Level A)
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Information about success criterion 2.4.1 Bypass Blocks
Outcome: Passed
2.4.2 Page Titled (Level A)
Web pages have titles that describe topic or purpose.
Information about success criterion 2.4.2 Page Titled
Outcome: Passed
2.4.3 Focus Order (Level A)
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.
Information about success criterion 2.4.3 Focus Order
Outcome: Failed
Findings: 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.
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.
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.
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.
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.4.4 Link Purpose (In Context) (Level A)
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.
Information about success criterion 2.4.4 Link Purpose (In Context)
Outcome: Passed
2.4.5 Multiple Ways (Level AA)
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.
Information about success criterion 2.4.5 Multiple Ways
Outcome: Passed
2.4.6 Headings and Labels (Level AA)
Headings and labels describe topic or purpose.
Information about success criterion 2.4.6 Headings and Labels
Outcome: Passed
2.4.7 Focus Visible (Level AA)
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Information about success criterion 2.4.7 Focus Visible
Outcome: Passed
2.5 Input Modalities
2.5.1 Pointer Gestures (Level A)
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
Information about success criterion 2.5.1 Pointer Gestures
Outcome: Passed
2.5.2 Pointer Cancellation (Level A)
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.
Information about success criterion 2.5.2 Pointer Cancellation
Outcome: Passed
2.5.3 Label in Name (Level A)
For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
Information about success criterion 2.5.3 Label in Name
Outcome: Failed
Findings: 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.
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.
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'.
2.5.4 Motion Actuation (Level A)
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
- Supported Interface: The motion is used to operate functionality through an accessibility supported interface;
- Essential: The motion is essential for the function and doing so would invalidate the activity.
Information about success criterion 2.5.4 Motion Actuation
Outcome: Inapplicable
3. Understandable
3.1 Readable
3.1.1 Language of Page (Level A)
The default human language of each Web page can be programmatically determined.
Information about success criterion 3.1.1 Language of Page
Outcome: Passed
3.1.2 Language of Parts (Level AA)
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.
Information about success criterion 3.1.2 Language of Parts
Outcome: Passed
3.2 Predictable
3.2.1 On Focus (Level A)
When any component receives focus, it does not initiate a change of context.
Information about success criterion 3.2.1 On Focus
Outcome: Passed
3.2.2 On Input (Level A)
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.
Information about success criterion 3.2.2 On Input
Outcome: Passed
3.2.3 Consistent Navigation (Level AA)
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.
Information about success criterion 3.2.3 Consistent Navigation
Outcome: Passed
3.2.4 Consistent Identification (Level AA)
Components that have the same functionality within a set of Web pages are identified consistently.
Information about success criterion 3.2.4 Consistent Identification
Outcome: Passed
3.3 Input Assistance
3.3.1 Error Identification (Level A)
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.
Information about success criterion 3.3.1 Error Identification
Outcome: Failed
Findings: 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)
Labels or instructions are provided when content requires user input.
Information about success criterion 3.3.2 Labels or Instructions
Outcome: Failed
Findings: 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.
3.3.3 Error Suggestion (Level AA)
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.
Information about success criterion 3.3.3 Error Suggestion
Outcome: Passed
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Information about success criterion 3.3.4 Error Prevention (Legal, Financial, Data)
Outcome: Passed
4. Robust
4.1 Compatible
4.1.1 Parsing (Level A)
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.
Information about success criterion 4.1.1 Parsing
Outcome: Passed
4.1.2 Name, Role, Value (Level A)
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.
Information about success criterion 4.1.2 Name, Role, Value
Outcome: Failed
Findings: 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.
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.
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.
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.
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.
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.
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".
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".
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.
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)
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.
Information about success criterion 4.1.3 Status Messages
Outcome: Failed
Findings: 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
- https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient
- https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient?2#REM89_0000000603
- https://bcberkwcagaudit-prod.plnd.cloud/home/BP/WebClient#PfM65-0000001686
- https://bcberkwcagaudit-prod.plnd.cloud/j_security_check
- My Account
Relied upon techniques
Web browsers (User Agents) and other software
The following software was used in this evaluation:- Chrome, version 126
- Firefox, version 127
- NVDA, version 2024.1
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.