-
Notifications
You must be signed in to change notification settings - Fork 0
Weekly Meeting 7
Date: 22.04.2026 Time: 20:00 – 21:00
- Ali Akkaya ✅
- Bora Aydemir ✅
- Ömer Belemir Delier ✅
- Arif Evren ✅
- Ulaş Sertan Kemeç ✅
- Ekin Kılıç ✅
- Baran Önder ✅
- Review of accessibility-related technical standards and their applicability to the project.
- Discussion on how identified standards will be integrated into the system.
- Clarification of pending tasks and finalization of the work distribution.
The team conducted a detailed review of relevant accessibility technical standards, including WCAG guidelines and platform-specific accessibility requirements for mobile and web interfaces. Each standard was examined in the context of the project's current implementation to assess which ones are directly applicable. The team discussed how these standards should inform design decisions, component behavior, and reporting categories within the system.
Following the standards review, the team discussed concrete ways to incorporate the identified requirements into the existing codebase. This included considerations for screen reader compatibility, color contrast, touch target sizing, and obstacle categorization aligned with accessibility terminology. The team agreed on a consistent approach to applying these standards across both the frontend and backend layers.
Pending tasks were revisited and responsibilities were clearly assigned to each team member based on the discussed standards and implementation priorities. The team ensured that every open item has a clear owner and that dependencies are accounted for in the timeline.
- Ali Akkaya: Implement frontend components in accordance with the identified accessibility standards.
- Bora Aydemir: Ensure backend data models and API responses align with accessibility-related requirements.
- Ömer Belemir Delier: Document the technical standards reviewed and maintain the accessibility requirements reference for the team.
- Arif Evren: Apply accessibility standards to the routing and obstacle reporting flows.
- Ulaş Sertan Kemeç: Update GitHub issues to reflect the newly clarified task assignments.
- Ekin Kılıç: Review UI components for compliance with the discussed accessibility guidelines.
- Baran Önder: Cross-check the existing implementation against the accessibility standards and report inconsistencies.
- Elicitation Questions
- Requirements
- Implementation Plan
- Test Plan & Coverage
- MVP Demo Plan
- Communication Plan
- Responsibility Assignment Matrix
- Use of Standards
- Project Retrospective
- Final Demo Plan
- Final Milestone Deliverables
- Report 1 - Requirements Elicitation & Repository Setup
- Report 2 - SRS Through Scenarios & Mock-ups
- Report 3 - From Scenarios to Use Case Diagrams
- Report 4 - Class Diagrams & Use-case Diagrams
- Report 5 - Git Workflow, Stub Application, and Planning
- Report 6 - Planning for Implementations & Tests
- Report 7 - Finalizing Plan for MVP Milestone Demo
- Report 8 - Standards & Plan Revision
- Report 9 - Requirements Review & Acceptance Testing
- Report 10 - Finalizing Plan for Final Milestone Demo
- 2026-02-18: Weekly Meeting #1
- 2026-02-18: Customer Meeting #1
- 2026-02-25: Stakeholder Meeting
- 2026-02-25: Weekly Meeting #2
- 2026-03-04: Weekly Meeting #3
- 2026-03-11: Weekly Meeting #4
- 2026-04-01: Weekly Meeting #5
- 2026-04-15: Weekly Meeting #6
- 2026-04-22: Weekly Meeting #7
- 2026-04-29: Weekly Meeting #8
- 2026-05-06: Weekly Meeting #9