https://wiki.evergreen-ils.org/ 2026-04-30T10:30:34+00:00 https://wiki.evergreen-ils.org/ https://wiki.evergreen-ils.org/lib/exe/fetch.php?media=wiki:logo.svg text/html 2023-07-19T15:48:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:aria&rev=1689781713&do=diff ARIA ARIA is a group of HTML properties and attributes that describe an element’s role, name, and state. Each of these attributes affects the way screen readers announce the element and what keyboard shortcuts it provides. The WAI-ARIA specification exposes built-in browser semantics that are used by assistive technologies (primarily screen readers), and allows us to manipulate them to provide better in-page navigation and support for interactive elements. However, there are many instances whe… text/html 2023-07-10T20:13:56+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:books&rev=1689020036&do=diff Books on Accessibility For everyone * Accessibility for Everyone, Laura Kalbag – an introductory book * Microcopy: the Complete Guide, Kinneret Yifrah – includes some valuable chapters on error messages, designing empty states, and cognitive accessibility For developers * Form Design Patterns, Adam Silver * Apps for All, Inclusive Design Patterns, and Inclusive Components by Heydon Pickering – the most highly respected books on accessible app design text/html 2023-07-10T20:15:01+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:browsers&rev=1689020101&do=diff Browser Support for Accessibility Features * a11ysupport.io text/html 2023-07-10T19:50:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:common_issues&rev=1689018629&do=diff Common functional issues * Alternative text for images and icons * Color contrast * Keyboard navigation * Link and button names * Page titles * Language attributes and multilingual content * Time limits * Sensory disruptions: flashing lights, animation, sounds * Data tables, dyslexia, and dyscalculia text/html 2023-07-13T22:01:03+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:component_references&rev=1689285663&do=diff Accessible Component Libraries * Deque University Code Library * Accessible Components by Scott O’Hara * Inclusive Components by Heydon Pickering * US Web Design System Components * Gov.UK Design System Components * Adobe React ARIA * Note that the table component here is actually a grid, meant for spreadsheet-style apps where every cell is interactive. This is not appropriate for a read-only (or read-mostly) table, even though that’s what they use in the demos. text/html 2024-07-11T19:19:03+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:documentation&rev=1720725543&do=diff Documentation Guidelines The Documentation Interest Group (DIG) has had some discussions regarding using language in official documentation that takes accessibility into account. Re: Fwd: [WebAIM] Protocol when writing app instructions - FIXME link not working 2024-07-11 text/html 2024-07-29T20:08:36+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:forms&rev=1722283716&do=diff Forms Forms are incredibly challenging for screen reader users and people navigating via keyboard. The most common problems are missing labels (or placeholders used as labels), custom controls that are inoperable via keyboard, and hints, instructions, and validation error messages that are misplaced, hidden, or otherwise not properly associated with the relevant inputs. text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:home&rev=1644518097&do=diff Accessibility Web Content Accessibility Guidelines (WCAG) 2.0/2.1 <https://www.w3.org/TR/WCAG20/> Open LP Bugs tagged as "accessibility" text/html 2023-07-10T22:12:55+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:intro&rev=1689027175&do=diff Introduction to Accessibility Types of Disabilities and Assistive Technology Types of disabilities that affect people’s ability to use web interfaces include visual, audio, motor, speech, and cognitive disorders. These may be chronic conditions or temporary problems due to illness or injury. text/html 2024-04-24T23:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:lang&rev=1713999611&do=diff Language Attributes, Multilingual Content, and Screen Reader Pronunciation Each page must have a primary language set via the lang attribute on the <html> tag. Any changes in language within the page should be marked using additional lang attributes on the surrounding text/html 2023-10-13T20:32:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:links&rev=1697229144&do=diff Links and Navigation Note: as of early October 2023, the Sandbox (/staff/sandbox) contains a series of examples for text-only buttons, buttons that look like links, icon-only buttons, and buttons with both icons and text. (See the commit.) Copy the appropriate example to ensure your links and buttons are accessible. text/html 2024-01-08T22:05:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:menus&rev=1704751545&do=diff Navigation Menus Top-level menu items should be <a> links if they go directly to another page or route, and <button> if they contain a dropdown or trigger some other JavaScript-based action. The top level link text and caret indicator should be part of the same button, not separated. The button should use the text/html 2024-11-08T21:30:10+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:opac-314&rev=1731101410&do=diff OPAC Accessibility bugs fixed in 3.14 Most of these bugs were identified by the 2023 Voluntary Product Accessibility Template / Accessibility Conformance Report for the OPAC and an early 2024 review performed by the National Network for Equitable Library Service of Canada. Note: this list does not include accessibility bugs fixed in the staff client. * #1409389 Bing SEO Analyzer complains about multiple <h1> tags in a single page * #1467645 OPAC's search results use of nested tables creat… text/html 2024-02-05T21:53:05+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:pagination&rev=1707169985&do=diff Pagination The US Web Design System's usability guidance on pagination is very thorough. Some brief highlights: * Wrap the list in <nav> and use an unordered list for individual items. The <nav> tag should have an aria-label attribute, and the label should serve to distinguish this from the main navigation menu. text/html 2023-07-10T17:20:35+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:quick_fixes&rev=1689009635&do=diff Quick Fixes (the TL;DR) * Run Axe Dev Tools tests after making changes to a screen. [Enable keyboard navigation](#testing-keyboard-navigation) in your browser and tab through the page to make sure the order is sensible, you can always see [which element has focus](#visible-focus), and you can reach all the interactive controls. text/html 2024-04-24T22:38:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:requirements&rev=1713998307&do=diff Accessibility Requirements The Web Content Accessibility Guidelines(WCAG) are a set of international standards for accessible web interfaces. The Authoring Tool Accessibility Guidelines (ATAG) apply to software used to produce web content, like content management systems and WYSIWYG editors. Generally, laws require web-based software to meet text/html 2023-08-07T21:25:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:select&rev=1691443547&do=diff Select Lists, Comboboxes, and Autocomplete The native HTML ''<datalist>'' element works well with screen readers, but (like <select>]], its options can’t be styled. The Open UI group is advocating with browser developers to open up more browser elements for CSS styling. In the meantime, we need to make our replacement components as accessible as possible. text/html 2025-03-07T22:04:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:sidebar&rev=1741385052&do=diff Accessibility Guide * Quick fixes (the TL;DR) * Introduction * Accessibility testing * Accessibility in the Evergreen stack * Requirements and legislation * Documentation Standards * Common functional issues * Alternative text for images and icons * Color contrast * Keyboard navigation * Link and button names * Page titles * Language attributes and multilingual content * Time limits * Sensory disruptions: flashing lights, animation, sounds * Data tables,… text/html 2023-07-10T19:48:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:stack&rev=1689018530&do=diff Evergreen’s Accessibility Context Evergreen is written in Angular using the ng-bootstrap framework, which is an implementation of Bootstrap. Evergreen therefore inherits most of the accessibility problems present in the frameworks, and it is up to us to work around them. Evergreen also includes some older screens written in AngularJS and Dojo, which may introduce their own accessibility bugs. These screens are in the process of being rewritten in Angular. text/html 2025-03-07T22:04:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:start&rev=1741385094&do=diff Accessibility * Quick fixes (the TL;DR) * Introduction * Accessibility testing * Accessibility in the Evergreen stack * Requirements and legislation * Documentation standards * Common functional issues * Alternative text for images and icons * Color contrast * Keyboard navigation * Link and button names * Page titles * Language attributes and multilingual content * Time limits * Sensory disruptions: flashing lights, animation, sounds * Data tables, dysle… text/html 2023-07-10T21:26:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:structure&rev=1689024385&do=diff Headings, Landmarks, and Structure Pages without semantic structural markup will sound like one long run-on sentence when read aloud by a screen reader. With proper structure, the user will get a better idea of what the content means. For example: text/html 2023-08-07T21:50:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:tables&rev=1691445024&do=diff Tables and Grids While it is possible to to use CSS flexbox and grid layouts to make any set of elements look like a table, you should use proper tables whenever both the horizontal and vertical axes contain information that is relevant to a cell. text/html 2023-08-07T21:37:06+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:tabs&rev=1691444226&do=diff Tab Sets (aka Navs in Bootstrap 4) Tabbed interfaces are generally considered problematic for accessibility purposes, because they make it difficult for visually impaired users to construct a mental model of the content on the page. There is an open debate about the order in which tab names should be read, and discoverability vs. usability. The text/html 2024-10-10T18:25:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:testing&rev=1728584712&do=diff Accessibility Testing Testing for accessibility involves a combination of automated testing tools and manual testing procedures using your keyboard. You can add screen readers, switches, or other devices as necessary, but you can find the majority of problems without any extra equipment or software. text/html 2023-07-10T20:57:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:titles&rev=1689022667&do=diff Page Titles Page titles should be unique. Screen readers will announce the page title when a new page loads, and users should be able to understand what new page they are being taken to. * #2008794 Several admin pages need <title>s text/html 2025-08-11T23:10:40+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:vpat&rev=1754953840&do=diff Evergreen VPAT / ACR Evergreen's Voluntary Product Accessibility Template / Accessibility Conformance Reports are below. * (early 2025) * 3.11 OPAC (2023) * Staff client: no third-party review available; see OPAC 2025 ACR for Evergreen 3.14 The latest Accessibility Conformance Report, for Evergreen 3.14, is now available. It reflects the significant progress made since 3.11. text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=accessibility:webclient_audit&rev=1644518097&do=diff Accessibility Web Client Audit In June 2019, the Center for Inclusive Design and Innovation (CIDI) completed an accessibility audit on the Evergreen web client. The audit was paid for with a grant from the Georgia ADA coordinator's office. It was completed on a test server using the PINES database, running version 3.2.3.