You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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/
The text was updated successfully, but these errors were encountered: