Skip to main content

Limitations of the Silktide Toolbar screen reader simulator

Current limitations of the Silktide Toolbar screen reader simulator and what it does not yet support.

Daniel Towers avatar
Written by Daniel Towers
Updated this week

We are committed to continually improving the Silktide Toolbar screen reader to make it as comprehensive as possible. That said, there are some things it is currently unable to handle.

Below is a clear list of the current limitations we are actively working to address.


Focus handling requirements

Our screen reader relies on websites using focus correctly for elements such as:

  • <dialog>

  • Custom select boxes

Incorrect implementation of focus for these elements can lead to issues.


Native <select> elements

Due to JavaScript restrictions, we cannot interact with native <select> elements.

Handling native <select> elements with long lists of options may not be optimal.


CSS :hover interactions

We cannot currently simulate hovering over elements that are controlled purely by CSS :hover.


aria-live, aria-selected, and aria-current

We do not currently:

  • Announce alerts or form validation errors announced using aria-live

  • Announce aria-selected

  • Announce aria-current


<details>, <summary>, and disclosure widgets

Some HTML elements such as:

  • <details>

  • <summary>

  • Other disclosure widgets

may not be fully supported unless they manage focus correctly.


Tables and grid navigation

Our software may not handle tables perfectly, including:

  • Reading column headers

  • Handling scope

Navigation within tables and grids is not optimal. We currently only handle moving left and right.


Supported navigation shortcuts

Our software focuses on the following navigation shortcuts:

  • H for headings

  • D for landmarks

  • F for form controls

  • K for links

We may not cover all screen reader shortcuts.


Specific ARIA roles

Some specific ARIA roles may not be fully supported, including:

  • tree

  • window

  • application


We are actively working to improve coverage in these areas. If you have feedback or encounter issues related to any of the above, please contact our support team.

Did this answer your question?