Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential accessibility issues to fix #863

Open
29 tasks
mialondon opened this issue Jun 17, 2020 · 3 comments
Open
29 tasks

Potential accessibility issues to fix #863

mialondon opened this issue Jun 17, 2020 · 3 comments

Comments

@mialondon
Copy link
Member

mialondon commented Jun 17, 2020

From https://web.dev/measure/ for https://www.libcrowds.com/collection/playbills

  • High Accessibility [role] values are not valid
  • High Accessibility Buttons do not have an accessible name
  • High Accessibility Image elements do not have [alt] attributes
  • Low Accessibility Heading elements are not in a sequentially-descending order
  • Low Accessibility Links do not have a discernible name
  • Low Accessibility Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

For https://www.libcrowds.com/collection/playbills/projects

  • High Accessibility [role] values are not valid
  • High Accessibility Image elements do not have [alt] attributes
  • Low Accessibility Heading elements are not in a sequentially-descending order
  • Low Accessibility Links do not have a discernible name
  • Low Accessibility Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

For an example task page https://www.libcrowds.com/collection/playbills/projects/260/iiif-annotation

  • High Accessibility [role] values are not valid
  • Low Accessibility Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

From https://web.dev/measure/ for https://www.libcrowds.com/ - will apply to all LibCrowds projects

  • High Performance Properly size images
  • High Performance Defer offscreen images
  • High Performance Remove unused JavaScript
  • High Performance Serve images in next-gen formats
  • High Performance Reduce initial server response time
  • High Accessibility Image elements do not have [alt] attributes
  • Medium Performance Avoid serving legacy JavaScript to modern browsers
  • Medium Best Practices Does not use HTTPS [actually the site says it is https?]
  • Medium Best Practices Links to cross-origin destinations are unsafe
  • Medium Best Practices Includes front-end JavaScript libraries with known security vulnerabilities
  • Medium Best Practices Missing source maps for large first-party JavaScript
  • Medium SEO Links do not have descriptive text
  • Medium SEO Image elements do not have [alt] attributes
  • Low Accessibility Heading elements are not in a sequentially-descending order
  • Low Accessibility Links do not have a discernible name
  • Low Accessibility Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
@mialondon
Copy link
Member Author

Looking at the front page, 'Crowdsourcing projects from the British Library' needs to be H1.

Is https://www.digitalocean.com/community/tutorials/vuejs-vuejs-accessible-announcements vue-announcer a useful option?

@mialondon
Copy link
Member Author

Notes for outsourced developer with context on the site's purpose and identified issues for core and task pages: https://docs.google.com/document/d/1NzZfeof4dl0PhqksHYxougZ4OCGu-vwwJUJWwqiRpIs/edit?usp=sharing

@mialondon
Copy link
Member Author

Updates after UAT at #884

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

No branches or pull requests

1 participant