You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/en/fundamentals/accessibility/06-outro/index.markdown
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -25,22 +25,22 @@ notes:
25
25
26
26
Congratulations on completing this course! Let's recap.
27
27
28
-
In these lessons, you've leaned about *focus*, *semantics* (built-in and custom), *ARIA*, and *styling*, and how they all fit into the WCAG and WebAIM checklist. While these are all important tools in our accessibility kit, don't forget that accessibility isn't about the low-level details — it's really about making sure **all** of your users can access your content.
28
+
In these lessons, you've leaned about *focus*, *semantics* (built-in and custom), *ARIA*, and *styling*, and how they all fit into the WCAG and WebAIM checklist. While these are important tools in your accessibility kit, bear in mind that accessibility isn't just about the low-level details — it's really about making sure that **all** of your users can access **all** of your content**all** of the time.
29
29
30
30
It's important to remember that there's a whole range of users out there, not just the narrow spectrum that we might be designing for at the moment. That is, try not to over-focus; to build only for that subset of users is to exclude not only anyone with a permanent disability or impairment, but also means your product might fail any user when they are in a context that impacts the way they use technology, such as trying to use a phone one-handed while wrangling a screaming toddler.
31
31
32
32
Another critical aspect is to make accessibility part of the process from the beginning, and make it part of everyone's job.
33
33
34
-
-*Developers* have an important role to play in making sure that we implement interfaces in a way that maximizes accessibility and takes advantage of the HTML platform.
34
+
-*Developers* have a responsibility to make sure they implement interfaces in a way that maximizes accessibility and takes advantage of the HTML platform.
35
35
-*Designers* have a responsibility to ensure that accessibility is considered from the beginning, both in terms of ensuring that the visual design is accessible, and considering keyboard usability, semantics, and labeling.
36
36
-*Managers* have a responsibility to ensure that insufficient accessibility is a blocking criterion for launch.
37
37
38
38
That's a best case scenario, though; we know the real world is messier than that. So what can we do to try to make things better right away?
39
39
40
-
Remediating accessibility, like any time you're looking at reducing the number of bugs in software, is best looked at through the lens of impact: how can you have the most impact on users with the least amount of effort? This often boils down to three pertinent questions.
40
+
Remediating accessibility, like any time you're looking at reducing the number of bugs in software, is best viewed through the lens of impact: how can you have the most impact on users with the least amount of effort? This often boils down to three pertinent questions.
41
41
42
42
-*How frequently is this piece of UI used?* Is it a critical part of the application, like a sign-in form, or something that might be a handy feature but is less commonly used?
43
-
-*How badly does this accessibility issue affect your users?* For example, is it something that prevents screen reader users from accessing this part of the UI, or is it something that is mildly annoying, but can be worked around?
43
+
-*How much does an accessibility issue affect your users?* For example, is it something that completely prevents screen reader users from accessing a part of the UI, or is it something that is mildly annoying, but can be worked around?
44
44
-*How expensive will it be to fix?* Could you fix three other critical accessibility bugs in the time it will take to fix this one?
45
45
46
-
In the end, the only true measure of accessibility is whether all users can use your product. Well designed and built products are going to work for a very broad range of users in a very broad range of situations. So, ultimately, **good accessibility equals good UX**— and making it part of your process benefits everyone.
46
+
In the end, the only true measure of accessibility is whether all users can use your product. Well designed products are going to work for a very broad range of users in a very broad range of situations. So, ultimately, **good accessibility equals good UX**— and making it a standard part of your process benefits everyone.
0 commit comments