When sending templated emails from the Aeon Client, the From Address and From Name are set to the default values in the LocalInfo Table or EmailFromAddress/EmailFromName customization keys instead of the values specified in the email template.

Bug# 13531

Users can submit duplicate requests through external requesting by rapidly clicking the submit button.

Bug# 4702

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

The focus indicator for several interactive controls in the default web pages (e.g., input fields, buttons, etc) does not meet the minimum contrast required by WCAG.

Bug# 17572

Hyperlinks on keyboard focus use the browser defaults for focus indicators which may not meet WCAG contrast requirements on the default web pages, particularly in the header and navigation bar areas.

Bug# 17571

The HTML tables used to format the appointment scheduling calendar on the web are improperly formatted and cause navigation issues for screen reader users.

Bug# 17528

CustomDropDown group selections displayed on web forms using the <#OPTION> tag can only be saved to a field with a name matching that of the CustomDropDown group name.

Bug# 17407

Using the <#OPTION> tag to generate a group of checkbox selections for a CustomDropDown group on the web will cause the data selected to be saved with a comma prepended to each value.

Bug# 17406