An App Builder styling property is a feature that allows a Lightning web component to expose CSS properties that can be set by an administrator in the Lightning App Builder. This way, theadministrator can customize the look and feel of the component depending on the context and use case. For example, a component can have a styling property for the background color, the font size, or the border radius. The administrator can then change these values in the App Builder without modifying the code of the component. References:
* [Create App Builder Styling Properties]

To view the history of cases that a specific customer has submitted, the representative should go through the following hierarchy of information: All Accounts > Account Detail > Contact Detail > Case Related List. This is because cases are related to contacts, and contacts are related to accounts. By navigating from the account level to the contact level, the representative can see all the contacts associated with a specific account. Then, by selecting a contact, the representative can see the case related list, which shows all the cases that the contact has submitted or been involved in. This way, the representative can view the history of cases for a specific customer in a logical and efficient manner. References: : UX Designer Certification Prep: Designing with Service Cloud | Trailhead : Service Cloud Basics | Salesforce Help

To restyle a Lightning Experience model to meet brand guidelines, the designer should use design tokens and find the appropriate component blueprint. Design tokens are variables that store visual design attributes, such as colors, fonts, and spacing. They allow the designer to customize the appearance of Lightning components without writing any code. Component blueprints are design specifications for Lightning components that provide guidance on how to use them, what properties they support, and how they behave in different scenarios. They help the designer to choose the right component for the model and apply the brand guidelines consistently. References: : Design Tokens | Salesforce Developer Guide : Component Blueprints | Lightning Design System : UX Designer Certification Prep: Designing with Lightning Components | Trailhead

CK can assign learning content to employees using In-App Learning functionality in the following two ways:
* Trailmixes: Trailmixes are custom learning paths that can include modules, projects, trails, and even external links. CK can create and assign trailmixes to learners based on their roles, goals, or interests.
Learners can access trailmixes from the Learning Home or the Guidance Center in Salesforce.
* Modules/Badges: Modules are units of instruction that cover specific topics and skills. Badges are earned by completing modules or projects. CK can assign modules or badges to learners to help them learn specific features or functionalities in Salesforce. Learners can access modules or badges from the Learning Home or the Guidance Center in Salesforce. References:
* : In-App Guidance in Lightning Experience
* : Learn MOAR in Spring '21 with In-App Learning
* : Enable Users to Learn in the Flow of Work

The Web Content Accessibility Guidelines (WCAG) are a set of standards that aim to make web content more accessible to people with disabilities. The WCAG are organized by four principles, which state that content must be:
* Perceivable: Users must be able to perceive the information and user interface components in ways they can sense, such as through sight, hearing, or touch.
* Operable: Users must be able to interact with the user interface components and navigate the content using various input methods, such as keyboard, mouse, voice, or gesture.
* Understandable: Users must be able to comprehend the information and the operation of the user interface, which means that the content must be clear, consistent, and predictable.
* Robust: Users must be able to access the content using a wide range of technologies, including different browsers, devices, and assistive tools, which means that the content must be compatible with current and future web standards. References: WCAG 2 Overview, Understanding the Web Content Accessibility Guidelines