1. Our accessibility goal
Bailiwick is actively working toward the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as its product target. We do not yet claim full WCAG 2.2 AA conformance because the complete product, every responsive state, every assistive-technology combination, and all newly authored game content have not completed independent human evaluation.
Accessibility is not a separate easy mode. When an activity uses audio, motion, dragging, speaking, or a time challenge, Bailiwick aims to offer another route that measures the same learning skill without requiring the inaccessible interaction.
2. Current supports and ongoing work
Supports already built into the product
- semantic headings, labels, landmarks, status messages, and named controls for screen readers;
- keyboard-operable answer choices, conversation controls, game actions, and visible focus treatment;
- responsive layouts for desktop and narrow screens, with text that can reflow;
- reduced-motion behavior that removes or shortens nonessential Bot and interface animation;
- forced-colors support on dedicated games and core learning controls;
- text transcripts or text-first alternatives for published conversation and listening content;
- audio replay, explicit skip controls, and untimed routes where speed is not the learning goal; and
- text choices when local speech recognition or temporary voice rehearsal is unavailable or not consented to.
Known limitations
Bailiwick is still completing human accessibility review of its eight practice games, new Bot animations, authored audio, Story Studio, Conversation Practice, and crossword packs. Some third-party browser speech and model-download experiences vary by device. Some older or experimental pages may not yet meet the same standard as the core learner path.
Automated checks are useful but cannot prove that a full learning experience works with a screen reader, switch input, zoom, voice control, reduced motion, or a learner's cognitive and language needs. Those scenarios require human testing, including testing by people with disabilities.
Standards and school use
WCAG 2.2 is our forward-looking target. Public schools and other public entities may have specific obligations under the ADA and may need to evaluate Bailiwick, school-added content, linked material, and local assistive-technology support under the rules that apply to them. A public statement is not a substitute for that evaluation or for an appropriate accommodation.
3. Getting another route
If a feature blocks access, a learner should not be penalized for using a text, replay, skip, keyboard, reduced-motion, or other equivalent route. Families and educators can also pause a feature such as voice processing and continue with available text-based learning.
When reporting a barrier, it helps to include:
- the page address and name of the lesson or game;
- what you were trying to do and what happened;
- the device, browser, and assistive technology, if you are comfortable sharing them; and
- the format or alternative that would help.
Please do not include a learner's password, PIN, diagnosis, or unnecessary identifying information.
4. Accessibility feedback
Email accessibility feedback or a request for an alternative to beginnerbookworms@gmail.com. We will review the barrier and respond with available next steps. Urgent school accommodations should also be raised through the learner's school process.
Read the current W3C Web Content Accessibility Guidelines 2.2 that inform this target.