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.

Sign up for GitHub

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

Jump to bottom

Accessibility review/edits for Desktop, Companion, WebUI #28

Open
3 tasks
lidel opened this issue Jan 17, 2018 · 8 comments
Open
3 tasks

Accessibility review/edits for Desktop, Companion, WebUI #28

lidel opened this issue Jan 17, 2018 · 8 comments
Labels
dif/medium Prior experience is likely helpful effort/weeks Estimated to take multiple weeks help wanted Seeking public contribution on this issue kind/maintenance Work required to avoid breaking changes or harm to project's status quo P2 Medium: Good to have, but can wait until someone steps up status/deferred Conscious decision to pause or backlog topic/design-content Content design, writing, information architecture topic/design-front-end Front-end implementation of UX/UI work topic/design-visual Visual design ONLY, not part of a larger UX effort

Comments

@lidel
Copy link
Member

lidel commented Jan 17, 2018 •
edited by jessicaschilling
Loading

Edit: April 2020

Placeholder issue for reviewing and acting on accessibility overall for Desktop, Companion, and WebUI. Suggest that we dig into this mid-2020 once we've got an additional round of issues for the apps overall knocked out. Please see specific issues that have been closed in favor of this meta-issue:

Original issue specs

This is a placeholder issue for coming up with a strategy to tackle accessibility in our apps and documentation

The Web is fundamentally designed to work for all people, whatever their hardware, software, language, location, or ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability.

Accessibility is essential for developers and organizations that want to create high quality websites and web tools, and not exclude people from using their products and services. #

Tasks

References / Reading Material
@lidel lidel mentioned this issue Jan 18, 2018
Closed
13 tasks
@jnthnvctr jnthnvctr mentioned this issue Jan 20, 2018
Closed
@ipfs ipfs deleted a comment from jnthnvctr Jan 21, 2018
@ipfs ipfs deleted a comment from jnthnvctr Jan 21, 2018
@lidel lidel mentioned this issue Apr 1, 2018
Closed
8 tasks
@olizilla
Copy link
Member

olizilla commented Apr 4, 2018

We want to include automated a11y testing from the start of the web-ui rebuild project. https://github.com/pa11y/pa11y looks worth testing out.

@lidel
Copy link
Member Author

lidel commented Apr 4, 2018

Another engine for automated Web UI testing: https://github.com/dequelabs/axe-core#axe-core

@olizilla
Copy link
Member

react storybook with the a11y info could be good combo https://github.com/storybooks/storybook/tree/master/addons/a11y

@lidel lidel mentioned this issue Jul 13, 2018
Merged
@lidel lidel mentioned this issue Nov 26, 2018
Closed
@ericronne ericronne added design topic/design-content Content design, writing, information architecture topic/design-front-end Front-end implementation of UX/UI work topic/design-visual Visual design ONLY, not part of a larger UX effort and removed design labels May 22, 2019
@jessicaschilling jessicaschilling changed the title Accessibility Accessibility review/edits for Desktop, Companion, WebUI Apr 6, 2020
@jessicaschilling jessicaschilling added dif/medium Prior experience is likely helpful effort/weeks Estimated to take multiple weeks help wanted Seeking public contribution on this issue kind/maintenance Work required to avoid breaking changes or harm to project's status quo P2 Medium: Good to have, but can wait until someone steps up status/deferred Conscious decision to pause or backlog labels Apr 6, 2020
@jessicaschilling
Copy link
Contributor

Linking to (closed) issue ipfs/ipfs-webui#756 for an existing discussion around keyboard navigation and thoughts for next steps.

@jessicaschilling jessicaschilling mentioned this issue Apr 7, 2020
Closed
@jessicaschilling
Copy link
Contributor

Also linking to (closed) issue ipfs/ipfs-webui#1350 for a user-provided specific suggestion for keyboard nav in breadcrumbs.

This was referenced Apr 7, 2020
Closed
Closed
@jessicaschilling jessicaschilling mentioned this issue May 5, 2020
Merged
@jessicaschilling
Copy link
Contributor

Excellent reference on color palette process here: https://stripe.com/blog/accessible-color-systems

@lidel
Copy link
Member Author

lidel commented Jun 2, 2020

ipfs-webui getting a11y treatment and automated checks in ipfs/ipfs-webui#1512 🚀

@jessicaschilling
Copy link
Contributor

ipfs/ipfs-webui#1631 (comment) references contrast issues in Files screen checkbox and browse box button/backkground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dif/medium Prior experience is likely helpful effort/weeks Estimated to take multiple weeks help wanted Seeking public contribution on this issue kind/maintenance Work required to avoid breaking changes or harm to project's status quo P2 Medium: Good to have, but can wait until someone steps up status/deferred Conscious decision to pause or backlog topic/design-content Content design, writing, information architecture topic/design-front-end Front-end implementation of UX/UI work topic/design-visual Visual design ONLY, not part of a larger UX effort
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: UX Design Needed
Milestone
No milestone
Development

No branches or pull requests
4 participants
@olizilla @lidel @jessicaschilling @ericronne