make gigadb.org accessible to all

User story

As a website user
I want to be able to access all contents despite any personal differences I may have in my senses. So that everyone can access gigadb.org content

Acceptance criteria

1319

Given a user visits gigadb.org When they choose the option to view page in dyslexic font Then text on page is displayed in dyslexie font
1320

Given a user visits gigadb.org When they click the audio option Then the page content is read to the user audibly
1322

Given a user visits gigadb.org When they choose the red-green button then the website is displayed in colours best suited to Red-Green colour blind suffers According to this website: https://equalizedigital.com/website-accessibility-color-blind/ Its very difficult to do this, so actually maybe this is its own ticket to be part of the CMS to consider the colour palet we use.

Additional Info

Section 2.3 from the COAR survey: 2.3 The repository supports access to its documentation and metadata for persons with disabilities (Essential) "Documentation" refers to the information about the repository that is provided by repository managers.

We understand that it might be hard to fulfill this "Essential" characteristic now, but if you've started accessibility discussions in your repository team - e.g. on how to apply The Web Content Accessibility Guidelines by the Web Accessibility Initiative of the World Wide Web Consortium - you could answer "Yes" to this question. The Web Content Accessibility Guidelines by the Web Accessibility Initiative of the World Wide Web Consortium: https://www.w3.org/TR/WCAG22/#later-versions-of-accessibility-guidelines

See examples: University of St Andrews: https://research-repository.st-andrews.ac.uk/page/accessibility University of Vienna: https://phaidra.univie.ac.at/detail/o:1594526

See article: Waugh, Laura; Lyon, Colleen; Shelton, Abigail; Park, Kristi; Hicks, William; and Lindsey, Nerissa, "Accessibility in Institutional Repositories" (2020). Copyright, Fair Use, Scholarly Communication, etc.. 165. https://digitalcommons.unl.edu/scholcom/165

Web accessibility standards, guidelines and tools:

Product Backlog Item Ready Checklist

[ ] Business value is clearly articulated
[ ] Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
[ ] Dependencies are identified and no external dependencies would block this item from being completed
[ ] At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
[ ] This item is estimated and small enough to comfortably be completed in one sprint
[ ] Acceptance criteria are clear and testable
[ ] Performance criteria, if any, are defined and testable
[ ] The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

[ ] Item(s) in increment pass all Acceptance Criteria
[ ] Code is refactored to best practices and coding standards
[ ] Documentation is updated as needed
[ ] Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
[ ] No deviation from the team technology stack and software architecture has been introduced
[ ] The product is in a releasable state (i.e. the increment has not broken anything)

gigascience / gigadb-website