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

Tag page - All page content should be contained within landmarks #14838

Closed
aitchiss opened this issue Sep 28, 2021 · 4 comments
Closed

Tag page - All page content should be contained within landmarks #14838

aitchiss opened this issue Sep 28, 2021 · 4 comments
Assignees
Labels
area: accessibility issues that need accessibility improvements (a11y) tech: frontend changes will primarily involve frontend technologies

Comments

@aitchiss
Copy link
Contributor

Describe the bug

For accessibility purposes, all content should be contained within landmark regions. On the tag page, e.g. https://dev.to/t/devops, the content in the left and right sidebars (desktop view) are not within any landmark:

screenshot of the tag page for DEV's devops tag. The right sidebar and left sidebar content have a red box around them to highlight them

In this case, the content could reasonably exist within <aside> elements ( "complementary" landmark), since they support the main content, but are not essential to it, and make sense when separated from the main content.

NB: This refers to the large-screen 'desktop' view pictured above only. On smaller screens, the content is triggered as a pop-up menu. For the purposes of this issue we do not wish to change any of the markup for the pop-up menu.

To Reproduce

  • Visit a tag's page
  • In devtools, use the axe extension to check the page
  • Notice the error "All page content should be contained by landmarks"

Expected behavior

  • The error should not appear in an axe report
  • When I navigate by landmarks using a screen reader, I should be able to select a landmark to navigate to this sidebar content

Additional context

There is a different class of accessibility issues associated with the smaller screen 'menu popup' view for this content. It will be captured in a separate issue, and needn't affect the fix here.

@aitchiss aitchiss added area: accessibility issues that need accessibility improvements (a11y) tech: frontend changes will primarily involve frontend technologies labels Sep 28, 2021
@github-actions
Copy link
Contributor

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.

To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

@metamoni
Copy link
Contributor

metamoni commented Oct 1, 2021

Hey, @aitchiss, I'd like to work on this one if that's OK :)

@aitchiss
Copy link
Contributor Author

aitchiss commented Oct 1, 2021

Yeeha! That's awesome - I've assigned it to you now @metamoni 😄

@rhymes
Copy link
Contributor

rhymes commented Oct 5, 2021

Closed by #14899

@rhymes rhymes closed this as completed Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: accessibility issues that need accessibility improvements (a11y) tech: frontend changes will primarily involve frontend technologies
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants