If the WebAuthType key is set to RemoteAuth in the Customization Manager and the force password reset option is toggled for a user using Aeon Authentication, the user will not be prompted to change their password upon logging in if the Aeon Authentication checkbox is not checked on the user record.

Bug# 18390

The Aeon System Manager caches custom field definitions defined in the Customization Manager and does not automatically refresh these when new entries are made.

Bug# 18405

The controls located within the Aeon Options form in the Aeon Client are not aligned properly within the borders of each section of options on this screen.

Bug# 18418

The DataRow_ElectronicDelivery data row template does not display the associated file size and transaction number for requests.

Bug# 18112

The default FAQ web page contains information about cookies stating that "the technology that we use sends a Session ID to be stored on your machine. You can refuse this cookie and still be able to use Aeon without any problems."

This information is inaccurate as the Session ID cookie is essential for the Aeon web interface.

Bug# 18264

Appointment merge fields used in Transaction type email templates will appear blank when emails are generated for the template.

Bug# 17993

The default ViewSearchResults.html web page contains an incorrect usage of the <u> tag to emphasize text where a <strong> tag should be used instead.

Bug# 17985

The Aeon Alma Primo and Alma Primo VE Catalog addons may only import one call number for a record associated with multiple call number entries.

Bug #17908

Creating a new request via the request creation endpoint that specifies a non-existent username will correctly return a validation error stating that the user does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid, even if valid values had been entered.

Bug# 17649

When a dropdown is opened from the main navigation bar and one of the containing links is hovered over or focused on, the default background color that appears does not meet WCAG contrast requirements against the default white background of the other links.

Bug# 17643

The default button colors in certain states such as "active" and "hover" don't meet WCAG contrast requirements with commonly used default background colors like grey or white.

Bug# 17604

When a request form is loaded for the first time, and a reading room is selected with no appointments scheduled, the Appointment dropdown remains blank instead of showing the "No Appointment" text. However, after swapping to a reading room with an appointment, it will display the "No Appointment" text even though there is an appointment scheduled in the room.

Bug# 17588

The "Details" button contained in the request DataRow files cannot be activated via the spacebar key like other HTML buttons.

Bug# 17580

When no item title is provided, the request datarows will contain an empty hyperlink which may cause confusion for screen reader users.

Bug# 17579

In situations where the hyperlink is around other body text, the default color (#08415c) does not meet WCAG contrast requirements when compared to surrounding body text colors used in the default web pages.

Bug# 17578

Errors involving the appointment fields may not be announced by screen readers in some cases.

Bug# 17577

In some display/screen sizes, the Switch button on the request forms overflows outside of the item information box and requires horizontal scrolling to access.

Bug# 17576

The request status tooltip found within the request DataRow template files does not meet accessibility requirements for the following reasons:

-It is not possible to make the tooltip appear via keyboard controls
-The item status popup does not stay visible when the mouse pointer moves over the popup content
-The tooltip may visibly flicker in some cases

Bug# 17575

The default page title within the <title> element of FirstTime.html is "Aeon Logon", which is too similar to the page title for Logon.html and Logon2.html and does not accurately describe the page's purpose.

Bug# 17574

The default border color for form fields in the Aeon web pages does not meet WCAG contrast requirements against a white background nor against the default form section background color.

Bug# 17573