Today, we have a sound awareness element to notify that someone is contributing, but, we don't have a visual element for that. So, we need to create a visual awareness element to notify that a colleague is contributing with the text.
There is a problem to use Web Component (.shadowRoot) in the Firefox and Safari. In the Firefox 59/60 we can enable custom elements and shadow DOM, so, set the dom.webcomponents.enabled and dom.webcomponents.customelements.enabled preferences to true, please, see for more information.
We need to check the below line in js/WebSocketApp.js do fix the issue var soundChat = cooperationEditor.shadowRoot.querySelector("sound-chat");
At the moment that we are navigating the historical, through the arrows, I believe that we could add (right corner) the number of the contribution 1, 2, 3 .. and so on.
We will implement a pre visualization of the contribution in the editor area. After 60 characters typed, the system notify the the blind users that a colleague is contributing with the text. We will use this event to also update the editor area, so, all users will have the opportunity to prepare theirselves to the next round.
When we enter in the editor area we normally use /editor/ + hash (/editor/faafc315b95987fc2b071bcd8f698b81). However, when we press the configuration link we loses the hash, so, if the user refreshes the page, the system show "Not found".
We need to keep the hash in with the configuration URL /configuration/ + hash, thus, when the users refresh the page, we can return to the right production/activity.
The icons in participating card must reflect the status of the users related with the produced text: waiting to contribute (icons:create), contributing (icons:build) and watching (icons:visibility).
We need to create a panel do inform the users the sound effects and sound position that they are using. So, in the first moment we will show this information yo the user in the sound configuration tab.
1 - Press the history button (the A symbol)
2 - Press the contribution button (the pencil)
3 - Save the new contribution, saving a history in a wrong way
So the history button can not be enabled if the user is writing a contribution. When the user press the contribution button (the pencil) the system must return to edit mode and disable the history button/arrows until the user press the save new contribution button.