https://github.com/patrickhlauke/wcag-interpretation
Presentation/rant on WCAG interpretation for auditors and developers
https://github.com/patrickhlauke/wcag-interpretation
Last synced: about 1 month ago
JSON representation
Presentation/rant on WCAG interpretation for auditors and developers
- Host: GitHub
- URL: https://github.com/patrickhlauke/wcag-interpretation
- Owner: patrickhlauke
- Created: 2019-10-08T23:04:43.000Z (over 5 years ago)
- Default Branch: gh-pages
- Last Pushed: 2023-11-04T08:39:02.000Z (over 1 year ago)
- Last Synced: 2025-03-30T11:22:59.551Z (2 months ago)
- Language: CSS
- Homepage: https://patrickhlauke.github.io/wcag-interpretation
- Size: 24.4 MB
- Stars: 5
- Watchers: 0
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# WCAG interpretation
## These (still) aren't the SCs you're looking for...
WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...
## Repository structure
* `gh-pages` contains the latest/most complete version of this presentation – a big brain-dump of all things relating to WCAG interpretation, current gaps and loopholes
* individual workshops/conference talks which use a shortened or adapted version of these slides live in their own separate branches – these are usually left dangling/unmerged