Keyboard / Voice input

• The remove search input button on the search field cannot be accessed
• The yellow visible focus indicator has insufficient contrast in some areas
• The hamburger menu doesn’t have a visible focus indicator

Zoom/low-vision

• The menu bar is unscrollable when the page size is increased.
• Some areas have insufficient colour contrast
• Content that appears on hover and focus cannot be easily dismissed by using a keyboard

Screen readers

• Some images have inaccurate alternative text
• Custom controls, such as accordions and tabs can be difficult to use
• Some form fields don’t announce whether it’s required or not
• Radio buttons haven’t been grouped using the appropriate HTML
• The registration progress bar isn’t communicated to screen reader users clearly
• Error messages aren’t automatically announced to screen reader users
• Some buttons are missing labels

Cognitive

• Some error messages are browser-based and have a time limit.

Non-accessible content

The content listed below is non-accessible for the following reasons.

• Tab panels, accordions and toggle buttons have not been marked up appropriately, failing “Name, Role, Value” (4.1.2)
• A number of images do not have appropriate text assigned, failing “Non-text Content” (1.1.1)
• There is no visible focus on the hamburger menu, failing “Focus Visible” (2.4.7)
• The remove search input button on the search field bar cannot be accessed with a keyboard, failing “Keyboard” (2.1.1)
• Some visible focus indicators do not meet the contrast threshold, failing “Non-Text Contrast” (1.4.11)
• The hamburger menu is unscrollable when the page is zoomed in, failing “Reflow” (1.4.10)
• An aria-required attribute has not been implemented on required form fields, failing “Info & Relationships” (1.3.1)
• Radio buttons titles have not been assigned as a “fieldset”, failing “Info & Relationships” (1.3.1)
• The progress bar visually communicates the users progress in the Registration, however this information is not conveyed to users who rely on a screen reader, failing “Name, Role, Value” (4.1.2)
• Error messages are not automatically announced to screen reader users, failing “Info & Relationships” (1.3.1)
• HTML didn’t conform to the W3C specification, failing “Parsing” (4.1.1)
• Some error messages rely on browser-based error messages which have a time limit and disappear after a few seconds, failing “Info & Relationships” (1.3.1) and “Timing Adjustable” (2.2.1)
• The search field is too small for users to see their input when the page is zoomed in, failing “Reflow” (1.4.10)
• Error messages & helper text are not associated with form fields, failing “Info & Relationships” (1.3.1)
• Labels were inaccurate on some form fields, failing “Info & Relationships” (1.3.1)
• The keyboard focus order can be confusing for keyboard users on the Register a Plant Name page, failing “Focus Order” (2.4.3)
• Content that appears on focus and hover cannot be dismissed with the use of keyboard, failing “Content on Hover or Focus” (1.4.13)
• Search results are updated automatically without users request, failing “On Input” (3.2.2)

We plan to resolve the issues on https://ipni.org/ over the next 12 months and will update this statement when progress has been made.