spelling and other small problems

slides/assessment2.html

@@ -64,29 +64,14 @@ Keyboard Accessible
 ]
 .right-column[
 
-No other input form has this flexibility or is universally supported and operable by people with different disabilities, as long as the keyboard input is not time-dependent.
+No other  form of input (besides keyboards) has this flexibility or is universally supported and operable by people with different disabilities, as long as the keyboard input is not time-dependent.
 
 Examples of who benefits
 - screen reader users (e.g. blind users, reading disabilities)
 - speech input users
 - switch input users
-
 ]
 
-
-<!-- --- -->
-<!-- # POUR: Operable: Guidelines 2.1-2.5 -->
-
-<!-- .left-column[ -->
-<!-- ## Guideline 2.1 -->
-<!-- Keyboard Accessible -->
-
-<!-- Discuss with your neighbor and post -->
-<!-- ] -->
-<!-- .right-column[ -->
-<!-- <iframe src="https://embed.polleverywhere.com/free_text_polls/SHF2YF26NRUApLALP0WHj?controls=none&short_poll=true" width="800px" height="600px"></iframe> -->
-<!-- ] -->
-
 ---
 # POUR: Operable: Guidelines 2.1-2.5
 

slides/best-practices.html

@@ -121,7 +121,7 @@ Notice details of WCAG guidelines low on this list!
 | Unclear scope & architecture requirements | Engage with relevant end users                       |
 | Difficulty testing                        | Use appropriate testing suites & integration testing |
 | Lack of complete access practices         | Rigorous refactoring                                 |
-| Innapropriate tools                       | Well-designed documentation    & training            |
+| Inappropriate tools                       | Well-designed documentation    & training            |
 | Domain-dependent issues                   | Appropriate end user engagement and testing                                                     |
 
 ---
@@ -178,7 +178,7 @@ Discuss similarities and differences from desktop
 .left-column-half[
 Different types of screen readers.
 - JAWS for Windows
-- NonVisual Desktop Access
+- Nonvisual Desktop Access
 - VoiceOver
 - TalkBack
 - ChromeVox
@@ -234,7 +234,7 @@ Speak(fa:fa-volume-up Button, Bar ):::bluelarge
 graph LR
 SR[fa:fa-volume-up <BR> Screenreader<BR>]:::bluelarge -->|Invokes object| API(fa:fa-codepen<BR> Accessibility API<BR>):::bluelarge
 API -->|Passes along request| ATK[<BR> Toolkit/<BR>Browser]:::bluelarge
-ATK -->|Invokse Callback| App[fa:fa-mobile <BR>App<BR>]:::bluelarge
+ATK -->|Invokes Callback| App[fa:fa-mobile <BR>App<BR>]:::bluelarge
 App -->|Updates Interface<BR>Announces Changes| ATK
 ATK -->|Passes along information| API
 API -->|Deleted text| SR
@@ -276,7 +276,7 @@ Reaching times
 
 Information you need to collect to assess this:
 - You need to know the linear order of a webpage or app. 
-- You need to know about any hierarchy that is programatically available (e.g. headers)
+- You need to know about any hierarchy that is programmatically available (e.g. headers)
 
 No way to automatically assess this! Hard to assess well without knowing best tricks for navigation that disabled people use. 
 
@@ -332,9 +332,9 @@ No way to automatically assess this! Hard to assess well without knowing best tr
 ---
 # Example: Swipe Order
 .left-column40[
-![:img A picture of facebook showing (in rows from top to bottom ad left to right): Logo/search and messenger; user image stating /what's on your mind?/; Live/Photo/Checkin text with icons; Scrolling set of live videos; a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; the final set of facebook controls (icons that look like a gui; a house; a person; a group of people; a bell; and a hamburger menu)  ,80%, width](img/assessment/facebook1.png) 
+![:img A picture of Facebook showing (in rows from top to bottom ad left to right): Logo/search and messenger; user image stating /what's on your mind?/; Live/Photo/Checkin text with icons; Scrolling set of live videos; a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; the final set of Facebook controls (icons that look like a GUI; a house; a person; a group of people; a bell; and a hamburger menu)  ,80%, width](img/assessment/facebook1.png) 
 ]
-.righ-column60[
+.right-column60[
 What focus order makes sense for the Facebook newsfeed? 
 
 Does this match the actual focus order?
@@ -346,7 +346,7 @@ When might you need to	*skip* things?
 ## What order do you think will be used (1 of 2)
 
 .left-column40[
-![:img A picture of facebook showing (in rows from top to bottom ad left to right): Logo/search and messenger; user image stating /what's on your mind?/; Live/Photo/Checkin text with icons; Scrolling set of live videos; a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; the final set of facebook controls (icons that look like a gui; a house; a person; a group of people; a bell; and a hamburger menu) ,80%, width](img/assessment/facebook1.png) 
+![:img A picture of Facebook showing (in rows from top to bottom ad left to right): Logo/search and messenger; user image stating /what's on your mind?/; Live/Photo/Checkin text with icons; Scrolling set of live videos; a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; the final set of Facebook controls (icons that look like a GUI; a house; a person; a group of people; a bell; and a hamburger menu) ,80%, width](img/assessment/facebook1.png) 
 ]
 .right-column60[
 Use chunks to group meaningful info and reduce number of navigation steps. 
@@ -357,10 +357,10 @@ ink over!
 ---
 ## What order do you think will be used (2 of 2)
 .left-column40[
-![:img A picture of facebook showing (in rows from top to bottom ad left to right): Logo/search and messenger; user image stating /what's on your mind?/; Live/Photo/Checkin text with icons; Scrolling set of live videos; a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; the final set of facebook controls (icons that look like a gui; a house; a person; a group of people; a bell; and a hamburger menu) ,80%, width](img/assessment/facebook1.png) 
+![:img A picture of Facebook showing (in rows from top to bottom ad left to right): Logo/search and messenger; user image stating /what's on your mind?/; Live/Photo/Checkin text with icons; Scrolling set of live videos; a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; the final set of Facebook controls (icons that look like a GUI; a house; a person; a group of people; a bell; and a hamburger menu) ,80%, width](img/assessment/facebook1.png) 
 ]
 .right-column40[
-![:img The same picture numbered. Numbers do not match reading order as shown in this alt text: (1) Logo/ (2) search and (3) messenger; (5) user image stating (4) /what's on your mind?/; (6) Live/ (7) Photo/ (8) Checkin text with icons; (9) Scrolling set of live videos; (10)  a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; (??) the final set of facebook controls (icons that look like a gui; a house; a person; a group of people; a bell; and a hamburger menu)   ,120%, width](img/assessment/facebook-actual.png) 
+![:img The same picture numbered. Numbers do not match reading order as shown in this alt text: (1) Logo/ (2) search and (3) messenger; (5) user image stating (4) /what's on your mind?/; (6) Live/ (7) Photo/ (8) Check in text with icons; (9) Scrolling set of live videos; (10)  a scrolling list of posts containing:  a post with title and meta data; the post text; number of comments; like and comment buttons; (??) the final set of Facebook controls (icons that look like a GUI; a house; a person; a group of people; a bell; and a hamburger menu)   ,120%, width](img/assessment/facebook-actual.png) 
 ]