feat: improved accessibility skipping to main content

[vladislavkeblysh]

Description

Jump user's focus skipping two navigation menus above it

• Progress page
• Course unit
• Dates page

Testing instructions

Progress Page

1. Go to Progress
2. Using the Tab key (Shift+Tab) get to the Skip to main content element above the header.
3. When user press the Enter or Space key, the focus should move to the Your progress heading.

Course Unit Page

1. Go to Course unit page.
2. Using the Tab key (Shift+Tab) get to the Skip to main content element above the header.
3. When user press the Enter or Space key, the focus should move to the active unit.

Dates Page

1. Go to Dates page.
2. Using the Tab key (Shift+Tab) get to the Skip to main content element above the header.
3. When user press the Enter or Space key, the focus should move to the Important dates heading.

Screen.Recording.2025-05-02.at.16.30.01.mov

[openedx-webhooks]

Thanks for the pull request, @vladislavkeblysh!

This repository is currently maintained by @openedx/committers-frontend-app-learning.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (af432ea) to head (7493dfb).
⚠️ Report is 65 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1599      +/-   ##
==========================================
+ Coverage   90.18%   90.24%   +0.05%     
==========================================
  Files         339      339              
  Lines        5810     5742      -68     
  Branches     1409     1398      -11     
==========================================
- Hits         5240     5182      -58     
+ Misses        552      543       -9     
+ Partials       18       17       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[itsjeyd]

@vladislavkeblysh Thank you for this contribution!

[itsjeyd]

@vladislavkeblysh Since this PR seems to include user-facing changes, you'll likely need to get product approval for it. When you're ready please follow the instructions from the bot to get that process started.

[itsjeyd]

Hey @vladislavkeblysh, just checking in to see if you're still planning to continue working on this PR?

[vladislavkeblysh]

@itsjeyd Ready to review

[itsjeyd]

@vladislavkeblysh Thanks for the update. Have you been able to get product approval for this change?

[PKulkoRaccoonGang]

[inform]: Awaiting Product Review

[PKulkoRaccoonGang]

[question]: Can we export these styles to a style file?

[PKulkoRaccoonGang]

[question]: Do we need this?

[PKulkoRaccoonGang]

[questions]: We use the MAIN_CONTENT_ID constant twice. Does it make sense to put it in a separate constants.js file?

[open-craft-grove]

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[itsjeyd]

Hi @vladislavkeblysh, just a quick update that I'm closing this PR now because it is stale. You're welcome to reopen this pull request, or open a new one, when you have time to come back to this work.