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

[UI/UX] APIM 3 General Accessibility #3935

Closed
tmkasun opened this issue Nov 5, 2018 · 12 comments
Closed

[UI/UX] APIM 3 General Accessibility #3935

tmkasun opened this issue Nov 5, 2018 · 12 comments
Assignees
Labels
Docs/No Impact No impact on the WSO2 Documentation Priority/Normal Type/Accessibility Issues related to UI/UX Web accessibility (also referred to as a11y)
Milestone

Comments

@tmkasun
Copy link
Contributor

tmkasun commented Nov 5, 2018

Description:
We need to consider the accessibility best practices mentioned in

http://www.w3.org/TR/wai-aria-practices/

when developing web apps for APIM products.

Since we are using Material UI for building the React SPA apps, MUI already supports ARIA practices and enforce it in some components.

Further, we need to follow the guidelines given in the React Documentation for adapting the aria practices.

WCAG21 reference

Affected Product Version:

  • APIM 3.x
@tmkasun tmkasun added 4.0.0 DEPRECATED Label; Use Milestone to track version Type/Improvement Type/UX Priority/Normal Docs/No Impact No impact on the WSO2 Documentation labels Nov 5, 2018
@tmkasun tmkasun added this to the Future milestone Nov 5, 2018
@tmkasun tmkasun self-assigned this Nov 5, 2018
@tmkasun
Copy link
Contributor Author

tmkasun commented Jan 31, 2019

We could use react-a11y to identify the missing ARIA practices at the development time.

We could use Google LightHouse command line tool and integrate it with the product build to get the accessibility coverage report or we could use @dakshika's pa11y-full-report tool to get a more descriptive report

@tmkasun
Copy link
Contributor Author

tmkasun commented Jan 31, 2019

For the comparison,

APIM 3.x accessibility report from Google LightHouse

image

accessibility report for latest WUM updated APIM 2.7

image

@tmkasun tmkasun added this to APIM 3.0.0 work backlog in API Manager 3.0 Release via automation May 16, 2019
@tmkasun tmkasun removed the 4.0.0 DEPRECATED Label; Use Milestone to track version label May 16, 2019
@tmkasun tmkasun added Type/Accessibility Issues related to UI/UX Web accessibility (also referred to as a11y) and removed Type/Improvement Type/UX labels Jul 23, 2019
@tmkasun
Copy link
Contributor Author

tmkasun commented Aug 5, 2019

Using react-axe article

@tmkasun
Copy link
Contributor Author

tmkasun commented May 1, 2020

Automating lighthouse report with puppeteer: Sample repo

@erangatl
Copy link

Created the following issues to track
#8390
#8386
#8383
#8380
#8379
#8374
#8370
#8342
#8143
#8129
#8102
#8101
#8086
#7988

@erangatl
Copy link

@tmkasun
Copy link
Contributor Author

tmkasun commented Jun 20, 2020

@erangatl , Above doc, is not publicly accessible? Shall we add it to wikis ?

@erangatl
Copy link

@erangatl , Above doc, is not publicly accessible? Shall we add it to wikis ?

The plan was to update the HIG, shall we update all the design-related stuff in HIG?

@erangatl
Copy link

React A11y library is deprecated.

@erangatl
Copy link

@erangatl
Copy link

Jest axe article
jest-axe

@rmsamitha
Copy link
Member

Closing the issue as this is older than 3 years. Please reopen if the issue is valid still.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs/No Impact No impact on the WSO2 Documentation Priority/Normal Type/Accessibility Issues related to UI/UX Web accessibility (also referred to as a11y)
Projects
No open projects
API Manager 3.0 Release
  
APIM 3.0.0 work backlog
Development

No branches or pull requests

3 participants