From 698e98206929f339487abcc153ded8e5dce6c7d5 Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Thu, 30 Aug 2018 01:28:48 -0400 Subject: [PATCH 1/6] typo: Double word "the" --- aria-practices-DeletedSectionsArchive.html | 8 ++++---- aria-practices.html | 14 +++++++------- examples/dialog-modal/dialog.html | 2 +- examples/listbox/listbox-collapsible.html | 6 +++--- 4 files changed, 15 insertions(+), 15 deletions(-) diff --git a/aria-practices-DeletedSectionsArchive.html b/aria-practices-DeletedSectionsArchive.html index 8faf46a581..4ffa1ac7e1 100644 --- a/aria-practices-DeletedSectionsArchive.html +++ b/aria-practices-DeletedSectionsArchive.html @@ -568,7 +568,7 @@

Keyboard Interaction

  • Enter -
  • @@ -942,7 +942,7 @@

    WAI-ARIA Roles, States, and Properties

  • - Navigation region: Each navigation widget should be wrapped in a container with role navigation and have a label that is the same as the label on the the widget. + Navigation region: Each navigation widget should be wrapped in a container with role navigation and have a label that is the same as the label on the widget. If multiple widgets are used to support a hierarchy and if the widgets are sequential in the Tab order, then the navigation regions for child widgets should be nested inside the navigation region of the parent.
  • @@ -1005,7 +1005,7 @@

    Keyboard Interaction

    Option 1: Listbox containing links

    Option 2: Toolbar containing toggle buttons

    @@ -1921,7 +1921,7 @@

    Managing Focus in Dialogs

    var node = evt.target; // get the target node of the keypress event if (evt.charOrCode === keys.TAB){ // find the first and last tab focusable items in the hierarchy of the dialog container node -// do this every time if the items may be added / removed from the the dialog may change visibility or state +// do this every time if the items may be added / removed from the dialog may change visibility or state var focusItemsArray = helper.getFocusItems(dialogContainerNode); dialog.firstFocusItem = focusItemsArray[0]; dialog.lastFocusItem = focusItemsArray[focusItemsArray.length-1]; diff --git a/aria-practices.html b/aria-practices.html index 3bf53c0a04..ab76993ce5 100644 --- a/aria-practices.html +++ b/aria-practices.html @@ -1986,9 +1986,9 @@

    WAI-ARIA Roles, States, and Properties

    Radio Group

    - A radio group is a set of checkable buttons, known as radio buttons, where no more than one of + A radio group is a set of checkable buttons, known as radio buttons, where no more than one of the buttons can be checked at a time. - Some implementations may initialize the set with all buttons in the unchecked state in order to + Some implementations may initialize the set with all buttons in the unchecked state in order to force the user to check one of the buttons before moving past a certain point in the workflow.

    @@ -2399,7 +2399,7 @@

    Keyboard Interaction

  • End (Optional): Moves focus to the last tab. Optionally, activates the newly focused tab (See note below).
  • Shift + F10: If the tab has an associated pop-up menu, opens the menu.
  • - Delete (Optional): If deletion is allowed, deletes (closes) the current tab element and its associated tab panel, + Delete (Optional): If deletion is allowed, deletes (closes) the current tab element and its associated tab panel, sets focus on the tab following the tab that was closed, and optionally activates the newly focused tab. If there is not a tab that followed the tab that was deleted, e.g., the deleted tab was the right-most tab in a left-to-right horizontal tab list, sets focus on and optionally activates the tab that preceded the deleted tab. @@ -2930,7 +2930,7 @@

    Keyboard Interaction

    See for cut, copy, and paste key assignments.

  • - +

    WAI-ARIA Roles, States, and Properties

    diff --git a/examples/dialog-modal/dialog.html b/examples/dialog-modal/dialog.html index f92ff59c2c..0fc889e401 100644 --- a/examples/dialog-modal/dialog.html +++ b/examples/dialog-modal/dialog.html @@ -65,7 +65,7 @@

    Accessibility Features

  • When the dialog closes as a result of the Cancel action, the user's point of regard is maintained by returning focus to the Add Delivery Address button.
  • When the dialog closes as a result of the Add action and the Address Added dialog replaces the Add Delivery Address dialog, - the Add Delivery Address dialog passes a reference to the Add Delivery Address button to the the Address Added dialog + the Add Delivery Address dialog passes a reference to the Add Delivery Address button to the Address Added dialog so that it can maintain the user's point of regard when it closes.
  • diff --git a/examples/listbox/listbox-collapsible.html b/examples/listbox/listbox-collapsible.html index 7fa46addd1..4129df45b4 100644 --- a/examples/listbox/listbox-collapsible.html +++ b/examples/listbox/listbox-collapsible.html @@ -35,7 +35,7 @@

    Collapsible Dropdown Listbox Example

    The following example implementation of the design pattern for listbox - demonstrates a collapsible single-select listbox widget that is functionally similar to an HTML select input with the the attribute size="1". + demonstrates a collapsible single-select listbox widget that is functionally similar to an HTML select input with the attribute size="1". The widget consists of a button that triggers the display of a listbox. In its default state, the widget is collapsed (the listbox is not visible) and the button label shows the currently selected option from the listbox. When the button is activated, the listbox is displayed and the current option is focused and selected. @@ -216,7 +216,7 @@

    Role, Property, State, and Tabindex Attributes

    • Set by the JavaScript when the listbox is displayed.
    • -
    • Otherwise, is not present.
    • +
    • Otherwise, is not present.
    @@ -254,7 +254,7 @@

    Role, Property, State, and Tabindex Attributes

  • When navigation keys, such as Down Arrow, are pressed, the JavaScript changes the value.
  • Enables assistive technologies to know which element the application regards as focused while DOM focus remains on the ul element.
  • - For more information about this focus management technique, see + For more information about this focus management technique, see Using aria-activedescendant to Manage Focus.
  • From de3b143055031c3681815eb5a37b7c1b47d1954b Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Thu, 30 Aug 2018 01:29:54 -0400 Subject: [PATCH 2/6] typo: Double word "a" --- aria-practices.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aria-practices.html b/aria-practices.html index ab76993ce5..7690b939ad 100644 --- a/aria-practices.html +++ b/aria-practices.html @@ -4200,7 +4200,7 @@

    Using aria-rowcount and aria-rowindex

    For example, specifying an invalid value for aria-rowindex or setting it on some but not all rows in a table, could cause screen reader table reading functions to skip rows or simply stop functioning.

    - The following code demonstrates the use of aria-rowcount and aria-rowindex properties on a table containing a a hypothetical class list. + The following code demonstrates the use of aria-rowcount and aria-rowindex properties on a table containing a hypothetical class list.

             
    
    From 3ed83289678dce039b4fd5068fcec9a5427a3503 Mon Sep 17 00:00:00 2001
    From: Nick Schonning 
    Date: Thu, 30 Aug 2018 01:30:38 -0400
    Subject: [PATCH 3/6] typo: Double word "have"
    
    ---
     aria-practices-DeletedSectionsArchive.html | 6 +++---
     1 file changed, 3 insertions(+), 3 deletions(-)
    
    diff --git a/aria-practices-DeletedSectionsArchive.html b/aria-practices-DeletedSectionsArchive.html
    index 4ffa1ac7e1..1b7dc7d154 100644
    --- a/aria-practices-DeletedSectionsArchive.html
    +++ b/aria-practices-DeletedSectionsArchive.html
    @@ -389,7 +389,7 @@ 

    WAI-ARIA Roles, States, and Properties

    tab order. If you create a text field without using a standard HTML text field form control then ensure that it is in the tab order. -
  • If the text field is not editable it must have have If the text field is not editable it must have aria-readonly = true.
  • The combobox must have WAI-ARIA Roles, States, and Properties field is in the tab order. If you create a text field without using a standard HTML text field form control then ensure that it is in the tab order.
  • -
  • If the combobox is not editable it must have have If the combobox is not editable it must have aria-readonly = true.
  • The combobox must have Changing the Reading Flow <img src="foo.jpg" id="333" title="Finance Manager Approval"> <img src="foo.jpg" id="334" title="Sales Manager Approval"> …
  • -

    Each element referenced by the flowto must have have a unique id. The combination of the unique id and the name allow the assistive technology to adequately assist the user in retracing their steps backward through a flow to reference or moving forward to it. Since the author sets only the target the user agent is responsible for mapping the backward reference relationship. Therefore, neither the user agent nor the user can get lost. The host user agent does not provide an alternative navigation order; this is an assistive technology function.

    +

    Each element referenced by the flowto must have a unique id. The combination of the unique id and the name allow the assistive technology to adequately assist the user in retracing their steps backward through a flow to reference or moving forward to it. Since the author sets only the target the user agent is responsible for mapping the backward reference relationship. Therefore, neither the user agent nor the user can get lost. The host user agent does not provide an alternative navigation order; this is an assistive technology function.

  • Make sure visual objects are keyboard accessible

    Use tabindex to enable objects to receive focus. Actually setting focus to them may be performed by an assistive technology, such as an alternative input device. This example places each drawing object in document order with respect to the tab sequence.

    From c4b0954bd8dff2af9c08eedf89f8c308e19926c3 Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Thu, 30 Aug 2018 01:31:14 -0400 Subject: [PATCH 4/6] typo: Double word "information" --- aria-practices-DeletedSectionsArchive.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aria-practices-DeletedSectionsArchive.html b/aria-practices-DeletedSectionsArchive.html index 1b7dc7d154..b914ff97d3 100644 --- a/aria-practices-DeletedSectionsArchive.html +++ b/aria-practices-DeletedSectionsArchive.html @@ -3122,7 +3122,7 @@

    Provision of the Accessibility State Information: "What meaningful properti analysis of the accessibility properties defined in MSAA and ATK. The following example extends the previous approach by adding the aria-haspopup accessibility property.

    -

    Example: Use of WAI-ARIA to incorporate accessible state information information into XHTML 1.x

    +

    Example: Use of WAI-ARIA to incorporate accessible state information into XHTML 1.x

     <?xml version="1.1" encoding="us-ascii"?>
     <!DOCTYPE html PUBLIC "Accessible Adaptive Applications//EN"
    
    From a8a4a52752a16af4013beceb2d5d7311ae8828d9 Mon Sep 17 00:00:00 2001
    From: Nick Schonning 
    Date: Thu, 30 Aug 2018 01:31:40 -0400
    Subject: [PATCH 5/6] typo: Double word "must"
    
    ---
     aria-practices-DeletedSectionsArchive.html | 2 +-
     1 file changed, 1 insertion(+), 1 deletion(-)
    
    diff --git a/aria-practices-DeletedSectionsArchive.html b/aria-practices-DeletedSectionsArchive.html
    index b914ff97d3..bd9479b1be 100644
    --- a/aria-practices-DeletedSectionsArchive.html
    +++ b/aria-practices-DeletedSectionsArchive.html
    @@ -1890,7 +1890,7 @@ 

    Managing Focus in Dialogs

    If the keypress is a Shift + Tab key and the target == the first tab navigable object, then set focus to the last tab-navigable object and stop the key press event. If there is only a single tab focusable item, then focus does not have to be set, but the key press event must be stopped.

  • - If the keypress is a Tab key and the target == the last tab navigable object, then set focus to the first tab-navigable object and stop the keypress event. If there is only a single tab-focusable item, then focus does not have to be set but the keypress event must must be stopped. + If the keypress is a Tab key and the target == the last tab navigable object, then set focus to the first tab-navigable object and stop the keypress event. If there is only a single tab-focusable item, then focus does not have to be set but the keypress event must be stopped.
  • If the keypress is an Escape key and the target node is the container node for the dialog box, then close the dialog box and hide or destroy the dialog underlay. From 48966e8abf2023bf1ca76e3b7df74bdb1d99b49b Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Thu, 30 Aug 2018 01:34:12 -0400 Subject: [PATCH 6/6] typo: Double word "Career" --- aria-practices-DeletedSectionsArchive.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aria-practices-DeletedSectionsArchive.html b/aria-practices-DeletedSectionsArchive.html index bd9479b1be..f8ffc66206 100644 --- a/aria-practices-DeletedSectionsArchive.html +++ b/aria-practices-DeletedSectionsArchive.html @@ -3305,7 +3305,7 @@

    Use of XHTML Role Landmarks to Improve Document Navigation

    extensions for Mozilla/Firefox from the University of Illinois at Urbana-Champaign to render the document landmarks. This picture shows the Firefox browser rendering the University of Illinois - Career Career Center home page. In this example. The "List of Navigation Bars" viewer is shown, launched from the extension on the + Career Center home page. In this example. The "List of Navigation Bars" viewer is shown, launched from the extension on the toolbar. The viewer shows that the secondary "Career Center Services" is selected resulting in that section of the document being highlighted in yellow. The Navigation Bar Lists Viewer lists the following list of titles corresponding to the navigation sections: