Check font size, font style, alt text, control contrast, focus indicators and accessibility issues before sharing a sales coaching deck.
Key takeaways
- Check small labels and captions as well as body text.
- Review generated image descriptions against the pictures.
- Test clickable controls against their backgrounds, including their focused appearance.
- Use the Accessibility Checker while building, after fixes and before sharing.
Why deck accessibility matters in coaching
A coaching deck is only useful if every rep in the room can read it, so this guide covers the checks to run before the deck reaches the team. It is written for managers who share slides in call reviews and coaching sessions. It does not decide whether any deck falls under a legal rule, so take that question to your own counsel. You can treat the checks as a habit for every deck, not a one-time fix.
The U.S. Department of Justice has consistently taken the position, according to U.S. Department of Justice, that the ADA applies to web content, and it has taken that position since 1996. The same source says that when Congress enacted the ADA in 1990, it intended for the ADA to keep pace with the rapidly changing technology of our times, according to U.S. Department of Justice, so you should review slides with the same care you give any shared file.
Your coaching is also affected when a slide a rep cannot read takes time away from the sales moment under review. You can protect that time by running the checks before the deck reaches the team, so the call stays on what the seller said and did. The checks are quick, and they are easier to repeat when you keep the same steps on every deck.
You can see the source behind each check in this guide, so you know where a rule comes from and where its wording stops. The rules stay close to the published wording, and any advice beyond that wording is editorial. That separation matters when a team member asks why a deck was changed.
You read the numbers as the sources give them, and you do not treat a passing check as proof that every rep can read every slide. The checks cover the deck file, so keep that limit in mind when you read the results.
Before building: font size and font style
1. Font size of 18pt or larger
Microsoft's guidance is to use a larger font size (18pt or larger), sans serif fonts, and sufficient white space, according to Microsoft, so you can start there when you set up a coaching deck. You check the font size on every slide, including the small labels, notes and captions that you add during a review.
You check the body text on your first slide, then any table, chart label or callout that sits off the main layout, since those are easy to miss. A label that looks fine at your desk may be harder to read when the deck is shared. Give those elements the same size rule as the body text, so the deck reads the same from the first slide to the last.
Microsoft also recommends choosing themes with these font settings, according to Microsoft, so you can check the theme once and reuse it for every coaching deck.
2. Sans serif fonts with white space
You pick one sans serif font for the body text and keep it across the deck, since a mix of faces adds visual noise that pulls attention away from the call. Review font style and spacing together on each slide. Keep the same font in titles and body text unless the theme sets a different heading style.
You check spacing by looking at the gaps between headings, bullets and captions on each slide. If a slide feels crowded when you read it at arm's length on your own screen, move a secondary point to the next slide and keep only the words the rep needs for the review. Leave the detail in your notes, where it is still available during the discussion.
Before building: alt text on photos and icons
3. Alt text on photos and icons
PowerPoint for PC in Microsoft 365 automatically generates alt texts for photos, stock images, and the PowerPoint icons by using intelligent services in the cloud, according to Microsoft, so a draft description may already exist before you write one. You look at what the tool produced before you accept it, since a generated line is a starting point for your own wording.
You read each generated description against the image and ask whether a rep who cannot see it would still know what the picture shows. If the text is vague, rewrite it in plain words that name the object, the chart value or the point the picture makes. Keep the wording short, because a long description can be as hard to use as a vague one.
You will find that icons often carry meaning, such as a warning sign or a checkmark, so you describe that meaning rather than only the shape. You describe each icon in the words your team uses on the call, so the description matches the conversation. Your review covers the photos, stock images and icons on every slide, including the image on the title slide.
You may find that decorative pictures add nothing to a coaching point, so they need the least attention in your review. If you leave one without a description on purpose, write down that decision in your file, so the next reviewer does not reopen the same question. A picture that carries no information is still part of the deck, so it deserves a deliberate choice.
After you swap a picture, reread its description so the text still matches the new image. You keep a short list of the images you described by hand, because those descriptions are the ones most likely to need a second read. Review that list before the session, not during it, and keep the list in the same file you use for the deck.
While building: contrast on controls and focus
4. Control contrast of 3:1
The W3C success criterion says that, unless the control is inactive, visual information needed to identify a control and how to operate it must have a minimum 3:1 contrast ratio with the adjacent colors, according to W3C, so you check the outline and icons around every button. You check each one against the background it sits on, since the same shape can look clear on white and weak on a tinted panel.
The contrast ratios referenced in this success criterion are intended to be treated as threshold values, according to W3C, so do not round a lower result up to a pass. You do not stretch this to every text element in the deck, because the criterion is about controls and the visual information that identifies them. For a separate text check, see contrast on the next demo deck.
5. Visible focus indicator
W3C illustrates a focused button with a grey focus indicator against white at a contrast ratio of 3:1, according to W3C. Use that as an example, then test your chosen outline against the background on your slide.
A focus indicator that blends into its background is hard to follow, so you pick an outline color that stands out on the background of the slide itself. You check the indicator on the lightest and darkest background in the deck, since a single outline color may not work on both. You keep the outline easy to see on a shared screen.
If your deck includes clickable buttons or shapes, you check the focused look as well as the resting look, so a reader can follow where the focus sits. You repeat the focus check after each theme change, because a new background can change how a button stands out, even when the button itself stays the same. You keep it in the same routine as the contrast check, so both are finished before the deck is shared.
Before sharing: run the Accessibility Checker
6. Use the checker during creation and after fixes
Microsoft describes working with the Accessibility Checker to tackle accessibility issues while creating a presentation, according to Microsoft. Running it only at the end can leave you with more fixes than the time you planned to spend.
During the build and before sharing, use the checker and read each issue before you change anything, so you know what each fix affects. You keep a record of the issues you fixed and the ones you left, along with a reason for each one you left. If a leftover issue cannot be fixed before the call, you note it at the top of the deck so the reader is not surprised.
You fix font, image and contrast problems first, since those are the checks covered in this guide. You then run the check again after your fixes, so the final version of the deck is the version you tested. That second run is the one to keep in your file for the deck.
You share the deck and the coaching notes together in the same message, so everyone reads the same version. You name the file with the date and the word final, so a reader who opens an older copy by mistake can spot it. The file name is a simple habit, and it keeps the review focused on the sales points.
You keep the call on sales behavior and treat formatting questions as a short follow-up after the call. A rep who sees an accessibility note on the first slide can ask for help before the session starts, which keeps the time on the sales points. Make the follow-up a named item in your coaching notes so it does not drift.
What to keep on file for each deck
You keep a short file for each deck that records the rules you checked and the source each rule came from. The table below lists each publisher this guide draws on and the topics covered. Use the file as the reference when a question about a slide comes up during the review. Keep it brief enough that a manager can read it in a minute.
| Publisher | Source | Topics covered |
|---|---|---|
| Microsoft | Make your PowerPoint presentations accessible to people with disabilities | Font size, font style, spacing, generated alt text and the Accessibility Checker |
| W3C | Understanding non-text contrast | Control contrast, threshold values and a focus-indicator example |
| U.S. Department of Justice | Guidance on Web Accessibility and the ADA | Web content and the ADA |
You store the file with the deck, in the same place your team uses for coaching materials, so a manager can answer a question about a rule without searching through old messages. You keep a separate file for each deck rather than one master file, so each review has its own record. A deck-specific file also makes it clear which version the team discussed.
You note the date you ran the checks and the version of the deck you tested, since a later edit can change the font, image or contrast result. You write the date in the file name as well as in the notes, so the record is easy to match to the deck. If the record and the deck disagree, you rerun the checks before anyone uses the deck in a coaching session.
You record which images you described by hand and which descriptions you accepted from the generated text, so the next reviewer knows where to look first. You add a line for any decorative picture you chose to leave without a description, along with the reason for that choice. You keep these notes short, because a long log is harder to use in a busy review.
You review the file when your team changes its theme, because a new theme may bring back fonts you already fixed. The file then works as a record of what you checked, not as a permanent verdict on the deck. Ask a second person to read the file before the next coaching cycle starts, so one manager's habits do not set the standard alone.
Illustrative example: review a crowded slide
A crowded coaching slide has a small caption and a picture described only as an image. Move secondary points to another slide, leave supporting detail in the notes and rewrite the description to explain the picture's coaching point. Review the caption against the font guidance. Check the changed slides, then save the results beside the deck so the record matches the version shared.
Related guides
For the session itself, review live captions before sales coaching calls. If you plan to record the discussion, review buyer privacy before recorded sales coaching.
Your next step
Open your next coaching deck today and review its smallest labels against the font guidance above. Keep the file from the previous section beside it and record what you change.
Questions
What font size should a coaching deck use?
Use 18pt or larger as your starting point, following Microsoft's guidance. Check small labels and captions as carefully as body text. A label that looks fine at your desk may need another look when the deck is shared, so include elements outside the main layout in your review.
Does PowerPoint write alt text automatically?
Yes, PowerPoint for PC in Microsoft 365 automatically generates alt text for photos, stock images and PowerPoint icons. Ask whether the wording explains the picture's coaching point, and reread it whenever you replace the picture.
What contrast ratio do controls need?
Visual information needed to identify and operate an active control needs at least 3:1 contrast with adjacent colors. Test against the background the control actually sits on, and check its focused appearance separately. A background change can affect the result even when the button itself stays the same, so keep this check in your review after theme changes.
Has the ADA applied to web content for long?
Yes; the U.S. Department of Justice position described above dates back decades. Ask your own counsel about your obligations. This deck review is a practical coaching routine, and a passing check does not decide whether a deck falls under a legal rule.