edrlab / thorium-reader

A cross platform desktop reading app, based on the Readium Desktop toolkit
https://www.edrlab.org/software/thorium-reader/
BSD 3-Clause "New" or "Revised" License
1.8k stars 154 forks source link

Screen reader support - Go to main content #1948

Closed jimmyfreiding closed 1 year ago

jimmyfreiding commented 1 year ago

When using Jaws 2023 or NVDA 2023. After jumping to the toolbar with CTRL+T and then back into the text with CTRL+F10, the screen reader cursor always lands on the top of the content, not to the place in the content where I was before jumping to the toolbar. Jaws version: 2023 NVDA: version: 2023 Thorium version: 2.2.0.0 Windows version: 10

danielweck commented 1 year ago

Hello, the "underscore" hidden link located at the beginning of the content (i.e. start of the EPUB XHTML document) must be followed in order to reach the "last known user reading location". This hyperlink can be reached with a single tab from the top of the content. However, note that screen readers typically do not interact with the HTML / DOM APIs in the same way as keyboard and/or pointing devices (i.e. mouse, trackpad). For example, screen readers use a separate buffer to access the HTML content which results in the visual scroll / page offset to be out of sync. Conversely, focus events are correctly received by the web browser engine (and therefore Thorium becomes aware of the user's reading location) with keyboard tabbing and / or mouse cursor clicking. In other words, Thorium is generally not aware of the user's current reading location inside the screen reader buffer, unless the screen reader user triggers standard web API events (such as mouse click anywhere in the text, or keyboard tab into focusable HTML elements).

jimmyfreiding commented 1 year ago

Hi!

This is information that I haven't found anywhere in the Thorium Reader documentation. Not very intuitive. The link only works if I press space bar in the content before I jump to the toolbar. Maybe this could be remediated by programmatically pressing the space bar when a "jump" key is activated. For instance, when I press CTRL+T or CTRL+N, before jumpint to the designated area add a keypress event for space bar? Also the link in the content is only read as "link", this is very non-descriptive.

Best regards:

Jimmy Freiding Accessibility Expert

Swedish Agency for Accessible Media Box 51, 201 20 Malmö Besöksadress: Hans Michelsensgatan 2, Malmö Tel: 040 653 27 68| Mobil: 0765 40 27 08 @.**@.> | www.mtm.sehttp://www.mtm.se/ | www.legimus.sehttp://www.legimus.se/ | Facebookhttps://www.facebook.com/tillgangligamedier | Youtubehttp://www.youtube.com/user/MTMedier @.***

Från: Daniel Weck @.> Skickat: den 24 maj 2023 13:31 Till: edrlab/thorium-reader @.> Kopia: Jimmy Freiding @.>; Author @.> Ämne: Re: [edrlab/thorium-reader] Screen reader support - Go to main content (Issue #1948)

Hello, the "underscore" hidden link located at the beginning of the content (i.e. start of the EPUB XHTML document) must be followed in order to reach the "last known user reading location". This hyperlink can be reached with a single tab from the top of the content. However, note that screen readers typically do not interact with the HTML / DOM APIs in the same way as keyboard and/or pointing devices (i.e. mouse, trackpad). For example, screen readers use a separate buffer to access the HTML content which results in the visual scroll / page offset to be out of sync. Conversely, focus events are correctly received by the web browser engine (and therefore Thorium becomes aware of the user's reading location) with keyboard tabbing and / or mouse cursor clicking. In other words, Thorium is generally not aware of the user's current reading location inside the screen reader buffer, unless the screen reader user triggers standard web API events (such as mouse click anywhere in the text, or keyboard tab into focusable HTML elements).

- Reply to this email directly, view it on GitHubhttps://github.com/edrlab/thorium-reader/issues/1948#issuecomment-1560949239, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMECOHVTH7OJJAI37XWH2X3XHXWNPANCNFSM6AAAAAAYNGHFIM. You are receiving this because you authored the thread.Message ID: @.**@.>>


Alla personuppgifter som du lämnar till MTM kommer att behandlas i enlighet med reglerna i Dataskyddsförordningen (EU 2016/679). För mer information se MTMs Personuppgiftspolicyhttps://www.mtm.se/hantering-av-personuppgifter/ All personal data that you provide to MTM through E-mail correspondence will be processed in accordance with the General Data Protection Regulation, GDPR (EU 2016/679). For information on how, please read MTM's Personal Information Policy at Personuppgiftspolicyhttps://mtm.se/english/processing-of-personal-data/

gautierchomel commented 1 year ago

Hello @jimmyfreiding thank you for pointing out missing in the documentation.

The screen reader position problem was actually indicated in the Where Am I section, with an information limited to page location. I added a clear mention in the Reading with a screen reader section.

Now I wonder where to add the tabbing sequence information, would it fit better in the Keyboard shortcuts section, in the Reading with a screen reader section or in the Moving around in a book section.

jimmyfreiding commented 1 year ago

Hi!

Sorry for late answer.

I thinnk it could be good to have the information in several places. I do not always go to the screen reader section when I am searching for the functionality. If the screen reader information is spread out in the sections it is easier to find. For example, if I am searching for information about navigating a book, it would be good if there is a section about navigating with a screen reader. Alternatively a link to the screen reader section.

The documentation is fairly good, so I think it only needs to be tweaked a bit.

Thank you for getting back to me so fast!

Best regards:

Jimmy Freiding Accessibility Expert

Swedish Agency for Accessible Media Box 51, 201 20 Malmö Besöksadress: Hans Michelsensgatan 2, Malmö Tel: 040 653 27 68| Mobil: 0765 40 27 08 @.**@.> | www.mtm.sehttp://www.mtm.se/ | www.legimus.sehttp://www.legimus.se/ | Facebookhttps://www.facebook.com/tillgangligamedier | Youtubehttp://www.youtube.com/user/MTMedier @.***

Från: Gautier Chomel @.> Skickat: den 24 maj 2023 14:45 Till: edrlab/thorium-reader @.> Kopia: Jimmy Freiding @.>; Mention @.> Ämne: Re: [edrlab/thorium-reader] Screen reader support - Go to main content (Issue #1948)

Hello @jimmyfreidinghttps://github.com/jimmyfreiding thank you for pointing out missing in the documentation.

The screen reader position problem was actually indicated in the Where Am I sectionhttps://thorium.edrlab.org/docs/210_reading/212_whereami/, with an information limited to page location. I added a clear mention in the Reading with a screen reader sectionhttps://thorium.edrlab.org/docs/300_accessibility/310_screenreaders/.

Now I wonder where to add the tabbing sequence information, would it fit better in the Keyboard shortcutshttps://thorium.edrlab.org/docs/400_ressources/402_keyboard-shortcuts/ section, in the [Reading with a screen reader section] or in the Moving around in a book sectionhttps://thorium.edrlab.org/docs/210_reading/211_moving/.

- Reply to this email directly, view it on GitHubhttps://github.com/edrlab/thorium-reader/issues/1948#issuecomment-1561073733, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMECOHTUGRFSLIMEDERZGP3XHX7D3ANCNFSM6AAAAAAYNGHFIM. You are receiving this because you were mentioned.Message ID: @.**@.>>


Alla personuppgifter som du lämnar till MTM kommer att behandlas i enlighet med reglerna i Dataskyddsförordningen (EU 2016/679). För mer information se MTMs Personuppgiftspolicyhttps://www.mtm.se/hantering-av-personuppgifter/ All personal data that you provide to MTM through E-mail correspondence will be processed in accordance with the General Data Protection Regulation, GDPR (EU 2016/679). For information on how, please read MTM's Personal Information Policy at Personuppgiftspolicyhttps://mtm.se/english/processing-of-personal-data/