├── src ├── favicon.ico ├── og-twitter.png ├── screen.css └── index.html ├── .editorconfig ├── .gitignore ├── LICENSE └── README.md /src/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mohammad-suliman/overlayfactsheet/develop/src/favicon.ico -------------------------------------------------------------------------------- /src/og-twitter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mohammad-suliman/overlayfactsheet/develop/src/og-twitter.png -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | # EditorConfig helps developers define and maintain consistent 2 | # coding styles between different editors and IDEs 3 | # editorconfig.org 4 | 5 | root = true 6 | 7 | [*] 8 | indent_style = space 9 | indent_size = 2 10 | end_of_line = lf 11 | charset = utf-8 12 | trim_trailing_whitespace = true 13 | insert_final_newline = true 14 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | ### PHP storm/ IntelliJ ### 2 | .idea 3 | .idea/* 4 | .idea/workspace.xml 5 | atlassian-ide-plugin.xml 6 | .settings 7 | *.iml 8 | 9 | ### vim ### 10 | [._]*.s[a-w][a-z] 11 | [._]s[a-w][a-z] 12 | *.un~ 13 | Session.vim 14 | .netrwhist 15 | *~ 16 | 17 | ### Emacs ### 18 | \#*\# 19 | /.emacs.desktop 20 | /.emacs.desktop.lock 21 | *.elc 22 | auto-save-list 23 | tramp 24 | .\#* 25 | 26 | /node_modules/ 27 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 Karl Groves 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # overlay factsheet 2 | 3 | [![Netlify Status](https://api.netlify.com/api/v1/badges/38981166-3465-41df-8561-55859185211c/deploy-status)](https://app.netlify.com/sites/overlayfactsheet/deploys) 4 | 5 | A non-biased, community-driven, fact-based information sheet aimed at educating customers on web-accessibility overlays. This repo powers the site at https://overlayfactsheet.com/ 6 | 7 | ## Contributing 8 | 9 | ### Endorse this statement 10 | 11 | #### EASY: If the whole PR thing is something you're not comfortable with you can do one of three things: 12 | 13 | * Log an Issue in this repo: Click "Issues" and follow the process of adding an issue that indicates that you want to sign 14 | * Send an email to karl@tenon.io to indicate that you want to sign 15 | * Send a Twitter DM to @karlgroves to indicate that you want to sign 16 | 17 | #### Harder, but more efficient 18 | 19 | Toward the bottom of the page in the `/src/index.html` file is a heading that says "Signed by". 20 | 21 | Below that is an ordered list (`
    `); 22 | 23 | Add your name as a `
  1. ` in that list, in the following format: Name, Title, Organization. For example: `Joe Schmoe, CEO, Acme Corp.` If you'd rather not put your title and organization down, that's fine. Feel free to do something like `Joe Schmoe, self` 24 | 25 | Please do not add links in the endorsement section. This isn't an exercise in SEO for anyone, it is a statement of unity. 26 | 27 | Please use the PR process described below, issuing your PR against the `develop` branch. 28 | 29 | ### Design and/or Code 30 | 31 | Contributions to the design and/ or code are encouraged! 32 | 33 | We follow a modified "git flow" type of workflow: 34 | 35 | 1. Create an issue that describes the change you want to make (or pick one from the list of desired changes) 36 | 2. Create a branch for that issue 37 | 3. Issue a pull request against the `develop` branch that is *solely focused* on the issue you're working against. 38 | 4. Once a repo admin approves the PR, it will be merged into `develop` 39 | 5. From there, it'll be verified on the preview version of the site and, if acceptable, a PR will be made to go from `develop` to `main`. 40 | 6. When the PR to `main` has passed, it will automatically deploy. 41 | 42 | ### Content 43 | 44 | Contributions of content will follow the exact same workflow as above. 45 | 46 | Please note the following general content guidance: 47 | 48 | 1. This project is aimed at conveying facts. Content should strive to avoid hyperbole, exaggeration, and logical fallacy. 49 | 2. Opinions should be avoided unless they are opinions of end users describing their experiences with overlays. 50 | 3. Advertisements for any product, service, or company is prohibited. 51 | 4. You should use [Wikipedia's Content Standards](https://en.wikipedia.org/wiki/Wikipedia:Understanding_Wikipedia%27s_content_standards) and [Principles](https://en.wikipedia.org/wiki/Wikipedia:Principles) as guides for what we're trying to accomplish here. 52 | 53 | 54 | -------------------------------------------------------------------------------- /src/screen.css: -------------------------------------------------------------------------------- 1 | /* All */ 2 | *, 3 | *::before, 4 | *::after { 5 | box-sizing: border-box; 6 | margin: 0; 7 | padding: 0; 8 | vertical-align: baseline; 9 | } 10 | 11 | 12 | 13 | 14 | /* Custom properties */ 15 | :root { 16 | --border-radius: 0.5rem; 17 | --border-thickness: 2px; 18 | --color-gray-100: #ffffff; 19 | --color-gray-200: #eaeaea; 20 | --color-gray-300: #afafaf; 21 | --color-gray-400: #aeaeae; 22 | --color-gray-500: #949494; 23 | --color-gray-600: #818181; 24 | --color-gray-700: #6a6a6a; 25 | --color-gray-800: #3f3f3f; 26 | --color-gray-900: #2c2c2c; 27 | --color-red-100: #FFE4D6; 28 | --color-red-200: #FFC3AD; 29 | --color-red-300: #FF9B83; 30 | --color-red-400: #FF7565; 31 | --color-red-500: #FF3632; 32 | --color-red-600: #DB2430; 33 | --color-red-700: #B71931; 34 | --color-red-800: #930F2F; 35 | --color-red-900: #7A092E; 36 | --color-yellow-100: #FFFACC; 37 | --color-yellow-200: #FEEBB1; 38 | --color-yellow-300: #FEDD89; 39 | --color-yellow-400: #FDCF6C; 40 | --color-yellow-500: #FCB93C; 41 | --color-yellow-600: #D8962B; 42 | --color-yellow-700: #B5751E; 43 | --color-yellow-800: #925813; 44 | --color-yellow-900: #78430B; 45 | --typeface-primary: 'Helvetica Neue', Helvetica, Arial, sans-serif; 46 | --line-height-100: 1.1; 47 | --line-height-200: 1.3; 48 | --line-height-300: 1.5; 49 | --line-height-400: 1.75; 50 | --line-height-500: 2; 51 | --vertical-rhythm: 1.5rem; 52 | } 53 | 54 | 55 | 56 | 57 | /* Core */ 58 | html { 59 | margin: 0; 60 | min-height: 100%; 61 | overflow-y: scroll; 62 | padding: 0; 63 | text-size-adjust: 100%; 64 | 65 | hanging-punctuation: first; 66 | 67 | -ms-overflow-style: scrollbar; 68 | -ms-text-size-adjust: 100%; 69 | -webkit-text-size-adjust: 100%; 70 | 71 | font-kerning: normal; 72 | -moz-font-feature-settings: "kern"; 73 | -ms-font-feature-settings: "kern"; 74 | -webkit-font-feature-settings: "kern"; 75 | font-feature-settings: "kern"; 76 | } 77 | 78 | html { 79 | @media screen and (-webkit-min-device-pixel-ratio: 2), screen and (min-resolution: 2dppx) { 80 | font-smoothing: subpixel-antialiased; 81 | } 82 | } 83 | 84 | html { 85 | @-ms-viewport { 86 | width: device-width; 87 | } 88 | } 89 | 90 | body { 91 | background-color: var(--color-gray-100); 92 | color: var(--color-gray-800); 93 | font-family: var(--typeface-primary); 94 | font-size: 120%; 95 | line-height: var(--line-height-300); 96 | min-height: 100%; 97 | } 98 | 99 | h2, 100 | h3 { 101 | color: var(--color-gray-900); 102 | line-height: var(--line-height-200); 103 | font-weight: 400; 104 | } 105 | 106 | h2 { 107 | font-size: 1.75rem; 108 | margin-top: calc(var(--vertical-rhythm) * 2); 109 | } 110 | 111 | h3 { 112 | font-size: 1.5rem; 113 | margin-top: calc(var(--vertical-rhythm) * 2); 114 | } 115 | 116 | p { 117 | margin-top: var(--vertical-rhythm); 118 | } 119 | 120 | ul { 121 | margin-top: var(--vertical-rhythm); 122 | margin-left: 2rem; 123 | } 124 | 125 | ol { 126 | margin-top: var(--vertical-rhythm); 127 | margin-left: 3rem; 128 | } 129 | 130 | li { 131 | margin-top: calc(var(--vertical-rhythm) / 2); 132 | } 133 | 134 | blockquote { 135 | margin-top: var(--vertical-rhythm); 136 | } 137 | 138 | a { 139 | color: var(--color-red-700); 140 | transition: 141 | 150ms background-color ease-in-out, 142 | 150ms color ease-in-out; 143 | } 144 | 145 | a:hover, 146 | a:focus { 147 | background-color: var(--color-red-100); 148 | text-decoration: none; 149 | } 150 | 151 | 152 | 153 | 154 | /* Utilities */ 155 | .text-align-center { 156 | text-align: center; 157 | } 158 | 159 | .container { 160 | max-width: 62ch; 161 | margin: 0 auto; 162 | padding: 1rem; 163 | } 164 | 165 | .skip-to-content-link { 166 | display: inline-block; 167 | background: #fff; 168 | padding: 8px; 169 | position: absolute; 170 | left: 50%; 171 | transform: translate(-50%, -100%); 172 | } 173 | 174 | .skip-to-content-link:focus { 175 | transform: translate(-50%, 20%); 176 | } 177 | 178 | 179 | /* Layout */ 180 | .header { 181 | background-color: var(--color-gray-900); 182 | padding: 3.5rem 2rem; 183 | } 184 | 185 | .in-their-own-words, 186 | .further-reading { 187 | margin-top: calc(var(--vertical-rhythm) * 2); 188 | padding: 0 2rem 4rem 2rem; 189 | } 190 | 191 | .quotes { 192 | display: grid; 193 | grid-template-columns: 1fr; 194 | gap: 2rem; 195 | } 196 | 197 | @supports (display: grid) { 198 | .quotes { 199 | margin-top: var(--vertical-rhythm); 200 | } 201 | } 202 | 203 | @media screen and (min-width: 60rem) { 204 | .quotes { 205 | grid-template-columns: 1fr 1fr; 206 | } 207 | } 208 | 209 | @media screen and (min-width: 80rem) { 210 | .quotes { 211 | grid-template-columns: 1fr 1fr 1fr; 212 | } 213 | } 214 | 215 | .in-their-own-words { 216 | background-color: var(--color-red-100); 217 | } 218 | 219 | .further-reading { 220 | background-color: var(--color-gray-200); 221 | } 222 | 223 | 224 | 225 | 226 | /* Content */ 227 | .logo { 228 | fill: var(--color-red-400); 229 | height: 6rem; 230 | width: 6rem; 231 | } 232 | 233 | .title { 234 | color: var(--color-gray-100); 235 | font-size: 1.25rem; 236 | font-weight: 400; 237 | letter-spacing: 0.05ch; 238 | margin-top: 0.5rem; 239 | } 240 | 241 | .summary { 242 | border: var(--border-thickness) solid var(--color-yellow-200); 243 | background-color: var(--color-yellow-100); 244 | font-size: 1.15rem; 245 | padding: var(--vertical-rhythm) calc(var(--vertical-rhythm) * 1.5); 246 | } 247 | 248 | .conformance-quote { 249 | background-color: var(--color-gray-200); 250 | font-size: 1.3rem; 251 | margin-top: 2.5rem; 252 | margin-bottom: 2.5rem; 253 | padding: 2rem; 254 | } 255 | 256 | .conformance-quote cite { 257 | display: block; 258 | font-size: 1.25rem; 259 | font-style: normal; 260 | margin-top: 0.5rem; 261 | } 262 | 263 | .quote { 264 | background-color: var(--color-gray-100); 265 | border: var(--border-thickness) solid var(--color-red-200); 266 | border-radius: var(--border-radius); 267 | margin-top: calc(var(--vertical-rhythm) * 2); 268 | padding: 2rem; 269 | } 270 | 271 | .add-your-name { 272 | background: var(--color-yellow-100); 273 | border: var(--border-thickness) solid var(--color-yellow-500); 274 | border-radius: var(--border-radius); 275 | color: var(--color-yellow-800); 276 | display: inline-block; 277 | font-size: 1.25rem; 278 | margin-top: var(--vertical-rhythm); 279 | padding: 1rem 2rem; 280 | } 281 | 282 | .add-your-name:hover, 283 | .add-your-name:focus { 284 | background: var(--color-yellow-300); 285 | color: var(--color-yellow-900); 286 | } 287 | 288 | @supports (display: grid) { 289 | .quote { 290 | margin-top: 0; 291 | } 292 | } 293 | 294 | .quote cite { 295 | font-style: normal;; 296 | display: block; 297 | margin-top: 0.5rem; 298 | } 299 | 300 | .further-reading-source { 301 | display: block; 302 | font-size: 1rem; 303 | } 304 | 305 | #webaim-quote{ 306 | margin: 2rem; 307 | } 308 | 309 | 310 | /* Dark mode */ 311 | @media (prefers-color-scheme: dark) { 312 | body { 313 | background-color: var(--color-gray-900); 314 | color: var(--color-gray-200); 315 | } 316 | 317 | h2, 318 | h3 { 319 | color: var(--color-gray-100); 320 | } 321 | 322 | a { 323 | color: var(--color-red-300); 324 | } 325 | 326 | a:hover, 327 | a:focus { 328 | background: var(--color-red-900); 329 | } 330 | 331 | .header { 332 | background-color: var(--color-gray-100); 333 | } 334 | 335 | .title { 336 | color: var(--color-gray-800); 337 | } 338 | 339 | .conformance-quote { 340 | background-color: var(--color-gray-800); 341 | } 342 | 343 | .summary { 344 | color: var(--color-gray-900); 345 | } 346 | 347 | .in-their-own-words { 348 | background-color: var(--color-red-900); 349 | } 350 | 351 | .quote { 352 | background-color: var(--color-gray-900); 353 | border: var(--border-thickness) solid var(--color-red-800); 354 | border-radius: var(--border-radius); 355 | margin-top: calc(var(--vertical-rhythm) * 2); 356 | padding: 2rem; 357 | } 358 | 359 | .further-reading { 360 | background-color: var(--color-gray-800); 361 | } 362 | } 363 | -------------------------------------------------------------------------------- /src/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | Overlay Fact Sheet 7 | 8 | 9 | 10 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | Skip to content 32 |
    33 | 39 |

    Overlay Fact Sheet

    40 |
    41 |
    42 |
    43 |

    Table of contents

    44 |
      45 |
    1. 46 | 47 | Introduction, definition, and history of web accessibility overlays 48 | 49 |
      2. 50 |
    2. 51 | 52 | Strengths and weaknesses of overlay “widgets” 53 | 54 |
      3. 55 |
    3. 56 | 57 | Strengths and weaknesses of automated repair 58 | 59 |
      4. 60 |
    4. 61 | 62 | Fitness for achieving compliance with accessibility standards 63 | 64 |
      5. 65 |
    5. 66 | In their own words
      6. 67 |
    6. 68 | Conclusion 69 |
      7. 70 |
    7. 71 | 72 | Statement from sponsors and signatories to this fact sheet 73 | 74 |
      8. 75 |
    8. Additional Reading
      9. 76 |
    77 |
    78 |
    79 |
    80 |
    81 |

    82 | Introduction, definition, and history of web accessibility overlays 83 |

    84 |

    85 | Overlays are a broad term for technologies aimed at improving the 86 | accessibility of a website by applying third-party source code (typically 87 | JavaScript) to make improvements to the front-end code of the website. 88 |

    89 |

    Website add-on products purporting to improve accessibility go back to the 90 | late 1990s with products like Readspeaker 91 | and Browsealoud. Both 92 | of which added text-to-speech capabilities to the website(s) on which they 93 | were installed.

    94 |

    Later, similar products came to market that added additional tools to 95 | their software that allow user-based control of things like font-sizes and 96 | changes to the web pages colors so that contrast is improved. Products like 97 | Userway, EqualWeb, AudioEye, User1st, MaxAccess, FACIL'iti, and accessiBe fall into this category. 98 | These products are sometimes also white labelled under additional names.

    99 | 100 |

    101 | Strengths and weaknesses of overlay “widgets” 102 |

    103 |

    104 | Overlay widgets are unnecessary and are poorly placed in the 105 | technology stack. 106 |

    107 |

    As stated above, some overlay products contain widgets which present a 108 | series of controls that modify the presentation of the page they're on. 109 | Depending on the product, those changes may do things like change the page 110 | contrast, enlarge the size of the page's text, or perform other changes to 111 | the page that are intended to improve the experience for users with 112 | disabilities.

    113 |

    To laypersons, these features may seem beneficial, but their practical 114 | value is largely overstated because the end users that these features claim 115 | to serve will already have the necessary features on their computer, either 116 | as a built-in feature or as an additional piece of software that the user 117 | needs to access not only the Web but all software.

    118 |

    On this latter point, it is a mistake to believe that the features 119 | provided by the overlay widget will be of much use by end users because if 120 | those features were necessary to use the website, they'd be 121 | needed for all websites that the user interacts with. Instead, the widget is  122 | as—at best—redundant functionality with what the user already has.

    123 | 124 |

    125 | Strengths and weaknesses of automated repair 126 |

    127 |

    128 | While some automated repair is possible, customers should be 129 | discouraged from using an overlay as a long-term solution. 130 |

    131 |

    Some overlay products have capabilities aimed at providing accessibility 132 | repairs to the underlying page on which the overlay is added. These repairs 133 | are applied when the page loads in the user's browser.

    134 |

    While it is true that a non-trivial array of accessibility problems can be 135 | repaired in this manner, the nature, extent, and accuracy of such repair are 136 | limited by a number of important factors:

    137 |
      138 |
    • Automated application of text alternatives for images is not 139 | reliable 140 |
      • 141 |
    • Automated repair of field labels, error management, error handling, and 142 | focus control on forms is not reliable 143 |
      • 144 |
    • Automated repair of keyboard access is not reliable
      • 145 |
    • Modern, component-based user interfaces, such as those using ReactJS, 146 | Angular, or Vue may change the state of all or some of the underlying page 147 | independently of the overlay, rendering it unable to fix those 148 | JavaScript-driven changes to content. 149 |
      • 150 |
    • Repairs to the page can either slow down page load times or cause 151 | unexpected page changes for assistive technology users. 152 |
      • 153 |
    154 | 155 |

    In addition to the above, overlays do not repair content in Flash, Java, 156 | Silverlight, PDF, HTML5 Canvas, SVG, or media files.

    157 |

    An additional class of product exists, which only perform automated 158 | repairs and are marketed as a temporary solution. These include Amaze by 159 | Deque Systems, Alchemy by Level Access, and Sentinel by Tenon. 160 |

    For purposes of this document, these products aren't considered to be in 161 | the same class of product as the overlays that provide widgets. The most 162 | notable difference, beyond the lack of a “widget” is that Amaze, 163 | Alchemy, and Sentinel are understood by their manufacturers as being intended 164 | for use as an interim solution.

    165 | 166 |

    167 | Fitness for achieving compliance with accessibility standards 168 |

    169 |

    While the use of an overlay may improve 170 | compliance with a handful of provisions in major accessibility standards, 171 | full compliance cannot be achieved with an overlay.

    172 |

    Among the many claims made by overlay vendors is the claim that the use of 173 | their product will being the site into compliance with accessibility 174 | standards such as WCAG 2.x, related and derivative standards, and laws that 175 | mandate compliance with those standards.

    176 | 177 |
    178 | Conformance to a standard means that you meet or satisfy the 179 | ‘requirements’ of the standard. In WCAG 2.0 the 180 | ‘requirements’ are the Success Criteria. To conform to WCAG 2.0, you need 181 | to satisfy the Success Criteria, that is, there is no content which 182 | violates the Success Criteria. 183 | 184 | Understanding 185 | WCAG 2.0: Understanding Conformance 186 | 187 |
    188 | 189 |

    Given that conformance is defined as meeting all 190 | requirements of the standard, these products' documented inability to repair 191 | all possible issues means that they cannot bring a website into compliance. 192 | Products marketed with such claims should be viewed with significant 193 | scepticism.

    194 |
    195 | 196 |
    197 |
    198 |

    In their own words

    199 |

    200 | Many users with disabilities have expressed strong words of 201 | dissatisfaction with overlay products. As shown below, overlays 202 | themselves may have accessibility problems significant enough for users 203 | to take steps to actively block overlays from appearing at all. 204 |

    205 |

    Please note: while this section may mention specific vendors, these 206 | comments are par-for-the-course when it comes to the user experience 207 | provided by overlay widgets which have, in themselves, a pattern of 208 | negatively impacting the user experience.

    209 |
    210 | 211 |
    212 |
    213 | ...assuming your tool can do a good job making something accessible, it can 214 | do an even better job making something accessible running directly on the 215 | user's machine having access to machine code and machine APIs 216 | 217 | DerekRiemer 218 | 219 |
    220 | 221 |
    222 | ...I finally managed to gain access to my @NameCheap account by blocking 223 | #AccessiBe in my Windows Hosts file. I should not need to do this to use 224 | the Internet. AccessiBe needs to AccessiBeGone 225 | 226 | WilfSplodNokit 227 | 228 |
    229 | 230 |
    231 | ...I know with 100% certainty, any site which has deployed an overlay in 232 | the past year and a half has been less useable for both my wife and 233 | me—both blind. 234 | 235 | GeauxEnder 236 | 237 |
    238 | 239 |
    240 | ...Still a pain to even try reading the article on a mobile device 241 | because of the constant interruption every few seconds. Considering 242 | every site using your service also has this problem… Nope. 243 | 244 | Big_D01 245 | 246 |
    247 | 248 |
    249 | ...Making a webpage accessible does take work, and simply telling a 250 | business they can install your plugin is absolutely foolish, you build, 251 | and design accessibility in to a webpage using WCAG standards. 252 | 253 | w9fyi 254 | 255 |
    256 | 257 |
    258 | ...Suggesting one line of code is cheap so you should do it by inference 259 | suggests disabled lives aren't worth investing in either. #a11y 260 | 261 | Kevmarmol_CT 262 | 263 |
    264 | 265 |
    266 | @AccessiBe Just to demonstrate my good faith, here's a quick free audit 267 | of https://t.co/1mQGCCtnIs. You capture "tab" which is the 268 | standard way to navigate. There's no way to not enable your overlay if 269 | I want to navigate the page. Once the overlay is enabled, wild things 270 | happen. 271 | 272 | eluberoff 273 | 274 |
    275 | 276 |
    277 | #AccessiBe makes sites harder to use by getting in the way of browsing 278 | and changing access barriers on a page, not fixing them. A student and I 279 | came across an "enhanced" website and to my shame, we left 280 | because navigating that mess was beyond my skills, on that day. 281 | 282 | turtlecatpurrz 283 | 284 |
    285 | 286 |
    287 | Accessibility overlays are not the answer, and AccessiBe is no exception. 288 | As a screen reader user, numerous sites have become less usable for me 289 | with this overlay. Discrediting reputable accessiblity professionals and 290 | advocates will not sway me on this view. https://t.co/ZgFt8JtsbZ 291 | 292 | SingingTigress 293 | 294 |
    295 | 296 |
    297 | An die Screen Reader nutzenden Follower: Vielleicht habt ihr schon von 298 | #Accessibe gehört, einem Overlay, das behauptet, Seiten, in denen es 299 | eingebunden ist, zugänglicher zu machen. Ich möchte nicht näher ins 300 | Detail gehen. Kurz gesagt: Kompletter Blödsinn. Finger weg! 301 | 302 | MarcoZehe 303 | 304 |
    305 | 306 |
    307 | Automated solutions which promise to make your site accessible can't. It 308 | takes more than automation to achieve this requirement. You won't be safe 309 | from liability. you will almost assuredly negatively impact your 310 | customers with disabilities. 311 | 312 | twithoff 313 | 314 |
    315 | 316 |
    317 | Every time I go on a website and I hear the #accessiBe notification that 318 | this site is adjusted to my screen reader, I know that my blocker isn't 319 | working properly, and I'm in for a hellish experience on that particular website. 320 | https://t.co/ZFzKMfUe0t 321 | 322 | BorrisInABox 323 | 324 |
    325 | 326 |
    327 | I tried using this @AccessiBe site with VoiceOver in Chrome on iOS. 328 | The 4-star rating is announced as "unpronounceable" 329 | 🤦‍♀️ https://t.co/f4MxQ2eLLP" 330 | 331 | racheleditullio 333 | 334 |
    335 | 336 |
    337 | I wrote an email to their customer service detailing that I can not use 338 | their site due to the overlay, but… I really am disappointed, but I hope 339 | they listen. @Goodfair_ - please stop using AccessiBe. 340 | 341 | kit_flowerstorm 343 | 344 |
    345 | 346 |
    347 | I'm not an accessibility expert, just a screen reader user with decent 348 | skills telling you that this thread is spot on and my experience with 349 | #AccessiBe is that it makes sites with accessibility issues even harder 350 | to work around. https://t.co/cfyrEqXwTy 351 | 352 | atfarnum 353 | 354 |
    355 | 356 |
    357 | ...If you are blind or low vision and rely on assistive technologies like 358 | screen readers, you may have begun finding popular websites becoming less 359 | usable… this page describes how to ban AccessiBe from ever reaching your 360 | computer… https://t.co/qbiKvolizS 361 | 362 | smartudlab 363 | 364 |
    365 | 366 |
    367 | OK, this seems very wrong to me. A local chain here named Fleet Farm is 368 | now using AccessiBe. It makes a mess of the search for location feature. 369 | This is what I now get on the start of the result page. 370 | 371 | kellylford 372 | 373 |
    374 | 375 |
    376 | Thank goodness Firefox blocks their accessibility detection. For me, 377 | focus jumps all over the place with #AccessiBe enabled. When it's 378 | disabled, it behaves itself. 379 | 380 | mhorspool 381 | 382 |
    383 | 384 |
    385 | There are 0 automated tools that can tetect accessibility problems 386 | accurately at anything above 30% of the time. 0. This is commonly known 387 | by anyone who's been in this space for at least a week. #AccessiBe 388 | 389 | cswordpress 390 | 391 |
    392 | 393 |
    394 | There's a perfectly practical tool for making websites accessible. It's 395 | called a programmer. The needs that matter in making a website accessible 396 | are those of the users. If you can't meet those, then you can't meet the 397 | basic costs of doing business. 398 | 399 | WTBDavidG 400 | 401 |
    402 | 403 |
    404 | When #AccessiBe is enabled, the page is flooded with headings. Lots of 405 | heading level 2's. The title of each phone remains a heading in both 406 | versions of the page, but with it enabled, things like cost, display, and 407 | all the other components of the tables become headings as well. 408 | 409 | CatchTheseWords 411 | 412 |
    413 |
    414 |
    415 | 416 |
    417 |

    418 | Conclusion 419 |

    420 |

    421 | No overlay product on the market can cause a website to become fully 422 | compliant with any existing accessibility standard and therefore cannot 423 | eliminate legal risk. 424 |

    425 |

    Accessibility on the Web is a big challenge, both for owners of websites 426 | and for the users of those websites. The invention of novel approaches to 427 | resolving this challenge is to be commended.

    428 |

    However, in the case of overlays—especially those which attempt to add 429 | widgets that present assistive features—the challenge is not being met. Even 430 | more problematic are the deceptive marketing provided by some overlay 431 | vendors who promise that implementing their product will give their 432 | customer's sites immediate compliance with laws and standards.

    433 |

    The ineffectiveness of overlays is something that has broad agreement among 434 | accessibility practitioners, per the WebAIM Survey of Web Accessibility Practitioners 435 | which found:

    436 |
    A strong majority (67%) of respondents rate these tools as not at all or not very effective. Respondents with disabilities were even less favorable with 72% rating them not at all or not very effective, and only 2.4% rating them as very effective.
    437 |

    438 | Statement from sponsors and signatories to this fact sheet 439 |

    440 |

    As a result of the above information:

    441 |
      442 |
    1. We will never advocate, recommend, or integrate an overlay which 443 | deceptively markets itself as providing automated compliance with laws 444 | or standards. 445 |
      2. 446 |
    2. We will always advocate for the remediation of accessibility issues at 447 | the source of the original error. 448 |
      3. 449 |
    3. We will refuse to stay silent when overlay vendors use deception to 450 | market their products. 451 |
      4. 452 |
    4. More specifically, we hereby advocate for the removal of accessiBe, 453 | AudioEye, UserWay, User1st, MK-Sense, MaxAccess, FACIL'iti, and all similar products and 454 | encourage the site owners who've implemented these products to use more 455 | robust, independent, and permanent strategies to making their sites 456 | more accessible. 457 |
      5. 458 |
    459 |
    460 | 461 |
    462 |

    Signed by:

    463 | 466 |
      467 |
    1. Karl Groves, Founder and President, Tenon.io
      2. 468 |
    2. Bill Dengler, totally blind computer science student and code contributor to the NVDA screen reader, Swarthmore College, Philadelphia
      3. 469 |
    3. Nicolas Steenhout, Independent accessibility consultant
      4. 470 |
    4. Rian Rietveld, web accessibility specialist, Level Level
      5. 471 |
    5. Weston Thayer, Founder, Assistiv Labs
      6. 472 |
    6. Denis Boudreau, Accessibility consultant
      7. 473 |
    7. Meryl K. Evans, accessibility advocate
      8. 474 |
    8. Makoto Ueki, Web accessibility consultant, Infoaxia
      9. 475 |
    9. Michael Spellacy, Accessibility Consultant
      10. 476 |
    10. Helen Burge, Accessibility Consultant
      11. 477 |
    11. Léonie Watson, Director, TetraLogical
      12. 478 |
    12. Eric Eggert, Co-Founder, outline
      13. 479 |
    13. Dale Reardon - Founder & CEO of TravelForAll.Guide
      14. 480 |
    14. Jason Gill - Certified Web Accessibility Specialist
      15. 481 |
    15. Michael Ausbun, CPWA, Accessibility Specialist
      16. 482 |
    16. Ronny Hendriks - Accessibility Consultant, Toegankelijk Online
      17. 483 |
    17. Charles Hall, Senior Accessibility Designer, CVS Health
      18. 484 |
    18. Hai Nguyen Ly, Accessibility Advocate
      19. 485 |
    19. David Luhr, Accessibility Consultant
      20. 486 |
    20. Justin L. Yarbrough, Accessibility Specialist, Rio Salado College
      21. 487 |
    21. Hidde de Vries, accessibility specialist and front-end developer
      22. 488 |
    22. James Fleeting, Technical Director, Monkee-Boy
      23. 489 |
    23. Alex Tait, Accessibility Specialist, AT Fresh Solutions
      24. 490 |
    24. Michael Fairchild, Accessibility consultant
      25. 491 |
    25. Gijs Veyfeyken, web accessibility specialist, Five Oaks
      26. 492 |
    26. Dennis Lembree, Web Axe & Easy Chirp
      27. 493 |
    27. Adrian Roselli
      28. 494 |
    28. Rob Whiting, Head of Research & Design, Merlan Ltd.
      29. 495 |
    29. Kitty Giraudel, Accessibility Specialist, Gorillas
      30. 496 |
    30. Derek Mohr, Front-end Developer, Mighty in the Midwest
      31. 497 |
    31. Alastair Campbell, Director of Accessibility, Nomensa
      32. 498 |
    32. Anders Fredericksen, Level Access
      33. 499 |
    33. Zoë Bijl, Senior Accessibility Engineer, CrowdStrike
      34. 500 |
    34. Jonathan Avila, Level Access
      35. 501 |
    35. Sheri Byrne-Haber, Senior accessibility evangelist
      36. 502 |
    36. Jared Smith, Associate Director, WebAIM
      37. 503 |
    37. Kazuhito Kidachi
      38. 504 |
    38. Yakim van Zuijlen, Designer
      39. 505 |
    39. Shannon Urban, Director of Accessibility, EVERFI
      40. 506 |
    40. Todd Libby, Accessibility Advocate and Consultant
      41. 507 |
    41. David Monnehay, Atalan
      42. 508 |
    42. Joschi Kuphal, CPWA & CEO, tollwerk
      43. 509 |
    43. Romain Deltour, web/accessibility/ebook specialist
      44. 510 |
    44. Craig Francis, Code Poets Limited
      45. 511 |
    45. Erik Gustafsson, Accessibility Specialist, Axess Lab
      46. 512 |
    46. Dan Payne, Accessibility consultant
      47. 513 |
    47. Ben Tillyer
      48. 514 |
    48. Matt Obee, Senior Product Designer and accessibility specialist, NearForm
      49. 515 |
    49. Florian Beijers, Accessibility Consultant, Developer, Screenreader User
      50. 516 |
    50. Donna Vitan, Design Systems Nerd
      51. 517 |
    51. Ruben Nic, Web Accessibility/Senior Engineer, Webflow
      52. 518 |
    52. Dennis Deacon, Accessibility Consultant
      53. 519 |
    53. Nicolas Loye, CTO, Actency
      54. 520 |
    54. Rachele DiTullio, accessibility engineer, CPWA
      55. 521 |
    55. Gerard K. Cohen, self
      56. 522 |
    56. Dr. Kate Deibel, Inclusion and Accessibility Librarian, Syracuse University Libraries
      57. 523 |
    57. Vincent Aniort, digital accessibility expert, Orange SA
      58. 524 |
    58. Arthur Rigaud, Accessibility Specialist and Front-End Developer
      59. 525 |
    59. Gary Jones, WordPress VIP
      60. 526 |
    60. Andrew Nevins, CPWA, Front-end developer
      61. 527 |
    61. Chris Heilmann, Principal Product Manager for Developer Tools
      62. 528 |
    62. Bruce Lawson, greedy accessibility consultant
      63. 529 |
    63. Peter Goes, Front-end developer, De Voorhoede
      64. 530 |
    64. Geoff Mortstock, Accessibility Consultant
      65. 531 |
    65. Marcus Herrmann, Web Accessibility Specialist and front-end developer
      66. 532 |
    66. Kelly Childs, Lead Developer, Be Accessible, Inc.
      67. 533 |
    67. Matthew Hallonbacka
      68. 534 |
    68. Kelly Wills, Access Technology Specialist, CPWA
      69. 535 |
    69. Joan Preston, Web Accessibility Coordinator, California State University, Long Beach
      70. 536 |
    70. Jon Gibbins, digital accessibility consultant, Dotjay Ltd
      71. 537 |
    71. Alicia Jarvis
      72. 538 |
    72. Anthony Fernando, CPWA, Accessibility QA Manager, Pearson
      73. 539 |
    73. Jennifer Strickland, Senior HCD + Accessibility Engineer at MITRE, Accessibility Consultant at Level Access
      74. 540 |
    74. Lainey Feingold - lawyer and author, Law Office of Lainey Feingold
      75. 541 |
    75. Andrew Hayward, Accessibility Engineer
      76. 542 |
    76. Jean Ducrot, Accessibility Engineer, CPWA
      77. 543 |
    77. Manuel Razzari - Accessibility educator, Buenos Aires National Technological University, Argentina
      78. 544 |
    78. Zack Kline, Accessibility Tester, ISoftStone
      79. 545 |
    79. Anna E. Cook - Senior Product Designer and Accessibility Specialist
      80. 546 |
    80. Christophe Strobbe, researcher and lecturer in HCI and accessibility, Stuttgart Media University
      81. 547 |
    81. Eric Bailey, The A11Y Project Maintainer
      82. 548 |
    82. Andre Polykanine, software engineer, web accessibility specialist, screen reader user
      83. 549 |
    83. Ben Myers, Software Engineer
      84. 550 |
    84. Eric Bednarz, self
      85. 551 |
    85. Olivier Keul, Accessibility consultant, Temesis
      86. 552 |
    86. Bogdan Cerovac, WAS, front-end developer and accessibility lead
      87. 553 |
    87. Lori Samuels, Accessibility Director, NBCUniversal
      88. 554 |
    88. Ryan Leisinger - UX Manager Department of Licensing WA State
      89. 555 |
    89. Ian Lloyd, Accessibility Engineer
      90. 556 |
    90. Pavel Pomerantsev, web accessibility engineer, Squarespace
      91. 557 |
    91. Dominik Wilkowski, People Director, Thinkmill
      92. 558 |
    92. Rowdy Rabouw, web and app developer, double-R webdevelopment
      93. 559 |
    93. Jen Smith, Accessibility Program Manager, Microsoft
      94. 560 |
    94. Toufic Sbeiti, accessibility advocate
      95. 561 |
    95. Amy Carney, CPWA, accessibility consultant & front-end web developer, Digilou
      96. 562 |
    96. Carly Gerard CPWA, Web Accessibility Engineer, Western Washington University
      97. 563 |
    97. Haben Girma, Human Rights Lawyer
      98. 564 |
    98. Katriel Paige, Accessibility Consultant, Fox Design Studios LLC
      99. 565 |
    99. Adrianne Mallett, Software Engineer
      100. 566 |
    100. Krista Greear
      101. 567 |
    101. Kim Krause Berg, CPACC Accessibility and UX Consultant
      102. 568 |
    102. Joseph Dolson
      103. 569 |
    103. Ashley Hannan, Accessibility Advocate
      104. 570 |
    104. Cara Hall, Accessibility Advocate
      105. 571 |
    105. Paul Grenier, Web Developer
      106. 572 |
    106. Glenda Sims, Accessibility consultant
      107. 573 |
    107. JF Hector Labram, WAS, Principal Front-End Engineer, Kooth Plc
      108. 574 |
    108. Anne-Mieke Bovelett, Accessibility Advocate
      109. 575 |
    109. Radimir Bitsov, Web Accessibility and Performance Engineer
      110. 576 |
    110. Beatriz González Mellídez, Principal Product Design, CPWA, CPUX-RE
      111. 577 |
    111. Wilfred Nas, Product Owner / User interface consultant
      112. 578 |
    112. Shawn Thompson, Digital Accessibility Advocate
      113. 579 |
    113. Kim Johannesen, CEO and Accessibility Consultant, Shift ApS
      114. 580 |
    114. Marco Hengstenberg, Front End Web Developer and Accessibility Consultant
      115. 581 |
    115. Nicola Saunders, Front-End Developer, Studio 24 Ltd 582 |
    116. Rogier Barendregt, Senior digital product designer, Rg/B
      117. 583 |
    117. Jeremy Keith, Founder, Clearleft
      118. 584 |
    118. Kasper Isager, Software Developer
      119. 585 |
    119. Angela P. Ricci, Web Designer/ Front dev
      120. 586 |
    120. Matt Jiggins, Developer/Designer
      121. 587 |
    121. Stefan Wajda, LepszyWeb.pl, digital accessibility specialist
      122. 588 |
    122. Sina Bahram, President, Prime Access Consulting, Inc.
      123. 589 |
    123. Kristina England, Accessibility Specialist, University of Massachusetts President's Office
      124. 590 |
    124. Birkir Gunnarsson, CPWA, digital accessibility lead
      125. 591 |
    125. Kerstin Probiesch, Accessibility Consultant
      126. 592 |
    126. Radek Pavlíček, CPWA, Accessibility Specialist, Teiresias Centre Masaryk University & Poslepu.cz
      127. 593 |
    127. Billy Gregory, TPGi
      128. 594 |
    128. Thomas Logan
      129. 595 |
    129. Brian Elton, Accessibility Engineer/Consultant
      130. 596 |
    130. Kevin Mar-Molinero, Director of Experience Technologies Kin+Carta Connect, Member of BIMA Inclusive Design Council.
      131. 597 |
    131. Crystal Preston-Watson, Quality and Accessibility Engineer
      132. 598 |
    132. Bob Dodd, Accessibility Consultant
      133. 599 |
    133. Chauncey McAskill
      134. 600 |
    134. David Swallow, Accessibility Engineer
      135. 601 |
    135. Marko Milanović, Developer, Tenon.io
      136. 602 |
    136. Joe Lamyman, Development Specialist
      137. 603 |
    137. Kevin Ackley, Accessibility Tech Consultant
      138. 604 |
    138. Stephen Clower, Software Developer and Accessibility Lead, Desmos, Inc.
      139. 605 |
    139. Nicolas Chardon, Digital Accessibility Expert
      140. 606 |
    140. Steve Faulkner, Chief Accessibility Officer, TPGi
      141. 607 |
    141. Andy Bell, Designer and Educator
      142. 608 |
    142. Patrick H. Lauke, Accessibility Trash Panda
      143. 609 |
    143. Yann Kozon, Front End Web Developer and Accessibility Consultant, Freelance
      144. 610 |
    144. Chris Taylor, Web Nerd, Yorkshire Twist
      145. 611 |
    145. Miriam Suzanne, Agency Co-Founder & W3C Invited Expert
      146. 612 |
    146. Robert Jolly, Product Manager & Accessibility Strategist
      147. 613 |
    147. Lena Chandelier, Accessibility Expert, Front-end Developer
      148. 614 |
    148. Thomas Parisot, Old Timey Web Developer
      149. 615 |
    149. Jesse Menn, Principal Web Developer
      150. 616 |
    150. Wendy Reid, Accessibility Lead
      151. 617 |
    151. Scott O'Hara, Accessibility Engineer/Consultant
      152. 618 |
    152. Phil Springall
      153. 619 |
    153. Dr Carl Myhill, Director, User Experience Design Limited
      154. 620 |
    154. Sumner M. Davenport, Specialist Web Accessibility
      155. 621 |
    155. Dana Byerly, Interaction Designer
      156. 622 |
    156. Jamie Knight, self
      157. 623 |
    157. Matt Richardson, Web Accessibility Expert
      158. 624 |
    158. Josephine Schwebler, Senior Consultant Accessibility / Accessible Documents
      159. 625 |
    159. Vegard Haugstvedt, Front-end Developer / Accessibility Specialist, Webstep
      160. 626 |
    160. Mikołaj Rotnicki, http://a11y.report, accessibility specialist
      161. 627 |
    161. William Bunch - Accessibility Consultant
      162. 628 |
    162. Kris Rivenburgh, Chief Accessibility & Legal Officer, Essential Accessibility
      163. 629 |
    163. Paul Kruczynski, Front-End UX/UI Developer
      164. 630 |
    164. Matthias Weston, Accessibility-Centered Freelance Developer
      165. 631 |
    165. Mat Harris, Accessibility Consultant, Level Access
      166. 632 |
    166. Lindsey Dragun, Developer / Accessibility Advocate
      167. 633 |
    167. Michail Yasonik, Senior Software Engineer
      168. 634 |
    168. Marcy Sutton, Independent Web Developer and Accessibility Specialist
      169. 635 |
    169. Talita Pagani, Accessibility and UX Consultant, Research Scientist in Web Accessibility for Neurodiversity
      170. 636 |
    170. Aaron Chu, UI Engineer + Disability & Design Researcher
      171. 637 |
    171. Adam Saucier, Web Accessibility Specialist
      172. 638 |
    172. Arnaud Delafosse, Web Quality & Accessibility Consultant, Temesis
      173. 639 |
    173. J.J. Meddaugh, Owner, A. T. Guys.
      174. 640 |
    174. Nicki Rios, CPWA, Founder, Accessibility Consultant & Engineer, Nock & Sparrow
      175. 641 |
    175. John E Brandt, head dude, jebswebs
      176. 642 |
    176. Heather Gray, Website Developer
      177. 643 |
    177. Santina Croniser, Senior Accessibility Engineer, VMware
      178. 644 |
    178. Stein Erik Skotkjerra, Accessibility consultant, CEO, Inklusio
      179. 645 |
    179. Bruno Pulis, Accessibility Advocate, Creator of Awesome A11y
      180. 646 |
    180. Brittany Roots, Accessibility Consultant
      181. 647 |
    181. James Nurthen, Accessibility Engineer & co-chair ARIA Working Group
      182. 648 |
    182. Shell Little, Inclusive Design Lead and Digital Accessibility Specialist
      183. 649 |
    183. Carlos Eriksson, Accessibility Lead, Studio 24
      184. 650 |
    184. Steven Mouret, Digital Accessibility Expert
      185. 651 |
    185. Adam Page, UX Designer
      186. 652 |
    186. David A. Kennedy, Designer and Accessibility Weekly curator
      187. 653 |
    187. Marc Solomon, self
      188. 654 |
    188. Ron Stauffer, Founder, Lieder Digital
      189. 655 |
    189. Nick Caskey, CPWA & Senior Accessibility Engineer, VMware Inc.
      190. 656 |
    190. Devon Persing, Technical Program Manager and Digital Accessibility Specialist
      191. 657 |
    191. Brian Olore, Developer
      192. 658 |
    192. Kathleen McMahon, Engineer, Designer, and Speaker
      193. 659 |
    193. Will Slone, Accessibility Engineer
      194. 660 |
    194. Peter Weil, Web Developer
      195. 661 |
    195. Brennan Young, Accessibility specialist, Laerdal Medical
      196. 662 |
    196. Emanuela Gorla, Accessibility Specialist, TetraLogical
      197. 663 |
    197. Paweł Choiński, Front-End Developer
      198. 664 |
    198. Eric Hind, Accessibility Specialist
      199. 665 |
    199. Sylvie Duchateau, Web Accessibility Consultant, Access42
      200. 666 |
    200. Rachel Cherry, Accessibility Specialist, Director of WPCampus, and Director of Technology and Design, Equal Made
      201. 667 |
    201. Lucy Greco, Accessaces
      202. 668 |
    202. John Lukosky, Accessibility Specialist
      203. 669 |
    203. Jennifer Grant, Senior Accessibility Engineer, Educational Testing Service
      204. 670 |
    204. Károly Szántai, WAS
      205. 671 |
    205. Sarah E. Lynch, Accessibility Engineer
      206. 672 |
    206. L. Jeffrey Zeldman
      207. 673 |
    207. Paul Shryock, WordPress Engineer, NBA
      208. 674 |
    208. Nick Colley
      209. 675 |
    209. Carlin Scuderi, Front End Developer
      210. 676 |
    210. Nicolas Zerr, Digital Accessibility Expert
      211. 677 |
    211. Derek Featherstone, Chief Experience Officer, Level Access
      212. 678 |
    212. Corey Megown, Front-End Developer
      213. 679 |
    213. Marcelo Sales, Accessibility Specialist, RD (Raia Drogasil)
      214. 680 |
    214. Scott Vinkle, Accessibility Specialist, Shopify
      215. 681 |
    215. Barry Pollard, Developer
      216. 682 |
    216. Anand Chowdhary, Creative Technologist & Entrepreneur
      217. 683 |
    217. Christian Alden Jacobs, UX Strategist
      218. 684 |
    218. Edward Pritchard, Digital Accessibility Consultant
      219. 685 |
    219. Hadley Luker, Accessibility Analyst, Level Access
      220. 686 |
    220. John Foliot (JF), Independent Accessibility Specialist / W3C Contributor
      221. 687 |
    221. Cullan Bonilla, Accessibility Specialist
      222. 688 |
    222. EJ Mason, Accessibility Specialist
      223. 689 |
    223. Michele Williams, Accessibility and UX Consultant
      224. 690 |
    224. Hala Anwar, Inclusive Design Consultant
      225. 691 |
    225. Johnny Taylor, Accessibility Advocate
      226. 692 |
    226. Joel McKinnon, Accessibility Specialist
      227. 693 |
    227. Olivier Nourry, General Manager & CAO, Be Player One
      228. 694 |
    228. Ross Mullen, Director, CANAXESS
      229. 695 |
    229. Steve Woodson, Developer
      230. 696 |
    230. Joe Yang, Senior UX Designer – Accessibility, ServiceNow
      231. 697 |
    231. Lee Bartholomew, Website Designer
      232. 698 |
    232. Amanda J. Rush, Self
      233. 699 |
    233. John H. Carson Jr., retired escalations specialist, Freedom Scientific
      234. 700 |
    234. Ka Li, Accessibility Consultant
      235. 701 |
    235. Adele M. Beeby, Web Manager, Leicester City Council
      236. 702 |
    236. James Scholes, Director of Digital Accessibility, Prime Access Consulting, Inc.
      237. 703 |
    237. Ian Kersey, Accessibility Analyst, Level Access
      238. 704 |
    238. Aaron Gustafson, Web Standards & Accessibility Advocate
      239. 705 |
    239. Wally Zielinski, WAS, Dell Technologies
      240. 706 |
    240. Martin Mengele, Front End Developer & Accessibilty Consultant, @accessabilly)
      241. 707 |
    241. Gaël Poupard, Lead dev, OnePoint
      242. 708 |
    242. Philip Kiff, D4K Communications
      243. 709 |
    243. Tim Kraut, Senior Frontend Developer, AWESOME! Software GmbH
      244. 710 |
    244. Jennifer Panighetti, Web Developer
      245. 711 |
    245. Jasmine Kaul, Founder and Digital Content Consultant, Happy Words
      246. 712 |
    246. Ian Hamilton, accessibility specialist
      247. 713 |
    247. Margie Chubin, Software Engineer
      248. 714 |
    248. Joe Lanman, Designer
      249. 715 |
    249. Jude Robinson, Global Head of Frontend Development, Springer Nature
      250. 716 |
    250. Luc Poupard, Front-end designer and WordPress developer, Proton Technologies
      251. 717 |
    251. David Sloan, UX Research Lead, TPGi
      252. 718 |
    252. Grady Thompson, Student, University of Washington
      253. 719 |
    253. Claudio Luis Vera, Accessibility leader, analyst, and public speaker
      254. 720 |
    254. Emmanuelle Gutiérrez y Restrepo, Fundación Sidar - Acceso Universal
      255. 721 |
    255. Homer Gaines, UI Engineer, and Accessibility Specialist
      256. 722 |
    256. Carolina Aguilera, Accessibility Consultant, Chile
      257. 723 |
    257. Kara Franco, CPWA, Accessibility Engineer
      258. 724 |
    258. Sarah Higley, Accessibility Specialist & Software Developer
      259. 725 |
    259. Benoît Dequick, Front-end dev & RGAA expert
      260. 726 |
    260. Peter Bossley, self
      261. 727 |
    261. Jennifer Gorfine, UX Engineer & Web Accessibility Specialist
      262. 728 |
    262. Heather Migliorisi, Web Accessibility Specialist
      263. 729 |
    263. Thinh-Lay Wonesky, Accessibility Consultant, Allerlay Wonesky Media
      264. 730 |
    264. Robert Kingett, Blind author
      265. 731 |
    265. Frances Jurek, Software Engineer
      266. 732 |
    266. Owen Edwards, Principal Accessibility Consultant, Level Access
      267. 733 |
    267. Jennifer Zhang, Senior Accessibility Program Manager, Microsoft
      268. 734 |
    268. Michael Vaughn, Accessibility Manager
      269. 735 |
    269. Desiree White
      270. 736 |
    270. Marco Salsiccia, Accessibility Specialist, Lyft
      271. 737 |
    271. Carter Temm, Accessibility Consultant
      272. 738 |
    272. Silvia Ceria, Interior Designer and Content Creator, DforDesign
      273. 739 |
    273. Maurizio Lepora, Full-Stack Developer, Lemaur
      274. 740 |
    274. Jared Clayton, Digital Accessibility Specialist
      275. 741 |
    275. Dirk Ginader, UX Engineer, Google
      276. 742 |
    276. Cordelia McGee-Tubb, Accessibility Engineer
      277. 743 |
    277. Ethan Marcotte, web designer, author of "Responsive Web Design"
      278. 744 |
    278. Jory Cunningham, Accessibility Engineer
      279. 745 |
    279. Lee White, Front-End & Accessibility Engineer
      280. 746 |
    280. Richard Boardman, Senior Director, Product Accessibility
      281. 747 |
    281. David Peter, Software Engineer
      282. 748 |
    282. Stefan Judis, Web Developer
      283. 749 |
    283. Dean Birkett, UX Designer & Accessibility Consultant
      284. 750 |
    284. Myles Lewando, Web Developer & Accessibility Specialist
      285. 751 |
    285. Michael Dowden, CEO, Andromeda Galactic Solutions, author of "Approachable Accessibility"
      286. 752 |
    286. Abdullah Norozi Iranzad, Web Developer
      287. 753 |
    287. Allison Ravenhall, Accessibility Consultant
      288. 754 |
    288. Ian Pouncey, Director, TetraLogical
      289. 755 |
    289. Chancey Fleet, Technology Educator
      290. 756 |
    290. Amanda Mace General Manager, Web Key IT
      291. 757 |
    291. Wendy Torres, Senior Instructional Technologist
      292. 758 |
    292. Janos Sitar, Web Accessibility Specialist, Central 1 Credit Union
      293. 759 |
    293. Dave Bahr, CEO of In-Sightful Living
      294. 760 |
    294. Momin Pasha Mohammed, CPWA, Accessibility Consultant
      295. 761 |
    295. Holly Scott-Gardner, usability assessor and disability rights advocate
      296. 762 |
    296. Sara Cousins, Mighty Spark Design
      297. 763 |
    297. Roger Fracé, Quality Assurance Specialist
      298. 764 |
    298. Pierre Albert, Accessibility consultant, Temesis
      299. 765 |
    299. Colleen Gratzer, Creative Boost and Gratzer Graphics LLC
      300. 766 |
    300. Kara Goldfinch
      301. 767 |
    301. Sally Thoun, Accessibility Consultant
      302. 768 |
    302. Ajaz Mohammed, Accessibility Test Consultant, HCL Canada Inc.
      303. 769 |
    303. Vincent Martin, Usercessible, LLC.
      304. 770 |
    304. Jessie Lorenz
      305. 771 |
    305. Amy Mason, Access Technology Specialist, San Francisco Lighthouse for the Blind
      306. 772 |
    306. Nadia Rasul, CPACC, Front-end Developer and Accessibility Lead
      307. 773 |
    307. Catherine M. Stager, Accessibility and Assistive Technology Specialist, Front Range Community College
      308. 774 |
    308. Avi Chandiramani, Program Manager for Accessible Technology Services, San Francisco State University
      309. 775 |
    309. Wink Harner Professor of Adaptive Technology In Higher Education/CUNY graduate school
      310. 776 |
    310. Annie Heckel, Lead Accessibility Auditor, Online ADA
      311. 777 |
    311. Courtney Heitman, Technical Accessibility Specialist
      312. 778 |
    312. Simon Bonaventure, Accessibility consultant, Empreinte Digitale
      313. 779 |
    313. Eric Wright
      314. 780 |
    314. Deborah Kaplan, Accessibility Lead, Suberic Networks
      315. 781 |
    315. Carie Fisher, Sr. Accessibility consultant, Deque
      316. 782 |
    316. Scott Boren, Accessibility manager
      317. 783 |
    317. Josie Davidson, Associate Accessibility Specialist
      318. 784 |
    318. Matt Campbell, Chief Technology Officer, Pneuma Solutions
      319. 785 |
    319. Quentin Bellanger, Front-end developer, /tmp
      320. 786 |
    320. Al Romano, Web Developer, Virtually(Creative)
      321. 787 |
    321. Derek Riemer, Frontend web application Developer, NVDA screen reader contributor
      322. 788 |
    322. Isabel Del Castillo, Digital Accessibility Consultant, Prime Access Consulting, Inc.
      323. 789 |
    323. Nic Chan, Front-End Developer
      324. 790 |
    324. Jeremy Neander, Senior Front End Engineer
      325. 791 |
    325. Nick Croft, Senior Full Stack Web Developer, WAS, CPACC, CPWA, 508 TT
      326. 792 |
    326. Dag Eikesdal, web developer & accessibility specialist
      327. 793 |
    327. Dylan M. Rafaty, Disability Rights Activist and Head of Accessibility Strategy & Partnerships at C-Hear, Inc.
      328. 794 |
    328. Randi Strunk, self
      329. 795 |
    329. Jörg Morsbach, anatom5
      330. 796 |
    330. Thomas Logan, Founder and CEO, Equal Entry
      331. 797 |
    331. Lindsay Reddick, self
      332. 798 |
    332. Mike Calvo, self
      333. 799 |
    333. Molly E. Holzschlag, Web Educator and Historian
      334. 800 |
    334. Armony Altinier, CEO & Accessibility Lead, Koena
      335. 801 |
    335. Olivier Camon, Web developer
      336. 802 |
    336. Liz Hare, PhD, Quantitative Geneticist, Dog Genetics LLC
      337. 803 |
    337. Luce Carević, Accessibility expert, Access42
      338. 804 |
    338. Roman Mkrtchian, Web developer, Koena
      339. 805 |
    339. Tori Clark, Accessibility Evangelist and Executive Director, Digital A11ies
      340. 806 |
    340. Sarah Jagrowski, Associate Product Designer, FiscalNote 807 |
    341. Jay Miles, Product Designer
      342. 808 |
    342. Benjamin Michoux, Front-end Engineer
      343. 809 |
    343. Daman Wandke, CEO/Founder, Wandke Consulting
      344. 810 |
    344. Laine Amoureux, CPWA, Independent Consultant, Amoureux AT Consulting
      345. 811 |
    345. Christian Vogler, Professor and Director, Technology Access Program, Gallaudet University
      346. 812 |
    346. Kevin Erickson, Accessibility Services Manager, Ablr
      347. 813 |
    347. Sanjay Nasta, CEO, Microassist
      348. 814 |
    348. Sue Brettell, Branding & UX Designer
      349. 815 |
    349. Steve Decker, self
      350. 816 |
    350. Fady Rizk, self
      351. 817 |
    351. Philip Fortier, Director, Perficient
      352. 818 |
    352. Natalie Stroud, self
      353. 819 |
    353. Kalib Watson, Accessibility Engineer II, Jackson
      354. 820 |
    354. Ryan Dudek, Software Engineer
      355. 821 |
    355. Eilana Benish, authorized Accessibility consultant from Israel
      356. 822 |
    356. Mohammad Suliman, blind master's degree computer science student, Tel Aviv University
      357. 823 |
    357. Shawn Hooper, Director of IT, Actionable.co
      358. 824 |
    358. Jim Allan, Accessibility Coordinator
      359. 825 |
    826 |

    827 | 828 | Add your name to this list 829 | 830 |

    831 |
    832 |
    833 | 834 | 929 | 930 | 931 | --------------------------------------------------------------------------------