A calendar is useful when you can read its dates, understand its controls and recover from mistakes. These are the accessibility practices the interface is designed to support.
Use the controls with a keyboard
Move through links and form controls with the keyboard and look for a visible focus indicator. Date fields, week-start choices, event controls, import review and export actions should have meaningful labels. A selected option needs a recognizable state as well as a different color.
When an editing panel or dialog opens, continue from its relevant control rather than losing your place behind it. Closing the panel should return you to a useful part of the workflow. Browser and assistive-technology behavior can vary, so the documentation also describes each step in ordinary text.
Read the page at a comfortable size
The site offers light and dark interface themes. The printable calendar remains white by default, independently of that screen preference. Use browser text and zoom settings when needed, and choose a calendar layout with enough room for the information you want to print.
Monthly date numbers, weekday labels and event names have different roles and should remain distinguishable. A compact year overview is not a substitute for a detailed monthly or weekly page when small text is difficult to read. Choose the level of detail that fits your use.
Keep meaning beyond color
Event colors can help you scan a calendar, but titles and category labels should carry the information as well. Keep a visible legend when the colors represent categories, and review a black-and-white version if the page will be photocopied.
An error, saved state or selected control should not rely on a colored border alone. Text should explain what happened and the useful next action. A save or export failure must remain different from successful completion.
Recover from input errors
An invalid date or import row should keep the entered value visible and describe the problem close to the field. Review the field name and message, correct the value, then check the result. Ambiguous dates need a clear YYYY-MM-DD replacement rather than an unexplained guess.
CSV and JSON review should preserve the current project until confirmation. Export progress and cancellation should leave the calendar available. These behaviors support people who need more time to inspect a step or repeat part of a workflow.
Describe a barrier with a small example
If you encounter a barrier, note the page, action, browser and assistive technology involved. Describe the result you expected and what prevented you from continuing. Use sample events when sharing screenshots or files so personal calendar details are not included unnecessarily.
The Contact page contains the help currently available. This statement describes design and use expectations; it is not a claim of an independent accessibility certification or a guarantee that every browser and assistive-technology combination has been tested.