Knowledge should be readily available for designers to be proactive in designing accessibility into the system. The reference sheet helps keep critical considerations in mind early and often in the design process.

We aimed to avoid the idea a "checklist"; something that typically comes into play after design is complete. Short, concise examples, not open to interpretation, help to motivate designers to achieve parity in quality.

• Color is the first thing we get wrong, and often the easiest to fix.
• Responsive design focused on magnification for our product, informing how they need to react when zoomed.
• Alteranative text on images, and ensuring decorative images are annotated.
• Keyboard accessibility keeps keyboard-only use cases in mind.
• Links & Buttons helps ensure that designers and developers use the right component for the right job.
• Headings & Page Titles broke down the logical structure of our product with headings.
• Forms are a big part of our product, so is getting them right and keeping them consistent.
• Multimedia , such as animation, is a popular way to add pizzazz to designs and important to keep accessible.
• Notifications are very important in enterprise products and for accessibility.

Annotations were added to all components in Tanzu's design system guidelines, informing both designers and developers how each building block worked and how they can work together. Accessibility was built into each design system component when possible.

Design wireframes were rarely annotated up to this point. Not only did the design guideline annotations provide their intended information, they also helped serve as informed examples to designers provide their own annotations within wireframes.

Design review expectations were updated to include accessibility annotations.