What are we doing here? We’ll need to work that out over time. For now, we’ll mostly be talking about accessibility, mostly on the web.
I’m mostly DC-based, so it should come as no surprise that DMV (the District, Maryland, and Virginia) and US government websites will come up. TBH, they’ll probably jump up and make themselves targets.
508 Conformance/Compliance: When federal accessibility comes up, the number 508 will come up with it. “508” is Section 508 of the Rehabilitation Act, the root of all accessibility in federal web space. “Conformance” is what the websites do (in theory): conform to the standards. “Compliance” is what feds and contractors do (again, in theory): comply with the rules. Right now, 508 mostly means following Web Content Accessibility Guidelines (WCAG) 2.0 AA, which I can’t possibly explain on one “About” page.
When we’re chatting about websites everywhere else in the world, we’re probably still going to mention accessibility and WCAG, but not 508. Also, we might talk WCAG 2.1, 2.2, or 3 — and things get a little complicated, when it comes to current guidance, so we’d better leave that for another day, too.
Who am I? Just a humble webby.
I practice Agile, but avoid the branded agiles when I can. IMHO, too many of them have lost the thread of what made the manifesto manifestly excellent. (Side note: If your customer needs a class, just to understand what you’re talking about, it’s not the customer who has the language problem.)
Remind me, some time, to discuss Kung Fu as a metaphor for Agile.
Time to wrap!