Skip to content

accessibility.md

Latest commit

 

History

History
19 lines (13 loc) · 2.33 KB

accessibility.md

File metadata and controls

19 lines (13 loc) · 2.33 KB
Raw

Accessibility and access options

The course supports reading, predicting, running, and explaining small examples. These options are not a claim of complete WCAG conformance or a substitute for testing with disabled learners.

  • Use Tab and Shift+Tab to move through links and controls. Enter activates links/buttons; Space activates buttons and opens worked-example disclosures. Use the skip link to reach the main content.
  • Change light/dark mode in the header. Browser zoom and phone layouts are supported. Long code lines scroll horizontally within their code area.
  • Explorer steps do not autoplay. Next step, Previous step, and Restart steps control the pace. Status text names the next line; code, variables, and output are also available as text. Highlighting is not the only cue.
  • The initial homepage code widget reveals prepared output. Only the labelled lesson explorers execute editable Python. Use Binder, Colab, or local Jupyter for the complete notebooks.
  • Python downloads on demand for explorers. If it cannot load, or if you need input prompts, use Binder, Colab, or local Jupyter. No new assignment is required to use an explorer.
  • With JavaScript unavailable, the original reading examples and notebook launch/download links remain usable. Worked-example disclosures use native HTML controls.
  • Completion progress stays in this browser's local storage. It is not a grade or proof of mastery, does not sync between devices, and is removed if browser data is cleared. Python edits in explorers are not saved.

Report a barrier

Tell your instructor which lesson, device/browser, and step caused difficulty. You may also open a repository issue. Avoid posting student records, credentials, or other personal information. A description of the task is enough; a medical diagnosis is not needed.

Verification scope

Maintainer checks cover image text alternatives, content heading structure, visible keyboard focus, keyboard interaction, reduced-motion preferences, and representative 320-pixel layouts. Automated checks and developer browser testing cannot establish full screen-reader usability; assistive-technology and student feedback remain part of evaluation.