Accessibility Examples
SmartSite Accessibility Guardrails
SmartSites built-in functionality will act as a guardrail against a variety of accessibility issues. Required alternative text, color contrast minimums, etc.
List of things to keep an eye on but not necessarily worry about:
- Alternative text (required before proceeding)
- Color contrast (built-in to each component, keep default settings)
Text Content Examples & Best Practices
Using the default color options for headers and text will maintain a cohesive style across the website. The standard color combinations already meet the WCAG standards. If you use custom colors for any reason, ensure they are the “official” school colors. SmartSites will automatically detect if there is a color contrast issue.
When creating a link within text or attempting to draw attention to a specific word or phrase, remember that color cannot be the only indicator. Take a look below at examples of good and bad links.
Example of a BAD link:
We are proud to live in Bloomington: Visit Bloomington
- There is no description of the link.
- There is only one indicator of a link.
Example of a BAD button:
We are proud to live in Bloomington!
Example of a GOOD link:
We are proud to live in Bloomington! Click the link to view the Visit Bloomington website: Visit Bloomington
- A written description precedes the link.
- There are multiple indicators of the link: color, size, and underline.
- The link opens in the same tab.
Example of a GOOD button:
We are proud to live in Bloomington! Click the button below to view the Visit Bloomington website.
Additional settings for Safari Browser.
