Users can submit duplicate requests through external requesting by rapidly clicking the submit button.
Bug# 47020 votes
The DataRow_ElectronicDelivery data row template does not display the associated file size and transaction number for requests.
Bug# 181120 votes
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# 182640 votes
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# 179850 votes
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# 176430 votes
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# 176040 votes
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# 175880 votes
The "Details" button in the request DataRow template files can't be activated using the spacebar key
The "Details" button contained in the request DataRow files cannot be activated via the spacebar key like other HTML buttons.
Bug# 175800 votes
When no item title is provided, the request datarows will contain an empty hyperlink which may cause confusion for screen reader users.
Bug# 175790 votes
Default hyperlink color does not have sufficient contrast with other body text used in Aeon default web pages
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# 175780 votes
Errors involving the appointment fields may not be announced by screen readers in some cases.
Bug# 175770 votes
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# 175760 votes
The request status tooltip within the request DataRow template files does not meet accessibility requirements
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# 175750 votes
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# 175740 votes
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# 175730 votes
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# 175720 votes
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# 175710 votes
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# 175280 votes
Using the <#OPTION> tag with a CustomDropDown group requires the group name to match the target field name
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# 174070 votes