-
Notifications
You must be signed in to change notification settings - Fork 496
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
Adding section Alternatives To Overlays #423
Open
stringyland
wants to merge
1
commit into
karlgroves:develop
Choose a base branch
from
stringyland:alternatives-to
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -64,6 +64,9 @@ <h2 id="toc">Table of contents</h2> | |
</li> | ||
<li> | ||
<a href="#in-their-own-words">In their own words</a></li> | ||
<li> | ||
<a href="#alternatives">Alternatives to overlays</a> | ||
</li> | ||
<li> | ||
<a href="#conclusion">Conclusion</a> | ||
</li> | ||
|
@@ -412,6 +415,19 @@ <h2 id="in-their-own-words">In their own words</h2> | |
</blockquote> | ||
</div> | ||
</div> | ||
<div class="container"> | ||
<h2 id="alternatives">Alternatives to overlays</h2> | ||
<p>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.</p> | ||
<ul> | ||
<li>Use one of the <strong>free automated accessibility checkers</strong> 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.</li> | ||
<li>Use one of the <strong>free accessibility tools</strong> 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.</li> | ||
<li><strong>Find or build a widget which exposes more user options</strong> 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.</li> | ||
<li>Use one of the <strong>paid automated repair overlays</strong> 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.</li> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this should be mentioned in this list at all. It has already been mentioned in the automated repair section that this is an ok short term solution so it doesn't need to be repeated here. |
||
<li>Hire an accessibility consultant to <strong>audit your site</strong> and recommend fixes. The consultant can then test your fixes and ensure that you are WCAG compliant.</li> | ||
<li>Hire an accessibility consultant to <strong>train your staff</strong> in how to build accessible digital experiences for your customers.</li> | ||
<li>Hire a UX designer to work with an accessibility expert to <strong>redesign your site</strong> 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 it guarantees the best results.</li> | ||
</ul> | ||
</div> | ||
|
||
<div class="container"> | ||
<h2 id="conclusion"> | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think links to specific tools should be added here and am very reluctant about the addition of this line overall.
Adding the principle of "consider creating or adding a user preferenced toolbar" is ok, but I think this could really confuse product owners.
My clients mostly want to include ReciteMe accessibility overlay because of the additional tools it offers rather than because they think it solves all accessibility issues. When I ask them what it offers which the browser or operating system does not already, they cite: easy translation, reading aloud, font changes, text size changes.
I worry that this may be interpreted by some as a recommendation of accessibility overlays.