Various typos - Githubissues

ZoeBijl commented 8 years ago

Separate issues for typos will result in a lot of issues, better pack them together here.

such as submitting a form, opening a dialog, cancelling an action

Source: APG: 2.6 Button

Unchecking the overall checkbox unchecks all options in the group.

Source: APG: 2.7 Checkbox

Unchecks is not a word, propose to change this to “will uncheck”.

of the week and calendar day numbers are layed out in table cells

Source: APG: 2.9 Date picker

Should this be “laid out”?

In the same section: datepicker should be two words.

This dialog box is dragable by the mouse user and an equivalent behavior (Drag & Drop) should be offered to the keyboard only user.

Source: APG: 2.11 Dialog (Non-Modal)

If a WAI-ARIA grid is not overlayed on a table, authors should mark the rowheader,

Source: APG: 2.14 Grid

Overlayed is not a word, should be overlaid.

“behaviour” occurs twice in the document. While I prefer the correct spelling, the APG is in American English and should thus use “behavior”.

or implemented with other methods that are more limitted in their usefulness.

the item in the widget that is currently active (e.g., currently displayed) should recieve the focus.

the navigation item must be able to programatically communicate the currently displayed status using aria-selected

Source: APG: 2.25 Site Navigator - General

the tab list, pressing Control+PageUpwill move focus to the first tab

Source: APG: 2.31 Tab Panel

Visually, disabled buttons are grayed-out, and typicially not placed in the navigation order

Toolbar that does not require mananged focus

Source: APG: 2.32 Tool Bar

In the case of a muti-selection list box a developer may gray selected items as they move focus to list box items to toggle their selected state.

Source: APG: 4.2.5 Managing the Perception of a Dual Focus

div role="**applicaton**" aria-labelledby="calendar" aria-describedby="info"

Source: APG: 4.2.7.1 Steps for Defining a Logical Navigational Structure

It is prefereable to have the descriptive text in prose as well so that it is readily available to all users.

Source: APG: 4.2.7.5.2 Marking Descriptive Sections

and you need to assocate a label for the dialog

Source: APG: 5.1.1 Labeling

That said, the DOM hierarchy is rigid and acyclical in that each node may only have one parent. In some situations, a child is reused by multiple parents or a child is separated from its sibilings or parent in the DOM tree.

Source: APG: 5.2.1 The Owns Relationship

and informs the user agent to not publish the element to the accessiblity API.

Source: APG: 7.1 Rationale

HTML to approximate a visual representation of a mathmatical expression

Source: APG: 9. Math

Cancelling a drag operation

APG is in American English, variant without extra L preferred.

where those roles reflect standard GUI elements that are recognized by accessility Application Programming Interfaces (APIs).

Accessibility information surfaced to assitive technologies is provided

Accessibility infomation mapped to a DOM element in the Document Object Model

DHTML example of GUI-like notebook tab with a data drid

When the datepicker is active a calender day of the week always has focus.

This dialog box is dragable by the mouse user and an equivalent behavior

ZoeBijl commented 8 years ago

All fixed in commit https://github.com/w3c/aria/commit/245945b7596d9b5fbda42e5d3a51733255d85ae4.

ZoeBijl commented 8 years ago

Related issues:

w3c / aria

Various typos #224