Accessibility: FullCalendar calendar view WCAG compliance and upgrade path

[tcdahlberg]

Summary

A community member raised accessibility concerns about the Summit Events calendar page (Trailblazer Community thread).
The calendar view (\SummitEvents.page) uses FullCalendar to render events from the SEA REST API feed. The accessibility limitations reported are inherited from FullCalendar itself, not from SEA's own markup.

What SEA controls vs. what FullCalendar controls

• SEA controls: the <select>\ audience filter, page structure, and the REST API feed that supplies event data
• FullCalendar controls: all calendar DOM rendering, keyboard navigation, ARIA roles, and interactive event markup
  The audience <select>\ element in the page already has a <label>\ and \ itle\ attribute, so that portion is reasonably accessible.

Options for affected users

1. Use the built-in calendar and monitor FullCalendar v7 — FullCalendar's accessibility docs acknowledge current limitations and v7 (currently in RC) may improve the situation.
2. Build your own calendar page using the SEA REST API feed and a more accessible calendar/list library of your choosing. A community recipe exists for this approach: Full Calendar Recipe.

Suggested actions

• Evaluate FullCalendar v7 RC against WCAG 2.1 AA criteria when it reaches stable release
• Consider whether a list/agenda view (rather than the grid calendar) could serve as an accessible alternative display mode within SEA
• Document the accessibility posture clearly in the SEA docs so admins can make informed decisions
• Engage FullCalendar upstream if specific WCAG gaps can be reproduced and reported

References

• FullCalendar accessibility docs: https://fullcalendar.io/docs/accessibility
• SEA full calendar recipe: https://sfdo-community-sprints.github.io/summit-events-app-documentation/docs/Recipes/full-calendar/
• Community thread: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000mn8o9