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

[Bug 29037] New: Accessibility: OPAC breadcrumb links don't have sufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29037 Bug ID: 29037 Summary: Accessibility: OPAC breadcrumb links don't have sufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The OPAC breadcrumb links are on a grey background and don't have sufficient contrast. This makes the text difficult to read and fails to meet accessibility criteria. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 29035] New: Accessibility: OPAC masthead_search label doesn't have sufficient contrast ratio
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29035 Bug ID: 29035 Summary: Accessibility: OPAC masthead_search label doesn't have sufficient contrast ratio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The contrast ratio for the OPAC mast_head search label fails to meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 29034] New: Accessibility: OPAC nav-links don't have sufficient contrast ratio
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29034 Bug ID: 29034 Summary: Accessibility: OPAC nav-links don't have sufficient contrast ratio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The contrast ratio for the OPAC navigation links (Cart, Lists, Login, Search history, Delete your search history)fails to meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 27279] New: "Checked out by" not populated on issuehistory.pl
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27279 Bug ID: 27279 Summary: "Checked out by" not populated on issuehistory.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Activating the sypref RecordStaffUserOnCheckout, the librarian who checked out the item is not displayed on "Checkout history" tab on biblio view as it's described in release notes for bug 23916. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 29106] New: Can we get rid of Koha::Item->effective_itemtype
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29106 Bug ID: 29106 Summary: Can we get rid of Koha::Item->effective_itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I file this bug to gather some ideas. Do we still need that pattern here? Right now we send a warning to the logs each time an item doesn't have an item type set. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 10385] item-level_itypes checks need to be refactored
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|item-level_itype checks |item-level_itypes checks |need to be refactored |need to be refactored -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10385] item-level_itype checks need to be refactored
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy(a)rijksmuseum.nl --- Comment #3 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- I would love to change this title to : item-level_itype checks need to be removed -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3142] Standardize how OPAC and staff determine requestability
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3142 --- Comment #47 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Bug 29106 comment14 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29019] New: Unable to delete HTML customization
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29019 Bug ID: 29019 Summary: Unable to delete HTML customization 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Hi all, I don't know if I'm just not doing it right, but I cannot seem to be able to delete an HTML customization. To replicate : 1. Go to Tools > HTML customizations 2. Click on New entry 3. Fill out the form (I tried it with OpacSuggestionInstructions and OpacLoginInstructions) 4. Click Save 5. In the list of HTML customizations, click on the Delete button at the end of the row -> Note that it goes back to Additional contents (News) instead of Additional contents (HTML customizations) 6. Go back to Tools > HTML customizations -> Note that the entry you deleted is still there Since it goes back to Additional contents (News) after deleting, I'm wondering if it has something to do with the separation of News and HTML customizations... Caroline -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 3142] Standardize how OPAC and staff determine requestability
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3142 --- Comment #46 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Jonathan Druart from comment #45) > (In reply to Jonathan Druart from comment #44) > > Created attachment 125951 [details] [review] [review] > > Bug 3142: Handle biblio level item type > > Something like that? Yeah, looks like it. But we should definitely get rid of this preference. The maintenance cost is much higher than the user benefit (where a large majority is not using it; 95% or more?) At upgrade time we could set items.itype correct for this minority and make sure that the itype at item creation defaults to 942c correctly. It was discussed already somewhere. We should do it in 22.05. Didnt test this change yet btw. -- You are receiving this mail because: You are watching all bug changes.

1 0