Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation

Aeon Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

91 results found

  1. Editing an appointment on the web forces manual confirmation

    An appointment must be manually confirmed/re-confirmed after it is edited on the web, even when the option to auto-confirm appointments has been enabled for the reading room in the Aeon Customization Manager.

    Bug# 24074
    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  2. Past appointments and future appointments with start dates exceeding the Min Lead Days for the reading room are not viewable on web

    Users cannot view appointment details on the web interface for appointments with start dates in the past or with start dates exceeding the Minimum Lead Days setting for the reading room. Clicking on an affected appointment will display the SLAppointmentAssociationError status line to the user (default text: "Error: You cannot view an appointment you are not associated with.").

    Aeon 5.2

    Bug# 22857
    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  3. Aeon 5.1 Scheduled Date date picker calendar does not properly color disabled dates

    Disabled dates are not colored correctly in the date picker tool used with the ScheduledDate field in the Aeon 5.1 web pages.

    Bug# 22802
    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  4. JavaScript console error may occur when using the appointment scheduling web interface

    After typing a date manually into the Appointment Date text field on a web request form, pressing the TAB key or clicking the mouse to move focus elsewhere will return a JavaScript console error in the web browser.

    Bug# 19926
    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  5. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  6. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  7. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  8. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  9. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  10. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  11. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  12. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  13. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  14. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  15. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  16. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  17. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  18. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  19. Default button colors do not meet contrast requirements in certain cases

    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
    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  20. 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# 17580
    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
← Previous 1 3 4 5

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)