Accessibility: WCAG 2.1 AA Compliance. (UXPROD-216)

[UXPROD-2194] Extended browser support besides Chrome Created: 12/Dec/19  Updated: 09/May/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Accessibility: WCAG 2.1 AA Compliance.

Type: New Feature Priority: P2
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: accessibility
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-730 Manually test of FOLIO test system in... Open
relates to UIEH-76 Cross Browser Support Closed
relates to UIIN-1489 Selection almost invisible when movin... Closed
Epic Link: Accessibility: WCAG 2.1 AA Compliance.
Development Team: None
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: 5Colleges (ERM Jun 2020): R4
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R4
Rank: MI State-Lib of MI (Sum 2021): R3
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Overview: Early on in the project we decided to use Google Chrome as the default browser, but it was never the intension that FOLIO should not be supporting other of the primary browsers, e.g. Mozilla Firefox, Opera, Safari and Microsoft Edge.

Background:
Web Content Accessibility Guidelines (WCAG) 2.1, an accessibility standard required by law in the European Union and many other countries, requires in its section 4:

4. Robust

Content must be robust enough that it can be interpreted by by a wide variety of user agents, including assistive technologies.

Guideline 4.1 Compatible

Maximize compatibility with current and future user agents, including assistive technologies.

Browsers are user agents. Supporting all primary browsers makes it more likely that we support a browser that works with the assistive technology (like braille display) the user needs.

Cross-browser compatibility is state of the art and is supported by most frameworks and software libraries, it requires little effort. Not supporting the primary browsers puts libraries at riskĀ of being sued for violating the disability act.

Status as of Juniper 2021:
FOLIO supports only Chrome. And in this context the "Support" means that the FOLIO project is obligated to fix rendering bugs for Chrome browser only. As of right now, if rendering bug found in Fire Fox, Safari or any other browser we don't have to fix it - Jiras are closed as "Won't Do": https://folio-org.atlassian.net/issues/?jql=(text%20~%20firefox%20OR%20text%20~%20safari)%20AND%20resolution%3D%22Won%27t%20Do%22%20


Generated at Fri Feb 09 00:21:56 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.