July 2024 - Koha-bugs - lists.koha-community.org

[Bug 23264] New: OPAC elements with class="dropdown" include incomplete WAI-ARIA Menu
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23264 Bug ID: 23264 Summary: OPAC elements with class="dropdown" include incomplete WAI-ARIA Menu Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: brian(a)mcneil.ly QA Contact: testopia(a)bugs.koha-community.org Details: Buttons that spawn items with role="menu" must indicate this fact with aria-haspopup="menu", and an aria-controls attribute referencing the id value for the element with role="menu". On expansion, focus should move to the first menu item, and focus should be tracked with either a roving tabindex attribute (so one menu item is always focusable) or tracked with an aria-activedescendant attribute on the element with role="menu". aria-expanded can be used to indicate the state of the button and its attached menu (e.g. expanded or collapsed). This paradigm may apply to over OPAC menus, such as the Lists Menu on the homepage. Steps to Reproduce: 1. Navigate to the element with id="langmenu" 2. Verify this item does not have an aria-haspopup attribute 3. Activate the element, verify a menu appears 4. Verify this content contains an element with role="menu" 5. Verify focus has not moved to the first menuitem beneath the menu 6. Use the arrow keys to adjust content within the menu 7. Verify tabindex attributes are not adjusted and aria-activedescendant is not set on the element with role="menu" Actual Results: Screen readers and other assistive technologies may be unable to interact with content as intended if ARIA controls are not coded to spec. Expected Results: The above listed attributes are added to the button item and element with role="menu". An example of a fully implemented button spawning an element with role="menu" (in this case using aria-activedescendant) can be found at: https://www.w3.org/TR/wai-aria-practices/examples/menu-button/menu-button-a… -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 26813] New: Accessibility: Review labels of page elements
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26813 Bug ID: 26813 Summary: Accessibility: Review labels of page elements Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: kathryn(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some page elements are not consistently labelled. Tested this on the staff interface home page only. Would be great to learn the best way to label page elements, make those changes, and test with a screen reader. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25153] New: Accessibility: 1.3.1 Info and Relationships
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25153 Bug ID: 25153 Summary: Accessibility: 1.3.1 Info and Relationships Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org Blocks: 23003 There are a few cases where we are not adhering to the 'Headings to Introduce content' guidelines for a A accessibility rating. Headings should be used to introduce the content on all pages, this bug serves as a collector bug for cases where this guideline is not being adhered to. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 [Bug 23003] Accessibility improvements -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 26811] New: Accessibility: Improve staff client usability for non-mouse users by changing order of page elements
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26811 Bug ID: 26811 Summary: Accessibility: Improve staff client usability for non-mouse users by changing order of page elements Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: kathryn(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The order of page elements could be improved to enhance the user experience for any user that does not use a mouse and instead tabs through, e.g. screen-reader users or those who prefer to only use the keyboard. To reproduce: When on the staff interface home page, try tabbing through the page elements. Notice the order you go through the elements. (I will open other bugs to address the highlighting of elements, and labels). Currently the first tab goes to the submit button, then back to the check out tab under the search box, then through everything in the left hand column. Suggested order: the next elements to tab across after submit and Check out are the Checkin, Renew, Search Patrons, Search the catalog (all the items across the tabs under the search box), then to the top News block (in case libraries use this for urgent announcements?), back to the modules, then on to the other things down the left hand navigation. Open to other input on the order or things. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25150] New: Accessibility: 2.4.10 Section Headings
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25150 Bug ID: 25150 Summary: Accessibility: 2.4.10 Section Headings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There are a large number of cases where we are not adhering to the Section Heading guidelines for a AAA accessibility rating. Headings should be incremental, this bug serves as a collector to find and fix cases of this rule being broken. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 37391] New: QR code for biblio record in OPAC should use canonical link
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37391 Bug ID: 37391 Summary: QR code for biblio record in OPAC should use canonical link Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: schodkowy.omegi-0r(a)icloud.com Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 35812 In /opac-detail.pl page there's an option to show a QR code to open up said record on your phone or share it with others in such a way. Currently, it simply uses the current `location.href` of the browser. This isn't ideal, because such URL can be much longer, resulting in more complex/harder to scan QR code, plus URL parameters can contain extra junk, such as our previous search query that led us to current record, which we might not necessarily want to share. Thus, now having simple canonical URLs after the "Depends On" patch was merged in, we can replace these QR codes to link to them instead. Example old URL: https://koha.example.com/cgi-bin/koha/ opac-detail.pl?biblionumber=12345&query_desc=test Example new URL: https://koha.example.com/bib/12345 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35812 [Bug 35812] Should specify canonical URLs to help search indexers -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 16846] New: Move patron related code to Koha::Patron
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16846 Bug ID: 16846 Summary: Move patron related code to Koha::Patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 70

[Bug 37362] New: Do not show the lists button if there are no public lists and opacuserlogin is off
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37362 Bug ID: 37362 Summary: Do not show the lists button if there are no public lists and opacuserlogin is off Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org If all of the following are true: - Lists are enabled (virtualshelves is on) - opacuserlogin is turned off (users cannot create their own lists) - There are no public lists ...then we should not show the "Lists" button in the OPAC header. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 36083] New: Not able to create customizable areas to intranet home pages that are library specific
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36083 Bug ID: 36083 Summary: Not able to create customizable areas to intranet home pages that are library specific Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When testing the enhancement coming in 23.11, bug 6419, it appears that library-specific text does not display as it should with the HTML Customization tool. Process to test: 1. Tools> HTML Customizations 2. Choose to create an entry in StaffAcquisitionsHome 3. Assign it to a specific library 4. Add text and publication date. 5. Save 6. Go to the Acquisitions Home page - logged into that library, no text displays. This enhancement does work if creating an entry for 'all libraries'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 35100] New: Items assigned to StockRotation do not advance if a reserve is triggered before the initial transfer
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35100 Bug ID: 35100 Summary: Items assigned to StockRotation do not advance if a reserve is triggered before the initial transfer Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I have not recreated personally, but we have found evidence of this multiple times on a site using stock rotation Scenario: 1 - Item is added to stock rotation 2 - The cronjob creates a 'StockRotationAdvance' transfer 3 - The item is checked in, which initiates the transfer, however, a hold is triggered 4 - The hold is confirmed, which cancels the StockRotationAdvance 5 - The item is checked out and returned 6 - The stock rotation cronjob eventually calls Koha::StockRotationItem->needs_advancing which looks for all StockRotationAdvance transfers, ordered by date arrived 7 - The only one has a NULL date arrived 8 - The date arrived is put into dt_from_string, which returns today when given null 9 - The date object above then calls 'delta_days' from dt_from_string() 10 - The number of days from NOW to NOW is always 0 11 - The item does not advance until manually forced -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 94