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

[PRIMARY FEATURE] Website Accessibility Check #62

Open
GuyWhoCode opened this issue Mar 12, 2024 · 2 comments
Open

[PRIMARY FEATURE] Website Accessibility Check #62

GuyWhoCode opened this issue Mar 12, 2024 · 2 comments
Labels
Feature New feature or request Medium This requires decent dedication to complete

Comments

@GuyWhoCode
Copy link
Member

User Story

As a developer, I want to ensure that our website can be accessible by anyone, including those with disabilities.

Technical Tasks

  • Run through the A11y Project Accessibility Checklist here
  • Based on assessment, improve websites to satisfy failed requirements

Acceptance Criteria

  • Website implements all accessibility recommendations within reason
    • Alright to fail some issues if it's impossible to implement with React for some unknown reason
@GuyWhoCode GuyWhoCode added Feature New feature or request Medium This requires decent dedication to complete labels Mar 12, 2024
@KaylaMLe
Copy link

Discord Name: beetleferr

@GuyWhoCode GuyWhoCode moved this from Todo to In Progress in Issues Board Mar 12, 2024
@KaylaMLe
Copy link

DONE:

  • prefers-reduced-motion: reduce disables all transition animations
  • the tab's title changes as you navigate through the page
  • appropriate alt text added
  • the logo in the navbar is no longer a button that does nothing
  • keyboard focus decoration is visible around all interactive elements
  • color contrast ratio is now at least 4.5 for body text and 3 for graphics and large text.
  • added a skip to main content link
  • added external link icons to the download links

ISSUES:

  • There are color contrast issues in auto-generated docs page.
  • an MUI (?) style overrode the coloring style I tried to apply to the title on the Documentation page, so I had to pass the title a style object instead.

TODO:
for screen reader compatibility:

  • thoroughly keyboard navigation
  • Refining landmark regions and heading consistency (would require a deeper reworking of the page's styling)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature or request Medium This requires decent dedication to complete
Projects
Status: In Progress
Development

No branches or pull requests

2 participants