Skip to content

Easier way to achieve 508 Compliance #538

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

Open
WebWeWantBot opened this issue Mar 30, 2022 · 0 comments
Open

Easier way to achieve 508 Compliance #538

WebWeWantBot opened this issue Mar 30, 2022 · 0 comments

Comments

@WebWeWantBot
Copy link
Collaborator


title: Easier way to achieve 508 Compliance
date: 2022-03-30T21:00:12.259Z
submitter: Brian Edwards
number: 6244c4dcf8cc280069bbb4f6
tags: [ ]
discussion: https://github.com/WebWeWant/webwewant.fyi/discussions/
status: [ discussing || in-progress || complete ]
related:

  • title:
    url:
    type: [ article || explainer || draft || spec || note || discussion ]

The most challenging part of web development is ensuring the solution is 508 compliant. You have to use a multitude of tools, techniques, and screen readers. I would like a web where you don't have to invest so much time just trying to meet accessibility requirements, be it additions to Devtools or browsers doing more and less need to figure out what combination of aria tags, role attributes, etc. are needed.


If posted, this will appear at https://webwewant.fyi/wants/6244c4dcf8cc280069bbb4f6/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant