Accessibility statement

The target for this site is WCAG 2.2 level AA. This page says what has actually been done against that target and what has not, because an accessibility statement that only lists intentions is not much use to somebody trying to read a page.

What is in place

• Contrast. Body and small text is measured, not assumed. The green used for links and labels is a deeper shade than the green used for borders and icons, specifically so that text clears 4.5:1 — links measure 6.58:1 on white and secondary text 7.1:1 or better.
• Links are never colour alone. Every green link and card call-to-action carries an underline as well as a colour, so it is identifiable without seeing the colour.
• Focus is always visible. outline: none is not used anywhere. The focus ring uses an offset rather than a radius, so focusing something never changes its size or shifts the layout.
• Targets are at least 44px. Navigation links, filter buttons, search fields, footer links and the source chips all meet that minimum, including the small inline ones, which are padded out rather than left as a 16px hit area.
• Keyboard use. There is a skip link to the main content. The menus and the video dialog are operable from the keyboard and return focus sensibly when they close; revealing more directory results moves focus to the first new card rather than dropping it on the page body.
• Live regions exist before they change. Result counts are announced through a region that is already in the page, because aria-live added to a newly rendered element announces nothing.
• Decoration is hidden. Icons, separators and the arrow glyphs are marked aria-hidden, and every outbound link (directory cards, video player, navigation) carries hidden text that says "(opens in a new tab)" so screen readers announce the behaviour.
• Nothing depends on JavaScript to be readable. The pages are static HTML; the interactive parts add filtering and search on top of content that is already there.

Known limitations

Being straight about the gaps:

• No dark mode. The site declares itself light-only. This is deliberate rather than an oversight, but if you rely on a dark or high-contrast theme, your operating system's or browser's forced-colours mode is doing that work rather than the site.
• No screen reader testing. The primary interactive components — homepage navigation, directory grid, video dialog, and function page tables — were reviewed at the code level in July 2026. One finding (missing new-tab warning on video player links) was fixed. There has been no third-party audit and no systematic testing with an actual screen reader, magnifier, or voice control. Absence of a reported problem is not evidence there isn't one.
• Embedded video is YouTube's player. Captions, transcripts and player accessibility are controlled by YouTube and by whoever uploaded the video, not by us. Some videos in the directory have no captions, and we cannot add them.
• Linked sites are not ours. A large part of this site points at other people's resources. We cannot make those accessible, and we do not currently record which of them are.
• Wide tables scroll. Some reference tables scroll horizontally on a narrow screen rather than reflowing.

Tell us about a barrier

If something here is hard or impossible to use, please say so: support@excelback.com. It helps to include the page URL, what you were trying to do, and what you use to browse — though a one-line "this page is unreadable" is genuinely better than nothing and will be looked at.

If you need something on this site in a different form, ask. The content is plain HTML and can be sent as plain text.

This statement

Prepared on the date shown at the top of this page, based on self-assessment of the current build rather than an external review. It will be updated when either the site or the list of known limitations changes.

Questions about this page, or anything else on this site: support@excelback.com. It is the only contact route the site has — there is no form here that submits to a server.