|
|
| (53 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| [[Category: Design]]
| |
| ==The Basics==
| |
| Accessibility refers to the design of products, devices, services, or environments '''for people who experience disabilities'''. The concept of accessible design and practice of accessible development ensures both "direct access" (i.e. unassisted) and "indirect access" meaning compatibility with a person's assistive technology (for example, computer screen readers). – [https://en.wikipedia.org/wiki/Accessibility Wikipedia]
| |
|
| |
| [[:Category: Types of Disabilities | Types of Disabilities]]
| |
|
| |
| == Why Accessibility ==
| |
| [https://twitter.com/jameswillweb/status/789212365325828096 [[File:Jameswilliamsaccessibilityquote.jpg|400px]]]<br />
| |
| Accessibility is the act of designing for an audience that includes people who have disabilities, and may (or may not) be using additional software or hardware to complete their goals. Accessibility is a way of thinking about design and development. Dylan Barrell explains it in his article "[http://unobfuscated.blogspot.com/2015/02/what-is-accessibility.html What is accessibility?]" in terms of a series of traits.
| |
| * '''Accessibility is empathy''' for your users.
| |
| * '''Accessibility is usability''' in the things you build.
| |
| * '''Accessibility is compliance''' with best practices, so you don't have to reinvent the wheel (or make your user do the same).
| |
| * '''Accessibility is making the experience better for all users''', with an emphasis on the users at the edge of the experience.
| |
| * And '''Accessibility is practical''' - not idealistic - in its pursuit of a better experience.
| |
|
| |
| (There's a great discussion of how a map can be accessible not by aligning with the letter of accessibility requirements, but by reassessing what the core user need actually is and building it instead or in addition to the map, in the "[http://unobfuscated.blogspot.com/2015/02/what-is-accessibility.html What is accessibility?]" article, by the way.)
| |
|
| |
| Paul Boag raises many of the same points in his article [https://boagworld.com/accessibility/accessibility-is-not-what-you-think/ Accessibility is not what you think], putting the emphasis on the fact that accessible solutions aren't strictly for the profoundly disabled edge cases. Yes, they are covered by good accessibility solutions, but good accessibility solutions benefit everyone. Accessibility is not a few things, though you'll meet people who think that it is. It is not a checklist of things to do so that your software passes a compliance test, a list of things to do so you don't get sued, or a pain in your ass. (Or rather, if it's a pain in your ass, so is User Experience and everything else that's going to make your product successful, so deal.)
| |
|
| |
| [http://www.claimingcrip.com/2016/01/accessibility-is-not-nice-thing-to-do.html Accessibility is not a "nice thing to do"], as Karin Hitselberger explains in her article of the same name. It's the law. And it's the law because Karin and you and I all share the same rights to life and dignity and safety and security. It's not kindness, and it's not charity. It's the baseline.
| |
|
| |
| [https://www.applevis.com/blog/advocacy-ios-apps-opinion/accessibility-not-feature-and-developers-should-never-treat-it-such?utm_content=buffer7f799&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer Accessibility is not a 'Feature' and Developers Should Never Treat It as Such]. Similarly, [https://timkadlec.com/2015/02/access-optional/ Access is not Optional].
| |
|
| |
| I've written a few things about Accessibility over the years, which can be boiled down to these two points:
| |
|
| |
| * [[You must be aware of your own stereotypes]]
| |
| * [[You will not always be able-bodied]]
| |
|
| |
| ==Legal issues==
| |
| One of the most, um, ''motivating'' aspects of accessibility law is the ability for someone with a disability to sue or register a complaint against the Office of Civil Rights (in the US, and similar offices in other countries) when a physical or virtual location is inaccessible.
| |
|
| |
| ==United States==
| |
|
| |
| [https://www.section508.gov/node/303 As of January 9, 2017], the [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/iii-major-issues-5 Standards and Guidelines of the ICT] state that federal governmental electronic content shall conform to [https://www.w3.org/TR/2008/REC-WCAG20-20081211/#contents Level A and Level AA Success Criteria of the WCAG 2.0] via changes to the [https://www.section508.gov/ Section 508] laws and guidelines. That means that if a company want federal contracts or to provide services to the federal government, it has to meet those accessibility standards. Many state and local governments, state colleges, libraries, etc. also use the Section 508 guidelines — so these potential clients would also request or require accessibility at the Section 508 levels.
| |
|
| |
| While officially these rules do not directly apply to non-federal-governmental websites or applications, there have been [http://www.adatitleiii.com/2016/03/tracking-the-trends-website-accessibility-lawsuits-by-the-numbers/ many web accessibility lawsuits] with the Wall Street Journal reporting [http://www.wsj.com/articles/companies-face-lawsuits-over-website-accessibility-for-blind-users-1478005201 over 240 businesses being sued in federal court] over sites inaccessible to the blind since 2015.
| |
|
| |
| Microassist.com’s [https://www.microassist.com/digital-accessibility/digital-accessibility-primer-legal/ What Lawyers Should Know About Digital Accessibility, the ADA, and More] covers a significant amount of US-based information about accessibility, including a timeline of landmark digital accessibility legal cases.
| |
|
| |
| ===Interesting or impactful legal rulings===
| |
| [https://www.w3.org/WAI/bcase/target-case-study A Cautionary Tale of Inaccessibility: Target Corporation] by the World Wide Web Consortium (W3C). This 2006 decision had a major impact on the Accessibility community because it successfully ruled that telling people with disabilities that they have to use a lower-feature mobile website instead of the full-featured desktop website was a violation of California law. “The [Federal] Judge found that California anti-discrimination law covers websites whether or not they are, or are connected to, a physical place, and that those aspects of Target.com’s services that are sufficiently integrated with those of physical Target Stores are covered by the ADA’s non-discrimination provisions.”
| |
|
| |
| [http://doc.lab.boomi.com/download/attachments/25627585/Legal+Landscape+Update+2016+Year+in+Review+Web_508.pdf?version=1&modificationDate=1515007552000SSB Bart Group reviews the legal rulings in 2016 in this whitepaper]. Summary points include:
| |
|
| |
| * 6601 ADA Title III Lawsuits were filed in federal court in 2016, a 37% increase over 2015. Many were settled out-of-court so details are unavailable.
| |
| * Both the US and the EU updated their compliance regulations in 2016/2017.
| |
| * Video captions were a major issue in the education, and entertainment sectors.
| |
| * Screen readers were a major issue in the education, and government sectors.
| |
| * Low-vision issues and forms were a major issue in healthcare, and government sectors.
| |
| * Major lawsuits included the Winn-Dixie case already referenced, BMI/BND Travelware (a luggage retailer) who was sued under both ADA law and a California civil rights law, Deckers Outdoor Corp (the company that makes Uggs) which is still pending, Sweetgreen (salad restaurant), Bank of America, and E*Trade.
| |
|
| |
| [http://www.chainstoreage.com/article/winn-dixie-case-puts-spotlight-website-accessibilitycompliance Winn-Dixie Case Puts Spotlight on Website Accessibility/Compliance] by Chain Store Age. This 2017 decision addresses the same kinds of complaints the Target case addressed — the website must be accessible because it is a gateway to the stores. Emphasis added.
| |
|
| |
| <blockquote> This Florida case also include an entire section on vendors: It is a common practice for businesses to host links on their websites that connect them to partners, vendors, or other third parties. The Court’s ruling this week suggests that even if a business hosts a compliant website, it may be held liable for noncompliance under Title III of the ADA, if it links up to websites that are inaccessible.<br /><br />
| |
|
| |
| The Court in Winn Dixie ruled that “There are 6 different third parties . . . who interface with Winn Dixie’s website so Winn-Dixie needs to make sure that those third parties also make sure that their websites are accessible” and “The Court also finds that the fact that third party vendors operate certain parts of the Winn-Dixie website is not a legal impediment to Winn-Dixie’s obligation to make its website accessible to the disabled. First, many, if not most, of the third party vendors may already be accessible to the disabled and, if not, Winn-Dixie has a legal obligation to require them to be accessible if they choose to operate within the Winn-Dixie website.” '''This language suggests that an operator or owner of an accessible website may face liability for the noncompliance of vendors that it features through its links.'''</blockquote>
| |
|
| |
| In January 2018, The New York Post announced [https://nypost.com/2018/01/07/blind-woman-sues-30-websites-over-handicap-accessibility/ a blind woman from Manhattan filed lawsuits against more than 30 websites] (mostly retail by the looks of it) for being incompatible with screen readers, and that a disabled man in Manhattan has filed 21 lawsuits for similar offenses.
| |
|
| |
| ==Other countries==
| |
| The Law Office of Larry Feingold posts an article entitled [http://www.lflegal.com/2013/05/gaad-legal/ Digital Accessibility Laws Around the Globe] dated from May 2013, but last updated May 2018 (as of this writing) that keeps track of what laws and rulings may affect each of roughly 16 countries. Other cases include:
| |
|
| |
| * [http://www.bbc.com/news/business-43968736 Blind customers locked out by bank web upgrades] in the UK
| |
|
| |
| == Standards and Guidelines ==
| |
| The official standard is the [https://www.w3.org/TR/WCAG20/ WCAG 2.0 standard] by the W3C. For resources related to the standard, see [[:Category: WCAG Guidelines]].
| |
| * [http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile BBC Mobile Accessibility Standards & Guidelines]
| |
| * [http://www-03.ibm.com/able/guidelines/ci162/accessibility_checklist.html IBM Web Accessibility Checklist Version 7]
| |
| == Getting it done ==
| |
| [[Accessibility 101]]: The things you need to get started
| |
| === Fostering the Culture ===
| |
| * [https://aneventapart.com/news/post/extreme-design-by-derek-featherstonean-event-apart-video Extreme Design] by Derek Featherstone is a one-hour video of how accessible design benefits everyone.
| |
| * [https://blogs.dropbox.com/tech/2017/04/creating-a-culture-of-accessibility/ Creating a Culture of Accessibility] by Cordelia McGee Tubs at the Dropbox Tech Blog. This article discusses generating excitement around accessibility, running an accessibility device lab, rewarding the organization's champions, spreading knowledge, and developing a culture of learning around accessibility.
| |
| * [https://alistapart.com/article/reframing-accessibility-for-the-web Reframing Accessibility for the Web] by me at A List Apart. This article discusses how stereotypes work, how they're interfering with our accessible design process, and one approach to testing for accessibility that takes the stereotypes out of the direct line of fire.
| |
| * [https://accessibility.digital.gov Accessibility for Teams] by the US Government outlines how each role at an organization or in a team can improve the accessibility of a product.
| |
| ===Agile and Accessibility ===
| |
| * [http://www.interactiveaccessibility.com/blog/how-write-user-stories-accessibility-requirements#.WWBfR8aZPUp How to write user stories user stories for web accessibility] by Kathy Wahlbin at Interactive Accessibility
| |
| ===Specific topics=== | | ===Specific topics=== |
| * [[Accessible Error Handling]] | | * [[Accessible Error Handling]] |
| * [[Writing Accessibly]] | | * [[Writing Accessibly]] |
| | * [[Accessible color systems]] |
| | * [[Accessibility overlays do not work]] |
| | * [[Screen Readers]] |
| | |
| == Testing tools == | | == Testing tools == |
| ===Why test with people who have disabilities?=== | | ===Why test with people who have disabilities?=== |
| * [https://uxdesign.cc/disabled-user-testing-a-cautionary-tale-b6cf64425adb Accessibility user testing: a cautionary tale] by Daniel Pidcock outlines one example of what can happen when we assume that our work is accessible. | | * [https://uxdesign.cc/disabled-user-testing-a-cautionary-tale-b6cf64425adb Accessibility user testing: a cautionary tale] by Daniel Pidcock outlines one example of what can happen when we assume that our work is accessible. |
| ===How to test=== | | ===How to test=== |
| | * [https://karlgroves.com/2012/09/15/accessibility-testing-what-can-be-tested-and-how Web Accessibility Testing: What Can be Tested and How] by Karl Groves in September 2012 outlines what can be tested by automated systems and what requires a person (preferably with disabilities) to test. He also encourages people and companies to [https://karlgroves.com/2012/02/02/web-accessibility-testing-do-automatic-testing-first Do Automatic Testing First] but not as the only thing you do. |
| * [https://www.deque.com/blog/considering-accessibility-when-designing-a-usability-test Considering accessibility when designing a usability test] outlines ways to integrate accessibility testing into usability testing -- since if it's not accessible, it's not usable. | | * [https://www.deque.com/blog/considering-accessibility-when-designing-a-usability-test Considering accessibility when designing a usability test] outlines ways to integrate accessibility testing into usability testing -- since if it's not accessible, it's not usable. |
| * [[Accessibility Testing Tools]] outlines information about testing code, such as how to use a screen reader and what automated tools are available. | | * [[Accessibility Testing Tools]] outlines information about testing code, such as how to use a screen reader and what automated tools are available. |
| Line 94: |
Line 22: |
| * [[An Alphabet of Accessibility]] | | * [[An Alphabet of Accessibility]] |
| == Related topics == | | == Related topics == |
| | * [[Accessibility-related memes and humor]] |
| * [[Disability as Inspiration Porn]] | | * [[Disability as Inspiration Porn]] |
| * [https://www.vox.com/the-goods/2018/9/20/17791354/products-people-disabilities-sock-slider-banana-slicer-lazy Products mocked as “lazy” or “useless” are often important tools for people with disabilities] by s.e. smith for Vox | | * [https://www.vox.com/the-goods/2018/9/20/17791354/products-people-disabilities-sock-slider-banana-slicer-lazy Products mocked as “lazy” or “useless” are often important tools for people with disabilities] by s.e. smith for Vox |
| Line 106: |
Line 35: |
| * [[WAI-ARIA]] <-- this totally doesn't belong here but I'm not sure where to put it yet | | * [[WAI-ARIA]] <-- this totally doesn't belong here but I'm not sure where to put it yet |
| * [http://webaim.org/resources/ WebAIM Resources page] | | * [http://webaim.org/resources/ WebAIM Resources page] |
| | |
| | [[Category:Design]] |
A-bad-designer-accessibility.jpg 500 × 713; 97 KB
Jameswilliamsaccessibilityquote.jpg 1,200 × 672; 80 KB
