In defense of websites… Hard to ind good code examples
•
Conformance vs guidance
•
AT/browser support vs actual usability
•
WCAG often can’t tell you what to do (for reasons, but still) f
•
Slide 11
We need to look for opportunities to build accessibility into systems
Slide 12
Like CMSes… Can they be accessibility assistants?
Slide 13
// features that do some accessibility // semantics for you, like popover <button popovertarget=”p”> Toggle popover </button> <div popover id=”p”> … </div>
See: On popover accessibility: what the browser does and doesn’t do https://hidde.blog/popover-accessibility/
Like web platform features…
Slide 14
Like user agents…
Slide 15
Like user agents…
Force colour contrast
Force focus indication
Slide 16
Like design systems… —nl-button-border-color: #2446AE —nl-button-color: #2446AE
Save
—nl-button-background-color: #ffffff
Slide 17
—nl-button-border-color: #2446AE
—nl-button-color: #2446AE
Save
—nl-button-background-color: #ffffff
Slide 18
—nl-button-border-color: #2446AE
—nl-button-color: #cccccc
Save
—nl-button-background-color: #ffffff
Slide 19
—nl-button-border-color: #2446AE
—nl-button-color: #cccccc
Save
🚨
—nl-button-background-color: #ffffff
Slide 20
“Built-in” accessibility
It’s not trivial, not a oneoff, not a quick “fix”. It can be done. It’s worthwhile.