Computing - Inclusion Strategies

Why Computing is Empowering for Pupils with SEND

Computing offers unique opportunities for inclusion. Technology can reduce barriers, provide alternative ways of working, and open up learning that might otherwise be inaccessible. For many pupils with SEND, computing is an area where they can excel.

However, computing lessons can also present challenges: abstract concepts, fast-paced screen work, fine motor demands for typing, and cognitive load from multiple simultaneous processes. The strategies below ensure all pupils can access and succeed in computing.

Visual Programming with Scratch

Block-based programming languages like Scratch are essential tools for inclusive computing. They remove the barrier of syntax errors while teaching genuine computational thinking.

Why Scratch works for inclusion

• No typing required; drag-and-drop blocks reduce fine motor demands
• Visual colour-coding helps pupils identify different types of commands
• Immediate visual feedback shows what the code does
• Impossible to make syntax errors
• Supports creativity and open-ended problem-solving
• Pupils can start simple and add complexity at their own pace

Supporting pupils using Scratch

• Provide visual guides showing where to find specific block types
• Use worked examples that pupils can remix and modify
• Break projects into small, achievable steps
• Celebrate debugging as a skill: "Finding mistakes is part of being a programmer"
• Allow pair programming with clear role definitions
• Provide block "menus" showing the blocks needed for each step of a task

Built-In Accessibility Features

Modern operating systems include powerful accessibility tools. Teaching pupils to use these features supports independence and demonstrates that technology should work for everyone.

Screen readers and magnification

• Windows Narrator or macOS VoiceOver: Read text aloud for pupils with visual impairment or reading difficulties
• Magnifier tools: Enlarge portions of the screen
• High contrast modes: Improve visibility for pupils with visual processing difficulties
• Colour filters: Support pupils with colour blindness

Text-to-speech and speech-to-text

• Immersive Reader (Microsoft): Simplifies text, adjusts spacing, reads aloud
• Dictation tools: Allow pupils to speak instead of type
• Read Aloud functions: Available in most browsers and applications

Motor and input support

• Sticky Keys: Press modifier keys (Shift, Ctrl) one at a time instead of simultaneously
• Mouse Keys: Control mouse pointer using keyboard
• On-screen keyboards: Alternative to physical typing
• Voice control: Navigate and control devices using voice commands

Teaching approach: Introduce accessibility features to all pupils as part of the computing curriculum, not just as "special" accommodations. This normalises their use and ensures pupils know they exist.

Reducing Cognitive Load

Computing lessons involve multiple processes simultaneously: reading instructions, planning steps, using the interface, typing or clicking, and checking output. Reduce cognitive load by simplifying one or more of these elements.

Provide visual step-by-step guides

• Use screenshots with numbered steps
• Annotate images with arrows and highlights
• Keep instructions visible while pupils work (printed or on a second screen)
• Use video tutorials pupils can pause and replay
• Create flowcharts showing the sequence of a task

Pre-built templates and starter files

• Provide partially completed projects pupils can build on
• Offer templates for common tasks (e.g., presentation layouts, spreadsheet structures)
• Give pupils working code they can modify rather than starting from blank screens
• Reduce setup time so pupils spend more time on the core learning

Break tasks into small steps

• Use checklists pupils can tick off as they progress
• Introduce one new concept or skill at a time
• Build complexity gradually across a sequence of lessons
• Allow pupils to consolidate each step before moving to the next

Alternative Input Methods

Not all pupils can type efficiently or use a standard mouse. Alternative input devices ensure computing is accessible to everyone.

Keyboard alternatives

• Large-print keyboards: Easier to see for pupils with visual impairment
• Colour-coded keyboards: Support pupils learning keyboard layout
• On-screen keyboards: Used with touchscreen, mouse, or eye-gaze technology
• Voice typing: Speak instead of type (built into most devices)

Mouse alternatives

• Trackball mice: Stationary; only the ball moves, reducing motor demands
• Touchscreens: Direct manipulation of on-screen objects
• Joysticks or gaming controllers: Easier to grip for some pupils
• Eye-gaze technology: Control devices by looking at the screen

Practical consideration: Ensure alternative input devices are available and normalised in your computing space so pupils can try different options without feeling singled out.

Unplugged Computing Activities

Not all computing teaching requires screens. Unplugged activities teach computational thinking without the access barriers of digital devices.

Why unplugged activities matter

• Remove screen-based barriers (fine motor, visual processing, reading)
• Make abstract concepts concrete and physical
• Allow movement and collaboration
• Accessible to pupils who find screen time overwhelming
• Demonstrate that computing is about thinking, not just technology

Examples of unplugged activities

• Algorithms: Write instructions for making a sandwich; follow each other's instructions literally to highlight the need for precision
• Debugging: Provide a set of instructions with deliberate errors; pupils identify and fix them
• Sequencing: Use picture cards to order steps in a process
• Binary: Use physical objects (on/off, black/white) to represent binary numbers
• Networks: Pupils stand in a circle and pass messages to model how networks transmit data
• Decomposition: Break a large task (planning a party) into smaller sub-tasks

Teaching Online Safety Inclusively

Online safety is essential for all pupils, but some pupils with SEND are particularly vulnerable. Make online safety teaching concrete, repeated, and accessible.

Make safety rules concrete

• Use specific examples, not abstract warnings: "Never share your address online" is clearer than "Be careful with personal information"
• Create visual reminders (posters, symbols) showing safe and unsafe online behaviours
• Role-play scenarios so pupils practise safe responses
• Use social stories to teach safe behaviour in different online contexts

Teach critical evaluation

Some pupils with SEND may struggle to evaluate whether online information is trustworthy:

• Teach specific questions: "Who wrote this? How do they know? Could this be an advert?"
• Use comparison activities: show two websites and discuss which is more reliable
• Explicitly teach how to identify adverts, sponsored content, and biased sources
• Provide checklists for evaluating websites

Revisit safety teaching regularly

• Online safety should be revisited throughout the year, not taught once
• Link safety teaching to new apps and platforms as they arise
• Involve parents and carers in reinforcing messages at home

Collaborative Computing

Pair programming and group work can support pupils with SEND, but only if roles are clearly defined and collaboration is structured.

Pair programming roles

• Driver: Controls the keyboard and mouse
• Navigator: Reads instructions, suggests next steps, checks for errors
• Swap roles regularly (every 5-10 minutes) so both pupils develop all skills
• Make role cards or badges so pupils know who is doing what

Supporting effective collaboration

• Teach collaboration skills explicitly: listening, turn-taking, giving and receiving feedback
• Model positive collaborative language: "What if we try...", "I think there might be a mistake here..."
• Provide sentence starters for peer support
• Match pairs thoughtfully; consider complementary skills and personalities
• Allow some pupils to work independently if collaboration is overwhelming

Celebrating Debugging and Problem-Solving

Pupils with SEND often fear making mistakes. In computing, errors are inevitable and valuable. Reframe mistakes as learning opportunities.

• Model your own debugging process: talk through how you identify and fix errors
• Celebrate finding mistakes: "Well done for spotting that bug!"
• Display a "Bug of the Week" showing an interesting error and how it was solved
• Teach systematic debugging strategies: check one thing at a time, compare working and non-working code, simplify and test
• Provide debugging checklists: "Is the spelling correct? Are the blocks in the right order?"
• Remind pupils that professional programmers spend most of their time debugging

Practical Classroom Organisation

Consistent routines

• Same login process every lesson
• Predictable structure: starter, main task, plenary
• Clear signals for screen-down time (visual cue, sound, timer)
• Established procedures for getting help without disrupting others

Reducing distractions

• Close unnecessary browser tabs and applications before starting tasks
• Use focus modes or distraction-free interfaces where available
• Provide workstations facing away from high-traffic areas for pupils easily distracted
• Allow use of headphones for pupils who find computer rooms noisy

Managing screen time

• Build in regular screen breaks (every 15-20 minutes for younger pupils)
• Use unplugged activities to break up screen-based lessons
• Be aware of pupils for whom extended screen time causes headaches or fatigue