Policy
Accessibility Statement
This site is built so that it can be used by people who navigate with a keyboard, who use a screen reader, who need large text, or who are on a small or old device.
What we aim for
RCF English aims to follow the Web Content Accessibility Guidelines (WCAG) 2.2, level AA as a standard of good practice. This is a statement of intent and of the work actually done; it is not a certificate, and no formal audit has been carried out.
What has been built in
- Semantic HTML — real headings, lists, tables and landmarks, so assistive technology can describe the page.
- A skip-to-content link at the top of every page, so keyboard users can pass the menu.
- Full keyboard operation — every menu, activity and form can be used without a mouse. Menus open with Enter or Space and with the Down arrow, close with Escape, and return focus to the button that opened them.
- A visible focus outline on every interactive element. It is never removed.
- Colour contrast that meets the AA ratio for body text, headings and interface text.
- No information carried by colour alone. A right or wrong answer is shown by a word as well as by a colour.
- Labels on every form field, and errors described in words beside the field they belong to.
- Reduced-motion support — if your system asks for less motion, animation and smooth scrolling are switched off.
- Large touch targets — buttons and links are at least 44 pixels high.
- Alternative text on images that carry meaning; decorative graphics are hidden from screen readers.
- Tables that become cards on narrow screens, so the class timetable is readable on a telephone.
- No horizontal scrolling at any screen width from 320 pixels upwards.
What has actually been tested
Being honest about this matters more than a long list. The following has been checked directly:
- Keyboard operation of the menus, the mobile drawer, the search page, the filters and all ten interactive activities.
- Layout at 320, 375, 768, 1024 and large desktop widths, with no horizontal scrolling.
- Heading order on every page.
- Colour contrast of the text and interface colours against their backgrounds.
- That every internal link on the site points at a page that exists — this is checked automatically every time the site is rebuilt.
Known limitations
- The interactive activities need JavaScript. Where JavaScript is unavailable, a message explains this and points to the written lessons instead.
- Search and the resource filters also need JavaScript. Without it, the menus and the How to Use This Site page list every section.
- The site has not been tested with every combination of screen reader and browser. If you meet a barrier, please tell us — that is more useful than any claim on this page.
Report an accessibility barrier
How this form works
This website has no server, so nothing is sent from here. The form writes your message and opens it in your own email program, where you press send yourself.