Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pfwg-action-1415 #2

Merged
merged 1 commit into from
Apr 24, 2014
Merged

pfwg-action-1415 #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/aria.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -300,7 +300,7 @@ <h2><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> States a
<p>Some accessibility states, called <em><a title="managed state">managed states</a></em>, are controlled by the user agent. Examples of managed state include keyboard focus and selection. Managed states often have corresponding <abbr title="Cascading Style Sheets">CSS</abbr> pseudo-classes (such as <code>:focus</code> and <code>::selection</code>) to define style changes. In contrast, the states in this specification are typically controlled by the author and are called <em>unmanaged states.</em> Some states are managed by the user agent, such as <pref>aria-setsize</pref>, but the author can override them if the <abbr title="Document Object Model">DOM</abbr> is incomplete and would cause the user agent calculation to be incorrect. User agents map both managed and unmanaged states to the platform accessibility <abbr title="Application Programing Interfaces">APIs</abbr>.</p>
<p>Most modern user agents support <cite><a href="http://www.w3.org/TR/CSS2/selector.html#attribute-selectors"><abbr title="Cascading Style Sheets">CSS</abbr> attribute selectors</a></cite> ([[CSS2]]), and can allow the author to create <abbr title="User Interface">UI</abbr> changes based on <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attribute information, reducing the amount of scripts necessary to achieve equivalent functionality. In the following example, a <abbr title="Cascading Style Sheets">CSS</abbr> selector is used to determine whether or not the text is bold and an image of a check mark is shown, based on the value of the <sref>aria-checked</sref> attribute.</p>
<pre class="example highlight lang-css">[aria-checked=&quot;true&quot;] { font-weight: bold; }
[aria-checked=&quot;true&quot;]:before { background-image: url(checked.gif); }</pre>
[aria-checked=&quot;true&quot;]::before { background-image: url(checked.gif); }</pre>

<!-- keep this note synced with other CSS examples using attribute selectors -->
<!-- Commented 30 Apr 2013; No longer relevant in modern browsers. <p class="note">At the time of this writing, this <abbr title="Cascading Style Sheets">CSS</abbr> example, while technically correct, will not redraw styles properly in some browsers if the attribute's value is changed dynamically. It may be necessary to toggle a class name, or otherwise force the browser to redraw the styles properly.</p>-->
Expand Down Expand Up @@ -556,7 +556,7 @@ <h4>Text Alternative Computation</h4>
</ol>
</li>
<li id="tac_gencss">
Text nodes are often visited because they are children of an element that uses rule 2C to collect text from its children. However, because it is possible to specify or alter textual content using CSS rules, it is necessary for user agents to combine such content, as appropriate, with the text referenced by the text nodes to produce a complete text alternative. An example is the use of <abbr title="Cascading Style Sheets">CSS</abbr> <code>:before</code> and <code>:after</code> pseudo-elements, where the user agent combines the textual content specified in the style sheet with that given in the DOM.
Text nodes are often visited because they are children of an element that uses rule 2C to collect text from its children. However, because it is possible to specify or alter textual content using CSS rules, it is necessary for user agents to combine such content, as appropriate, with the text referenced by the text nodes to produce a complete text alternative. An example is the use of <abbr title="Cascading Style Sheets">CSS</abbr> <code>::before</code> and <code>::after</code> pseudo-elements, where the user agent combines the textual content specified in the style sheet with that given in the DOM.
<ul>
<li id="tac_gencss_imagetext">When an image replaces text, then the UA should use the original text, since that text is presumably the equivalent.</li>
<li id="tac_gencss_textimage">When text replaces an image, then the UA should provide that text.</li>
Expand Down