/
2025-12-01 Cross App SIG Meeting notes

2025-12-01 Cross App SIG Meeting notes

 Date

Dec 1, 2025

Attendees

  • @Tara Barnett

Homework

  • None!

Housekeeping

Recording:

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 min

Announcements/Housekeeping

 

 

Recent Activity in Slack

 

  • Kimberly’s Post:

    • While having to create various records for testing, and using tab for navigation, I realized that in a lot of apps when you press the space bar to create a new accordion item (e.g. address in Organizations), the active location lands on the button after the new accordion. If you prefer tabbing through things, this means you have to tab all the way back to the beginning of the accordion (or use the mouse) to get to the beginning field. It's not really a huge thing, and I'm not even sure whether an alternative would be possible, but it could save a little bit of time if the active field landed at the beginning of the new accordion. I can add this to the Acq Implementer's list for those apps, but I wondered if it would fit here? I know it is true of Data Import profile creation as well. Not sure of other apps.

      • Kimberly asked if there's a desire for consistent positioning of the cursor/focus in apps across FOLIO. Assuming there is, is this a problem for Cross App SIG or for the individual SIGs?

        • There are several apps where the cursor jumps *past* the expected location--Kimberly specifically points out the first new address in Organizations.

        • There was some discussion in slack with Owen, John, and Zak. Zak points to the guidelines available here: https://dev.folio.org/stripes-components/?path=/docs/guides-accessibility-accessibility-overview--docs#focus-management

        • Owen says "It sounds like in terms of fixing any existing behaviour it would just down to us to report issues one-by-one to the appropriate teams?" All agree--these issues should be submitted individually.

        • So then, the only outstanding question is, do we as a SIG pick through FOLIO to find as many bad cases as we can, or do we let these surface naturally within their individual SIGs?

          • Should this go to the accessibility SIG?

          • We will post to the accessibility SIG.

  • Item State (Laura)

    • Does anyone else see Item state (https://folio-org.atlassian.net/browse/UXPROD-1321 ) and related features as relevant to Cross-App SIG? I'm bringing it up here because I was reminded by an event earlier today that the work was never completed and some of the ways Item status functions now cause some major headaches, at least at Cornell. I'm thinking we might want to look at it because while Item status resides in Inventory its relevance is largely in other apps, and it often can only be added or changed through processes in other apps.

      • Laura asked if Item State is within the purview of Cross App SIG, and if we're interested in making an effort here.

        • Martina and Owen discussed on slack. Because of the movement of information between apps, this feels like a cross-app issue. Item state was previously discussed as part of a cross app sig working group: https://folio-org.atlassian.net/wiki/spaces/AppInt/pages/4096977

        • Should we take this on? What do we want to accomplish by looking at it?

  • Search Documentation Discussion

    • Covered above and previously--but do check it out!

Notes

 Action items