Keyboard and assistive technology
A skip link, visible focus, semantic landmarks and real links keep the principal routes available without pointer gestures or scripted imitation controls.
Accessibility
Bibby Philosophy is built for keyboard and touch, assistive technology, reduced motion, browser zoom, narrow screens and classroom projection. When a resource cannot meet that standard, the route around it should remain clear.
The short version
Core navigation, search, lesson routes and activities use ordinary web links, headings, labels and controls. They should remain understandable without a mouse and should not make colour, hover or animation carry the meaning alone.
The working target is WCAG 2.2 Level AA. This is not a claim that every page and teaching file has passed an independent conformance audit. Automated checks and focused keyboard, reflow and reduced-motion tests are useful; people still find the failures those checks miss.
Built into the route
A skip link, visible focus, semantic landmarks and real links keep the principal routes available without pointer gestures or scripted imitation controls.
Controls are sized for touch and the main reading layouts collapse into one clear column. Text can enlarge without turning an ordinary page into a sideways expedition.
Reduced-motion preferences remove decorative travel and lift. Focus, labels, borders and contrast remain, so stopping an animation does not erase the instruction.
Meaningful images receive text alternatives; decorative images stay silent. Lesson viewers retain titles, context and a direct link to the original resource.
The honest bit
Embedded Gamma and PowerPoint presentations, PDF documents and older classroom files can differ in reading order, keyboard support, text alternatives, contrast and zoom behaviour. Bibby Philosophy can provide a labelled frame and a direct opening route, but it cannot repair every part of a third-party viewer from outside it.
Complex activities and new visual material are checked as they are added, but no automated test can reproduce every screen reader, switch, voice-control setup or cognitive access need. If something blocks the route, that is an access problem—not a test you have failed.
Found a barrier?
You do not need to diagnose the fault or know a WCAG reference. Say which page or resource you were using, what you were trying to do and what happened. If you are comfortable doing so, your browser, device or assistive technology can help reproduce the problem.
You can also ask for a more usable route to a teaching resource. Please do not include pupil names, pupil work or sensitive personal information.