Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a section: Alternatives to overlays? #36

Open
karlgroves opened this issue Mar 11, 2021 · 6 comments
Open

Add a section: Alternatives to overlays? #36

karlgroves opened this issue Mar 11, 2021 · 6 comments

Comments

@karlgroves
Copy link
Owner

No description provided.

@joedolson
Copy link

Are you thinking on broad terms (e.g., the types of issues overlay vendors tend to address and what other methods are available for that), or in terms of what the clients of overlays (site owners) should do instead of using overlays?

Case 1 example: An overlay provides a tool to enable high contrast; alternative is for end users to use their operating system's modes for high contrast.

Case 2 example: A site owner should ... remedy the problems. I guess. ;)

@karlgroves
Copy link
Owner Author

I'm thinking both?

@stringyland
Copy link
Collaborator

I think a list with a bit of detail would be good. With a range of options from minimal intervention to full on inclusive design.

Here's a draft, if folks feel like it works I'll make a pull request for it. If you have edit requests let me know and I'm happy to include them.


Alternatives to overlays
Since we don't recommend overlays, what do we recommend instead? Here are some options, beginning with free and low-effort and increasing in committment.

  • Use one of the free automated accessibility checkers and make the fixes it recommends for your site. This will only fix about 30% of the potential accessibility problems with your site, but it will not cost you anything except time and it will make improvements for several groups of people without creating problems for others. Most of the free automated audits include useful advice on how to fix the problems they find, but there are also many blog posts and tutorials available online.
  • Use one of the free accessibility tools which include a guided manual test as well as an automated check, and make the fixes it recommends for your site. You may not become 100% WCAG compliant but you will be able to address the majority of problems, which will make your site usable for a wide range of people with disabilities.
  • Build your own accessibility widgets to add to your site, such as a control to increase contrast or text size. You will need to employ a developer to do this, and preferably a designer as well. These can only address a small number of accessibility problems, and are unlikely to be used by people who have had a disability for some time. However, if your site's target audience is people who have recently acquired a disability it may be a useful introduction to what types of assistive technology are available.
  • Use one of the paid automated repair overlays. As mentioned in the automated repair section above, this can only be a short-term solution while you use one of our other recommended alternatives.
  • Hire an accessibility consultant to audit your site and recommend fixes. The consultant can then test your fixes and ensure that you are WCAG compliant.
  • Hire an accessibility consultant to train your staff in how to build accessible digital experiences for your customers.
  • Hire a UX designer to work with an accessibility expert to redesign your site in consultation with people with disabilities in your target market. Hire graphic designers and front-end developers who know how to build accessible websites which work for a wide range of people using a wide range of devices. This is the most time-consuming and expensive option, but guarantees the best results.

@mgifford
Copy link

I do think that personalization widgets can be a good thing. Whether that's controlling font size, turning off animations or switching between dark/lite modes. Yes, the browser & operating system can generally do all of that, but there are quite a few users who still don't have cut/paste keyboard controls memorized. IDRC has a good example of what is possible here https://docs.fluidproject.org/infusion/development/preferenceseditor

@mgifford
Copy link

@stringyland I'm thinking of a change to your suggestion above:

  • Find or build a widget that simply exposes more user options and add that to your site. Giving your users more options to control the personalization of your site is useful for many people who are not tech savvy. Being able to easily increase contrast or text size is useful. Tools like the Fluid UI Preference Editor supports this and other customizations, but you will likely need to employ a developer. To make it look intentional, might be good to hire a designer as well. These can only address some accessibility problems, and definitely are not sufficient on their own.

  • Use one of the paid automated repair overlays by reputable accessibility companies. As mentioned in the automated repair section above, this can only be a short-term solution while you use one of our other recommended alternatives.

@stringyland
Copy link
Collaborator

Thankyou @mgifford ! I've taken your suggestion and folded it in. Making the pull request now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants