Aeon Known Issues
186 results found
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages
-
Aeon System Manager does not refresh custom field definitions
The Aeon System Manager caches custom field definitions defined in the Customization Manager and does not automatically refresh these when new entries are made.
Bug# 18405
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Aeon Client Options form controls are incorrectly aligned
The controls located within the Aeon Options form in the Aeon Client are not aligned properly within the borders of each section of options on this screen.
Bug# 18418
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.2.11 Default Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 default web pages
-
Appointment merge fields are blank when used in Transaction type email templates
Appointment merge fields used in Transaction type email templates will appear blank when emails are generated for the template.
Bug# 17993
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.2.11 Default Web Pages
-
Alma Primo Catalog addons do not display linked records
The Aeon Alma Primo and Alma Primo VE Catalog addons may only import one call number for a record associated with multiple call number entries.
Bug #17908
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Alma Primo Catalog Addon v1.5.4 and Aeon Alma Primo VE Catalog Addon v1.0.3.
-
Request creation validation error message is inaccurate when the specified username doesn't exist.
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 casesBug# 17575
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages