Skip to content

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

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

    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. Errors related to appointment fields are sometimes not announced by screen readers

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

    Bug# 17577

    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. Switch buttons on request forms can overflow on certain display/screen sizes

    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

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

    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. Default page title for FirstTime.html is not sufficiently unique and descriptive

    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

    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. Default form field border colors do not meet contrast requirements

    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

    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. Focus indicators for interactive controls do not meet contrast requirements

    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

    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. Focus indicators for hyperlinks do not meet contrast requirements in some cases

    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

    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. Keyboard controls cannot be used to dismiss cookie notification popup

    Keyboard controls cannot be used to dismiss the cookie notification popup in certain web browsers.

    Bug# 16945

    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. Reading rooms may allow overbooking when a full-day appointment is modified by staff

    If a reading room is configured to only allow full-day appointments (i.e., if the minimum and maximum appointment length are equivalent to the open hours duration), and one of the booked appointments for a particular day is manually adjusted by staff in the Aeon Client to a shorter duration, the reading room will allow an additional appointment to be booked that day, leading to potential overbooking.

    Bug# 16912

    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. Billing Account field label has incorrect 'for' attribute value

    The Billing Account field found in the PhotoduplicationRequest.html file, Generic Photoduplication request pages, and all corresponding edit pages for these files contains an incorrect value in the label element's 'for' attribute. This value should match the 'id' attribute value in the field's input element to avoid accessibility issues.

    Bug# 16833

    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. Selecting a "Request For" value may cause validation issues with billing fields on EADRequest.html

    If any billing fields (Format, Service Level, Shipping) are marked with the HTML5 'required' attribute on an EADRequest.html form that also uses a photoduplication request toggle option, selecting a "Request For" value may enable these fields when they are hidden by the toggle and cause the request to fail browser validation.

    Bug# 16440

    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. Appointment scheduling web calendar incorrectly shows the entire day as unavailable when a Reduced Availability exception is set

    When setting a Reduced Availability exception for a reading room in the Customization Manager's Appointment Scheduling tab, the appointment scheduling calendar on the web pages shows the entire day as unavailable, even if seats should be left after the reduced availability is set.

    Bug# 16362

    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. SLRequestLimitMet status line appears incorrectly on ViewUserReviewRequests

    When submitting a request that would meet or exceed the request limit on the ViewUserReviewRequests page, the SLRequestLimitMet status line text will appear but will be formatted incorrectly on the page. The user also will not be returned to the top of the page.

    Bug# 15801

    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. Status lines are missing from GenericRequestManuscript/MonographPhotodup when using Clone to Copy option

    Accessing the GenericRequestManuscriptPhotodup or GenericRequestMonographPhotodup request forms from the Clone to Copy option in the Actions menu or Transactions details page will cause the status line(s) not to appear on the page.

    Bug# 15485

    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. "Skip to main content" link remains invisible when focused on in certain browsers

    The "Skip to main content" link remains invisible when it is focused on using the keyboard in certain browsers including Chrome and Safari. The link appears as intended in Firefox.

    Bug #15254

    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. Edit option within the Transaction Menu can still be activated by keyboard when disabled

    When the Edit action is not allowed for a request, the button is visually disabled and made un-clickable within the Transaction Menu options but can still be activated using the keyboard, which takes the user back to the main menu page with a status message.

    Bug #15246

    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. <#OPTION> web tag cannot be used to automatically generate a list of checkbox options for CustomDropDown-type custom fields

    Using the <#OPTION> web tag to automatically generate a list of checkbox options for a group defined in the CustomDropDown table does not work if the group is a CustomDropDown-type field defined in the CustomFieldDefinitions table.

    Bug# 14532

    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. Cloning a photoduplication request in the web creates a non-photoduplication request

    Cloning a photoduplication request from the web interface will take the user to the default request form for a non-photoduplication request.

    Bug# 14459

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

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)