Aeon Known Issues
55 results found
-
Duplicate Requests in Aeon by double clicking submit button
Users can submit duplicate requests through external requesting by rapidly clicking the submit button.
Bug# 4702
0 votes -
1 vote
-
The Save for Later button on the EAD Request form may submit requests for processing
When the SubmitEadRequestsUpToRequestLimit customization key is set to Yes, using the Save for Later button on the EAD request form submits the request for processing instead of saving it for user review. As a result, requests can bypass the appointment requirement.
Bug# 21000
0 votes -
Search box on ViewSearchResults.html has poor contrast in some browsers
The border used for the search box on ViewSearchResults.html does not meet color contrast requirements in some browsers, including Safari.
Bug# 19937
0 votes -
Duration of a booked appointment can't be shortened for reading rooms configured with a single seat
Attempting to shorten the duration of an existing appointment booked in a reading room configured with only a single seat on the web will return a "No appointment availability for this start and stop time" error.
Bug# 19849
0 votes -
Using the Enter key on the Saved Requests page selects all requests without announcing selection to screen readers
Pressing Enter on the ScheduledDate field on the Saved Requests page (ViewUserReviewRequest.html) will checkmark select all requests on the page, without this change being announced to screen readers.
Bug# 19801
0 votes -
MinimumLeadDays behavior functions differently for appointments vs requests
The MinimumLeadDays value for a reading room configured in the Aeon Customization Manager will consider not only the current date, but also the current time when calculating whether a request can still be submitted for an appointment, but will not consider the current time when making the same calculation for whether an appointment can still be scheduled in the room.
This means that it is possible for an appointment to be scheduled for the room that would then not allow any requests to be associated with it.
Bug# 19633
0 votes -
ItemSubTitle (Series) field on EditEADRequest.html contains an incorrect 'required' attribute
The ItemSubTitle (Series) field on EditEADRequest.html contains a 'required' attribute even though that field is not intended to be required by default.
Bug# 18920
0 votes -
Transaction menu button text is not fully visible on certain display sizes
The text content of the transaction menu buttons does not fully display on small screen sizes or high zoom levels and requires horizontal scrolling to view. In some cases, horizontal scrolling is not enough to read the full button text.
Bug# 18917
0 votes -
Actions dropdown options are not fully visible on certain display sizes
The Actions dropdown options do not fully display on small screen sizes or high zoom levels and require horizontal scrolling to view.
Bug# 18915
0 votes -
ReadingRoomID field label contains incorrect 'for' attribute value on ViewAppointments.html
The ReadingRoomID field label in the ViewAppointments.html file contains an incorrect value in its 'for' attribute and is not read by screen readers.
This value should match the 'id' value for the field ("ReadingRoomID").
Bug# 18913
0 votes -
Hyperlinks added to the cookie consent banner will fail color contrast requirements
If a hyperlink is added to the cookie consent banner, the default hyperlink color will not provide sufficient contrast against the banner's background color.
Note: Hyperlinks are not present in the banner by default.
Bug# 18486
0 votes -
The label color for fields that fail server validation does not pass color contrast requirements
When a field fails server validation, the web pages set the color of the field label to a red color that does not pass contrast requirements with the default form section color.
Bug# 18758
0 votes -
Current Password field on ChangePassword.html has a broken 'aria-describedby' attribute
The 'aria-describedby' attribute for the Current Password field on ChangePassword.html is broken and may be flagged as an issue by accessibility checkers.
Bug# 18687
0 votes -
Modal dialog for web alerts contains broken 'aria-labelledby' attribute
The 'aria-labelledby' attribute used on the modal dialog for web alerts is broken and causes an accessibility issue.
Bug# 18686
0 votes -
DataRow_ElectronicDelivery.html does not display File Size and Transaction Number
The DataRow_ElectronicDelivery data row template does not display the associated file size and transaction number for requests.
Bug# 18112
0 votes -
Default FAQ web page contains inaccurate information about cookies
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
0 votes -
ViewSearchResults.html contains an incorrect <u> tag
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
0 votes -
The default selection in the Appointment dropdown is inconsistent
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
0 votes -
Request datarows contain an empty hyperlink when item title is missing
When no item title is provided, the request datarows will contain an empty hyperlink which may cause confusion for screen reader users.
Bug# 17579
0 votes