The close button for the modal dialog was marked up as a paragraph,
containing a graphical text character, inside two div elements, with an
associated click event. This made the button unusable for keyboard
users.

Replaced <divs> with a link element (<a role="button"), adapted the CSS
accordingly, and updated the existing <a> modal close buttons.

Added a 'aria-hidden="true"' attribute to the modal initially, then
toggle the value of that attribute to "false" when the modal is shown.
Also remove the attribute when the modal is closed, whether it's through
a click on the close button or on the overlay.

> To make this change explicit to assistive technology, focus should be
> moved programmatically to this div after it has been made visible. To
> allow the div to be focused via scripting (without adding it to the
> regular focus order that keyboard users cycle through), a tabindex=”-1”
> should be added.

> In addition, the invalid fields should be given a an
> aria-invalid="true" attribute.

Also adding the email description to the login page and applying the
same aria attribute to the correspondin input on that page.

From LMS-602:

> There is additional explanatory text, marked up in a span element after
> the email input. The input elements should be explicitly associated with
> this additional text using the aria-describedby attribute. This will
> require an ID to be assigned to the span element.

also even when we have a marketing site, we still need a course image fo...

Staff information about duplicate ORA submissions

Release

fix edit tab bug and add unit test

Add datadog tracking for bulk email

Remove Studio JS template loader

refactoring of platform to xblock 0.3 w/ refactoring of inheritance in the platform to a consistent representation.

Include mixins in advanced component class loading and preview modules

Fix nopathtoitem error

update mitxmako lookup / fixes FOR-150

Updated static-pages test to add retry logic

Dependency warning message on requirements files

Provide CAS authentication integration

update mitxmako lookup / fixes FOR-150

Adding debugging messages for Video player.

Valera/video single yt xhr jasmine test

Removed extra check for console.log() existance. Modified error
messages. Formatted entire file to fit in 80 lines or less.

Formatting files so that they fit under 80 lines. Adding debug info for
what type of YouTube video player is being used. Also comment on whether
playbackRates is available for HTML5 mode.

Changed back Anton's original function _checkPlaybackRates(). Now logging for
this function's result is done only on error (in the function that is invoking)
it).

For now outputting main flow of loading YouTube or non-YouTube videos.

Forgot to include local variables in var statement.