Create accountLogin

Recent searches

No recent searches

Search options

Not available on dragonscave.space.
dragonscave.space is one of the many independent Mastodon servers you can use to participate in the fediverse.
A fun, happy little Mastodon/Glitch instance.

Administered by:

Server stats:

243
active users

dragonscave.space: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-alpha.4+glitch

Public

Following today's post on the Microsoft Edge blog, I've started a page of ARIA Notify examples that currently only function in Edge Canary:

jscholes.github.io/ariaNotify.

The blog post:

blogs.windows.com/msedgedev/20

jscholes.github.ioARIA Notify API Tests
#accessibility#screenReader#screenReaders
Public

On one hand, I'm glad that screen readers can do something with this new API out of the box. On the other, long-standing bugs exhibited by using live regions are still present with this new API, such as not interrupting a normal-priority message when a high-priority one comes in.

*

@jscholes That particular interruption bug would be an NVDA bug, right?Not a browser/API issue.

·Quiet public·Enafore
0boosts·0favorites
Quiet public

@fireborn Yes.

Quiet public

@jscholes @fireborn does this new notify API also only still work, like ARIA, when the document is in focus?

Quiet public

@cachondo I think it's using the same machinery under the hood, so I would imagine that is still true. I can add a delayed announcement example to test. @fireborn

Quiet public

@jscholes @fireborn begs the question, when is a notification not a notification?
if I'm waiting for a background process to do something on the web, should my screen reader announce that even if I'm in a different tab or focused on a different app altogether?

Quiet public

@cachondo I think that should probably be your choice. Unfortunately the concept of consent hasn't made it into Windows screen readers yet. @fireborn

ExploreLive feeds
About