Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Support
  • News
  • News Accessibility workshop for OpenProject

Content

News Accessibility workshop for OpenProject

  • More
    • Print
    • Table of contents

Accessibility workshop for OpenProject

Summary

OpenProject aims to be accessible for people of all abilities and disabilities. During a one day workshop the team is coached in important aspects to be considered when designing and developing accessible software.

Accessibility workshop for OpenProject

When an application or a website is correctly designed and developed, all users can equally access the information and functionalities. This is a goal of OpenProject. Already for the first release of OpenProject, major aspects with regard to accessibility have been considered when designing and implementing new functionalities. Now, we set the goals even higher and also want to eliminate remaining barriers within the software and coach the team with regard to future design and development of the software.
Carola Meixner, Consultant User Centered Test, from T-Systems Multimedia Solutions was invited for a one day accessibility workshop with the OpenProject Foundation in Berlin.

What have we learned during this day?

What is digital Accessibility?

There are several definitions of accessibility. In general, one can say that the software should be usable for disabled people without any major difficulties and without the help of others.
The principles of the WCAG 2.0 divide this by:

  • Perceivable (e.g. visual content needs text alternatives)
  • Operable (i.e. key board usage)
  • Understandable
  • Robust (compatibility with a variety of user agents and assisitive technologies)

What to consider when building accessible software?

Software cannot just be accessible at some point and loose the user at one specific functionality. Everything needs to be designed and implemented with regard to accessibility. There shouldn’t be any traps or dead ends.

How can we better understand the user groups?

Users can have a multitude of different disabilities, e.g.

Disabilities in visibility, e.g. for colours, contrasts or eye sight

What to consider for the development?

  • Perceivable
    • enough contrasts
    • big font size
    • scaleable font size
    • avoid use of images of text

Physical disabilities

What to consider for the development?

  • Operable
    • each functionality can be used with the keyboard
    • there is no limitation in time
    • there are no keyboard traps or dead ends
    • assistance for orientation and navigation are available
    • skip groups of elements
    • alternative access points
    • understandable focus order
    • visual keyboard focus
    • visual position in the application
  • Understandable
    • focus and activation are separated
    • change of settings does not lead to context change
    • navigation mechanisms are standardized
    • avoiding errors and error correction is supported

Deaf users

What to consider for the development?

  • Perceivable
    • videos have subtitles
    • sign language for videos and audio
  • Understandable
    • easy language will be used
    • avoid abbreviations

Blind users

What to consider for the development?

  • Perceivable
    • videos have alternative audio or texts
    • visuals have alternative texts
    • colour is not the only point of information
    • relations and information are available without layout
    • meaningful order of content
    • control of audio play
  • Operable
    • structural elements are available
      • headers
      • labels
      • field groups
      • lists
      • table headings, etc.
    • website headers are available
    • the purpose of a link is clear
  • Understandable
    • focus and activating are separated
    • change of settings does not lead to context change
    • avoiding errors and error correction is supported
    • same content is named equally
    • obligatory fields are marked
    • navigation mechanisms are standardized
    • language is marked
    • avoid or explain abbreviations
  • Robust
    • correct syntax
    • name, role, value will be detected by program

What to consider for OpenProject?

For design and development of OpenProject we follow the criteria of the Accessible information technology regulation (BITV 2.0).
Further information: WAI ARIA, the official site of Web Accessibility initiative W3C: http://www.w3.org/TR/wai-aria/complete

Loading...