Ojas writes from an archivist's report:
The Firefox Reader Mode doesn't work in our finding aids hosted by Islandora.
The text compacts and simplifies as hoped, however all of the files within a
series or subseries of a finding aid disappear. Try it out with one of our finding aids,
https://digital.library.pitt.edu/islandora/object/pitt%3Aus-ppiu-ua90f68?search_api_fulltext=starzl#aspace_ref1993_g84
First un-nest the finding aid by clicking the "Expand All" link. I wonder if there is something in our Islandora configuration
that causes the browser to interpret the files (the lowest level entry in a finding aid in our nested Series, Sub-Series, File) as
extraneous, like an image or some other useless thing on a web page.
The issue seems to be the fact that nested fieldsets aren't well supported by screen readers. Given that we probably want our website to be accessible via screen readers, this does seem like an actual bug that should be fixed, rather than just one person's preference.
Matching the heuristics of a non standardized tool like this will always be a moving target, and so being downstream to changes can make any effort we put irrelevant if heuristics change (the time scale of changes from git blame seem to be on the order of 2-10 years). However, firefox and chromium based browsers make up a large majority of browser market share with no real competition either.
Both chromium and firefox implement reader views. The tag doesn't show up on either chrome or firefox. I don't think we need to hold a commitment to supporting reader views, but given the small number of targets, it is worth a conversation with web services.
Ojas writes from an archivist's report:
The issue seems to be the fact that nested fieldsets aren't well supported by screen readers. Given that we probably want our website to be accessible via screen readers, this does seem like an actual bug that should be fixed, rather than just one person's preference.
Matching the heuristics of a non standardized tool like this will always be a moving target, and so being downstream to changes can make any effort we put irrelevant if heuristics change (the time scale of changes from git blame seem to be on the order of 2-10 years). However, firefox and chromium based browsers make up a large majority of browser market share with no real competition either.
Both chromium and firefox implement reader views. The tag doesn't show up on either chrome or firefox. I don't think we need to hold a commitment to supporting reader views, but given the small number of targets, it is worth a conversation with web services.