Skip to content

Summary

Madison TUG's Q3 2026 meeting, "A Smorgasbord of Bite-Sized Topics", held in person at the Goodman Community Center in Madison with presenters and attendees online. Robert Salas hosts the tasting menu.

Elisa Davis and Emily De Padua, who started critiquing each other's Iron Viz entries and presented this session at Tableau Conference, open with "How to Critique Dashboards (and Build Better Ones)". Dashboards are a communication tool, so vague feedback leads to miscommunication and scope creep. Elisa's Plus/Delta asks what is working and what to change; Emily's CLEAR framework (Context, Layout, Encoding, Attention, Refinement) is a checklist for keeping feedback objective. The room critiques one of Elisa's own expense dashboards, the frameworks turn the result into 35 objectives, and the session shows how to group and prioritise them before revealing the rebuilt dashboard. They close with where to practise (Back 2 Viz Basics, Makeover Monday, Iron Viz qualifiers, the #community-viz-feedback Slack channel) and how to find a friend you trust with feedback.

Paul Costanzo then shows parameter use cases: a Top N parameter that also groups everyone else into All Others, a measure swap (and why aggregate and non-aggregate fields can't be mixed in it), swapping whole worksheets with a parameter, and a parameter list that updates from another data source. Questions cover tracing daisy-chained parameters, documenting workbooks with Describe Sheet or a plan-build document, and letting Claude run Tableau to write documentation.

Robert Salas builds a hex map of Wisconsin's counties from a hand-plotted grid, explains why hex maps give Rhode Island the same weight as Texas, adds a second measure with a dual-axis shape layer, and wires a drill-down to a county map using a parameter as an empty cup, a change-parameter action and sheet navigation.

Olivia Butler closes with Tableau accessibility: the WebAIM numbers (56.1 million errors across a million pages, with low-contrast text and missing alt text the top failures for seven years), POUR and WCAG AA, which Tableau elements screen readers can reach, mobile layouts, tab order, plain language, colour rules (never the only signal, consistent across categories, and build in grayscale first), extensions such as Export All and natural-language summaries, embed-code fixes, and when an HTML table on the page serves users better. The meeting ends with upcoming Wisconsin and Madison TUG events and a swag draw.

Listen to this TUG

Prefer to listen? This meeting is also an episode of the Tableau TUG recordings podcast.

Key points

  • Dashboards are a communication tool, so vague feedback causes miscommunication and scope creep.
  • Plus/Delta asks what is working and what you would change; start with the plus.
  • CLEAR (Context, Layout, Encoding, Attention, Refinement) keeps dashboard critique objective and complete.
  • Group and prioritise feedback before acting on it: 35 objectives is a list, not a plan.
  • When in doubt, add more padding; space lets the pieces breathe.
  • A Top N parameter with a set can show the top customers and lump everyone else into All Others.
  • A parameter can act as an empty container that a dashboard action fills, which makes drill-downs possible.
  • Hex maps give every state or county equal visual weight, so small areas are as visible as large ones.
  • Low-contrast text and missing alt text have been the top web accessibility failures for seven years.
  • Never use colour as the only signal; build in grayscale first and add colour where it shows the trend.
  • Some Tableau content is better served as accessible HTML on the page than forced into a viz.

Jump to a chapter (44)

  1. 0:00 Welcome to a smorgasbord of bite-sized topics
  2. 2:40 Elisa Davis and Emily De Padua: how to critique dashboards
  3. 6:53 The problem with dashboard feedback
  4. 9:51 The Plus/Delta framework
  5. 10:30 The CLEAR framework
  6. 14:34 Using the two together
  7. 15:11 Live critique of an expense dashboard
  8. 20:18 Plus/Delta on the example
  9. 21:35 CLEAR on the example
  10. 26:57 35 objectives: prioritising the feedback
  11. 30:14 The reveal: before and after
  12. 32:26 Resources, and finding a feedback friend
  13. 36:18 Why feedback matters
  14. 37:50 Parameters, Tableau's superpower
  15. 39:53 Paul Costanzo: parameter use cases
  16. 40:17 Top N plus All Others
  17. 43:42 Swapping measures
  18. 46:14 Swapping worksheets with a parameter
  19. 48:10 A parameter list from another data source
  20. 51:52 Q&A: Top N and parameters as containers
  21. 54:53 Q&A: tracing parameters and documenting workbooks
  22. 1:01:25 Q&A: letting Claude document a workbook
  23. 1:04:08 Robert Salas: hex maps
  24. 1:08:50 Building a hex map in Tableau
  25. 1:12:19 A second measure with dual-axis shapes
  26. 1:15:49 Drilling down to a county map
  27. 1:20:10 A parameter as an empty cup
  28. 1:22:09 Change-parameter and sheet navigation actions
  29. 1:25:39 A custom icon resource
  30. 1:29:46 Olivia Butler: Tableau accessibility
  31. 1:31:29 Web accessibility by the numbers
  32. 1:34:11 POUR and WCAG AA
  33. 1:37:45 What screen readers can reach in Tableau
  34. 1:39:03 Mobile layouts
  35. 1:42:07 Navigation devices and tab order
  36. 1:43:03 Plain language
  37. 1:44:31 Colour rules
  38. 1:47:36 Cognitive overload
  39. 1:48:46 Extensions and natural-language summaries
  40. 1:50:19 Testing with assistive-device users
  41. 1:53:18 Embed code fixes
  42. 1:55:40 When HTML beats a viz
  43. 1:57:21 Q&A
  44. 2:01:39 Wrap-up, upcoming events and swag

Transcript

0:01 Robert Salas: I'm gonna be wearing my sunglasses a little bit, 'cause I, uh, had my eyes dilated a few hours ago, so please don't, uh, judge me.

0:08 Uh, we're gonna go through a number of topics today. We're glad to have you here.

0:11 Couple of bite-sized presentations on a couple of different topics.

0:16 We have two, um, lead speakers that we're going to… Or, or headline speakers that we're gonna start with, Elisa Davis and Emily De Padua, who are gonna talk about how to critique crap dashboards, not bad nothing, and then build better ones from that, using critique and a critical eye to design better dashboards.

0:33 Paul is gonna talk about using parameters. Hi, Paul, in the back.

0:37 I'm gonna then talk about, um, mapping. We're gonna do a hex map today with some interactive drill down, and Olivia is gonna talk about bringing accessibility, um, rules, policies, and guidelines into our dashboard stuff. Now, I just named a bunch of people, but I f- didn't mention Jen. So this is our Madison TUG leadership team. Jen Shepherd, long time, everybody knows her.

0:57 Paul Costanzo in the back.

0:59 Emil- excuse me, Olivia Butler, and myself, Robert Solis. So we're glad to see you here, and thanks for coming out, coming out of the house. Who came from work?

1:08 Who came from your office?

1:10 Who came from work from home? Thank you. Thank you for leaving your house and coming out, and not in pajamas. That's how we want it to come. Um, we have been hoping to rebuild our in-person events, and so thank you for supporting that and being here today. It means a lot.

1:25 Um, our next event, 'cause it's winter, will be virtual. But in the new year, 2027, we'll be doing, um, in-person events again as we mix them in. So anyway, again, welcome. I'm gonna switch over here in a few minutes to Emily and Elisa, who are gonna present virtually on their talk, How to Critique Dashboards and Build Better Ones.

1:46 If you want some snacks, they are in the back. We have fruit snacks available. There's goodies on your table. Uh, sparkling water of various ilks. There's some cold in the cooler bag. There's some li- larger variety, uh, in the box on the table.

1:59 Let us know if you need anything. If you can't hear the presentation, definitely let me know, and I'll try to adjust volume and whatnot. We know it's always tricky to do these, uh, combined events.

2:10 So, um, you can read on the screen a little bit of the bio of these two. I'm gonna let them introduce themselves as they see fit a little bit more. I didn't have room for their full bios, 'cause they are both very, very accomplished women. Not only are they are both, um, Tableau ambassadors, visionaries, uh, representatives, have been to, uh, Iron Viz and, uh, well beyond me.

2:31 I'll let them toot their own accolades as they see fit. We're very honored to have them presenting for us today. So ladies, I'm gonna turn it over to you and struggle with the sharing screen nonsense here again. Just a moment.

2:46 Okay, should be yours to take over.

2:49 Emily De Padua: Okay. Thank you for having us.

2:52 So I…

2:55 Elisa, I can't see you because of the way that it's set up, so we'll just…

3:01 Actually, one second. Sorry. 'Cause that, that kind of weirds me out that I can't see.

3:07 Um, just this real quick.

3:11 Elisa Davis: Yeah. It's, it's worth taking the time to get our faces.

3:14 Emily De Padua: Yeah. It, it's kind of weirding me out. Okay.

3:17 All right.

3:18 Elisa Davis: Um, and I can do a little bit of introductions while you're fiddling with that.

3:22 Emily De Padua: Yeah.

3:22 Elisa Davis: So I'm Elisa Davis, and I am thrilled to be presenting today with one of my good friends, Emily De Padua. Emily and I go way back. We met on Twitter when everyone was still there, uh, doing critique of each other's Iron Viz competition entry submissions before we turned them in. Um, it was my very first year.

3:46 Emily, unbeknownst to me, had already been selected as a runner-up, so I was glad that I hadn't looked up who she was before we got to chatting. But we started out with feedback and accountability, and then this year at Tableau Conference, uh, several, several years later, we got to talk about bringing our special sauce of critiquing dashboards in order to help people design better ones to the Tableau Conference stage.

4:14 We had about 300 somewhat attendees.

4:18 Um, but if you weren't able to catch us, here we are today doing a rerun. Um, so forgive us if we're a little rusty. We've given this talk a couple times, um, but not recently, and I'm gonna hand it back over to Em, who is our, uh, official kicker-offer.

4:36 Emily De Padua: Thank you, Elisa, and hi, everyone. Uh, thanks for bearing with me as I figured, you know, I figured out the lay of the land, but also really appreciate Elisa for being such a great vampir.

4:49 Um, as she mentioned, this is How to Critique Dashboards and Design Better Ones. Um, Robert already gave us a really great introduction to the group. Um, but here we are, Elisa Davis and Emily De Padua coming at you live-

5:05 Elisa Davis: And what do you do for work right now, Em?

5:07 Emily De Padua: I am currently a lead business intelligence analyst. Um, I'm based in New York, but I live in New Jersey. Woot, woot. Um, what about you, Elisa? What do you do?

5:18 Elisa Davis: I am a freelance full-time consultant, and I have some availability on my calendar. So if you want to bring me in-house to talk about what this looks like in practice, give me a call after this.

5:31 Um, I'm mostly focused on Tableau, but I'm also exploring a lot of AI work and how we can use AI to accelerate our builds and go beyond the dashboards.

5:44 Emily De Padua: All right. And so for today's, for today's agenda, we've already knocked out one of our items, the introduction. Hello, hello, everyone. Incredible. Then we're gonna talk through the problem with feedback. Why sometimes we love it, and other times we… hate it, but at the end of the day, we really ultimately do need it.

6:06 Um, th- from there we're gonna introduce two frameworks that will help you turn vague opinions into actionable insights.

6:15 And then from there, because you gotta see it to believe it, we're g- then gonna give you an e- a demonstration of applying these frameworks in action. And finally, we're gonna have a conclusion, sharing some resources. We baked in Q&A directly into our timing and everything, so please feel free to save your questions for the end. We will get through them, and ultimately say thank you for joining us today.

6:39 Elisa Davis: Mm-hmm.

6:39 Emily De Padua: Um, sounds good? Yeah.

6:42 Elisa Davis: Sounds good to me.

6:43 Emily De Padua: Cool.

6:43 Elisa Davis: And we can't see the room, so it's just gonna be-… how it goes.

6:49 Emily De Padua: Okay.

6:52 Okay. So Elisa will take it away to talk about the problem with dashboard feedback.

6:58 Elisa Davis: So I'm assuming, and we did a show of hands, but I can't see your hands, but I'm assuming that our audience here is mostly developers, people who create dashboards.

7:11 And the thing with dashboards is that we're not usually the primary consumers of our work product. So because dashboards are a communication tool, um, it's ultimately trying to communicate with other humans about typically a complicated decision. So you make your best guess at a product, but since you're not making it for yourself, you can't give yourself feedback on whether or not it answers the question or suits the tool.

7:38 So you have to go ask someone, "Is this what you had in mind? Does this work?" Or, "How can it be improved?" And feedback can be tricky.

7:50 Um, you know, it can be really helpful to guide design decisions.

7:57 Um, say, "Yes, this is what I'm looking for. Yes, these metrics look correct." Or, you know, "I wish that we could click this. I wish that, you know…

8:08 That this is fantastic. How, when can I get it, my hands on it?" But sometimes if you just ask somebody, "Hey, can I get some feedback on this?" You'll get scope creep. If you ask three people, they might love or hate different parts of what you've built. Uh, different teams can have different priorities, whether that's in terms of how the information is displayed, how it's sliced, or want to control how it's interpreted, for really reasonable reasons.

8:40 And then finding that balance of if it's simple enough to be understood but complicated enough, complex enough to be useful, that's a hard needle to thread. So, uh, and you can end up at the end of the day with massive scope creep as a result of feedback that can get in the way of shipping a usable, usable, useful product. So

9:04 why is all of this so hard? It is hard because, as I alluded to before, dashboards are a communication tool that help people make decisions based on complex information. And the thing that we know about human communication is that the only natural outfor- outcome of communication, the thing that's definitely gonna happen at least a little bit every single time, is miscommunication.

9:30 But thankfully, we can use some frameworks to reduce that.

9:39 So when Emil and I were putting together this talk, we talked about what feedback frameworks we each personally used, and how we wanted to approach this.

9:52 I typically use a Plus Delta framework in evaluating almost anything, um, including when I have my eight-year-old trapped in the backseat and I want to know, uh, his reaction to how gymnastics class went.

10:09 But it applies very well to dashboards.

10:13 Um, it's straightforward.

10:16 It's called Plus Delta. We'll get into the details in the next slide.

10:20 And you can communicate effective dashboard feedback in any context with any data partner. It really does fit any situation.

10:31 Emily De Padua: And then I will be talking about the CLEAR framework. So for me, I need an… a lot of objectives. Kind of like a list of what to look for, keep my focus. And so the CLEAR framework, it's a mnemonic device for context, layout, encoding, attention, and refinement. And it's ul- the goal of it is ultimately to empower teams to identify the actual tasks.

10:55 Like, I'm looking at this dashboard, what am I supposed to look at? And actually, like, have I gone through this entire checklist of things? To kind of keep the feedback objective, but also focused and, um, intentional.

11:08 And so CLEAR framework, you're… I was saying these like categories, what does it all mean?

11:14 Well, in this handy-dandy table, 'cause, you know, we all love tables, um, I lay out here the focus of context, layout, encoding, attention, and refinement. So, and the supporting questions I'm trying to answer. So for context, who is this dashboard for? What is this supposed to drive? And then examples of what that looks like. So someone asking, "Is this like a rep- a static report, or am I supposed to be able to explore this as an operational dashboard?" Layout is, how is the information being organized?

11:46 And that could be someone's feedback of like, "What does… Hey, can we put the KPI cards to the top of the dashboards instead of like to the left-hand side?" Um, encoding, which is how is… Ultimately how is this designed, and are we using the right visuals? So that could be feedback, getting… such as like, "Hey, I think the insight's a little clearer to me when it's a bar chart instead of a pie chart." Attention.

12:10 So first impressions are important. And so attention is what draws the eye first, what is being emphasized.

12:17 And again, that's qui- that's an example of the color used has me focused on segments underperforming versus over-performing, which we'll talk about in our example. And then finally, refinement, which is after looking at these, the first four categories with a fine-tooth comb, magnified glass, pointing out these little bugs, can we take a step back and look at the whole product as a whole and go, "How can this be elevated?" And it's a little bit of thinking of a next step, because as we know, dashboards are not always one and done things.

12:48 They're maintained products that we have to iterate on. Um, and so an example of that as a dashboard feedback is someone going, "Hey, for the next iteration, can we include different date cuts, or can we make the date cuts dynamic?"

13:03 Um, and with that, I will hand it over to Elisa to talk about the Plus/Delta framework.

13:10 Elisa Davis: Thanks, Em. So as I alluded before, uh, the Plus/Delta framework is simple enough to be applied to any situation. Um, it… The plus part of Plus/Delta is what's working well.

13:23 And when it comes to dashboards, some examples or more specific questions of what's working well. You might think, "What's clear at a glance? What design choices support the main insight, and what should stay? If you threw out this entire dashboard to completely rebuild it from scratch, what would you save?" Um, the proverbial baby in the bathwater.

13:47 And then the Delta represents the question, what would you change? What's unclear, distracting, or missing?

13:56 Is there anything that you could change to make the insight easier to see?

14:01 And the goal here is to suggest specific, realistic improvements, something that a developer might actually be able to do if they had another 15 minutes to touch the project, hour to touch the project, day.

14:17 Um, things that could get accomplished, and ideally that would stay somewhat adjacent to the original scope of the project.

14:28 That's the realistic part of the, uh, realistic improvements.

14:34 Emily De Padua: And so we're not trying to say use one or the other. Actually, it's the opposite. We're saying you can actually use Plus/Delta and CLEAR hand-in-hand together. Um, we suggest starting with the plus in Plus/Delta to kind of identify, hey, here's what's working. Then going through CLEAR, the CLEAR framework that we just discussed, and then ultimately ending the feedback process with the Delta takeaways.

14:59 So it's kind of like a spectrum, kind of like our lovely little demonstration we have here.

15:05 Um.

15:10 Elisa Davis: So that's been a lot of us yapping, talking about some very abstract ideas and feedback frameworks.

15:19 Um, we thought that you might enjoy seeing this in practice. So, uh, always one to, uh, you know… You don't… We, we talked about what dashboard to pick, and we didn't wanna pick on someone else, so we're picking on me.

15:37 Uh, this dashboard in the QR code might or might not work, but if you're, um, if you're online, the link, this is the before dashboard at the top of the chat.

15:52 Um, and apologies if you're in the room. You can search for Elisa Davis on, um…

16:02 Emily De Padua: Got it.

16:03 Elisa Davis: Perfect.

16:04 Emily De Padua: Wow.

16:08 Elisa Davis: It, it's, it's on my Tableau Public page. And so this before was an exercise that I did taking an accelerator, which was very complicated, and trying to pull out a few core ideas.

16:21 I made it easier to understand, but it was far from perfect. So we decided to pick on this as an example of the CLEAR and Plus/Delta fe- frameworks, and we would like to pause for a solid two minutes. What do you think, two minutes?

16:39 Emily De Padua: Yeah, two minutes. And by then, hopefully my Wi-Fi hasn't crashed.

16:44 Elisa Davis: And give you guys a chance to think about what's going well, um, what you would suggest changing, and run through those elements of the CLEAR framework.

16:55 We've got them up on a slide.

17:02 Robert Salas: Okay, this is an in-team activity, you guys, to take a look at it and then think for yourself what-

17:06 Elisa Davis: Yeah

17:06 Robert Salas: …

17:07 positive about this, what do you like, what are the pluses?

17:11 Look for contacts, layout.

17:13 Elisa Davis: Em, do you wanna click back over to the slide?

17:15 Emily De Padua: Yes.

17:17 Robert Salas: There we go.

17:19 Um, I'll be, I'll give you a second.

17:23 Elisa Davis: Who is this for? What action should it drive? How is it organized, designed?

17:30 What do you pay attention to?

17:33 How could it be elevated?

17:36 Robert Salas: Yeah. So if you… Could you put the QR code back up real quick please, ladies? If you have a laptop and you go to Tableau Public and search for Elisa Davis, D-A-V-I-S, um, you can get on your laptop and look at it more clearly.

17:49 Yeah.

17:50 Bring your own thoughts and critique to it. What would you say you like about it, do not like about it? What could you do better?

17:58 What would you change about it?

18:00 Emily De Padua: Ooh, the QR code isn't working.

18:02 Robert Salas: All right, we're gonna start the clock for two minutes.

18:06 Amazing how fast two minutes goes by.

18:09 I'll try and serve as a liaison for collecting Uh, feedback from our room here.

18:16 Ladies, can you put your, uh, dashboard back up on the screen?

18:19 Emily De Padua: Sure.

18:20 Elisa Davis: Yeah, sure.

18:22 Robert Salas: Anybody wanna volunteer a thought?

18:25 Yay.

18:26 Audience member: Hi, yay. Ooh, we, we liked, uh, the KPIs, um, and, uh, how they show a trend.

18:35 Robert Salas: She said that they like the KPI and how it shows the trend.

18:38 Which looks like up and…

18:42 Oh, that's an area chart behind there, okay.

18:45 What else?

18:47 Other thoughts on…

18:49 Be courageous, shout something out.

18:52 Yeah?

18:54 Audience member: Five seems like a lot of bar charts.

18:57 Robert Salas: Five does seem like a lot of bar charts.

18:59 How many is enough, really?

19:02 How many is too many?

19:05 Audience member: Five.

19:08 Robert Salas: Who agrees that five's too many for one dashboard?

19:12 Yeah?

19:13 Elisa Davis: It depends.

19:14 Robert Salas: It depends. Well, I, I would say that's a lot of colors. I don't think they go together. It's a lot of golden rod.

19:22 Other thoughts? Is that kind of a hand?

19:24 Audience member: I was gonna say, five with all different axes.

19:27 Robert Salas: Five with all different axes. That's actually a really specific critique, yeah.

19:31 They're not very comparable.

19:33 Elisa Davis: Yeah.

19:35 Robert Salas: What else?

19:38 Audience member: Um, the titles are, are too wordy.

19:42 Robert Salas: The titles are too wordy.

19:44 They also seem a little bit small. I can't quite read them, but that might just be me today.

19:50 Uh, last, last thou- yes?

19:55 I was wondering what the colors mean. What do the colors mean? Yeah, I didn't see a legend. Like the bars?

19:58 Yeah, like blue versus red. Blue versus red. Okay.

20:02 Yeah, so that's our in-room critique, constructive con- criticism.

20:09 Elisa Davis: Perfect.

20:12 Um, we, we had a lot of the same thoughts, and now we're going to run through the PLUS Delta framework and the CLEAR framework together, and look at how we would fix this. And then we will end with, uh, the reveal of our after, where we incorporated this feedback.

20:33 So the plus in PLUS Delta, to answer what is clear at a glance, and remember we're just focusing on the good parts right here.

20:45 Um, consistent color palette, and there are clear titles and dates.

20:52 Um, which design choices support the main insight? KPI and trends are a good orientation.

21:00 The information is clearly presented and not overwhelming.

21:04 And while, uh, you could debate the correct number of bar charts, the design is fairly streamlined, and we wanted to keep that aspect of the dashboard in a redesign.

21:18 But Em, we had plenty of stuff to pick apart.

21:22 You wanna run us through it?

21:25 Emily De Padua: I will, with pleasure. Um, a- similar to what Elisa was saying, a lot of what we hear in the room is very much aligned to what we discover as we go through the frameworks. Um, by this point we're gonna introduce the CLEAR framework, so o- objectively just going focus area by focus area on what we're looking for. So when we were asking the question, who is this for, the question that we came up with was like, ooh, we're not really sure.

21:49 Like, is this for executives, department leaders, individuals? You know, if it's for execs, then it's not really appropriate to have individual employees called out by name in one of the five bar charts. Um, and then in terms of function, we asked, could users understand, track, and mitigate year over year company spending?

22:08 And that led to these objective an- actions of like, okay, so we have to align the data granularity and views to be for executives. That's what we ultimately came away with. Being like, let's make this an exec facing view.

22:20 Um, we're gonna aggregate views featuring individual employee names, so no one's getting called out on a big dinner out on company money. Oopsies. Just kidding. No one said that. And then re- ultimately reframing this as an operational dap- dashboard that can inform and enable decision making.

22:39 Um, so the next section, we then went to L, as in layout, had… and tried to answer questions of how is this information organized. Our thoughts and takeaways were, well, the current iteration is more like a report than a dashboard, which, fair.

22:54 The content flow could be a little hard to follow. It's not really, you kind of go left to right, and you're going down, and then, like, the areas kind of jump a little bit.

23:03 Um, while there is a visual hierarchy introduced that we can see at a glance, titles and sections, there's not a real clear de- delineation with that. And who, I can't see in the room, but how many of you saw there was a filter pane in the original viz?

23:21 Elisa Davis: I forgot and I built it.

23:24 Emily De Padua: And so that led to some objective f- actions, like you're seeing. Some more objectives being added of like, okay, so let's update the layouts to be more classic business dashboard layout with a clear filter pane placement, establish a consistent visual hierarchy, and experiment with section sequencing to have a bit more of a flow. Cool. Now we're at, like, what six?

23:45 Six objectives, let's keep going.

23:47 Elisa Davis: Let's keep going.

23:48 Emily De Padua: E as in encoding. So how is this designed?

23:52 What we thought, color. While there is a consistent use of color, we're just not sure what the colors are meant to convey, which is a common thing being said in the room and on… as we were going through this exercise. Um-

24:04 Elisa Davis: And they're ugly.

24:06 Emily De Padua: Beauty's in the eye of the beholder.

24:10 Or your QA developer.

24:12 Um, so chart choice selection Mo- makes sense, but we hear you in the room of, like, let's have some variety. We love, we love variety in life. Um, the titles are clear in the sense of, like, it's telling you- What question is this chart supposed to answer?

24:27 Um, and then ultimately we wanted to reconsider the use of reference lines for benchmark comparison since, again, it's just, like, not quite clear to us.

24:35 Um, so two more objectives came out of that. One was to use color with purpose, either as a category or as a highlight. Explore alternative visualizations, both for the benchmark comparisons and as the room I- I'm gathering would be like, overall, we've more than just five bar charts.

24:54 Cool.

24:55 Now we're at A, as in attention. So what's drawing the eye first? For us, the color was what grabbed our attention, even more than the leading question section headers.

25:05 Uh, the reddish colors on the KPIs pulls the attention to them, but it isn't clear if it's being used as in an alert or a default color. So it's not just the color palette itself, but it's also the use of the color. And then ultimately, like for us, the KPI overview, we kind of glazed over it and went straight down to the middle of the page and went downward.

25:25 So the KPI overview didn't really stand out to us, um, which meant an objective action was add a legend and some user guidance to communicate color meaning across the dashboard.

25:36 Increase or maybe reorganize how the KPI overview section sizing or how it's laid out, maybe to have a bit more of an eye-catching design.

25:45 We got one more section, which is R, as in refinement. So we've been going through the first layers, um, the first letters, all our different focus areas, but now we're trying to take a step back. Instead of looking at a particular corner of the viz or a section of it, now I just want to look at it as a whole and ask, "How can this be elevated?" And one is, can we introduce company branding style to standardize the visual hierarchy?

26:08 So font size, color, et cetera.

26:11 Let's consider some UI/UX feature enhancements, and again, a metric storytelling flow.

26:17 Um, that leads to four more objective actions of, let's refresh the color sect- selection to align with company brand standards.

26:26 Explore adding in a download data button, a reset filter button, et cetera. Ensure cohesive visual flow from an overall to a detailed granularity, which is kind of like an expansion of some previous objectives we identified earlier. And then ultimately at the end of the day, um, this is like my personal take, is when in doubt, add a little more padding to all your elements because letting your pieces kind of breathe within the viz in spacing really can elevate a design.

26:58 Let's do the math, though. That was like, what? 35 objectives. Uh-oh. That's a lot of objectives. That's a lot.

27:04 Um, so how do we, how do we prioritize, how do we decide what's, what is gonna be going to be done? What can be done? Because I don't know about you, but as, as a developer, if I were to get 30, 40-something objectives, I would just be like, "Okay, you hate my work. Cool. Thanks for letting me know. Let's start over." Just kidding.

27:30 Um, I wouldn't throw the towel in like that. But you know, it's just like, where, where do we even begin beyond just rolling our sleeves up?

27:42 Elisa Davis: And so that's where we come back to the plus delta framework. We can use those sub-questions to organize and prioritize the feedback to turn it from, you know, a laundry list brainstorm session into an email or Slack or whatever, whatever your communication method of choice is, that you could hand back to the developer or have as the takeaway from the meeting notes.

28:08 So inter- the answer of what feels unclear, distracting, or missing, what would make the insight easier to see.

28:15 Audience and intended key takeaway is unclear. Use of color is distracting.

28:21 And a clear visual hierarchy aligned with story flow would make the insights easier to see. The s- specific realistic improvements that we suggest are clarify the dashboard purpose and audience, align views to exec or operational use, create a stronger visual hierarchy, which includes all of the objectives around reworking the layout, filters, KPI placement, and section flow.

28:52 Use color intentionally. Decide whether it means category, alert, or emphasis.

28:58 And then as nice to have refinements, we suggest using brand styling, reset download buttons, or added padding.

29:08 And I wanna make the point here that a dashboard, like this is k- a great tool to use if you've inherited a dashboard.

29:17 Even if it's you're being asked to take a second look at a dashboard that you made as good as you had the time for in the first iteration, there's always the opportunity to come back and improve it. And I think that, um, if I got this as a developer, I would feel pretty good about what I needed to do to make it stronger for my audience. And if I was a consumer sending this feedback back to a developer, I would feel pretty confident that I wasn't going to make them go cry in a corner or, you know, flip me off and drink a beer.

29:53 So since we're, we're aligned around trying to get the work done and improve communication and improve the data product, uh, you know, it's, it's nice to be able to communicate a need for change in a way that, uh, you hope will make the recipient open to change.

30:12 So as our after, uh, Em did take this dashboard. She took the feedback, and if you want to, uh, to give us the reveal.

30:25 Emily De Padua: Some drum roll in the room a little while later.

30:30 We now have this expense dashboard.

30:35 Um, I will also throw this up on my screen so everyone can have a little bit of a look.

30:42 Um,

30:44 so before, and here is our after.

30:47 Elisa Davis: Ooh.

30:47 Emily De Padua: You can see here…

30:49 Yeah. Thank you. So you can see here we've introduced a layout change color. We decided to align it to the company's standard, the company branding standards. We introduced some new chart types. We got a scatter plot, we have a tree, we have some tree maps up here. We have a reset filter button that if you just click, so if you go through all the filtering.

31:12 Of course. Of course, Tableau filter. But, um, again, and we have a filter pane to our left. So who, who can see the filter pane now?

31:21 Um, again, this isn't, like, an end stage, you know.

31:26 In the next iteration someone could, like, in our hypothetical demonstration, someone would see this and be like, "Okay, cool." So, like, the next step, and then we go through the whole Clear saga all over again.

31:39 Elisa Davis: Mm-hmm.

31:39 Emily De Padua: Clear plus Delta saga all over again.

31:42 And then with that,

31:47 ends up with our conclusion.

31:50 And so we're just gonna wrap up some…

31:53 A- after going through our frameworks and everything with you all, as well as the demonstration, seeing the before and after, we're just gonna wrap up our conversation with, um, with some key takeaways, some resources, and then of course Q&A, and ultimately saying thank you for having us.

32:09 Robert Salas: Anybody have any questions for them?

32:11 Comments? What a different dashboard, eh?

32:14 Two hands up who thought it was way better.

32:17 Two hands up who didn't think it was way better.

32:20 Two hands up. Everybody thought it was way better.

32:22 Emily De Padua: Cool. Thank you. Thank you for being our eyes in the room, Robert.

32:26 So just some additional resources from Elisa and I. These are a smattering of books that we have read over the years as we've gotten more comfortable giving and receiving feedback. And again, it's, it's a process of figuring out what works best for you, what works best for you and your team, the people that you work with. Um, and yeah, just we love reading.

32:50 And then we also, in additional resources, we also have some community challenges, um, that has really helped us kind of refine our process. Um, as well as the Community viz feedback channel on Tableau Community Slack. And you could be like me and Elisa and just find a friend and start your own feedback circle.

33:11 Robert Salas: I'm curious with the find a friend and start your own, did you guys have any hurt feelings to begin with?

33:16 Elisa Davis: No.

33:16 Robert Salas: You have to find a friend you, you trust with feedback.

33:21 Elisa Davis: How do you find a friend you trust with feedback? I think…

33:25 Well, so for us, Emily and I were both creating public work.

33:30 And putting ourselves out there.

33:32 So I knew that I liked her design eye, and we were originally just working on a project together, and it started as accountability of like, "Hey, I'm doing this. Are you doing it?" You know? And getting that last pair of eyes. Uh, you know, like, "Can you look at this real quick before I release it to the world?" So you kind of start with lightweight feedback of like, "Hey, does, is my slip showing?" That level of feedback.

34:00 Um, you know, not that we wear slips anymore, but uh, and yeah, like look for somebody else who's putting things out there or whose opinion you would respect. And I think starting by asking for feedback is, is the way to go. Or another thing is if anyone is participating in any of these community challenges, a lot of times when they share their work, they'll say, "Be open to feedback," or "Feedback requested." Um, I actually did 2 or 300 iterations of Plus Delta, uh, feedback on Twitter back in the day, uh, using Plus Delta for the Back to Basics project.

34:45 Specifically one tweet of feedback, so that's like 230 characters, um, for anyone who had specifically requested it.

34:56 So I don't give feedback to people who don't want it, but if you ask for it, it's a great way to practice looking at things and thinking about what is working well, um, what could be better.

35:08 And it's really fun when people take the suggestions and go do another iteration, and you can see that it, it really did make a difference.

35:16 Robert Salas: That's very kind of you to do so many. 100 and change.

35:20 Elisa Davis: Wow.

35:20 Robert Salas: But yours asked for feedback. I know Jen and I worked together for a while, and I, I call it fresh eyes syndrome. Sometimes you just need a pair of fresh eyes, right?

35:27 Elisa Davis: Yeah.

35:27 Robert Salas: Like, "Can you take a look at this?" 'Cause you, you, you've looked at it too much and you're not seeing the things, and it takes like 30 seconds for somebody else to, to see the thing a lot of times, right?

35:36 Um, so yeah, just start-

35:38 Elisa Davis: And another thing is that it's a great way to network if you're an introvert, 'cause you're not just reaching out to someone cold. You actually have something to talk about. Or you're asking them for a small favor or, you know, you're doing a small favor for them.

35:54 Robert Salas: Awesome.

35:54 Elisa Davis: Builds trust, gets to know each other.

35:56 Robert Salas: Yeah.

35:56 Elisa Davis: And then, you know, you might find out that you have a lot of fun things in common.

36:01 Emily De Padua: Yeah.

36:02 Robert Salas: That's true.

36:03 Emily De Padua: I-

36:03 Robert Salas: A discussion about work can lead to other social discussions.

36:07 It's fun.

36:08 Emily De Padua: Elisa, I have a question.

36:09 Elisa Davis: What's up?

36:10 Emily De Padua: Why does this all matter? Asking feedback. Why does feedback and asking, like asking, receiving feedback, giving it, why does this, why does this all matter at the end of the day?

36:21 Elisa Davis: Well, as we talked about in the beginning, whether you want it, need it, hate it, love it, feedback is- Part of communication, and it's specifically part of dashboard development, and it can either bring you together or push you apart. So we encourage you to bridge the gap and hope that these tools will help you do that.

36:49 Yay.

36:50 Emily De Padua: Thank you, everyone.

36:53 Elisa Davis: And we do have time for questions, I think.

36:55 Robert Salas: I'm channeling the applause.

36:58 We really appreciate you joining us today. You're welcome to stay, but thank you for the, uh, fascinating presentation. I plan to use this. I'm gonna draft it for my teaching. It's such an easy, clear framework. So I hope I can steal it, borrow it.

37:10 Emily De Padua: Uh, it's clear. It's clear.

37:14 Here's a little slide if everyone wants to take a picture or screenshot this. Um, we're happy to share the slides after this as well, but this kind of gives you the little… like a little summary cheat sheet.

37:25 Robert Salas: Awesome. Good resource.

37:26 Elisa Davis: And I don't see any Q&As in the chat online. Were there any in the room that we haven't addressed yet?

37:35 Robert Salas: I like how you guys went back and forth, and, and I like the, the plus clear delta. That's actually, um, the way you laid that out I think works really well.

37:44 All right. We are gonna proceed to our next part, which is Paul, who's gonna talk about using parameters.

37:51 We use Tableau to accomplish a bunch of things. Does anybody not know what parameters are? Kind of as a baseline. Okay. I'll give a… Do you mind if I give a quick-

37:59 Paul Costanzo: Go for it.

38:00 Robert Salas: Parameters. Parameters, hmm. Parameters are, parameters are like the superpower of Tableau. I use them all the time because they live above the data sources, and you can have them go over to this data source and do some stuff, and go over here to this data source and do some stuff. And the data sources themselves don't actually have to really interact with each other.

38:17 The parameter translates between them and says like, "I picked the value. Give me your stuff and give me your stuff, and I'll display them together even if they aren't, you know, joined in a normal database way." Um, we also can use parameters to drive filtering. We can use them to drive sheet behavior, which Paul's gonna show.

38:35 Um, as noted on here, we use it to do a variety of swapping.

38:39 No, it's not the TV show White Swap. It's dimension swapping, measure swapping, and sheet swapping. And it just means when you pick a parameter value, I want to see sales, Tableau's like, "Okay, I'll give you sales." And you're like, "No, never mind. I changed my mind. I want to see gross margin dollars," and it'll display that instead. Or, "I want to see count of students," it'll give you that instead.

39:01 But it does it in the same chart, so it saves you a lot of real estate to do swapping, whether it's dimension, parameter, um, or worksheets. I just pulled one of these the other day, and our client wanted to basically replicate this archaic system they have where they can build their own report but in Tableau.

39:20 Paul Costanzo: Okay.

39:20 Robert Salas: And he's like, "I think we need fifteen tabs for all these different combinations." And I was like, "How about one, and I do dimension swapping and measure swapping? And I'll give you two dimensions, so you can pick your left and your top and make your own cross tab, and you can choose what measure to shove in there." And they were pretty happy with that.

39:37 Um, it's a little slow because of the amount of data, but you can even do dates across the top if you want that running, so.

39:44 All right, we're gonna do, uh, our own swapping. You ready?

39:47 Paul Costanzo: I think so.

39:48 Robert Salas: All right, patience, patience ready. Life support's good.

39:51 Here you go.

39:53 Paul Costanzo: Hello. I'm Paul. Um, and I am the, I should say one of the old, but probably the old dog at Navique. Um, and in all fairness, it's, it's been a bit since I've done a, a non-client technical presentation. So as you can see, please, please bear with me as I knock some of the, some of the rust off, um, to go through some things. Robert gave you a great overview.

40:17 We're just gonna take a couple minutes here and talk about some use cases, um, for parameters and, and really three main topics, and we'll start off, um, in the idea of using a, an, a parameter as a top end to give me N number of values for a certain found set. So put the glasses on to see. So I'll show you the end result here, and then we'll come back.

40:38 So if we have a file with customers, I can come in here and I can do, you know, a parameter setting that I can turn around and determine, you know, how many customers we're going to show in the view, and I can, you know, fill in those different types of values. The other, the other thing– I'll, I'll show you the whole thing first and then go back and show you the pieces as far as the build.

40:57 The other thing that was kind of interesting is I, I had seen a, a presentation where they took not just, not just the top end customers, but then using that same value to, to lump everybody else into others. So saying, "Okay, I wanna see the top four customers, but then tell me how that rates to all the others in, in there as well." So that's this idea of I can come up and say, "Well, you know what?

41:20 I wanna see the top nine, but yet I also wanna see the totals for what everybody else does at the exact same time." Okay? So kind of an interesting, kind of an interesting use case as far as bringing those together. And then the nice thing is at the end of the day, we can turn around and we can go to, you know, bringing these, those together and saying, "Okay, now I wanna see top six customers, you know, by sales, but then also see the top six customers versus everybody else." And so that's kind of the idea here of what we're looking to get to.

41:51 Make sense? I did, we did take some time, so, so these files will be uploaded. You'll be able to look at these. But we took each of those panels and gave you kind of– we just labeled them start, where if you did wanna go through and try some of these and, and go through kind of step by step, do each of the elements here in terms of, you know, create a parameter, show the parameter control, build the rows.

42:12 And all of those are already spelled out for you. I won't, I won't bore you with the idea of going through step by step, even to the point where, you know, if you wanna make the titles dynamic, you can go in here and click on that, you know, and you can do all those types of things. So we tried to make it as much of a how-to as possible if someone hasn't had experience with these types of, um, these types of things.

42:34 Um, and then one of the things that the talking point here, y- you know, the, the idea- Is this, this fact that the parameter, it's just a number. So really what we're doing is we're basically using that parameter in conjunction with a calculated field to then determine what is and isn't going to show. Make sense?

42:53 Any questions, comments on that?

42:55 Good. Okay, so that's, that's simple.

42:59 The next thing we'll show is Robert mentioned kind of a, a file, a swap file. Um, and this is really just the idea of using a parameter to swap different things within, within the worksheet. So we can use the parameter to swap dimensions. So in this case, I can come up here and say very simple, again, super short demo, sales by ship mode. I can come out and say, "Well, let me sh- see sales by region." So all I'm doing is using the parameter to sh- to, to swap that different dimension in place and then use that to see, to adjust my view.

43:33 Okay? Really simple pro- simple concept in terms of the how that goes. The next part of that, in addition to swapping a parameter, or I'm sorry, a dimension, is the ability to swap a measure. So again, we're just swapping it across. So we're sitting and saying, if I wanna see, you know, everything relative by sales, I can sw- I can swap that measure.

43:56 If I want to see profit, I can see it from that, and we're still gonna see all of our segments, so we're still gonna get our distribution based on segment. But yet we have the ability to adjust, you know, based on what it is that we want to adjust those different things at the, at the exact same time. And again, in both of these cases, we did the same thing.

44:15 So again, I, I, I won't bore you with the thing of watching me go through and fumble with a keyboard of going through step by step. But all of those things are listed here. So you can sit and see if you do wanna take this and say, how, how exactly is that being done, we've got the steps listed for you, especially 'cause on that screen they're really small.

44:34 Um, but you basically can go through and build the view and figure out exactly how, you know, how to accomplish that. Um, so I think that's… The other… The one thing I did wanna point out here that I do think is worth looking at, I, I just wanna look at this calculated field. Um, it's even s- small on my screen.

44:53 Um, for selected, for selected measure.

44:59 Where are we here?

45:02 Um, I think this is interesting to look at because these are the types of things that trip me up all the time, and it's this idea that you can't mix that ability of aggregate and non-aggregate fields. I mean, I invariably end up with those kinds of errors coming back. And so that's the whole reason why in this calculation, you'll notice that in some of these cases, we're, we're using the sum function to aggregate those fields so that then we can include profit ratio, which is already aggregated.

45:30 Can you zoom in? Uh, that's a- Can you just- Yeah, that's a really good, I think, but I'm not sure.

45:36 I can try, but let's just see what happens here.

45:40 It's been a few minutes now.

45:43 I don't know, did that help any?

45:48 So the idea here is, like we said, profit ratio is already an aggregate field. Don't need to worry about it. Whereas, you know, quantity is not aggregated, so that's why we wrap it in the sum function. Okay? Just something… And those are the types of things that when I'm doing this I always get the, the lovely, you know, not valid calculation button, and it's kinda like I'm scratching my head, and so just kind of a, a, a quick talking point in terms of that one.

46:12 Um, so really simple. The, the last one I wanna show you, this is kind of an interesting thing, 'cause I, I believe, and, and these folks, you, you folks probably know, but it's only been fairly recently this idea of, you know, i- in terms of swapping, swapping sheets, swapping worksheets, and I think the, the, the catchphrase is that dy- dynamic zone visibility, I guess, is the r- what it's called, and I think this is a fairly recent, three years, something like that, something, or less, two?

46:40 I don't know. Fairly recent thing. But the idea here is, is kind of interesting because i- it's that ele- that ability to kinda multipurpose space, you know, and not have to just have stuff stacked up all over. I can turn around and say in this case, "Well, do I wanna view this by measure or do I wanna switch over?" Yeah, we were just showing you a dimension analysis and a measure analysis.

47:01 If I wanna say, "Well, no, I wanna look at it by dimension," so all I'm doing is I'm switching my worksheet here just by using a parameter that then is giving me the ability to… I can still use my, my sorts, like, or I'm sorry, my, my other parameters where I can say, "Well, I wanna see it by segment," or, "I wanna see it by, uh, by ship mode," whatever the case may be.

47:21 But then at the end of the day, I'm just going up there swapping between these two worksheet views, you know, through use of a parameter. Make sense?

47:30 Um, and again, that, that one, same, same idea. We've given you that star panel. In this one it's, it's, it's fairly a, it's pretty much a blank sheet. But the steps are all detailed there that if you do wanna go through… And there's some, there's some thi- some, some elements in here where you need to go and show/hide, you know, and some, you set some visibility settings.

47:50 When you go into layout mode, you're gonna have to control visibility. So that'll be… Is that off the screen? So that'll be one of the things that, um…

47:59 I'm not gonna be able to zoom in on that. That'll be one of the things you're gonna have to refer to if you do wanna walk through this, um, this example.

48:06 Questions? Anything? Okay.

48:09 Last one. This was, this was Robert. I think when we met about this, this is the first thing he brought up, was this idea of… And, and this is really a, it's really a cool thing, is if we go to data, a data source, I just took a sim- really simple ca- coffee, um, coffee chain sample data source that's out there online. And just standard data. You'll notice that in that data source I do have a state, you know, a state field.

48:33 It's called fields. It's state. Okay? But in this, in this file, I also, I also have my sample store, um- My, my Superstore sample data set in here. So now you'll notice in here, we also ha- we have a field, but the other thing in here you'll notice, it's named state province, okay? Because the Superstore data set contains states, and it also contains Canadian provinces.

48:57 So the question is, if I want to utilize those together in some way and be able to filter those, how do I do that? I mean, you could do a blend and different, different operations, but, but the other option is to go right to this idea of saying, "Okay, I want to go through…" And, and I, I'll kind of walk through this a little bit. So I've got, you know, coffee chain, I can sit and I can, you know, basically I'm, I'm doing, using the state field in the coffee chain to basically filter.

49:26 Or I could do the, um, the Superstore. Again, this would be the state field. But then when I bring them together using the parameter, I can now sit down and say, if I want to, in here, if I want to select New York, now I can see I'm, I'm filtering both data sources with one parameter, okay? And to the point where if I go out and I actually look at, um, like we said, Prince Edward Island, you'll notice that, like we talked about, that's not…

49:55 The coffee chain only has 14 states in it. It doesn't have any provinces. So it's gonna respect that. That parameter is gonna respect what's in the, the specific data source itself.

50:05 Questions, concerns?

50:10 Um, and that's pretty much it. And again, like I said, um, the files are there. There are some elements in here if you do wanna walk through, you know, as far as building out some of these things, um, it's there for you if you'd like to take a look at that and see kind of how that works. Um, and that's pretty much it. Yeah, sure.

50:28 Robert Salas: Typing all those things would be, take a long time. Do you wanna-

50:33 Paul Costanzo: Okay

50:33 Robert Salas: … show how you would-

50:35 Paul Costanzo: Sure

50:35 Robert Salas: …

50:36 copy all those at once?

50:37 Paul Costanzo: So there's a couple, there's a couple different… That's a really great point.

50:41 So that's like a, almost like a prompt that I could, that I planted you inside of the audience there.

50:47 And I didn't, I don't think we've ever met.

50:49 Robert Salas: Yeah.

50:49 Paul Costanzo: So the idea, the point here was that we're not gonna type in a value list. Okay? So I'm gonna go out and I'm gonna select state. I'm gonna do a string and set this up. So I'm actually, as part of setting up the parameter, I'm actually using it from… And I can say values from, I can do it fixed. I can make this dynamic such that it will respect the fact that if all of a sudden the coffee chain adds the 15th state, the value list will update as well.

51:14 Okay? So now it's totally dynamic. Or I may choose to not allow it to be dynamic, and I wanna just cut it off at a certain point. Is that what you're… Thank you. Thank you very much. I appreciate it.

51:25 And I, I just don't, I mean, I'm trying to be mindful 'cause I think we have a high level… I'm sure there's a lot of folks that this is second nature to you, and so I don't, I don't wanna bore you to death. Um, but at the same time, if you do have questions, like I said, I think this is a really, um, in all fairness, I say we, and the we is myself and Claude, um, who did the-…

51:45 who did the, the steps analysis. So we're really big on agentic development, so that's kind of a big thing. But questions? Yes.

51:55 Audience member: Related to the top end functionality-

51:57 Paul Costanzo: Mm-hmm

51:57 Audience member: …

51:59 can you also do that in the public filter function? Is there, I don't know, maybe you could drop on the filter on your top end. I guess I don't care better.

52:09 Paul Costanzo: Uh, that's a really good question. Do you guys know?

52:12 Audience member: Yeah, I know.

52:13 Paul Costanzo: In a filter?

52:14 Robert Salas: Some things. The filter function is basically taking five and 10.

52:19 Paul Costanzo: Yeah.

52:19 Robert Salas: You can also set it to 100.

52:22 Audience member: I see. Okay.

52:23 Paul Costanzo: Like, see, and maybe, and maybe that's the thing that, you know, again, I didn't, I didn't dive in here, and I apologize. I didn't mean to just gloss over stuff, but it's kinda this is that same pr- this, that same piece where you're setting that up, and this is where you have that ability to specify, you know, what's the range, you know, from one to 50, what's the step size.

52:42 You can set up all of those things. And again, I can set it fixed. I can set it to be a dynamic piece, as someone said. So I think the idea of doing it this way is you're actually, when you set the parameter up, you have control over all those elements. Does that, does that help?

52:57 Robert Salas: But the way that it functions is, yeah, you put, you set your filter to top end, and instead of specifying it at a constant of five, you set it to parameter. So one of the functions of the parameter I didn't describe in my very animated shenanigans earlier is, we can also use it as, as just a container.

53:12 As sort of a holder. I'm gonna show that in a minute related to maps is, hmm, I'm gonna accept a cup, and I'm gonna put something in that cup. And then I can do other stuff with it. I can go over here and affect the filter, um, with the top end functionality.

53:26 And so the, the parameter liaises between the filter and your data input.

53:30 Audience member: That's the part I meant.

53:32 Robert Salas: Yeah.

53:34 For the, uh, for the all other… So that one's, you're using the filter with the parameter. For the all, when it has all others, is that a random function, or is there a more base level functionality?

53:45 Paul Costanzo: What that's actually doing is it's actually, so, so for all others, there's actually a calculation in here that is-

53:55 Robert Salas: Like an LOD. Oh, okay.

53:58 Paul Costanzo: So basically all we're saying is we're saying, saying take the top end, you know, then customer name, and then group that into all others. So it's basically saying, if it's not within, if it's not within the top end, add them together.

54:10 Does that, does that make sense?

54:12 Robert Salas: So what is the top end customers?

54:14 Paul Costanzo: The, the top end would be, that would be what we're getting out of the, uh,

54:23 another-

54:23 Robert Salas: Oh, that's a set.

54:24 Paul Costanzo: Yes, exactly. So it's just a set where we're doing the same thing.

54:29 Robert Salas: Oh, yeah, that's right.

54:30 Paul Costanzo: So we're set as a set. So we're taking top, that's a function where I can sit and say top.

54:35 Again, use the top end parameters and then basically do it based on sale, sum of sales is what I'm, is what I'm adding together. So that's kind of the, the logical piece. Does that make sense?

54:51 Any other questions, comments? Yes.

54:53 Audience member: On a relative analysis of Tableau.

54:55 Paul Costanzo: Uh-huh.

54:55 Audience member: One of the things I've been gathering is I go into a preexisting dashboard, and I see a parameter, and I see a field. I open up the parameter, it references a calculated field. I open up that calculated field, it references a set, and then it references another calculated field.

55:11 Paul Costanzo: Yeah.

55:11 Audience member: It ends up being an exception sort of daisy chain type situation, and it's kind of hard for me to map out mentally what's going on if I didn't build it.

55:19 Paul Costanzo: Right.

55:20 Audience member: My question is, like, I'm kind of wondering if Tableau has a feature that it can show you, like, a decision tree or like a- Like, what's in there?

55:31 Paul Costanzo: Mm-hmm.

55:32 Robert Salas: Right into that. I– My, my strategy is to track from both sides.

55:36 Paul Costanzo: Yeah.

55:36 Robert Salas: Uh, some silicon gathering outside in. So the parameter is the starting point.

55:40 You found a calculated field that references it to go as far as you can go, and then start with what's in your view that's being controlled by it, and kind of backtrack that until you find where they collide, and that's interesting.

55:51 But I like that daisy chain, uh, description. That is true. And they're hard to chase down, genuinely.

55:56 Audience member: I don't know that there's a complete change like that when it comes to parameters and calculations. They're getting better with maybe more data source lineage of where your fields are coming from in terms of all of these, so that your workflow is the same. But yeah, somebody else has an extension or, um…

56:15 Paul Costanzo: Yeah.

56:16 Audience member: It's not a problem.

56:18 One of the things-

56:18 There's probably something out there.

56:21 Robert Salas: Yeah. You see that with developers who are usually getting the data sources that weren't built re-really well for visualization stuff, where you're, you're layering a calculation on top of calculation on top of calculation. You split off over here. Maybe you got your set, and then you got some parameter coming in, too. It's, there's no easy utility way to break that apart.

56:38 Audience member: They do have dependencies now, which I found very useful for that.

56:42 Paul Costanzo: Yeah.

56:43 Audience member: Not sure how long that's been there. I've been around Tableau for a while, but yeah.

56:50 Robert Salas: I, I do have one strategy to identify all the data elements that are involved, which is delete whatever is on-

56:54 Paul Costanzo: That's what I was gonna say. Is just start stripping stuff away.

56:58 Robert Salas: Right?

56:59 Paul Costanzo: Well, and that's probably because I think the one, and it's kind of silly, but I think one of the features that I use a lot is the idea, the restore, like the going back a function, where I will do that. Where I will go in and delete something at one end and then see what happens, and then just go back a step, you know, 'cause I know I can restore it.

57:16 So it's almost like… I mean, it's– I don't think it's real efficient 'cause it's a trial and error approach. But the, the one thing I will say, and I, and I know I don't want to open up a can of worms, but that's where the agentic thing of putting it to a tool like Cloud or some other tool, it is am– you will be amazed at what will come back and what it will tell you.

57:35 You know, that– it's– I just– I mean, yeah, I think that's kind of a whole other thing. But I think utilizing those tools, it was just crazy to watch some of this occur, you know, in real time on my machine.

57:48 But kind of a whole other…

57:51 Did you have a question, too? I'm sorry.

57:53 Audience member: Well, kind of along the same thought process. As we develop, does anybody have recommendations how to best document what you're doing? Like, even like when I build something and I come back six months later, and I'm like, "I figured out myself," but I try, like, different parameters. You know, does anybody have a solution for how best to document and support it?

58:16 Robert Salas: Um, prebuilt comments in calculated fields.

58:18 Audience member: Yeah, comments.

58:19 Robert Salas: That's, that's something that goes-

58:20 Audience member: But it's almost like you need, like, your own visual.

58:22 Robert Salas: Yeah.

58:23 Audience member: I didn't know if anybody had thoughts.

58:25 I believe a good solution. So DPHS Plan Build, it's a decent start, um, that you can use at DHS.

58:32 Um, I will get you the copy of it.

58:36 Um, we weren't allowed to use Git at the state agencies. Git will get you part of the way there. But now we can. We weren't allowed to use it for Tableau build integration when I was there. That being said, we built what we call a Plan Build document. I can share it with you. Essentially, the first page is your requirements gathering process. Your, if you've got any sort of targets or reviews, whatever you're doing goes on the first bit.

59:01 The second page is the feature creation. So your parameters, your calculated fields, why you built it, and why you didn't take another way, et cetera.

59:09 Um, and then that can live with the workbook as technical documentation moving forward. 'Cause I think you've got limitations if you do a technical notes type of a workbook. You obviously have text problems and limitations on what can be included. If you're using a code promotion tool like Git or some other form for moving that content, it's gonna capture metadata around the content but not why you built it, what's in there, et cetera.

59:32 And if you're using the prebuilt comments, you've got the downside of having to have Tableau and needing to open it up every time. And of course, if you need to add technical notes and share information about your dashboard, having some supplementary Plan Build with it may save you some entryway down the line.

59:51 Paul Costanzo: Awesome.

59:54 Oh, sir.

59:59 Audience member: Oh, uh, there's– I was just gonna say, uh, if, uh, you're on a worksheet and go to kind of the Describe Sheet, um, yeah, uh, the worksheet in that, um…

1:00:20 Uh, Describe Sheet.

1:00:23 Paul Costanzo: Okay, I'm totally missing it. Where am I looking? Enter.

1:00:27 Audience member: Yeah.

1:00:27 Paul Costanzo: Oh.

1:00:28 Audience member: Thanks.

1:00:30 Um, th- like, that has some documentation built in. I think it's read-only, but if you're inheriting a dashboard-

1:00:40 Paul Costanzo: Hmm

1:00:40 Audience member: … like, that can– it tells you everything that's on that worksheet.

1:00:45 Might be good to see what the devs have built with this, too. The Tableau devs might have written

1:00:54 Yeah

1:00:56 Paul Costanzo: I never use that, so whatever. That's very cool. Thank you. That's very good.

1:00:59 Robert Salas: I used to be a utility available that you could purchase called Dashboard Documenter. It basically wrote a marked DWD file, which is kind of complex XML, and dumped it all out, gave you a lot of documentation, generated documentation, show kind of worksheet, um, connections, data connections, but they, they went kind of defunct. So nothing else has come out that does that.

1:01:21 But it can be done to Olivia's point, it's sort of codes it.

1:01:26 Audience member: So you mentioned that you use Cloud documentation. How, how do you use Cloud within like Tableau SCP? Do you… Is it run-

1:01:34 Paul Costanzo: No, I actually use Cl- I mean, basically, we, we use it in, in a lot of our development. So I'm opening up Claude Desktop, and basically, like, I did two things. I did a couple experiments where I told it one worksheet ep- one workbook what I wanted and had it build it and down- and I downloaded the file, and that was kind of… It was, it was average.

1:01:55 Then I took one that I built and, and told Claude to use that on my machine and granted control, and it literally went in. So when you see, when you see this, these elements were done.

1:02:08 I had the finished worksheet sitting there and told it I wanted to provide documentation for the steps for someone to replicate this. All of that in that, in that caption was done by Claude.

1:02:18 Audience member: Okay. Is it, is it writing the XML or is it running Tableau then?

1:02:22 Paul Costanzo: It's run… It's, it's, it's running Tableau on your machine. It's you're giving control of your application to Claude.

1:02:29 Audience member: Okay.

1:02:29 Paul Costanzo: So it's literally running. It's lit- literally running the machine. So you see it in the, in that side window viewer or whatever, and it's going through actually doing. You know, you'll actually see everything. You'll see, you'll see the mouse move. You'll see it creating every-

1:02:41 Audience member: It'll do computer use. Okay.

1:02:43 Okay.

1:02:43 Paul Costanzo: Well, it's, it's, it's wild.

1:02:47 Robert Salas: I, I love the use of Claude. I'm just curious how many people are Cloud writing and using data. I mean, we're not.

1:02:54 Paul Costanzo: Uh-huh.

1:02:56 Robert Salas: It's like a whole option for Tableau.

1:02:58 Audience member: I think it isn't really being connected to anything like that essentially.

1:03:03 Robert Salas: There's a thread.

1:03:09 Paul Costanzo: Yeah, I, I mean, we, we have the conversation all the time internally. It has literally changed how we work. I mean, I can't ima- I, I, I can't imagine. I mean, and even, even not even in production pieces, a great… Again, just a tidbit.

1:03:24 We had a c- long-time client wanted a, a specific project that they wanted to look at, but they had to sell it to their higher-ups so– because the company's getting ready to go public.

1:03:34 And so one of our guys sat down and spent two hours and put together literally a prototype of what we– what this would phase would be, what the sprint would be, and they approved it in twenty minutes.

1:03:46 Audience member: Mm-hmm.

1:03:46 Paul Costanzo: And, and it's, it's, it's eighty hours. It's gonna be eighty hours of work to actually do it, you know? And so that's… And, and versus us sitting down and saying, "Well, you know, here's, here's, you know, here, here's a mock-up, and this is a workflow, and da, da, da, da." Like, anyway, I'm sorry. It's getting off topic. I apologize.

1:04:04 Anything else?

1:04:06 I will pass the, pass the baton back.

1:04:09 Robert Salas: All right. I will just go with window, and we'll just kind of change it up back and forth. So what I'm gonna talk about is mapping.

1:04:15 Um, specifically hex mapping and how to create a, a hex map that's not one of the generic ones out there, and then how to still use that to kind of convey some measures and do some viz-y stuff with it, and then drill down through a hex map into a real map. So I'm gonna build that in front of you.

1:04:33 All right. Hex map. Everybody knows what a hex map is.

1:04:36 Um, we see these all the time. It's election season. Boo-hoo-hoo-hoo.

1:04:40 And they use it a lot to represent the United States. Occasionally, you'll see some other permutation of hex maps, which are kind of goofy. Like, here's an electoral college map. We know California's got bajillions of votes and so on and so forth. So we use hex maps for what purpose? Why do we use hex maps?

1:05:00 What's the advantage of a hex map?

1:05:02 And the United States one here is a classic example.

1:05:05 How big is Rhode Island? How big is Texas, right? So when you have geographic spaces that are of vastly different sizes, um, a hex map or s- even a square map or simple map overcomes that. Every single unit has equal visual weight, equal visual size. You can see Rhode Island's performance, right, as easily as Alaska or Texas or California.

1:05:27 Occasionally, we get a decent layout that it looks like the thing we're looking at. Uh, if you've ever seen a hex map of Europe, it's a little more amorphous and, and goofy.

1:05:36 So what I'm gonna show you is a hex map I built

1:05:41 of Wisconsin, a little bit more localized, of the counties of Wisconsin that I put together, uh, a number of years ago when I was at DCF.

1:05:51 And the key to this is that you actually have to come up with the data yourself. And so I had literally printed out a map of Wisconsin myself. It's a little hard to see the thin map, but Wisconsin then, right?

1:06:03 And then I took that and I drew a grid on it, just kind of overlaid in Excel, and I drew an axis, and then I just sat there for about thirty minutes. This is not the real one. I had to recreate this last minute. Anyway, it's to kind of lay out, like, what are the coordinates of each given county on your standard X, Y axis system? So just from, like, one to fifteen, or excuse me, zero to fifteen in each direction.

1:06:29 As I counted over, uh, I think Grant County's here in the bottom left. I wound up, uh, putting them at three and a half X and zero on Y. So that's my bottom leftmost county. And then I had to leave some space in each direction. And so I went through this exercise on paper to kind of plot out how can I assign coordinates to each and every county.

1:06:50 Audience member: Robert, that's the last way to do it.

1:06:55 Robert Salas: How can I assign coordinates to each and every county that allows me to plot it on just a standard grid map, right? In a sense, this isn't really a map map. This is, um, a visual representation of a geographic thing, but if I turned on the axes, you would see it just goes 0 to 15 and up, uh, and there.

1:07:16 The reason Grant is three and a half is because in order for the hexes to look nice, we kind of increment them, we zigzag them. Um, so we have even number, halfway, even number, halfway, integer, half, integer, half, integer, half as you go up.

1:07:30 And then going up the Y axis, you just increment one, two, three, four, five, six, seven, eight, nine, all the way up to, I think, 11 on here. So the first step happened on paper. I had to make some preparations and assign each county a numeric coordinate. Dane County, which we're sitting in right now, for me was six one, six on the X, one on the Y.

1:07:48 And that's where it will plot it out. So that's where this data came from.

1:07:53 Now, if I jump into Tableau, that's our starting point.

1:07:57 If I jump into Tableau, you know, it's hard to see, but I have all the counties here, all 72, with their names. Wisconsin is an abbreviation, so I don't have to say it in full. And then their X coordinate and their Y coordinate. And that's it. That's the whole data file that I put into Excel. It took me, I don't know, 20 minutes to type it in.

1:08:15 Jen Shepherd: Can you share your Tableau?

1:08:17 Robert Salas: Oh, I gotta change Windows.

1:08:24 All right, just a moment.

1:08:28 Stop sharing.

1:08:36 All right, I'll spend the rest of this time in Tableau, so let me…

1:08:43 We can, we can commit to this now. All right, there we go.

1:08:46 In Tableau, the data set that I used, again, I, I put it into Excel, um, and then I just connect to it in Tableau to use it. And it's just an XY coordinate system.

1:08:55 So when I use this, I'm gonna simply bring my columns onto the column shelf and my rows onto the row shelf. And as usual, if you bring in two measures in Tableau, you get a scatter plot with one mark because it's aggregated them all together, and you can see it says sum of column, sum of rows.

1:09:15 Now the magic happens. Watch this. I'm gonna add in the county name.

1:09:19 Oh, first I'm gonna rename that name to county so we can use this later. I'm gonna rename the name of the county to county, and I'm gonna give it a geographic role right now 'cause I know I need that later.

1:09:34 Okay.

1:09:35 So now I'm gonna bring county onto detail, and poof, I have the makings of a map. It looks like Wisconsin, right? Door County, Kewaunee, Order, et cetera, et cetera.

1:09:49 If you look at the numbers, all I have is from 0 to 12 and 0 to 10. It's just an XY coordinate system.

1:09:57 Now, if you've ever looked at visualizations on Tableau Public of, like, basketball shots, how many three-pointers they got, football tackles, it's all done in the same way. They plot out things in an XY coordinate, and then they overlay it on a background of a basketball court or a football field or a whatever. You can do this with anything if you're willing to plot the data.

1:10:18 Now, to make this into a hex, we just simply need a shape. I personally really like the website thenounproject.com. It's $40 a year, I think. Um, 5 million icons and shapes and everything to choose from. I use it all the time.

1:10:32 So I'm gonna change the mark type here to shape, and then I'm gonna go change my shape to one that I have already downloaded.

1:10:44 Bing, I have hex map.

1:10:46 And then we just play with size for a minute. Mm, pretty good, pretty good. Bah.

1:10:53 Right? So here's where we do that plus delta kind of thing. This is pretty good.

1:10:57 Little too much.

1:10:59 Eh, just need a little bit of visual, visual balance. Nope.

1:11:05 All right. Hey, Wisconsin hex map. Whoop-de-do.

1:11:08 So we can do a lot of stuff with this though, right? Because we can represent our hexes with colors.

1:11:14 So if I wanna create just a random, uh, calculated field,

1:11:20 I'm just gonna say color one.

1:11:22 So I'm just gonna do this based off of a random thing, which is if the county number…

1:11:28 Somebody get a number between 1 and 72. Actually, give me a number between 8 and 52.

1:11:34 Audience member: 24.

1:11:34 Robert Salas: All right, if the county is below 24,

1:11:38 then I'm gonna make it green.

1:11:39 Somebody give me another number, please.

1:11:44 Audience member: 31.

1:11:45 Robert Salas: Okay.

1:11:47 And I like to assign names to my colors when I make color calculated fields.

1:11:51 Makes it easy for me to pick it, 'cause I've got a little monkey brain.

1:11:55 And so when I add my colors in and I want to assign them, I know what color I'm supposed to pick.

1:12:01 Like, I've literally already pre-assigned it. I just have to go find it. So gray is gonna become gray.

1:12:07 Green is gonna become green.

1:12:09 Red is gonna stay red.

1:12:12 There we go.

1:12:13 Okay. Yay, I've assigned some sort of typical traffic light color schemes to my performance of individual counties.

1:12:20 Now, one of the problems we usually have with maps is you can only represent one measure, right? I can't make my counties simultaneously green and orange or blue and orange.

1:12:30 But we can overlay shapes. We can represent multiple shapes, but only the, the base one plus another.

1:12:37 So if I turn this into a dual layer chart or dual axis chart, it acts like a dual layer map.

1:12:45 And so that's what I'm gonna do and create a shape that I can lay on top of here.

1:12:49 And so I'm gonna duplicate my measure. I'm gonna just bring rows up here again. If you're a little more sophisticated, usually we use Control and copy it over.

1:12:58 I'm gonna right-click my second pill and make this a dual axis map.

1:13:04 And then I'm gonna synchronize the axes, 'cause that's just always good practice.

1:13:07 Okay.

1:13:08 Now, what happens when you add another measure is you get an extra marks card.

1:13:13 You get an extra marks card you configure.

1:13:15 So my first one is my hex, and my second one I'm gonna have be something else. I'm gonna change the shapes to reflect something else, something else performance related.

1:13:26 So once again, I'm gonna create a calculated field, um, shape definition.

1:13:34 Somebody give me a different county number.

1:13:38 Audience member: 13.

1:13:38 Robert Salas: 13, then we'll go with, um, high.

1:13:42 And another county number, a bigger one.

1:13:48 Audience member: 40.

1:13:48 Robert Salas: 40.

1:13:57 Okay.

1:14:00 So I've assigned a performance measure to this, and I'm gonna change my shape to reflect that. I'm gonna get rid of color.

1:14:11 And

1:14:15 my highs I'm gonna indicate as up, my lows as down, and my mediums will be a circle.

1:14:23 Okay.

1:14:25 And then I'm gonna give that same definition to the color, and I will reflect high as red.

1:14:33 Actually, let's go with green. Let's assume this is, like, sales or something.

1:14:36 Red, and medium is, uh, yellow.

1:14:40 Okay.

1:14:42 What a gobbledygoop maps I've created.

1:14:44 But if I dial the size down, I can play around with and tinker with the size of the secondary shape, and now I've double encoded my county.

1:14:53 I could have the hex mean something, and I could have the shape mean something. Maybe the hex is population or per capita income or something.

1:15:03 Uh, one of the stats I had at DCF was, like, child poverty population.

1:15:07 And maybe the, the marker in the middle is this measure that we care about is going up, or this measure we care about is going down, or it's holding steady. I've double encoded my counties to tell me two things.

1:15:19 Now, we wanna make sure that we can tell which county is which, 'cause unless you, um, work in state government, it's not that common you know exactly which one's which. So I'm gonna bring the labels in, and I will align them a little bit.

1:15:34 Let's see. I'll put a space there. That should do it.

1:15:37 And I get my county names underneath, so I know which one's which.

1:15:42 Cool. I could stop here, but why stop now?

1:15:45 What I wanna do is, let's say I had another data set, which I don't to demonstrate today, where I had, um, pinpointed data. Right? Let's say I had addresses or providers, childcare providers, good example. And I had their addresses and geocodes, and I could plot those onto a real geographic map.

1:16:01 And so if I cared about a county, I wanna click on it, I wanna drill down and go, pop over to a real map and see them. So kind of map drill down through a hex.

1:16:11 So we're gonna, we're gonna build that too, and then I'll put the two pieces together.

1:16:15 So on this next tab, I'm gonna build a county map.

1:16:21 And I'm actually just gonna use the county, uh, object that I assigned the county geographic location on

1:16:31 to create a real map.

1:16:34 Now, if you've created a map in Wisconsin before with counties, you know that many of our counties are elsewhere in the country, and it doesn't know what to do with them, so you have to tell it what to do.

1:16:42 But luckily, I have a field that tells me what state we're in. State abbreviation, Wisconsin. And so there we go.

1:16:52 Oh, by the way, in my hex map, does anybody know what this fold is? Can you guess what that fold is?

1:16:59 Audience member: Lake Winnebago.

1:16:59 Robert Salas: Lake Winnebago, yeah. I couldn't, I couldn't get the counties around it to kind of connect, and I thought, you know, as a visual reference it's pretty good.

1:17:05 So we can see that in the real geographic map. Here's where that fold is. So pretty, pretty decent hex representation, right? Okay.

1:17:12 What I want here is a choropleth map, where I see the county values, and if I were to zoom in on a single county, I would see its geography.

1:17:21 I'm gonna turn on

1:17:25 a nicer, um, map version. There we go.

1:17:30 And I'm gonna take a pause here and talk about design structure.

1:17:35 Because it always helps if you know what you're trying to accomplish. When I worked in the restaurant business, I had a boss who was like, "If you don't know where you're going, you might not like where you wind up or get there at all." So what I wanna do is be able to select a hex that's going to filter my other map to that one county that I've selected, and also take me to that sheet so I can see it.

1:17:55 That's what I want to happen. That's the, the functional interactivity that I want.

1:17:59 What I need for that is, ba, ba, a parameter. I need a place to hold the county that I clicked on and put it in there, and then use that parameter to drive my functionality, not only of filtering but also of sheet navigation.

1:18:13 So we're gonna do a couple of things, and those two things I described you can only do, um… well, we're gonna do at the dashboard level when I put them together. So I'm now gonna take my sheets that I've created, and I'm gonna create dashboard number one.

1:18:28 Make it a little bit bigger so we can see it.

1:18:34 And on here…

1:18:37 Why don't I see any sheets? There we go.

1:18:40 Sheet number, uh, sheet number two, my hex map.

1:18:46 I'm gonna get rid of all this junk. I don't really want it.

1:18:51 Hm.

1:18:56 There we go.

1:18:57 And I'll adjust the sizing of this a, a little bit, 'cause it's gotten a little wonky.

1:19:02 Then I'm gonna create another dashboard, and on here I'm gonna bring in my geographic map, just of Wisconsin. And then I'll trust that it's gonna do what I want it to do.

1:19:12 So let's go back. Geographic map. I wanna filter this based on the hex that I click. I need a parameter to do that with, and I need a filter to affect the map, so I have to build two things.

1:19:23 First is a parameter.

1:19:27 And I always just call this selected, or excuse me, county selector. Something selector.

1:19:33 I always name it that.

1:19:35 We want this to be a string, 'cause the county name's text, but I actually want it to be blank. I want an empty cup.

1:19:42 You got it. Yeah.

1:19:43 We're actually not seeing the publish screen. Oh. Sorry for the recording purposes. Is this important? Not really. Okay. It's, I'm creating a parameter. Yeah. No. Explain it for the people. Okay.

1:19:57 All right. So real quick, I'll edit that parameter so our online folks can see.

1:20:07 That I created a parameter called county selector. The type is string. Do you see the parameter now, Jen? Yeah. Okay. And again, the current value I'm leaving as blank, 'cause I want it to be an empty cup to hold. Importantly, you wanna set the, um, allowable values to all. I can shove any value into, I can drop anything into my, my cup, my holder.

1:20:25 Okay?

1:20:26 A parameter by itself does nothing.

1:20:29 Okay? That's a really important development rule to remember. Parameter by itself does nothing. You always have to have something that interfaces it, uh, to what you want to happen. So in this case, a calculated field is gonna be my connector for my county filter.

1:20:43 And so county name, county equals selected county. That's all.

1:20:50 It's gonna come back as a Boolean true, false.

1:20:52 If I select Dane County, then my county will be equal to Dane.

1:20:56 I'm gonna test this real quick, 'cause I like to unit test things, and right now because I have every county… Excuse me, I have my cup empty, there's no true value.

1:21:08 So I'm gonna edit my parameter real quick, manually type in Dane.

1:21:15 Test my filter.

1:21:17 Now I'll get a true option.

1:21:22 And sure enough, my map scales in and zooms in on Dane County. Great. I don't have to change my filter. I want it to only come back when it's true. So this is one of the little tricks you sometimes have to do with filters and Booleans, is you have to fake it out to be able to select true, um, in order to test your work.

1:21:39 So I'm gonna go back and I'm gonna zero out my county filter.

1:21:43 And the map is gonna disappear completely, 'cause now I have nothing there. Ah, imaginary map.

1:21:50 Okay.

1:21:51 So now we're gonna implement this, um, drill-down functionality.

1:21:56 So when I click on a hex, I want it to fill my parameter with the value I picked, and also I want it to take me to the other sheet.

1:22:04 So that is done through dashboard actions. That's why I had to add this to a dashboard first.

1:22:10 In dashboard actions, one of the choices is change parameter. We used to call it set parameter, but the actual thing is change parameter.

1:22:20 And this allows me to configure when I do something on some given sheet, what do I want to happen?

1:22:26 On select, which is the radio button on the right, I want to put a value into my parameter, my target parameter, county selector.

1:22:35 My source field is going to be county, the name of the county, from my data sheet.

1:22:41 And when I come back and I clear my selection, I wanna set the value to blank. I wanna blank out my geographic map again, so that as I go back and forth, the counties are clearing out. Click Okay. So now my parameter action is ready. I could test that out, but I'll keep going.

1:22:58 And then the next thing I wanna do is go to sheet.

1:23:02 And so this I'm gonna call, um, sheet nav, just for some fun today. My source sheet is dashboard number one. I click on a county.

1:23:12 On select. I wanna do this with single select only, 'cause I'm gonna filter for, um, I… My parameter can only hold one value.

1:23:19 My target sheet can be either dashboard or individual worksheets, and in this case, I want it to be dashboard number two.

1:23:28 So kind of describing what happens here, when I click something, this action, the, the sheet nav action, is gonna jump me to the other dashboard.

1:23:36 And when I do so, when I click on, uh, Jefferson County here, it jumps me to the other sheet, has selected Jefferson County on the geographic map, and is zoomed in and scaled to fill the screen with what is there. Now, again, if I had a bunch of data points that I was geocoding dots and, and whatnot in this map, it'd be a lot more meaningful. It's a lot more data set up and so on and so forth.

1:23:59 Uh, what I would typically do then is I would build a little navigation object into here.

1:24:10 That would take me back to my other sheet. So I'll grab this.

1:24:15 You have to have a way to go back.

1:24:17 And do, do, do.

1:24:21 I want this to take me to dashboard number one.

1:24:24 And you could use icons here like a back arrow, but return to main. I'll just call it that.

1:24:32 Okay. So click on this, takes me back here. I click a different, um, county.

1:24:38 Let's go with Pepin.

1:24:40 Okay. I did my analysis, whatever I needed to do.

1:24:43 And here's where hex maps pay off, right? Is that there are some counties that are really goofy shaped, and in a normal map you can barely see them,

1:24:53 versus Dane or… Well, actually Milwaukee is one of the hardest ones to see, right? Milwaukee County is that super skinny, right on the lake, and often we don't see it unless it's got the biggest value of something.

1:25:07 So this is a way of using two different approaches to mapping.

1:25:11 The hex map or the shape map gives you the ability to kind of weight- All of your units equally.

1:25:17 If you use multiple, um, layers, you can use color to encode one thing and a shape to encode another. So you could have multiple measures represented.

1:25:25 And then by using, uh, change parameter and sheet navigation, drill down, drill through that map into something with more detail.

1:25:35 There you go.

1:25:36 Any questions?

1:25:38 That was kind of fast. Yeah.

1:25:40 What was the, um, the place where you got the shapes?

1:25:46 You, you mentioned the- The Noun Project. All one word. Yeah. Yeah. Here, I'll, I'll bring it up. Yep. I'll bring it up. It's great, great resource.

1:25:53 Um, thenounproject.com.

1:25:59 Give me a topic. Anything. Pull something out of the air.

1:26:03 Okay.

1:26:10 Uh, there's hundreds and hundreds to choose from, and what's nice… So I have a subscription on here. Let's say you like, uh, I don't know, this one, is if the, if you set your default, it downloads with a transparent background, which is a great download, and you can change the color to be something else. So let's say you want it to be, I don't know, red for some reason.

1:26:31 It'll download a red icon with a transparent background, you can put it anywhere you want. But if you leave it black, if you leave it black, it allows you to use Tableau's color functionality to color that black.

1:26:44 So these icons are really handy. If you bring in a black icon like I did with the hexes, and you add a color differentiation dimension, it'll color it for you. So I can turn that boat any, any color I need it to for any purpose.

1:26:57 Uh, you can download different sizes.

1:26:59 Um, so typically our icons are pretty small. You can scale down the storage space if you need to.

1:27:05 Yeah.

1:27:06 Millions and millions and millions of icons. Anything you could possibly imagine. Give me your favorite hobby subject.

1:27:14 We use it at public health actually. Oh, do you? Oh, yeah. The Noun Project? Yes. All right. We'll, we'll go with virus. Yeah. Oh, yeah.

1:27:22 Hey, that's fun.

1:27:24 That one looks like a bicycle wheel. Yeah, anything you can imagine. So if it's worth it for the, for the money, um, and you, you need a lot of custom icons, cannot recommend a, a better resource than this. Um- We use them in other products. Yeah.

1:27:37 Now, just as a little hint, I let my students choose icons from here for some of their projects, and if I click on something, and please don't judge me, uh, if you were to, to look up at the URL, there's a little six-digit number up there. That six-digit number is the ID of that image. So if I sent it to her, I could be like, "Hey, could you get me 822194?" And

1:28:04 just for practice, and hypothetically speaking. Okay. Stop glaring at me.

1:28:11 It's not like this is being recorded or anything. Yeah, it's not like it's being recorded or anything. Oh, my. It's not like I work in academia or anything. But just as a, as a resource for like, "Hey, I really like this icon. Could you look at it?" Right. "And review it? Is that okay?" Yeah. "Because then I'll purchase it with my account."

1:28:24 Any other questions? I have just a question- Yeah… about the hex map.

1:28:27 Does, does the public understand them?

1:28:31 I think so in this day and age. Okay. Again, we are seeing them so often, um, dur- especially during election season, and I think some are confusing, but I think people are used to seeing them.

1:28:44 I just can't imagine the confusion with this. I don't think they know what to make of this one. Well, yeah.

1:28:48 Um, and, and this one comes up on the news a lot, but yeah, during election season I see them all the time. They've got different representations. And I think it's fascinating 'cause they'll have the hexes split- Yeah… like red and blue, and there's different shades, like how strong it means that way. They've, they've encoded a lot of information in them.

1:29:05 Um, and we can do that if you had, let's say, eight flavors that went from completely red to red and half-blue, light blue, dark blue, medium blue, and the in-betweens, and then you had a calculated field that assigned them the value of one, two, three, four, five, six, seven, eight.

1:29:19 You just need to calculate your number and show the right flavor of that icon.

1:29:24 Um, using hexes is, is just kind of common and popular. You could use squares or circles. Doesn't matter. It's just a shape. Hexes fit together nicely.

1:29:40 Questions?

1:29:41 Thoughts? Useful? Marginal?

1:29:44 Mm. Okay.

1:29:46 All right. I will hand off here to Olivia then.

1:29:49 Yay.

1:29:54 Olivia's gonna talk to us about accessibility, which is a hot topic.

1:29:59 Olivia Butler: Okay. All right. Um, I should mention that I also work in IT and not audio.

1:30:03 Um, we introduced each other, everybody earlier, um, but I am Olivia Butler. I'm the BI and analytics lead, um, for the employee trust funds group here at the State of Wisconsin. Um, today is a little bit of a whirlwind on accessibility. We're doing bite-sized topics. That being said, I have been making the rounds with the other state agencies if anybody's interested in talking in more detail about your accessibility needs.

1:30:29 Hit me up. I am available outside of these meetings as well. Um, but I wanted to kind of get a pulse of the room before we get started. How many of you feel like you are an expert in accessibility and can help me today with this presentation?

1:30:44 How many feel like you sort of got a handle on Tableau accessibility, but you really don't understand the details or the complexities?

1:30:52 How many of you think accessibility is a curse word and would rather not think about it?

1:30:58 Fair. Fair. Okay.

1:30:59 Most people feel like accessibility is overwhelming, that you are, you are not alone. Um, and the reason is because un- unfortunately, um, and mildly ironically, accessibility is not a one-size-fits-all solution. Um, every single dashboard you build, every single webpage that you have your dashboards on are gonna behave completely differently. You are gonna need a- Unique solution for your needs, um, and that's overwhelming, especially when you have multiple pieces of content being shared with a lot of different audiences.

1:31:30 So I broke the slides today into a couple of different sections, um, and I wanna kind of talk through each of them. Um, the very first thing is let's start with what is accessibility? So individuals should be able to perceive, understand, navigate, interact with, and contribute to anything that is on a webpage, including your Tableau dashboards. Here's the problem, Tableau doesn't come accessible out of the box.

1:31:57 You have to know what to configure, what to build, and work with your web teams to make your access- your webpages and your content accessible.

1:32:08 It's also not just one accessibility challenge. You have cognitive challenges, you have visual challenges, you have speech, neurological, auditory challenges to ha- that you have to face in order to be accessible.

1:32:21 So WebAIM is one of my favorite places. They did a quick survey of about a million homepages across a variety of sectors, and they lo- in February 2026, I've got it linked, don't worry, you can see it later, and all the rest of the data, but they looked at over a million pages and found over 56.1 million distinct accessibility errors on those webpages.

1:32:47 That's about an average of 56.1 per page.

1:32:51 They've got 1.4 billion page elements, and an assistive device will read every single element on that page. That means that users would expect to encounter errors in one of every 26 elements on a homepage.

1:33:10 Last but not least, over 95.9% of these webpages had at least one failure of the AA WCAG standard.

1:33:21 83.9% of those were low contrast text.

1:33:25 53.1% were missing alt text for images.

1:33:30 That means that, and those two failures, the low contrast and the missing alt text, have been the highest accessibility failures in the last seven years. We're not making progress, people.

1:33:44 So it matters, and the sheer volume of this matters because it's not just your dashboard, it's not just your webpage. This is an experience every time an individual gets onto a web environment. So it becomes very, if you put yourself in their shoes, it becomes very frustrating to have to find anything in our m- modern world of everything being on the web.

1:34:10 WCAG, uh, um, has what we call the POUR principles. We can go into these into more detail later, but your content, to meet AA standards, needs to be perceivable. The information and the user interface components must be presented to users in a way they can perceive. This is text alternatives, descriptive text in titles and captions, plain language alt text, et cetera.

1:34:34 Your content needs to be operable, so the interface components and navigation have to be accessible to different devices or methods, including keyboard shortcuts, enabling toolbar access, and data downloads for us.

1:34:50 Understandable, the information needs to be pres- understandable to your users. For example, you want clearly distinguishable names and labels for different elements in your view. If every single view, which we'll talk about later, of your Tableau dashboard has ID'd as a Tableau viz, that is not a distinct, meaningful title for your visualization on the webpage if an assistive device is reading that HTML.

1:35:16 And last but not least, it needs to be robust so that it can be interpreted reliably by a wide range of audiences, and this one gets really tricky with Tableau. Um, to our earlier question, can a general audience understand a hex map?

1:35:31 Most of us are gonna be working with a fourth-grade literacy level on our public webpages. The, and we have to design for that. But our data needs to tell a story. Our data is being used by advanced reacher- researchers, individuals that completely understand our subject matter. So we have to be able, as designers of Tableau content, to understand the balance, who our audience is, and design very deliberately for those different accessibility needs in our audiences.

1:36:02 I'm not gonna go through all of this, but state agencies especially have been super concerned, um, about accessibility lately because as of April 24th, 2026, all content must be AA accessible on every public-facing webpage that the state agency's on.

1:36:19 Um, for many of our agencies, especially the big three, this is thousands of webpages, hundreds of Tableau dashboards.

1:36:26 Um, AA compliance is what we've always been working towards. This is the most desirable. For you all to know, AAA is not always gonna be possible in Tableau. If your comms office is telling you to do AAA, you can apologize profusely and tell them that Tableau will never meet the standard. I'm gonna tell you right now it won't. Mainly, real quick example, sequential color palettes can never be AAA compliant with contrast.

1:36:52 No matter what you do, either the light or the dark is not compliant against the background.

1:36:57 So you're aiming for AA. There are a lot of contrast checkers, there's a lot of compliance that you can get towards with AA, and here's the trick, this is the loophole, conforming alternative versions matter.

1:37:12 So if Tableau can't do it accessibly, something else can, and we'll talk through what some of those options might be for you. Um, but Tableau isn't, and I know, please forgive me, recording in the universe YouTube gods.

1:37:27 Tableau isn't always gonna be the best way for you to display your information in an accessible format. You, again, really need to think about your audience, what questions you're trying to answer, and how to deliver that information in the most efficient way possible.

1:37:43 Okay, let's talk about Tableau itself first.

1:37:46 I'm not gonna go through all of these. Like I said, we're in a whirlwind today. We will dive into any of these details if you want more later.

1:37:52 These are the only screen reader accessible elements in Tableau. If you use anything else, it will not be compatible with a screen reader.

1:38:01 Um, you need to make sure that you're picking the right filters, enabling those captions, and this is counterintuitive for a lot of what we've been taught over the years as Tableau developers, to put text in with your visualizations. Text is readable, especially text formatted on a sheet. Fun tip: put your text in a sheet, it will be screen readable.

1:38:22 It will not be screen readable always in your text objects.

1:38:26 Um, also other tip, most of the time the default HTML link, you know, when it changes the link, your link text colors. In Tableau, it's not always contrast compliant. We get a lot of failures because the default hyperlink is not compliant against the background that you've chosen for your dashboard. So in the world of accessibility and designing for the public, some of our traditional mainstays of what we've been taught as a Tableau community aren't necessarily always gonna be the most accessible for your audience, and you have to design with that in mind.

1:39:03 One of the big things that people forget about with accessibility is mobile layouts.

1:39:08 The majority of your audience, 80% plus if you run your metrics on your public webpage, are gonna be accessing it on a phone, not a desktop device.

1:39:18 If the majority of your users are accessing your content on a phone, you need to be developing custom mobile phone layouts.

1:39:25 There's a couple tricks and tips that I wanted to share on this one.

1:39:29 One, use custom worksheets. There is absolutely no rule that says your entire visualization only needs to be on one sheet in your workbook. Make a view for a desktop, make duplicate that sheet, limit the number of marks in the view. That's your mobile version. Now, if you're gonna use this, it is critical that you understand whatever information is displayed on the desktop also needs to be available on the mobile version.

1:39:53 You are not being accessible if you're purposefully excluding information to make the marks fit onto your phone. So reduce the number of marks in your view to make it friendly for the device that you're building for, but make sure that they have an alternative way to access the rest of that information that you're no longer displaying.

1:40:13 White space is your best friend. Fit width on your containers is your best friend, especially given that our Androids and iPhones are not gonna have the same screen size. I generally recommend you design for a generic phone layout, fitting width, and what we'll talk about later, scaling your embed code are gonna ensure that those minor little inch or less adjustments between devices are handled without you needing to worry about that variance on the design side.

1:40:40 Audience member: Can I just ask a question about, um, when you're doing these mobile views, the font size requirements are kind of impossible, right?

1:40:49 Olivia Butler: Yeah. Well, and it depends on what your-

1:40:51 Audience member: Because-

1:40:51 Olivia Butler: It depends on what your font size requirements are. I recommend nine point or higher for desktop.

1:40:57 Um, for your phones, you could probably get away with six, but you should test, and that comes to the end.

1:41:04 Um, I generally would say nine point or higher for all things accessible. Um, but with the scaled layout, you can probably go down to about six on mobile and… But m- again, I would encourage you to test that, make sure that's true with your content, with the phones that are using it, et cetera.

1:41:23 And testing sometimes is a challenge, especially for state agencies. I just like to call this out. If you are at a state agency, VPN is the bane of your existence.

1:41:33 Um, VPN will often not let you test your mobile layouts because you have to be on the VPN to test them, and most of us do not have work-issued phones with VPN enabled on them.

1:41:44 So be really careful with the testing challenges for mobile. Make a plan ahead of time, um, but also understand that Mo- almost all of your content going to the public webpage, and I would argue probably all of it, needs to have a custom mobile phone layout, um, because that's the way the majority of the people are gonna be accessing your content.

1:42:04 So improving navigation device accessibility. What I mean by navigation device, screen readers like JAWS or NVIDIA are examples of this technology. What it will do is pick up those accessible elements that are kind of highlighted in this picture here, and they're gonna read them in the hierarchy order. If you're ever curious what screen readers or assistive devices see when they see your dashboard, go to your layout tab on your dashboard and down to the hierarchy and see if it would make sense for you if it was reading, because that hierarchy is built in the same way you drag elements onto your dashboard.

1:42:43 So you don't design left to right, top to bottom. No one does. It doesn't intuitively make sense to us as Tableau developers.

1:42:51 It also will not intuitively make sense if that's the way your hierarchy is organized, and it starts reading this caption or a label before it reads the title of your view.

1:43:03 So descriptive text. Plain language gets said a lot. I want to just say, in my opinion, plain language is plain language for your audience. Sometimes that's general public, right, with a fourth-grade literacy level, and you need to write for that. If you're building a dashboard, though, for your internal audiences, it's just as important to be accessible.

1:43:23 You do not always know what challenges others might face.

1:43:28 Don't write out the abbreviation that everyone in your business uses on a daily basis. They don't need that. That makes it extra text for the reader. It makes it harder for you. So make your plain language plain language for whatever audience you're building for. Don't just always go to the lowest common denominator.

1:43:48 Last but not least, and this is the least, least favorite thing we want to do, but plan in advance. Think about how much size do you have to build your dashboard. No one wants an inner horizontal scroll bar. You are limited to 1,000 pixels or less on almost every single web application and webpage known to man these days. So do not design wider than 1,000 pixels because by the time it goes to your webpage, they cannot see or read all of that content simultaneously.

1:44:20 Uh, color rules, we could be here all day. So I've broke it down to a couple of things, big things that you need to focus on to bring your dashboards into compliance.

1:44:29 Number one, and I'm so sorry to do this to you all, I feel like I'm a little bit of the fun police when I talk about color and accessibility.

1:44:37 I want to be very clear that if the world could be every single color, I would support that completely. The problem is that there's a very substantial population that cannot distinguish color well for a variety of different reasons.

1:44:54 And instead of trying to fit and meet all of those different interpretations of your view, one of the very first things you can do to take that weight off your shoulder of having to think this through, don't use it as a distinguishing mark.

1:45:06 It should not be the only reason. See, this is better, not best.

1:45:10 It's not the only reason somebody can see that line.

1:45:13 The other thing to think about is use it consistently across categories.

1:45:17 If your female category is blue, they should be blue everywhere.

1:45:22 Do not switch it up on the next one. This is getting towards cognitive interpretation, lowering that burden of your dashboard to your users.

1:45:31 Last but not least, and this one's a weird one. Bear with me. I promise it works.

1:45:36 Try, I'm encouraging you all, homework. Take home homework challenge.

1:45:42 Build a dashboard and don't put a single ounce of color on it.

1:45:46 Build it in black and white or grayscale.

1:45:49 Not a single drop of color.

1:45:52 Build all your views, put them in every single sheet, put them onto your dashboard the way you want your content organized, and then look at that content and say, "Where would color help me?

1:46:02 What trend am I seeing from all of this data?" That's what I'm gonna color. There is nothing that says you can't have a gray and blue dashboard just like this live.

1:46:12 There's nothing that says your dashboard has to have any color on it.

1:46:16 We like it. It's fun. I know I'm the fun police, but I really truly challenge you all to design in gray first, or black or white or whatever you want to do. If you're a black background person, pick white. If you're a white background person, pick black. I don't care, but just try it and see what happens.

1:46:35 Yeah?

1:46:36 Audience member: Um, I'm not sure if this has come up, but this graph on the right where there's a single blue line that's better, not best, what would you do to make it, to add another distinction?

1:46:47 Olivia Butler: I'd use shapes on the points

1:46:51 so the color isn't the only thing.

1:46:52 Audience member: Would adding-

1:46:53 Olivia Butler: So maybe put triangles on there or squares or whatever to denote the marks.

1:46:59 Audience member: Like, this obviously has a lot of lines, but, like, let's say it was just two or three. Would adding just a label help?

1:47:08 Olivia Butler: Yes, in the sense that it addresses any visual accessibility challenges. No, because it would not be screen reader friendly.

1:47:17 So if the challenge is with an assisted device reading the marks in your view, they're not– that will not solve the problem.

1:47:26 That's where accessibility gets tricky. You can fix one problem and immediately cause another.

1:47:32 Excellent question.

1:47:34 Okay.

1:47:36 Cognitive overload, I have, like, 18 links to eye tracking studies. I'm fascinated by this as a side note. All I'm gonna say today is cognitive interpretation of your content is just as important as it being mobile friendly or navigation friendly.

1:47:52 Use big numbers.

1:47:54 Everybody starts in the top left first in Western culture.

1:47:58 Guide by contrast.

1:48:01 And this one's again really weird.

1:48:04 Put text in your visualizations. I know it's weird. It's uncomfortable. Most of the time we turn off all the text. Use those captions.

1:48:11 Use your text. Use an extension with an NLG on it. We'll talk about that in a second. And last but not least, if it doesn't need to be on your dashboard, why is it?

1:48:19 We often tend to use our dashboards as catchalls.

1:48:23 Somebody asked a question during requirements gathering, and therefore it must go on the content.

1:48:28 Um, reevaluate that at the end when you're looking at everything and say, "Does this really need to be here?" Get rid of it if it doesn't. And to our earlier conversation, we very much support the keep it simple philosophy and accessibility. Five or less views per dashboard, period.

1:48:47 Extensions.

1:48:49 This originally was an Export All slide. I have Export All demonstrated here. The state is a big fan of Export All. Here's the thing. There's also data tables, supertatos, tables, and export to Excel. These are all in a permanently extension. Your security teams will love it. And you can download it and put it on your server and Tableau Desktop, and it will take all of that information and turn it into a screen reader readable Excel format.

1:49:14 You can control what's in the column names. You– Why don't you use the default download?

1:49:18 If you've got dirty data, you've got column names that are formatted for data analysts, not the general public. You have weird formatting because you're using Tableau to calculate a percentage, and so in your underlying data you have twenty-two decimal places.

1:49:32 These export extensions are gonna get you a long way to that conforming alternative version of your content.

1:49:39 There's also NLG. So there's automated narrative insights in area NLG. If you are on Tableau Cloud, you have built-in native language processing that will take the data that is displayed in your dashboard and turn it into text, and make it dynamic based on your filters.

1:49:56 That really moves us forward and past the screen reader accessibility problem in your content. The trick is, where do you put it?

1:50:06 Where they don't have to tab through 100 elements to get to their version of the content.

1:50:14 Couple of things you can do on the website that I wanna run through really quickly.

1:50:19 First of all, on assistive device navigation, first RAM, uh, NVIDIA and JAWS almost always can be installed on your computers. Most of your places of work will have them already through software. You can put them on your computers and use them. It is not the same as somebody who has an actual need for the navigation technology. It gets you part of the way there.

1:50:41 It's a good interim solution. Um, what we did when I worked at Department of Health Services is we worked with the Wisconsin Council of the Blind, and they had users that are very familiar with assistive devices, that use them in their day-to-day life, read through several of our web pages that had Tableau content on them.

1:50:58 And they shared their screen, and we watched as they navigated through our web page. It was incredibly telling because we didn't notice a lot of the code on the back end, the missing headers, not in the right s- order, et cetera.

1:51:12 Um, and we were able to identify some quick fixes on our content and the way we had it shared in the web pages to make it more friendly to those users. Um, one thing I'm gonna say, permalink to the keyboard navigation shortcuts, I don't care if that's in your dashboard or on your web page, but there is a permalink available for the navigation controls for moving through Tableau content that Tableau hosts and maintains.

1:51:36 So it will tell them how to Control+Shift+Enter. It will tell them how to view data. It will tell them how to navigate marks where they can.

1:51:44 Um, include that somewhere near your Tableau visualization to help anyone who maybe is unfamiliar with Tableau to know how they can use their screen reader to navigate your content.

1:51:56 Th- this one's a tricky one, and I… Who's heard of hidden periods?

1:52:02 Love it.

1:52:04 Screen readers, when they're reading a bunch of text, go at different paces. If you have something that you want to be emphasized, like a title, put a period and change it to white, and the screen reader will pause without you seeing it in the text on the dashboard.

1:52:25 So it creates natural conversation pauses in the text that you're using so that as those assisti- assistive devices are going through, they're pausing at places of import like the titles, the filter selections, et cetera.

1:52:41 Alt text.

1:52:42 I mentioned it's been the biggest issue for the last seven years according to WAI, WebAIM, A- AIM. You have accessibility options in Tableau now to add alt text to literally everything you're doing.

1:52:53 Use them. This is gonna be a big one for your web comms teams, too, when they're running checks on your web pages. Yeah.

1:53:02 Audience member: A- And, uh, your tool tip can be your alt text now, um, which is, uh, really helpful.

1:53:10 Olivia Butler: Yes.

1:53:11 Yep.

1:53:13 Thank you, Sarah. Yeah.

1:53:16 Okay. Embed code magic.

1:53:18 Scale for mobile.

1:53:20 This viz ID that says Tableau viz, if you have more than one Tableau viz on your web page, they all say Tableau viz because this is the default embed code generated out of Tableau Server. Change that. It will not have a unique ID for your embedded element otherwise, and your web compliance checkers will flag them. Your comms teams will get mad, and it hurts everybody because what the heck is a Tableau viz?

1:53:42 That does not describe anything. Change it.

1:53:46 Width to 100%.

1:53:48 This was originally a pixeled value, just like the height at 871.

1:53:52 Change it to 100%, and it will introduce horizontal scroll bars on your viz even without a custom mobile phone layout.

1:54:00 Um, so this is your workaround to not have to do custom mobiles on every single dashboard that's already embedded right away.

1:54:07 Last but not least, no one talks about this, but think about the bottom. Your toolbar is accessible.

1:54:14 Why is it at the bottom of your visualization? If you know you have a substantial number of people accessing your content and it's embedded halfway down a page, and the only way for them to see all of the data in an accessible format is for them to download it from the toolbar, put it at the top.

1:54:30 Make their lives easier.

1:54:32 Audience member: So you literally just change that word to-

1:54:34 Olivia Butler: Top

1:54:36 Audience member: Okay, cool.

1:54:36 Olivia Butler: Super straightforward.

1:54:39 Yeah?

1:54:39 Audience member: What would you change, uh, the Tableau viz ID to do?

1:54:45 Olivia Butler: I would call it whatever my workbook name is.

1:54:48 Audience member: Oh, what-

1:54:48 Olivia Butler: I would make it something meaningful

1:54:50 Audience member: … workbook name? Okay.

1:54:52 Olivia Butler: So the Tableau embedding API exists now. It's using JavaScript 3. Um, there's a lot of help on parameters using JavaScript code to manipulate your embed, et cetera. We're not gonna go through all of that today. Um, but I am gonna encourage you, if you're not messing with the JavaScript API bit of the embed code, y- think about adding p tags.

1:55:13 Um, in HTML world that's just a paragraph, but you can add a p tag and boundary it in the middle of your embed code and put a description of your Tableau dashboard in there, or the title, or whatever else you want it to be, and that will be screen reader accessible when they're reading through the HTML of your page.

1:55:31 All right.

1:55:32 Last but not least.

1:55:35 This is the Tableau's not accessible, how do I get around it slide.

1:55:40 Um, if you have something in Tableau that cannot be read by a screen reader or cannot display well on a mobile device, does it need to be in your dashboard?

1:55:51 Could it be in HTML on your already accessible webpage, and save yourself some time formatting a sheet?

1:55:57 Think about moving text and where it matters. Um, I will tell you right now, people don't have a lot of patience anymore for scrolling and waiting for things to load, so consider not putting a giant amount of text above your dashboard.

1:56:12 How do you get it to them in an intuitive way? That could be accordions. That could be putting some above, some below. It could be putting links to additional information so that the title's still at the top, they have a place to go to get the rest of the details. Think through what makes sense there.

1:56:29 Alternative sources for data downloads. This goes back to your extensions. You can use the Tableau extensions. You can write your own, um, code to export data out of your dashboards and place it somewhere. Um, you can use open data portals to connect to your data, provide it in a format there.

1:56:46 Um, and again, just encour- think about putting those keyboard navigation shortcuts on the webpage, not on your dashboard. Mainly because it takes design space up on your dashboard. Who wants to give up more of their playroom? But also, it could be really helpful before they even begin interacting with the content to let them know how they can click through each of the elements that are accessible.

1:57:11 Okay.

1:57:12 You all, whirlwind of accessibility, you stayed with me. Everyone seems awake. I'm very proud of you.

1:57:17 Um, does anybody have any other questions, comments, concerns, thoughts?

1:57:22 And then I have one question for you all.

1:57:27 I can't tell if that's 'cause I'm… Go ahead.

1:57:29 Audience member: Well, I'm just curious. Accessibility is not a huge part for the-

1:57:32 Olivia Butler: Yeah

1:57:32 Audience member: … private sector, but, uh, is, is there any conversation about AI making things generally more accessible to people?

1:57:38 Olivia Butler: Yes, but we're limited at the state because we are on on-prem servers still.

1:57:45 Um, so a lot of the AI assistive device, NLG improvements that Tableau is making are in cloud.

1:57:52 Um, and we do not have permission to collect, connect AI to anything on our local machines in the state 'cause of privacy security rules. So yes, but only if we can get to Tableau Cloud and use the newer functions there.

1:58:06 But great question.

1:58:07 We, if we weren't hamstrung and hands tied behind our backs, we probably, I would have a different answer.

1:58:14 Yeah?

1:58:14 Audience member: Could I ask, so a lot of times we build our dashboard, the visual part looks nice, but the data download's a mess. But we, we, like, we've started playing with the idea of just building a version of just like the table.

1:58:29 Olivia Butler: Mm-hmm.

1:58:29 Audience member: Right? That's accessible.

1:58:31 Is there a way within the same workbook to, like, can I, like, hide the toolbar on my visual ones so you can't download the data and then just make the data download accessible on the table version? And is that considered meeting the accessibility requirements?

1:58:47 Assuming, like, all the, like the-

1:58:49 Olivia Butler: Yeah.

1:58:49 Audience member: Right.

1:58:50 Olivia Butler: As long as it's in the same location or linked to in the same lo-

1:58:54 Audience member: Like, it's on the same page. Like-

1:58:55 Olivia Butler: Yep

1:58:55 Audience member: … right now, like the, the, the table and, like, an accordion. So for, if you're someone who really needs it, it's there, but the visual is, like-

1:59:03 Olivia Butler: Yep

1:59:04 Audience member: … the main. Is that accessible?

1:59:06 Olivia Butler: Yes. Minnesota's done it to their webpages. That's a really good example if you wanna look at the Minnesota Public Health webpages. They did data tables in accordions on theirs.

1:59:15 Audience member: Okay.

1:59:15 Olivia Butler: Um, the other way if you don't wanna have the toolbar is an Excel PDF navigation or a download button from your web, of your dashboard objects.

1:59:25 Audience member: Yeah.

1:59:26 Olivia Butler: Um, and so, like, put the image of an Excel file or a PDF-

1:59:29 Audience member: Sure

1:59:29 Olivia Butler: … and then hide the toolbar, and then they just click on that instead of going to the toolbar. Sometimes that's easier if you want them to get the full download data anyway.

1:59:37 Audience member: I don't think you can get the full download there anyways.

1:59:37 Olivia Butler: 'Cause you have that weird…

1:59:39 If you have to click into a visualization to then get the data download to show up, that's not always the most accessible for folks. So yeah, accordion data table would be great.

1:59:49 Um, the other option would be to just have that download right at, underneath the title, and then that's the first thing the screen reader would take them to.

1:59:56 Audience member: Yeah.

1:59:57 We, we still have a rather to look for that extension.

2:00:01 So we tried to find all-

2:00:02 Olivia Butler: I'll talk to you after, Rachel. And I'll email Tom for you and get that moving.

2:00:07 Um, there's no… It's, yeah, it's improved at the state already, so it's a hold up on the FIT side, I'm sure. Yeah.

2:00:14 I will work on that with you.

2:00:17 Anybody else?

2:00:20 All right, my question for you all:

2:00:23 Accessibility is sort of one of those topics where it feels like we could go on for years, but we don't h- always have that.

2:00:28 Would it be helpful to do an extension on this series?

2:00:35 Either in, like, some sort of doctor sessions or a deep dive into color or cognitive eye tracking studies or anything like that?

2:00:43 Audience member: I think that's-

2:00:44 Olivia Butler: Use a chance to a stretch.

2:00:46 Yes.

2:00:46 Audience member: I could do a lot of repeat.

2:00:50 Olivia Butler: Okay. Um, do you have a preference?

2:00:52 Audience member: For, like, what part of accessibility? I feel like we're good with plain language and color.

2:00:57 Olivia Butler: Yeah.

2:00:57 Audience member: It's, like,

2:00:59 the data screen readers stuff, which we're all struggling with.

2:01:04 Olivia Butler: Okay.

2:01:05 Data we can do.

2:01:08 Audience member: Lots of yeses online as well.

2:01:19 Olivia Butler: Okay.

2:01:20 Lovely humans, I think that's it for me today. If you guys have additional questions, um, don't hesitate to reach out. Um, all my contact information is available in a variety of places, and I will share these slides with you all too.

2:01:32 Thanks.

2:01:39 Robert Salas: Right. We are in the home stretch. Everybody stretch. Olivia gave us a stretch.

2:01:44 So today, covered a lot of subjects, right? We had our critiquing dashboards, how to design them better, plus clear delta. Hopefully people will use that. I like that.

2:01:54 Uh, parameters. Paul's version of parameters, measure swapping, dimension swapping, dynamic zone visibility, exists sheet swapping.

2:02:01 Mapping, also using parameters. Hex maps, shape maps, drill down.

2:02:06 And the huge topic of accessibility, which it sounds like a follow-up for that. So yay.

2:02:13 Um, upcoming in, gosh, two weeks from now is the Wisconsin Tableau User Group event. Always virtual, always online. Doesn't suffer from these, uh, hiccups and bumps of getting the screen to share 'cause it starts online and it stays online.

2:02:26 Um, so we have a nice lineup of, uh, presentations, topics, and events for that as well. So if you're not part of Wisconsin Tableau User Group, why? You can do it from the comfort of your own home or from your desk. We always do it over the lunch hour. I say we 'cause I'm also on the leadership team for Wisconsin Tableau. So look for that. If you're interested, um, I can get you, uh, on the user group registration, and you'll get notifications when that's up.

2:02:50 There's a LinkedIn group for that you can also follow, much like ours. So that event, again, online over the lunch hour, uh, Tuesday, October 13th.

2:03:01 Our next event, um, is December 10th. It'll also be virtual 'cause it's cold, and we don't think we can lure you out into the icy winter, so we'll do it online. Also gonna be over the lunch hour, 11:30 to 1:00. But that day we are gonna have an in-person event, which is our, our with Madison TUG holiday party, which is gonna be at Delta Beer Lab. Anybody ever been to Delta Beer Lab?

2:03:23 Yeah. Kinda fun. Do things. You bake your own pizza, hang around, we'll play board games, or drink, have some food, chit-chat, et cetera. So that is December 10th. I don't remember what day of the week that is. Thursday. Thursday. Thank you.

2:03:39 We come to the end. So we have, uh, kind of a combined swag giveaway. We have all of our in-person people here. You have bingo ball numbers.

2:03:48 Who's our bingo drawer, Jen?

2:03:50 Right here. And then we have our online folks. We're gonna do a wheel of names spin for that, so hang tight.

2:03:57 Whoo. If you're here in person, you get the double reward, you get to choose. Double reward. We have a table of swag in the back with some T-shirts, some books, some tote bags, and some, uh, beverage containers that you've chosen, so you can pick. Winner? G55. Two. G55? G55. All right.

2:04:16 G55. Take your pick from the table, or we can offer you a gift card for the Tableau swag store online, which, uh, offers a lot of things. They're a little spendy, but we'll give you a gift card for something online.

2:04:26 Or you can choose from the table and have immediate gratification.

2:04:30 Yes, that dopamine right now. And our second winner is B10.

2:04:35 B10. B10?

2:04:39 B10? Hey, over here. Hey.

2:04:41 Same choice.

2:04:43 Table in the back. Grab whatever you'd like.

2:04:45 Book, shirt, notebooks, et cetera, et cetera, et cetera.

2:04:48 Oh, Jen, let's… Did you put them away already?

2:04:51 Huh? Did you put them away already?

2:04:53 No. Let's draw one more.

2:05:00 One more? Yeah. Online folks. See, I keep all the swag at my house, and I have to take it all to home. It's like, "Please." He's actually mapping. "I'm hoarding all that." "I don't need to get rid of some stuff." G59.

2:05:10 G59. G59? Hey.

2:05:14 Mercury Marine wins too.

2:05:17 All right. And then Jen, do you wanna do the wheel of names online or are you just gonna-

2:05:23 Sure. What T-shirt did you go with? You went to, um, giving to people, I think. Nice. Yeah. And you're a rock star.

2:05:32 Nice. John Standard is our first winner online. Whoo-who.

2:05:37 Who's that? Can you say that for them again? Who is it? John Standard.

2:05:43 John Standard. John Standard, you're our winner online.

2:05:48 Let me- You are.

2:06:04 Comes to the end.

2:06:05 Good meeting? One hand, two hands. Thumbs, yeah. Yay. Thanks.

2:06:10 Uh, thanks for coming out today. Again, it is a hard thing in this post-COVID life to… All right, guys. For all of you online, again, John Standard and Brad, um, Davidson, please hang for just a second or DM me. Just send a private message with your email address.

2:06:25 Um, and then for all of you here, if you'd like to hang for a little bit and get to know each other or us, have some food, have some beverages, please do so.

2:06:35 Thanks for coming. Thanks very much for coming.

2:06:36 Audience member: Thank you.

2:06:37 Robert Salas: Yeah.

2:06:38 Thanks to you. All of you online, take care.

Shorts for this TUG

Leave a comment

Your email address will not be published. Required fields are marked *