[Koha-devel] API use in intranet and OPAC

[dcook at prosentient.com.au]

This certainly makes me wonder.

In Australia, JAWS appears to be the recommended Microsoft Windows screen reader (https://www.visionaustralia.org/information/adaptive-technology/using-technology/computer-screen-readers), and the Wikipedia entry says that Internet Explorer is the recommended browser for JAWS (https://en.wikipedia.org/wiki/JAWS_(screen_reader)). After some searching around, it seems that there are a mix of Accessibility APIs out there. The free screen reader NVDA (https://www.nvaccess.org/download/) is said to work best with Firefox (and it looks like Firefox and Chrome may use the same API protocols so maybe it works well in Chrome too). I haven't noticed anything about specific browser versions at this point. 

I know we use ARIA attributes a bit... mostly through Bootstrap boilerplate I think: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA

After reading https://www.levelaccess.com/how-browsers-interact-with-screen-readers-and-where-aria-fits-in-the-mix/, I think it would be naïve to think that we can make Koha totally accessible without more specialized knowledge and resources. 

Plus, most modern web apps out there that people are interacting with are using Javascript. (Although they might be implemented in a way that is conducive to screen reader use.)

I think a number of Koha developers use Mac, which I think comes with VoiceOver. They could see how well that fares with Koha. I had a classmate from Atlassian build a completely Javascript driven app and he leveraged VoiceOver to read the screen (it was a flashcard app for learning Chinese). So perhaps modern technology is sufficiently advanced at this point not to have to worry too much.

I'm not saying that we should mandate accessibility at this point as that could be a prohibitive mandate for contributions, but it might be interesting to try out some tools to see how we're doing and if there is little things we could do to try to do the best we can for people with accessibility needs. 

David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia

Office: 02 9212 0899
Direct: 02 8005 0595

-----Original Message-----
From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Fridolin SOMERS
Sent: Monday, 14 October 2019 6:24 PM
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] API use in intranet and OPAC

+1 for me.
I'm sure modern web-browsers can provide a good accessiblity even with JS/Ajax.

Le 07/10/2019 à 13:28, Kyle Hall a écrit :
> I think it's pretty practical at this point in time to agree that if 
> we are to continue making a modern web app, we need to require javascript.
> ---
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com ) Meadville Public 
> Library ( http://www.meadvillelibrary.org ) Crawford County Federated 
> Library System ( http://www.ccfls.org )
> 
> 
> On Mon, Oct 7, 2019 at 7:16 AM Marcel de Rooy 
> <M.de.Rooy at rijksmuseum.nl <mailto:M.de.Rooy at rijksmuseum.nl>> wrote:
> 
>     Yeah I guess we reached the point that we just need javascript in OPAC ?
> 
>     ​
> 
> 
>     http://www.rijksmuseum.nl <http://www.rijksmuseum.nl/>
> 
> 
>     ​Museumstraat 1
>     Postbus 74888
>     1070 DN Amsterdam
>     *Rijksmuseum.nl* <http://www.rijksmuseum.nl/>
>     ​
>     ​Nu te zien:
>     ​​*​Louise Bourgeois in de Rijksmuseumtuinen*
>     <https://www.rijksmuseum.nl/nl/louise-bourgeois-in-de-rijksmuseumtuinen>
>     ​*Operatie Nachtwacht* <https://www.rijksmuseum.nl/nl/nachtwacht>
>     ​
>     ​Verwacht:
>     ​*Rembrandt-Velázquez. Nederlandse & Spaanse meesters*
>     <https://www.rijksmuseum.nl/nl/nu-in-het-museum/tentoonstellingen-verwacht>
>     ​
>     ​
>     ​T/m 18 jaar gratis
> 
>     Please think before you print
> 
>     _______________________________________________
>     Koha-devel mailing list
>     Koha-devel at lists.koha-community.org
>     <mailto:Koha-devel at lists.koha-community.org>
>     https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>     website : http://www.koha-community.org/
>     git : http://git.koha-community.org/
>     bugs : http://bugs.koha-community.org/
> 
> 
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/ git : 
> http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
> 

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
BibLibre, France - software and system maintainer
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20191015/62750411/attachment.sig>