Accessibility optimization for main navigation section in customer portal
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- perl
- Domain
- accessibility, frontend
Research direction
Search the customer-portal templates for the div with id "oooNavigation" and inspect how the main navigation is rendered. Add the requested navigation role, then verify the rendered markup and run the relevant existing frontend or accessibility checks if available.
Written by the indexing model from the issue text.
Description
Add attribute role "navigation" in the div tag with the id "oooNavigation"
- Dominant language
- Perl
- Stars
- 337
- Forks
- 89
- Avg merge
- 20h 52m
- Merged PRs (30d)
- 37
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RotherOSS/otobo
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
style
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
change
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
style
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Similar issues
-
1.severity: security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
api7/lua-resty-saml#63 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100