Bphh 2165 add tool tip to auto compliance to explain what this means

[guri-dev]

Description

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📦 Chore (Release)
• ✅ Test

Related Tickets & Documents

Steps to QA

UI Accessibility Checklist

Note the following checklist is not an exhaustive list. Check
the WebAIM checklist for
a user-friendly checklist with more details. Aim to meet at least AA conformance level where applicable. Check
the WCAG guidelines for the full guidelines.

• Markup uses semantic HTML?
• Additional context added through aria-roles and aria-labels?
• Checked
  with Wave Browser Extension
  for accessibility errors?
• Usable with a keyboard and navigable in a logical order?
• Usable using a screen reader (e.g. Voiceover for Mac) with enough context for the user?

General Checklist

• ✅ Provide tests for your changes where relevant
• 📝 Use descriptive commit messages
• 📗 Update any related documentation and include any relevant screenshots
• 📱 For UI-related tasks, ensure responsive design is implemented across multiple screen size
• 🗂️ Move your relevant story/task to the Ready for Code Review state

[optional] Are there any post-deployment tasks we need to perform?