Accessibility

We target WCAG 2.1 level AA of the Web Content Accessibility Guidelines. An automated suite runs axe-core against that ruleset on the pages listed below, and a run fails on any serious or critical finding that is not written down on this page.

The suite was last run against yuptrack-staging on 2026-09-09.

Automated checks find some barriers, not all of them. They cannot tell you whether a label makes sense or whether a flow can be finished without a mouse, so a passing run is a floor and not a claim that a page is easy to use.

• Landing page /
• Sign in /login
• Request access /request-access
• Research library /research
• Team roster /team
• Fund performance /funds
• Fund leaderboard /funds/leaderboard
• Fund policies /fund-policies
• For recruiters /recruiters
• Guide /guide
• Club notices /notices
• Questions and answers /faq
• Newsletter /subscribe
• Privacy policy /privacy
• Terms of use /terms
• API reference /docs/api
• How a Call record is scored /docs/call-record
• Accessibility statement /accessibility
• Copyright and takedowns /copyright
• How we use AI /ai
• Invite link that is not valid /join/not-a-valid-invite-code

Signed-in pages are checked too, including the dashboard, the trading terminal, the desk, the learning pages and the privacy settings. They are not listed here because a visitor cannot open them to check the claim.

• Landing page (color-contrast)The 'Request access' button on the landing page renders cream text (#e0d2b7) on a sand background (#cdb892). That is a contrast ratio of 1.29 to 1 where WCAG asks for 3 to 1 at this size, so the label on the page's main call to action is hard to read in bright light or with reduced contrast vision. It is one element and no information is lost, since the button is still the only one there, but it should be recoloured, and recolouring it is a decision about the brand palette rather than a fix a test run can make. One node.Recorded 2026-09-09
• API reference (color-contrast)The code samples on the API reference render pale green text (#ecfdf5) on a translucent black panel that resolves to grey (#94928c) over the page behind it, giving 2.95 to 1 where WCAG asks for 4.5 to 1 at this size. Thirteen nodes, all of them example requests. The samples are also given as plain text in the surrounding prose, so nothing is only available in the low-contrast form, but the panel should be given a solid dark background instead of 40 percent black over a light page.Recorded 2026-09-09

If something on this platform blocks you, tell us and we will treat it as a defect, not a request. Members can use Report a problem in the top bar of any signed-in page, which sends us the page you were on. If you are not a member, or cannot reach that, write to a club administrator, or use the access request form and say what happened.

Tell us the page, what you were trying to do, and what you use to browse (a screen reader and its version, keyboard only, a zoom level). We will reply, and we will add anything we cannot fix quickly to the list above rather than leaving it unsaid.

The standard, the page list and the known barriers above are read from the same files the test suite runs on. Nobody types them here, so this page cannot claim coverage the suite does not have.