UX Enhancements (UXPROD-856)

[UXPROD-1668] Make FOLIO Work with IE 11 Created: 14/Mar/18  Updated: 30/Jun/22  Resolved: 30/Jun/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: UX Enhancements

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: IE, accessibility, front-end, triaged, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File inaccessibleIE11.png    
Issue links:
Relates
relates to FOLIO-730 Manually test of FOLIO test system in... Open
Epic Link: UX Enhancements
Development Team: None
PO Rank: 2
PO Ranking Note: CB: Leaving ranking at calculated
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: MO State (MVP June 2020): R5
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

1. Access IE 11
2. Go to any folio URL (or use this one - http://folio-snapshot-stable.aws.indexdata.com/)
3. See screenshot below of what you will see ... a blank screen

NOTE: I know that the goal for beta is to support Chrome but at some point we will need to support IE 11 as it is a key browser for using a screenreader.



 Comments   
Comment by Marc Johnson [ 25/Apr/19 ]

Cate Boerema Khalilah Gambrell Given that this issue is unlikely to be resolved soon, and likely requires changes across multiple modules by many teams.

Is there a way that we can classify this differently to reflect that scope, maybe as an umbrella or a feature?

Comment by Cate Boerema (Inactive) [ 26/Apr/19 ]

I converted it to a UXPROD feature.

Comment by Kristin Martin [ 03/May/19 ]

Chicago is not ranking and will defer to the Accessibility work. If IE is truly the only mechanism some users have to successfully read screens, then it seems like this work will be necessary. However, I would really question this even Microsoft is recommending people move away from this browser, it would seem like screenreader applications will need to adjust and work with other browsers as well.

Comment by Erin Nettifee [ 18/Sep/19 ]

Should this be a feature instead for Edge? What's expected for screen reader work?

Comment by Tod Olson [ 09/Oct/20 ]

Given where IE 11 is in its life cycle, I would suggest closing this ticket and opening a new one for the needed accessibility hooks.

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