- From: timeless <timeless@gmail.com>
- Date: Wed, 10 Jun 2015 19:57:29 -0400
- To: public-pfwg-comments@w3.org
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#relations
> Marked up content or widgets will often need additional context to make clear what the meaning or purpose is.
ending a sentence with `is` is awkward.
what the meaning or purpose is => the meaning or purpose
> It is also reasonable that some content media types will need additional descriptions in another format to give clarity to those who are unable to consume the origin format.
It is also reasonable that some => Some
will => may
origin => original
> Generally you should always add these attributes to any widgets on your site as they are often merely a construct of HTML and JavaScript which provides no obvious insight as to what the widget's behavior or interactivity is.
what the widget's behavior or interactivity is => the widget's
behavior or interactivity
(Please address the pattern if you use it past this point)
> For example, you could have a dialog box erected from HTML <div> and you need to assocate a label for the dialog.
HTML => an HTML
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#Descriptions
> and then elsewhere in the HTML
add a `:`?
> If an object or widget lacks describedby the user agent or AT may try to extract information from the label or th tags, if present.
> The label and th tags have limited use in that they can only be applied to forms or tables, respectively.
please write `<label>` and `<th>` or somehow mark up `label` and `th`
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#Descriptions_external
> alt="Histogram of Blackberry tree heights"
blackberries [1] don't grow on trees, they grow in brambles/thickets
or on canes/wires
your example is bad :)
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#relations_owning
> These are aria-owns and aria-controls . The aria-owns relationship completes the parent/child relationship when it cannot be completely determined from the DOM created from the parsing of the markup.
there are two stray spaces around the `.`, please drop them.
> The aria-owns property is set on a document element, and its values are the unique IDs of all the adopted children.
`document element` is a technical term, you don't mean it, consider
`element in a document`…
> The aria-owns property is set on a document element, and its values are the unique IDs of all the adopted children. These elements may appear anywhere in the DOM, yet they are treated as siblings of each owning parent.
you don't mean that a child is treated as a sibling of its adoptive
parent, but that each adopted child is treated as a sibling of all the
other adopted children.
> At that instance of walking the DOM, the parent of the adopted children is the adopted parent and not the DOM parent. This will avoid recursion problems.
I don't know what this means, but:
<div id="a" aria-owns="b"><span id="b" aria-owns="a">This is a mess</span></div>
> Each child, adopted or natural, should have the appropriate aria-posinset and aria-setsize properties set consistent with their rendering, if these cannot be determined from the DOM from a direct parsing of the host language.
I think the last `,` is probably inappropriate. I also hate this
sentence structure, please reorder it as:
if {blah} can't be determined, each child should have …
> Places where direct parsing does not allow the user agent to determine aria-posinset and aria-setsize are long lists where only the currently visible items are loaded (via Ajax).
in principle, AJAX should be written as such, it's an acronym. I don't
think writing Ajax adds value here…
> If the children are re-sorted then the aria-posinset and aria-setsize values should be updated consistent with their visual rendering.
updated consistent => updated to be consistent
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#toc
> <a class="tocxref" href="#relations_owns_reuse"><span class="secno">5.2.2 </span> Using Owns with Reusable Content</a>
the ` ` shouldn't be there
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#relations_owns_reuse
> 5.2.2 Using Owns with Reusable Content§
nor should it be here…
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#relations_controls
> Here, you would want the radio group to assign a aria-controls relationship to the listbox which will be updating without a page reload.
a aria => an aria
> Therefore, an assistive technology immediately presents changes to a live region when the controlling widget is the one which has user keyboard focus. For example, if a tree view controls a help document pane, each time
random line break
> the tree item changes the new tree item and then the new help contents should also be read.
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#relations_flowto
> aria-flowto establishes the recommended reading order of content, so that the an assistive may overriding the default of reading in document order to its user.
assistive => assistive technology|agent|??
this doesn't make sense even with that fix
> Example 33
i don't understand the paragraph describing this example. I'm pretty
sure I understand the theoretical UC…
> To implement this technique do the following.
that should end with `:`
> Make each object in the work flow accessible
this should probably end with `.`
> Example 34
> <img src="foo.jpg" id="331" title="What is the Invoice Value?">
while numeric id's are valid html5, they weren't valid html4, and
they're pretty poor for examples.
also, using the same src= for all of the items is bad…
> After a choice is made, then the AT can move focus to the target object; or in the case of a screen reader, it may just move the user to that location in the screen reader's virtual buffer.
drop `then`
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#relations_haspopup
> In order for menus, menubars, and menuitems to indicate that it opens a menu, set its aria-haspopup property to "true."
please leave punctuation outside of quotation marks.
> Combo boxes, or drop down lists, work differently.
this is to hard to parse.
Combo boxes (drop down lists) ?
Combo boxes and drop down lists ?
drop the other `,` too
> All of the menuitems associated with the menubar have aria-haspopup set to 'true'.
here you use `'` instead of `"`, i'm not sure why…
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#LiveRegions
> By default, the user will hear additions and text type changes. If you wish to explicitly define the types of changes, you need to set relevant="THE_TYPES_OF_CHANGES". If more than one type of change is relevant, the types are separated by a space. For example, to define additions and removals as relevant but not text, set relevant="additions removals".
you normally write aria-{property}, here just {property} `relevant`,
that's confusing, also, it isn't marked up (colored, etc.).
> This example shows two live regions. If both regions update simultaneously, liveRegionA should be spoken first because its message has a higher priority than liveRegionB.
> Example 38
it'd be better if the assertive region wasn't first in the DOM,
typically first things have priority anyway
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#chobet
> alert - You must use the alert role for a one-time notification which shows for a period of time and goes away and is intended to alert the user that something has happened. The assistive technology should be notified by the user agent that an alert has occurred, if your operating system supports this type of event notification.
the second person (`you`, `your`) changed between these two sentences.
You [the specification author] should not do that, it confuses
readers.
> marquee- You must use a marquee role when you need to mark an area with scrolling text such as a stock ticker.
you're missing a space before `-`
> <!-- Live region 'log' role used with TABLE element: the 'log' role is not consistently mapped to platform AAPI. -->
this is the only instance of `AAPI`, it isn't defined
> <a href="www.somewhere.com">Ancient Roman Architecture</a>
you should use `https://` before `www.`…
and you should use the example.com domain space
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#ariaform
note that html5 should have stuff for this…
http://www.w3.org/TR/html/forms.html#the-required-attribute
http://www.w3.org/TR/html/forms.html#the-maxlength-and-minlength-attributes
> Use aria-invalid and aria-required To Improve Access to Forms§
this should be 8.1
> Alert the User When Maximum Length Value Is Reached§
this should be 8.1.1 ??
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#math
> Editors' note: This section was added as part of disposition of comment 4, but is very incomplete.
there should be a link to `comment 4`
> The examples need better introductions, and the positive examples should preceded [sic] the negative examples, which need to be explained more fully.
precede
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#aria-write
> An example of such an API is Linux's AT-SPI.
Please link to something, e.g. [2]
Personally, I'm not sure why you choose to link to AT-SPI instead of
MSAA IAccessible or NSAccessibility…
> However, with respect to ARIA 1.0, the flow of information is one way only from WAI-ARIA to the accessibility API.
only from => only; from
> The following States and Properties are unlikely to be manipulated by an assistive technology: An AT would need to have greater understanding of the application and the results could be adverse.
There's a sentence after the `:`, you should reword this so that the
reasoning precedes the portion introducing the `:`.
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#reuse_comp_lib
> According to the SecuritySpace Technology Penetration Report,
please don't make me click a link just to find out when a report was published.
> According to the SecuritySpace Technology Penetration Report, more than 55% of all Web sites today contain JavaScript, dramatically affecting the ability for persons with disabilities to access Web content.
I don't think the report covers the affect of JS on people with
disabilities. Please reword to avoid that implication.
> Until now, the W3C WAI has discouraged the use of JavaScript per [WAI-WEBCONTENT], Checkpoint 6.1).
There's no `(` to match `)`…
> The W3C WAI PF working group is working with User Agent manufacturers, assistive technology vendors, and accessibility tool providers, to ensure an end-to-end working solution.
Working Group should be capitalized (and probably just written as WG).
It'd be really nice if you actually linked to your page.
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#problemstatement
> shows the same DOM node provided in Figure 1.0 but with JavaScript acting as the new controller.
`shows` isn't capitalized, this sentence is broke, perhaps you want
`Figure 2 shows` ??
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#solution
> The goal is to make these standard features in HTML 5.
As mentioned earlier, HTML5 was published, this needs to be revised to
reflect what was published.
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#html_support
> Limited to HTML 4.0 - Alt Text, title text
this table needs to be updated to reflect current published documents
(esp HTML5)
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#Fill
> At this time,W3C WAI Protocols and Formats working group's primary focus is on extensions to HTML 4.01 and XHTML 1.X by extending the host language to include WAI-ARIA with a migration path to HTML 5.
there's a space missing after `,`
Note that XHTML is supposed to be dead… also, all of the `(X)HTML`
text in the document is a real pain to read. `HTML` should work w/ a
single line in the introduction noting that pretty much everything
that applies to HTML also applies to the dead XHTML…
> This will require the creation of new hybrid document type definitions (DTDs) that incorporate the extensions.
DTDs are mostly dead. Requiring them isn't the way forward.
> The comprehensive gap analysis of (X)HTML, used to form WAI-ARIA is found in Table 1.0 and how WAI-ARIA fills those gaps […].
You're missing something, the table doesn't have any mention of WAI-ARIA.
> Less critical for (X)HTML but helpful for accessibility will be the descriptive extensions to XML events and the new [[XHTML Access]].
I'm not sure what XHTML Access is, but it's listed raw here.
> Web Content Accessibility Guidelines 2.0 calls for the WAI-ARIA properties in guideline 4.1 Maximize compatibility with current and future agents, including assistive technologies (roles, states, properties, and values) and section guideline 1.3 Create content that can be presented in different ways (for example spoken aloud, simpler layout, etc.) without losing information or structure (relationships).
This thing (perhaps it's a sentence?) is entirely unreadable.
> The next section describes how the specifications are used together as well as how they will be implemented in HTML 4.
HTML4 is expired…
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#new_provisions
> This is the case for [JAPI], [MSAA]], [AXAPI], and the [ATK], or [UI-AUTOMATION] (called content type in UI Automation).
There's a `]` without a matching `[` here.
> WAI used RDF/OWL to model our taxonomy for WAI-ARIA.
RDF/OWL should be a link or referenced document…
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#properties
> Example: Use of WAI-ARIA to incorporate accessible state information information into XHTML 1.x
| <!DOCTYPE html PUBLIC "Accessible Adaptive Applications//EN"
| http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
|
| >
this last `>` is bogus, rendering your cute xhtml (xml) document invalid.
It's missing `<html>`, and `<head>…<title>…</title>…</head>`
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#ariahtml
> Firefox 3 is leading the way to implement this, and other browser manufacturers are working to support it as well.
Firefox 3 is long gone…
also, `manufacturers` is wrong, try `vendors`
http://www.w3.org/TR/2015/WD-wai-aria-practices-1.1-20150514/#ack_others
> Alex Russell (Dojo Foundation) (
unclosed `(`
[1] http://en.wikipedia.org/wiki/Blackberry
[2] https://git.gnome.org/browse/at-spi2-core/tree/README
Received on Wednesday, 10 June 2015 23:57:57 UTC