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

[a11y] Issue 8: Missing main element/landmark (Participation Page) #66

Closed
NewJerseyStyle opened this issue Oct 31, 2024 · 2 comments · Fixed by #32
Closed

[a11y] Issue 8: Missing main element/landmark (Participation Page) #66

NewJerseyStyle opened this issue Oct 31, 2024 · 2 comments · Fixed by #32

Comments

@NewJerseyStyle
Copy link
Member

Description:

Similar to Issue #4, the participation page lacks a main element/landmark and various other landmarks (header, nav, footer). These elements are essential for defining page structure and improving accessibility for assistive technologies.

Steps to Reproduce:

  1. Navigate to the participation page (e.g. https://pol.is/4cvkai2ctw)
  2. Inspect the HTML structure.

Expected Behavior:

Presence of main, header, nav, and footer elements for proper semantic structure.

Actual Behavior:

Missing landmark elements, hindering accessibility.

Component/Area: Participation page

Source: Auto evaluation

Affected Elements: header, nav, main, footer

@NewJerseyStyle NewJerseyStyle converted this from a draft issue Oct 31, 2024
@thomassth
Copy link

Should be fixed with #32

@thomassth thomassth moved this from Backlog to In Progress in UI accessibility test Oct 31, 2024
@NewJerseyStyle NewJerseyStyle linked a pull request Oct 31, 2024 that will close this issue
@NewJerseyStyle
Copy link
Member Author

True, we don't have navigation as its single page app

@github-project-automation github-project-automation bot moved this from In Progress to Done in UI accessibility test Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants