#LoqiAccessibility is the practice of designing so that people with disabilities can have equal access to information and functionality, applicable to both websites as well as physical environments https://indieweb.org/accessibility
#LoqiIt looks like we don't have a page for "accessibility statement" yet. Would you like to create it? (Or just say "accessibility statement is ____", a sentence describing the term)
#[tantek]gRegor, I think we need both. rather, I think we need an direct /accessibility_statement page that has an accessibility statement about http://indieweb.org itself, per https://www.w3.org/WAI/planning/statements/ and that page should also have links to "How to" make your own for your own personal site, and links for IWC event organizers for how to make an AS specific for each event
#[tantek]we could even make "accessibility statement examples" its own page, similar to
#gRegorI don't remember, did we decide to use indieweb- prefix for pages about IW, like indieweb-accessibility-statement is our statement, accessibility-statement is the general concept, how to, examples?
#gRegor[tantek], ^ as a starting point since wasn't sure which slug to put it at
#[tantek]this is a great slug start. I think the only things I would drop would be claims of equality (because no one actually achieves that and even aspirationally it sets an unreasonable bar. I'd look at the kind of language that the W3C WAI uses), and add citations from the existing /accessibility page
#[tantek]this is an area that I wouldn't make up new language nor use specific phrases from /accessibility unless it came from a well written expert source (like the WAI documents)
#[tantek]so maybe the right answer is to include the IWC accessibility statement (for events & the site) at /accessibility also, and then focus /accessibility_statement on dfn, how to, etc.
#gRegorSeems to focus mainly on digital accessibility though, and I wonder if that exclusion is partly to cover for shortcomings. idk, I liked the "commitment" language from WAI and I feel like a "commitment to equal access" is different than saying you actually have it.
#gRegor(shortcomings in the site, like "oops we forgot alt text", things accidentally breaking, etc.)
#gRegorLike at /2017/Bellingham I was committed to equal access for attendees, but unfortunately the venue didn't have an elevator for day 1. That was the main reason for the notice in the Where section.
#[tantek]by the evidence that even experts in accessibility do not make or ask others to make a "commitment to equal access", it strikes me as an unwise thing to claim, promise, or set expectations. it's also arguably impossible given the nature of some disabilities
#[tantek]a "commitment to accessibility" seems to be the more common pattern
#[tantek]that's the term to use, not making up a new phrase like "equal access" which no expert in accessibility is using or proposing
#kvibber.comedited /bookmark (-29) "/* Other bookmarking silos */ remove link on StumbleUpon (shut down in 2018)" (view diff)
#gRegorEqual access isn't a new phrase, though. Disability justice advocates use it and I've seen it in legal contexts, like the DOJ. I guess this is getting more philosophical for me, but I think it's always a "pursuit of" not a destination. Weaker language feels like it makes it easier to shrug shoulders instead of working for better outcomes.