panweitong 610c72b394 update 4 éve
..
libs 610c72b394 update 4 éve
media 610c72b394 update 4 éve
README.md 610c72b394 update 4 éve
app.component.js 610c72b394 update 4 éve
audio.service.js 610c72b394 update 4 éve
clipboard.service.js 610c72b394 update 4 éve
field-segment.component.js 610c72b394 update 4 éve
messages.js 610c72b394 update 4 éve
notifications.service.js 610c72b394 update 4 éve
toolbox-tree.component.js 610c72b394 update 4 éve
toolbox.component.js 610c72b394 update 4 éve
translate.pipe.js 610c72b394 update 4 éve
tree.service.js 610c72b394 update 4 éve
utils.service.js 610c72b394 update 4 éve
workspace-tree.component.js 610c72b394 update 4 éve
workspace.component.js 610c72b394 update 4 éve

README.md

Accessible Blockly

Google's Blockly is a web-based, visual programming editor that is accessible to blind users.

The code in this directory renders a version of the Blockly toolbox and workspace that is fully keyboard-navigable, and compatible with most screen readers.

In the future, Accessible Blockly may be modified to suit accessibility needs other than visual impairments. Note that deaf users are expected to continue using Blockly over Accessible Blockly.

Using Accessible Blockly in Your Web App

The demo at blockly/demos/accessible covers the absolute minimum required to import Accessible Blockly into your web app. You will need to import the files in the same order as in the demo: utils.service.js will need to be the first Angular file imported.

When the DOMContentLoaded event fires, call ng.platform.browser.bootstrap() on the main component to be loaded. This will usually be blocklyApp.AppView, but if you have another component that wraps it, use that one instead.

Customizing the Toolbar and Audio

The Accessible Blockly workspace comes with a customizable toolbar.

To customize the toolbar, you will need to declare an ACCESSIBLE_GLOBALS object in the global scope that looks like this:

var ACCESSIBLE_GLOBALS = {
  mediaPathPrefix: null,
  toolbarButtonConfig: []
};

The value of mediaPathPrefix should be the location of the accessible/media folder.

The value of 'toolbarButtonConfig' should be a list of objects, each representing buttons on the toolbar. Each of these objects should have four keys:

  • 'text' (the text to display on the button)
  • 'ariaDescribedBy' (the value of the button's aria-describedby attribute)
  • 'onClickNotification' (a notification that the screenreader should read when the button is clicked)
  • 'isHidden' (a function that returns true if the button should not be displayed, and false otherwise)
  • 'action' (the function that gets run when the button is clicked)

Limitations

  • We do not support having multiple Accessible Blockly apps in a single webpage.
  • Accessible Blockly does not support the use of shadow blocks.