ritaccess / blockly Goto Github PK

Something in the XML selection code is breaking, so you cannot add function blocks.

When entering a hotkey mode the screen reader should somehow announce which mode you are in.

When trying to add an else or else if block to an if block while in hotkeymode it shows that these blocks are disabled in the drawout menu.

Be able to jump into the workspace when something else on the page is selected

The color selection outline of blocks needs to be adjustable as well as the background color of the UI to ensure users are able to have full access to the interface.

Update: Dropdown menus can be navigated and read aloud however, the pop-up window is hidden and only the field itself changes. This happens because under the hood, the selection is being changed and not the highlight, when the selection is changed the pop-up menu is auto closed. A potential work around is overwriting the field select method to disable auto closing and instead only close when enter is pressed.

Old:Voiceover uses the arrow keys by default so dropdowns should be controlled with WASD to be consistent.

Sometimes when a block is dragged into the workspace all of the connecting blocks within the block are scattered across the workspace in no particular order. Also some connections are not able to be made on the first try and it may take 3 to 4 tries to get them to connect.

When the toolbox is selected the user is able to press a key corresponding to any of the first letters of the categories. Only works on the first key pressed. This should be disabled.

Applies to all blocks that have a dropdown menu including true/false, while, a = b etc.

There are a lot of functions that can only be used by right clicking that need to be changed.

In interface make a block program and click the run javascript button and a caution appears in the javascript console saying "No workspace specified in workspaceToCode call. Guessing." from line 74 of generator.js.

The onkeyup and onkeydown in keystrokes is being checked numerous times per keypress. When any key is down the keys are check and when the key is up it is check again. If a key is down and held for a second and then is let up the keys would be called 3 times. (This is possibly not an issue but will be left until that is decided.)

Blocks can now be disabled in the toolbox for the matching compatibility and they are read as "connection doesn't match" but you can disable things in the workspace and they would be read the same. We either need to remove the disabling blocks in the workspace functionality or handle it in another way.

Up and down arrows can currently be used to traverse through the menu but we would like to add a way to quickly jump to each category and block

Currently supported browser screen reader combinations.

Drop down menus and text boxes highlight above the actual field.

Right now, navigating and adding new outer containers(statements) and functions(procedures) is very buggy. So far the only solutions found seem to cause other problems. Here is a list of scenarios that should work at the same time but currently only work interchangeably:

• adding any combination of statements/procedures
• navigating up and down block by block (sometimes connected statement blocks are skipped)
• having all blocks vertically separated (if the 5th or 6th block is a procedure, it will end up underneath the last statement for some reason)
• connecting more than 3 blocks

It should probably be called on Add/Modified comments in the workspace and when blocks are moved in the workspace

There is a blank html page in the Quick Reference Guide that needs to be filled in with all of the hot keys and what they do. The idea is to have sections for the different types of hotkeys (navigation, menu access, etc.) this way the user can understand their hotkey options at each toggle-able keyboard state.

The comment widget has incorrect scroll bars. Refer to the Blockly Playground for the correctly working scroll bars on the comment widget. The scroll bar should not show up at until there is overflow and only should have the ability to scroll up and down. This issue has arisen since a change made from the blockly playground to the blockly interface.

Keystrokes will register incorrectly sometimes or not allow for any typing.

Blocky/core/realtime.js
Line 129 - 143

Current Process to add a connection block:

• Press 'e' to enter edit mode
• Use 'a' and 'd' to choose a connection in the block
• Press 'c' to select the connection
• Press 'e' twice (to update the connection?)
• Open the menu and select block
• press 'g' to attach the block

Goal process:

• Press 'e' to enter edit mode
• Use 'a' and 'd' to choose a connection in the block (selection stored and updated at this point)
• Open the menu and select block
• press 'enter' to attach the block

To access the prefix's you use a hashmap with the block's id ex. map[21] returns: A2 you need that and getting the comments from blockArr[index].getElementByTagName('comment');

Hotkeys were set up at the beginning of the summer before we built a lot of functionality. There are functions that don't have buttons mapped out for them and they are a bit messy so they need to be cleaned up and reassigned.

General

• mouse usage will cause random words and symbols to be read

FireFox/Voiceover

• Does not update continuously (This is an error on Firefox's end)

The help key brings up information on each type block in a new webpage. Click on a block and then use the correctly designated hot key. Some of the webpages that are used are github and wikipedia. Neither of these are accessible. Pages that are accessible with short concise information about the blocks would be better to link to.

This refers to blocks such as 'create text with' and 'create list with'

When navigation inside of the menu flyout the blocks are selected when currently on them but the flyout does not automatically scroll. This scrolling needs to be added for when some is navigating through the flyout, so they will be able to see what is currently highlighted and selected on.

New blocks are added to the flyout when variables are created and flyoutArr is not updated with the new blocks so you can't navigate to them.

Find the bottom most block and add the menu block below it that way blocks aren't overlapping

This is a reminder for later when it has been decided what the URL's will be. The blocks each have a website that it is connected to and that URL simply needs to be switched to the correct one.

If blocks are not connected you cannot use the hot keys to select them

For some reason whenever you select a connection and go to the menu you will get errors when trying to navigate between blocks so you have to enter and exit the original block for the scrolling to work so you can select another block.

Blocks currently cannot be connected via keyboard.
We need to figure out how to connect them as they are made as well as inserting them later.

The blocks with the gear icon have mutators which are currently drag and drop. The blocks with mutators are: if, create text with, create list with, function with return, and function no return.

Blocks can now be disabled in the toolbox for the matching compatibility and they are read as "connection doesn't match" but you can disable things in the workspace and they would be read the same. We either need to remove the disabling blocks in the workspace functionality or handle it in another way.

Else blocks should not be compatible with non if blocks.

Is this supposed to be an array? If so, could we try adding inline blocks to this array instead of having them all in childBlocks_ in order to make the F keyboard nav more simple?

Using a letter/ number system to label where you are and being able to quickly jump to that location.