When to Involve AX

Changing the content of a string

• Involve AX!

• Do NOT Involve AX!

Answer explanation

You should have Patient Literacy folks check out that change!

Creating a small fix log for an AX QAN.

• Involve AX!

• Do NOT Involve AX!

Answer explanation

Yes! You should also ALWAYS have a design for fixes to AX QANs! These fixes are not always as straightforward as they seem which is why it's good to have an expert on hand.

Changing the location or size of a string

• Involve AX!

• Do NOT Involve AX!

Answer explanation

If the font is small or has suddenly gone somewhere very different from where it used to be, at some point you have to assume you have a group of users who just can't read it. Involve me so we can make sure the change is positive!

Changing the color of a button

• Involve AX!

• Do NOT Involve AX!

Answer explanation

Involve AX for two reasons!

1. Some colors may have no change to folks with different kinds of colorblindness. If we're choosing that color, it should be purposeful.

2. 2. A good amount of standard MyChart colors don't meet WCAG contrast requirements unless they're in high contrast :/ Let's not introduce more components using bad colors if possible.

Making something process or call for code faster than it used to

• Involve AX!

• Do NOT Involve AX!

Answer explanation

Nah, you got this bestie. If you magically create a process so fast that it's going to permanently impact how a screen reader behaves (very unlikely, but maybe now screen readers start to say loading and we actually will never show a loading symbol cuz it's SO FAST) then you can involve me.

Redesigning an activity

• Involve AX!

• Do NOT Involve AX!

Answer explanation

Redesigning an activity is going to hit SO MANY aspects of AX work. How are we structuring it with headers, tables, etc? Are we changing how we navigate TO the activity? THROUGH the activity? Are we adding decorative or workflow-relevant images? Does this activity link out to something else?