accessibility problems #19

Closed
sukiletxe opened this Issue May 12, 2015 · 5 comments

Comments

4 participants
@sukiletxe

Hello,
I'm a screen reader user, and notice some major problems when using Parchment. Basically, the screen reader doesn't speak new text as it reaches the screen. Browsing the Google Code project, I notice there is acommit which experimented with ARIA and Live Regions. I don't know if this was reverted for some reason, but now it doesn't work.
I also noticed that Andrew Plotkin self-hosts his games in Parchment, and in there the screen reader behaves as it should (see any online game at http://eblong.com/zarf/if.html).

@curiousdannii

This comment has been minimized.

Show comment
Hide comment
@curiousdannii

curiousdannii May 12, 2015

Owner

I don't think Andrew has done anything to his version of Parchment, so I don't know why it would be any better. @erkyrath did you add any ARIA stuff to it?

Owner

curiousdannii commented May 12, 2015

I don't think Andrew has done anything to his version of Parchment, so I don't know why it would be any better. @erkyrath did you add any ARIA stuff to it?

@erkyrath

This comment has been minimized.

Show comment
Hide comment
@erkyrath

erkyrath May 13, 2015

No.

My site uses an old release of Parchment. I made a few changes to display better as a scrolling document with a header and footer, and I think to simplify the status line. But I didn't specifically invoke ARIA.

(It's this branch: https://github.com/erkyrath/parchment/tree/zarfsite )

No.

My site uses an old release of Parchment. I made a few changes to display better as a scrolling document with a header and footer, and I think to simplify the status line. But I didn't specifically invoke ARIA.

(It's this branch: https://github.com/erkyrath/parchment/tree/zarfsite )

@sukiletxe

This comment has been minimized.

Show comment
Hide comment
@sukiletxe

sukiletxe May 13, 2015

Then, it should be because of him using an older version (I don't know JS so I can't browse the source). It reads almost everything. I can't remember when it didn't work.

Then, it should be because of him using an older version (I don't know JS so I can't browse the source). It reads almost everything. I can't remember when it didn't work.

@dfabulich

This comment has been minimized.

Show comment
Hide comment
@dfabulich

dfabulich Jul 17, 2016

Since this bug was filed, Zarf actually did an easy fix to Quixe that substantially fixed this bug there. erkyrath/glkote@f938f03

The fix is to add three attributes to the "main" div:

<div
    aria-live="polite"
    aria-atomic="false"
    aria-relevant="additions"
>

Since updating iplayif.com to the latest Quixe, Glulx games now work pretty well in screen readers, but Z-Machine games don't. Adding these attributes to the main element would do the trick.

dfabulich commented Jul 17, 2016

Since this bug was filed, Zarf actually did an easy fix to Quixe that substantially fixed this bug there. erkyrath/glkote@f938f03

The fix is to add three attributes to the "main" div:

<div
    aria-live="polite"
    aria-atomic="false"
    aria-relevant="additions"
>

Since updating iplayif.com to the latest Quixe, Glulx games now work pretty well in screen readers, but Z-Machine games don't. Adding these attributes to the main element would do the trick.

@curiousdannii

This comment has been minimized.

Show comment
Hide comment
Owner

curiousdannii commented Jul 17, 2016

Thanks @dfabulich!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment