Azure / Azure/api-management-developer-portal
Developer Portal -WCAG Compliance Issues
- Dominant language
- TypeScript
- Stars
- 545
- Forks
- 360
- PR merge metrics
- No merged PRs in 30d
Description
**Attention**: Mike Budzynski
Cognizant uses the Developer Portal as part of our Interoperability solution. As part of our agreement with Horizon BCBS of New Jersey, we performed a WCAG Compliance scan using AXE. The scans found 500+ issues, come critical, which appear to be in areas of the developer portal which must be solved by the organization that controls the source code. The attached XLS includes a complete set of our findings, related to the items that we believe must be solved by your team. Please review these as soon as possible, and get back to me with details regarding:
- Follow Up Questions
- Timeline to review the issues
- Timeline to solve the issues, starting with Critical, then Serious, etc.
thank you,
Matt
[All AXE Findings - Developer Portal - Microsoft - Core Issues.xlsx](https://github.com/Azure/api-management-developer-portal/files/7121717/All.AXE.Findings.-.Developer.Portal.-.Microsoft.-.Core.Issues.xlsx)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the attached “All AXE Findings - Developer Portal - Microsoft - Core Issues.xlsx” and mapping its findings to the Developer Portal. No source files, entry points, or tests are identified in the issue. Done would require resolving and verifying the reported WCAG issues, prioritized from Critical through Serious and lower severities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100