You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code guide: Use short encoding declaration and avoid /> (#2069)
* Use short encoding declaration and avoid />. Don't include a trailing slash in self-closing elements—the HTML standard says they're optional.
* Use htmlhint 'empty-tag-not-self-closed' rule. This rule checks that HTML void elements do not use '/>' syntax.
Co-authored-by: Michael "Z" Goddard <[email protected]>
Co-authored-by: Howard Edwards <[email protected]>
behavior of the element. The user agent's default behavior at the
2838
2838
document element forms the controller. </p>
2839
2839
<figureid="fig1">
2840
-
<imgalt="Accessibility information mapped to a DOM element in the Document Object Model" height="512" longdesc="#desc_fig1" src="img/accessibleelement.png" width="640"/>
2840
+
<imgalt="Accessibility information mapped to a DOM element in the Document Object Model" height="512" longdesc="#desc_fig1" src="img/accessibleelement.png" width="640">
2841
2841
<figcaption>Accessibility Interoperability at a <abbrtitle="document object model">DOM</abbr> Node without JavaScript</figcaption>
2842
2842
</figure>
2843
2843
<pid="desc_fig1">The box between the DOM node
@@ -2850,7 +2850,7 @@ <h3> The Problem</h3>
2850
2850
information, and relations). For HTML and other W3C markup, the
2851
2851
accessibility information provided solely depends upon what the element's tag name and any accessibility attributes that map to that tag provides. For example, the accessible role of a table is <code>table</code>. The author provides an accessible description by assigning a <code>title</code> attribute.</p>
2852
2852
<p>In contrast, with JavaScript, user actions can trigger updates in the data and presentation, but the default accessibility information available in the element tags is no longer valid.</p>
2853
-
<figureid="fig2"><imgalt="DOM Element with JavaScript controller" height="502" longdesc="#desc_fig2" src="img/accessibleJSelement.png" width="476"/>
2853
+
<figureid="fig2"><imgalt="DOM Element with JavaScript controller" height="502" longdesc="#desc_fig2" src="img/accessibleJSelement.png" width="476">
2854
2854
<figcaption>Accessibility
2855
2855
Interoperability at a DOM Node with JavaScript</figcaption></figure>
2856
2856
<pid="desc_fig2"><ahref="#fig2"></a> shows the same DOM node provided
@@ -3308,7 +3308,7 @@ <h3> Use of XHTML Role Landmarks to Improve Document Navigation</h3>
3308
3308
user to view a list of navigation landmarks.
3309
3309
This tool, shown in <ahref="#fig3"></a>, lists the navigation sections on the page. Keyboard navigation of the list of navigation bars causes the
3310
3310
corresponding document section to be highlighted. The title for each navigation region displays in the list.</p>
3311
-
<figureid="fig3"><imgalt="Table of Contents from Landmarks" height="813" longdesc="#desc_fig3" src="img/navlandmark.jpg" title="Table of Contents from Landmarks" width="877"/>
3311
+
<figureid="fig3"><imgalt="Table of Contents from Landmarks" height="813" longdesc="#desc_fig3" src="img/navlandmark.jpg" title="Table of Contents from Landmarks" width="877">
3312
3312
<figcaption>Table of Contents generated from navigation landmarks in the header</figcaption>
3313
3313
</figure>
3314
3314
<pid="desc_fig3"><ahref="#fig3"></a> shows the <ahref="http://firefox.cita.uiuc.edu/">accessibility
@@ -3332,7 +3332,7 @@ <h3> WAI-ARIA Role Taxonomy - Extensible Semantic Role Model, using RDF/OWL</h3
3332
3332
W3C standards-based approach to represent this information.</p>
<imgalt="Sample Semantic Map for Taxonomy" height="564" longdesc="#desc_fig4" src="img/taxonomy.png" title="Sample Semantic Map for Taxonomy" width="500"/>
3335
+
<imgalt="Sample Semantic Map for Taxonomy" height="564" longdesc="#desc_fig4" src="img/taxonomy.png" title="Sample Semantic Map for Taxonomy" width="500">
3336
3336
<figcaption>Example, Partial RDF Map for a possible ButtonUndo role as an extended role to WAI-ARIA</figcaption>
3337
3337
</figure>
3338
3338
<pid="desc_fig4"><ahref="#fig4"></a> shows a basic RDF mapping that
@@ -3372,7 +3372,7 @@ <h4> Interoperability Example: Grid Role </h4>
3372
3372
The user uses arrow keys to navigates the data grid and among the page tabs.
3373
3373
Using the Tab key, a user navigates between the notebook tab, the edit fields, buttons, and
3374
3374
the data grid.</p>
3375
-
<figureid="fig5"><imgalt="DHTML example of GUI-like notebook tab with a data grid" height="633" longdesc="#desc_fig5" src="img/DHTMLexample.png" title="DHTML Example" width="844"/>
3375
+
<figureid="fig5"><imgalt="DHTML example of GUI-like notebook tab with a data grid" height="633" longdesc="#desc_fig5" src="img/DHTMLexample.png" title="DHTML Example" width="844">
3376
3376
<figcaption>DHTML Example</figcaption>
3377
3377
</figure>
3378
3378
<pid="desc_fig5"> Accessible role and state
@@ -3383,7 +3383,7 @@ <h4> Interoperability Example: Grid Role </h4>
3383
3383
the Microsoft Active Accessibility rendering of the new
3384
3384
accessibility markup provided on the DataGrid page tab which has
3385
3385
focus.</p>
3386
-
<figureid="fig6"><imgalt="MSAA Inspect Tool diagnostics for Notebook page tab" height="647" longdesc="#desc_fig6" src="img/inspectofpagetab.png" title="MSAA Inspect Tool diagnostics for Notebook page tab" width="490"/>
3386
+
<figureid="fig6"><imgalt="MSAA Inspect Tool diagnostics for Notebook page tab" height="647" longdesc="#desc_fig6" src="img/inspectofpagetab.png" title="MSAA Inspect Tool diagnostics for Notebook page tab" width="490">
3387
3387
<figcaption>Microsoft Inspect Tool rendering of the page tab
3388
3388
DataGrid</figcaption>
3389
3389
</figure>
@@ -3502,7 +3502,7 @@ <h3>Building Accessible Applications with <abbr title="Accessible Rich Internet
3502
3502
</ol>
3503
3503
<sectionid="exampletree">
3504
3504
<h3>Example: Building a Tree Widget</h3>
3505
-
<imgalt="Graphic of an example tree view." class="role-screenshot" src="img/exampletree.png" width="188" height="327"/>
3505
+
<imgalt="Graphic of an example tree view." class="role-screenshot" src="img/exampletree.png" width="188" height="327">
3506
3506
<p>A basic tree view allows the user to select different list items and expand and collapse embedded lists. Arrow keys are used to navigate through a tree, including left/right to collapse/expand sub trees. Clicking the visible expander button with the mouse also toggles expansion. Further keyboard implementation details for tree widgets may found in the <ahref="#aria_ex"></a>.</p>
3507
3507
<p>To make this feature accessible we need to:</p>
<p>WAI-ARIA and WCAG 2.0 coding techniques are useful for developing content and applications that can scale across a variety of user agents, including those on mobile devices. </p>
3640
3640
<p>For all these reasons, adopting WAI-ARIA makes good technical as well as business sense. For a further illustration, compare how accessibility is achieved with WCAG techniques without and with WAI-ARIA, as shown in <ahref="#fig7"></a>. </p>
<pclass="ednote">Editor's Note: Figure 7, described as WAI-ARIA tree widget usability comparison, refers to a resource that has not yet been found.</p>
3644
3644
<figcaption>Usability of Tree Widget Using WAI-ARIA Semantics to Implement WCAG 2.0 Guidelines Compared to WCAG 1.0 Without WAI-ARIA</figcaption>
Choose the role that best matches both the visual design and semantics of the user interface.
2634
2634
For instance, there are some circumstances where the semantics of <q>on or off</q> would be easier for assistive technology users to understand than the semantics of <q>checked or unchecked</q>, and vice versa.
2635
2635
Consider a widget for turning lights on or off.
2636
-
In this case, screen reader output of <q>Lights switch on</q> is more user friendly than <q>Lights checkbox checked</q>.
2636
+
In this case, screen reader output of <q>Lights switch on</q> is more user friendly than <q>Lights checkbox checked</q>.
2637
2637
However, if the same input were in a group of inputs labeled <q>Which of the following must be included in your pre-takeoff procedures?</q>, <q>Lights checkbox checked</q> would make more sense.
0 commit comments