01
Accessibility goals and practical assistance
The website aims to support keyboard navigation, readable contrast, larger text, clear form labels and reduced-motion preferences. These are design goals that need ongoing testing across different devices and assistive tools. A statement of intent is not a guarantee that every feature meets every accessibility criterion. Families should be able to report a barrier without needing to explain a technical standard or prove that a particular tool was used correctly.
When requesting help, describe the information or task you cannot access and the format that would work better for you. You can name a screen reader or device setting if it helps explain the issue, but you do not need to disclose a diagnosis or personal medical history. The team can consider a practical alternative while the website issue is reviewed. Venue access and participation requirements are separate from website accessibility; ask the organizer about the actual facility and event arrangements. Keep those questions specific to the session so the response reflects the location and activity you plan to attend.
02
Using the site with a keyboard
The site's accessibility goals include reaching navigation, links and form controls without a mouse. Use the Tab key to move between controls and look for the visible focus indicator showing the current position. The skip link at the top of public pages is intended to move directly to the main content. A menu or dialog should offer a clear way to close it and should not leave you unable to return to the rest of the page.
If a player illustration changes on hover, the written information should still explain the kit without requiring that effect. Decorative motion should not be the only way to understand an action or status. If you encounter a control you cannot reach or activate, report the page, the control's label and the sequence that led to the problem. You do not need to identify the underlying technical cause. Accessibility is a continuing improvement goal, not a claim that every screen has passed a complete independent audit. Ask the team for another way to receive essential information when a barrier prevents you from completing a task.
03
Reading comfortably on a small screen
Families often check team information while travelling or standing near a field. The page should therefore keep important actions clear and allow text to wrap without requiring precise gestures. You can use your device's text size or browser zoom settings to make information easier to read. Larger text should not remove an essential action, hide a form label or force you to guess a value. A schedule may contain several details, so read the date, time and status together.
On a phone, use the navigation menu and the page's guide links to move to the section you need. A long guide should not require you to read every paragraph before finding the main schedule or contact action. If something overlaps, is cut off or scrolls sideways unexpectedly, tell the team which page and device were involved. Include whether you were using enlarged text or a particular orientation. Screenshots can help, but remove private account or player information before sharing them. The aim is a readable, practical experience across devices rather than a layout that works only at one screen width.
04
Clear labels and readable information
A useful team website explains actions in familiar language. Labels should distinguish an event's arrival time from its start, an upload from a published image and a request from an approved family link. A short heading helps readers find the subject without needing to understand the website's internal systems. Written status information is important because colour alone may not communicate a cancellation, error or selected option to every visitor.
Longer pages are organized into sections so readers can choose the detail they need. Examples should help a family make a decision without implying that an unconfirmed arrangement is already official. If a sentence, abbreviation or button label is confusing, tell the team what you thought it meant and what you were trying to accomplish. That feedback can improve the wording for everyone. Images that convey information should have a meaningful text alternative, while decorative graphics should not compete with the content. If information is available only in an inaccessible attachment, ask for a readable explanation of the relevant instructions rather than guessing from the file's appearance.
Back to page overview ↑