# Feature DREAM-607 - Improve Accessibility of Calendar and Team Planner Modules

Project: Stream Design System
Status: new
URL: https://community.openproject.org/work_packages/DREAM-607

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | a11y report 2026 |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Accessibility, Modules and project features / Calendar, Modules and project features / Team planner |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | Yes |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a keyboard-only and screen reader user  
**I want to** view, add, remove, and reschedule work packages in calendar-based views using accessible interactions  
**so that** I can plan, manage, and adjust work schedules without relying on mouse-only or visual drag interactions

**Acceptance criteria**

*   Calendar and Team Planner views provide a clear and understandable structure for assistive technologies.
    
*   All work packages displayed in calendar-based views are reachable and operable via keyboard.
    
*   Users can:
    
    *   Navigate between dates, weeks, and calendar regions using the keyboard
        
    *   Select a work package from the calendar
        
    *   Add a work package to the calendar using accessible controls
        
    *   Remove a work package from the calendar
        
    *   Change work package dates using a keyboard-accessible alternative to drag and drop
        
*   Screen readers announce:
    
    *   Date context (day, week, month)
        
    *   Work package titles and relevant metadata (e.g. assigned user, start/end date)
        
    *   Changes to work package dates and scheduling actions
        
*   Drag and drop interactions for rescheduling have a fully accessible keyboard alternative.
    
*   Focus order is logical and predictable across calendar grids, toolbars, and dialogs.
    
*   Visible focus indicators are present for calendar cells, events, and interactive controls.
    
*   Dynamic updates (e.g. work package moved to a new date) are announced via accessible feedback without disrupting focus.
    
*   The Calendar and Team Planner modules pass automated accessibility checks and are manually tested with screen readers and keyboard-only navigation.
    

**Technical notes**

*   Follow WAI-ARIA Authoring Practices for grid- and calendar-based components.
    
*   Represent calendar views using appropriate semantics:
    
    *   Grid roles for date cells
        
    *   Meaningful headings for current view (e.g. “Week of March 4–10”)
        
*   Ensure keyboard interaction patterns support:
    
    *   Arrow keys to move between days or time slots
        
    *   Enter or Space to select events
        
    *   Escape to exit event interaction modes
        
*   For rescheduling:
    
    *   Provide keyboard-based date editing (e.g. date picker or dialog-based adjustment)
        
    *   Announce changes using ARIA live regions (e.g. “Work package moved to April 12”)
        
*   Ensure modals and popovers triggered from the calendar manage focus correctly.
    
*   Avoid relying solely on visual positioning or color to convey meaning.
    
*   Test with NVDA and VoiceOver in both Calendar and Team Planner contexts.
    

<br>
