Applies to: This article is for customers using CMS Module. If your organization uses the Content Legacy Module, refer to the corresponding article for that module.
At TeamSideline, we are committed to helping organizations create websites and content that are accessible to all users, including individuals using assistive technologies such as screen readers and keyboard navigation.
While no website platform can automatically guarantee ADA compliance, the TeamSideline Content Editor includes tools and best practices that support accessibility standards such as WCAG 2.1 AA.
What Accessibility Means
Accessibility helps ensure your website can be used by visitors with disabilities, including users who may:
- Use screen readers
- Navigate by keyboard instead of a mouse
- Require larger text or higher contrast
- Have visual, auditory, motor, or cognitive impairments
Accessibility standards are commonly based on:
- WCAG (Web Content Accessibility Guidelines)
- ADA (Americans with Disabilities Act)
Accessibility Features in the TeamSideline Content Editor
The TeamSideline Content Editor includes several built-in features that support accessible website design.
Structured Content & Headings
The editor supports proper heading structures (H1, H2, H3, etc.) which help screen readers understand page organization.
Best Practice
- Use one H1 per page
- Use headings in order
- Avoid using bold text in place of headings
Image Alt Text
All images should include descriptive alternative text (“alt text”) so screen readers can describe the image to visually impaired users.
Example
Instead of:
image1.jpg
Use:
Youth soccer players shaking hands after a game
Decorative Images
If an image is purely decorative, alt text may be left blank.
Color Contrast
Choose text and background colors with sufficient contrast to improve readability.
Recommended
- Dark text on light backgrounds
- Avoid light gray text on white backgrounds
- Avoid relying on color alone to communicate information
Keyboard Navigation
Pages created in the editor are designed to support keyboard navigation for users who cannot use a mouse.
Best Practice
- Ensure buttons and links are clearly labeled
- Avoid adding content that traps keyboard focus
- Test forms and menus using only the Tab key
Accessible Links
Links should clearly describe their destination.
Avoid
Click Here
Recommended
View Baseball Registration Information
Video & Media Accessibility
If you embed videos or audio content, accessibility best practices include:
- Closed captions for videos
- Transcripts for audio-only content
- Avoid autoplay when possible
Accessibility Apps & Tools
Organizations looking for additional accessibility functionality may choose to add third-party accessibility applications to their site.
Common options include:
These tools may provide features such as:
- Text resizing
- Contrast adjustments
- Dyslexia-friendly fonts
- Enhanced keyboard navigation tools
- Screen reader assistance
- Accessibility toolbars
Important Note
Accessibility apps and overlays can help improve usability for some visitors, but they should be considered supplemental tools and not a replacement for accessible website design and content practices.
True accessibility compliance depends on the overall accessibility of your website content, structure, forms, media, and navigation.
Important Compliance Information
Using the TeamSideline Content Editor does not automatically guarantee ADA or WCAG compliance.
Accessibility compliance depends on:
- The content added by your organization
- Ongoing maintenance and testing
- Third-party embeds or integrations
- Overall site structure and design choices
Recommended Accessibility Checklist
Before publishing content, we recommend reviewing the following:
✅ All images include alt text
✅ Headings are used properly
✅ Links clearly describe destinations
✅ Text is readable with sufficient contrast
✅ Forms include labels and instructions
✅ Pages can be navigated by keyboard
✅ Videos include captions when applicable
Ongoing Accessibility Maintenance
Accessibility should be treated as an ongoing process rather than a one-time setup.
We recommend:
- Periodic accessibility reviews
- Testing new content before publishing
- Reviewing feedback from users
- Updating older content over time
Need Assistance?
If you have questions about accessibility features within the TeamSideline Content Editor, please contact our support team: