Review of Navigation, Accessibility and Hierarchy for Queue monitoring

[cdpestitschek]

Where: Flex - Queue monitoring (real time)
To: Supervisors
Scenario: We’re adding a feature that allows us to define groups of queues to be monitored. This includes a queue configuration page and the respective dashboards for those queues, as well the display definition of those queue groups. Below each category on the Figma file, you’ll find the questions I’d like feedback on, along with the proposed examples.

Side navigation - Would the correct approach be to extend the component with the entry point, or have a separate bar with only the submenus?

Side navigation - Should the menu indentation be on the same level as the configuration page, or should there be extra space to highlight that they are subpages?
On the left is the Component I got from Paste Figma file, and on the very end right there is one example how it is implemented on Flex today

Switch component - Is it necessary to have a label to the right of each component switch?

Action per row - Is it necessary for the "Delete Dashboard" button to be red (destructive colour)?







:figma: Figma

[TwilioPasteBot]

Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary.

---

Sorry, I don't know how to help with that.

I did do a search though, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:

• Insights - Editor mode, renaming, accessibility and feature find ability (updated: 05/11/2023, similarity score: 86%)
• Flex teams - Combobox functionality and Search (updated: 10/02/2024, similarity score: 86%)
• Accessibility in Flex Insight UI (updated: 04/26/2024, similarity score: 86%)

[roxanagomez]

Hey @cdpestitschek thank you for signing up for office hours. To help clarify before meeting, could you expand a bit on the hierarchy and content? For example:

• Queue monitoring: Does it contain a table with all the created queues?
• Queue detail pages: Are these for specific settings or configurations for each queue?
• All queues: What kind of information would go here?

Also, is there a reason why you would not want to have the "Delete Dashboard" button red?

See you soon!

[cdpestitschek]

Hi @roxanagomez thanks for getting back. Here are some clarifications:

Queue Monitoring: Does it contain a table with all the created queues?
Yes. All created queues are displayed and managed on this page.

Queue Detail Pages: Are these for specific settings or configurations for each queue?
The Queue Group detail page displays the specific group of queues defined, along with configuration options (or customisations), such as filters and thresholds.

All Queues: What kind of information would go here?
“All Queues” refers to a default dashboard page that includes a group of all queues. The Supervisor will be able to view this default layout with values populated, so they won’t initially face a blank page or be prompted for an initial configuration.
Additionally, this setup helps with feature onboarding, as the Supervisor can see the default view (“All”), with the option to create a new group for a customised dashboard view.

Also, is there a reason why you would not want the “Delete Dashboard” button to be red?
There’s no strong reason, but it could be too visually prominent, especially considering the number of queue groups.

Please let me know if you need any additional information.

Kind regards,
Carol

[serifluous]

Hey Carol! Thanks for joining office hours today. Here's the recording for today's meeting.

We talked about:

• Exploring using the In Page Navigation component as sub-navigation
• Using the Table Header as a label for all Switches in a single column, and using Screen Reader Only to visually hide labels from each individual Switch control while still allowing it to be available to assistive technology.
• Making sure there's a confirmation message when groups are deleted with an "Undo" action. And testing whether using the destructive variant of the Button is necessary given that the action is fairly low-risk and low-priority, especially when paired with an "Undo" button. Or exploring moving actions into an overflow menu.