Accessibility

Next Tech is focusing heavily on accessibility over the next few months to ensure that our products can be used by everyone. Below is a summary of our projected timeline for rolling out these changes:

  • By the end of the week: Enabling screen reader for the embedded terminal, as well as some quick wins for buttons, tooltips, etc.
  • By the end of October: Completion of all changes except for code editor (see below). This includes tab navigation, screen reader support for instructions, button labels, and more. These will be released on a rolling basis so your users with disabilities may notice improvements as this progresses.
  • By the end of the year: Screen reader / keyboard navigation support for code editor. We need to switch to entirely different software for this so it’s going to take the longest to get done.

By the end of the year we will be conformant with WAI Level A and Level AA. Note that these updates are focused on our core project interface, but we’ll be continuing to improve the accessibility of our other webpages as we continue to improve our products.

Keep an eye on a section of our Changelog posts dedicated to accessibility over the next few months as we roll out these changes!

We have made the following improvements over the past weeks:

  • Enabled screen reader mode in the terminal

    • Note: As of October 22, 2019 screen reader mode is disabled in Chrome 77 due to a bug that causes the tab to crash.
  • Added type attribute to all buttons as well as aria-labels where needed.

  • Updated many elements to <button> elements where appropriate.

  • Added a number of landmarks (<main>, <nav>, <section>, etc.).

  • Fixed a case where <div> was a direct child of <ul>. :flushed:

  • Made many color contrast adjustments to improve readability.

  • Increased text size and spacing of instructions to improve readability.

  • Enabled zooming on touch devices.

  • Updated instructions to ensure no more than one <h1> per page.

  • Updated instructions to allow for image captions using <figure>, <img>, and <figcaption>.

  • Various other improvements.

In the coming weeks, we will be working on making interactions accessible by keyboard as well as other improvements to keyboard navigation.